From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
user-mode-linux-user@lists.sourceforge.net
Subject: Re: [uml-devel] [PATCH] Mconsole exec support - rewritten completely
Date: Mon, 26 Jul 2004 14:16:28 -0400 [thread overview]
Message-ID: <200407261816.i6QIGSfL001860@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Thu, 22 Jul 2004 16:53:38 +0200." <200407221653.38293.blaisorblade_spam@yahoo.it>
blaisorblade_spam@yahoo.it said:
> Jeff, you can still think that this feature should not be in the
> kernel support (but why then bother with the "proc" command?),
Because "proc" is needed to diagnose sick UMLs, which may not be able to run
commands. It's also handy to make measurements which may be affected by logging
in.
> even
> if this time there is no more any parsing code; but anyway, it will
> stay available for who wants it.
You can maintain this yourself if you want, but it's going nowhere near my
tree. I've said why I don't like it, and haven't heard any real arguments
for it, just whining by people who think parsing login sequences and shell
prompts is hard.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
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-07-26 18:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 14:53 [uml-devel] [PATCH] Mconsole exec support - rewritten completely BlaisorBlade
2004-07-26 18:16 ` Jeff Dike [this message]
2004-07-27 3:13 ` Matt Zimmerman
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=200407261816.i6QIGSfL001860@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@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