From: Jeff Dike <jdike@addtoit.com>
To: Dan Shearer <dan@shearer.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Draft docs for port console channel
Date: Sat, 24 Jan 2004 13:20:21 -0500 [thread overview]
Message-ID: <200401241820.i0OIKLY3002404@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Sat, 24 Jan 2004 18:50:57 +1030." <20040124082057.GG4203@erizo.shearer.org>
dan@shearer.org said:
> Another fumbling newbie question: why can't we just have the fd for
> the unix socket for xterm connected before xterm is exec'd? Then there
> would be no need for open_socket in port-helper. I'm sure there's an
> obvious reason.
I think that's just paranoia. IIRC, I was more confident about command-line
switches getting through xterm than open file descriptors. I think I needed
to pass an open file descriptor through telnetd because there is no way to
influence the command line of the -L login program.
Thanks for the patch.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-01-25 17:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 3:56 [uml-devel] Draft docs for port console channel Dan Shearer
2004-01-23 14:43 ` Jeff Dike
2004-01-24 8:20 ` Dan Shearer
2004-01-24 18:20 ` Jeff Dike [this message]
2004-01-25 23:38 ` Dan Shearer
2004-01-26 18:14 ` Jeff Dike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401241820.i0OIKLY3002404@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=dan@shearer.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox