From: Jeff Dike <jdike@addtoit.com>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: uml devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: [uml-devel] Re: [ann] kraxel's 2.6.8 uml patch kit
Date: Fri, 20 Aug 2004 15:01:40 -0400 [thread overview]
Message-ID: <200408201901.i7KJ1eIF003843@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Fri, 20 Aug 2004 14:24:45 +0200." <20040820122445.GA21790@bytesex>
kraxel@bytesex.org said:
> uml-core-on-panic
> Make the uml kernel dump core on kernel panics for later analysis.
> Default: off, there is a kernel cmd line arg to enable that.
I like this, but I think it would be better done in a panic_notifier.
> uml-fix-mconsole-proc
> fix kernel crash triggered by running "uml_mconsole <umid> proc
> <some-file>"
> multipole times.
I didn't do it this way on purpose. I create an internal procfs mount in
case the UML root user has mounted something else on /proc. I don't want
the mconsole on the host to be faked out by that.
> uml-net-flush-on-ifup
> flush incoming packets on ifup -- fixes networks stalls which happen
> in
> case the unix socket buffer is already full when the interface is
> up'ed
> (due to SIGIO never signaling arrived data).
Applied, BTW, this one is mangled on your site:
@@ -129,6 +129,7 @@ static int uml_net_open(struct net_devic
It's in my 2.4 tree and will get moved over to 2.6 in due course.
> uml-terminal-cleanup
> tty / console handling cleanups. The patchfile itself has a long
> description.
I like this one, but it's big and I'm going to have to take a good look at it.
I'm somewhat unhappy about the command line change, where you need to specify
a console or UML doesn't boot. That'll break everyone's scripts. Is it
possible to provide a default console if there isn't one on the command line?
> What is the status of the amd64 port? The 2.6.4 patch on sf.net
> produces lots of rejects when I try to apply it on top of the 2.6.7
> uml patch. Is a newer version available somewhere? Or can I just
> ignore all the rejects (guess not)?
It's stuck on 2.6.4 for now. I'm going to get it caught up, but haven't
decided when yet.
Jeff
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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-08-20 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 12:24 [uml-devel] [ann] kraxel's 2.6.8 uml patch kit Gerd Knorr
2004-08-20 13:14 ` Geert Uytterhoeven
2004-08-20 16:52 ` Gerd Knorr
2004-08-20 19:01 ` Jeff Dike [this message]
2004-08-20 21:05 ` [uml-devel] " Geert Uytterhoeven
2004-08-21 19:28 ` Gerd Knorr
2004-08-22 13:22 ` Werner Almesberger
2004-08-23 11:06 ` Gerd Knorr
2004-08-22 11:17 ` Gerd Knorr
2004-08-31 0:25 ` D. Bahi
2004-09-14 12:36 ` Gerd Knorr
2004-09-15 20:59 ` D. Bahi
2004-09-16 10:29 ` [uml-devel] [patch] core-on-panic next take ;) Gerd Knorr
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=200408201901.i7KJ1eIF003843@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=kraxel@bytesex.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.