From: Jeff Dike <jdike@karaya.com>
To: linux-kernel@vger.kernel.org, user-mode-linux-user@lists.sourceforge.net
Subject: UML 2.5.31
Date: Tue, 13 Aug 2002 12:27:50 -0500 [thread overview]
Message-ID: <200208131727.MAA02464@ccure.karaya.com> (raw)
UML has been updated to 2.5.31 and UML 2.4.18-52.
The changes since 2.5.30 have been mostly bug fixes and cleanups.
I fixed a "I'm tracing myself and can't get out" race.
The kernel entry and exit code was cleaned up and reduced from three copies
to one.
telnetd is now killed when UML shuts down, so telnet connections to UML
consoles die properly.
Fixed a crash caused by a non-GFP_ATOMIC allocation in an interrupt.
UML now exits when 'debug' is asked for and CONFIG_PT_PROXY is disabled.
Fixed some bugs in the ubd device plugging code.
Fixed ethertap by making CLOEXEC optional in os_pipe.
Made UML build on 2.2 by defining the SHUT_* macros if no header file does.
The patch is available at
http://uml-pub.ists.dartmouth.edu/uml/uml-patch-2.5.31-1.bz2
For the other UML mirrors and other downloads, see
http://user-mode-linux.sourceforge.net/dl-sf.html
Other links of interest:
The UML project home page : http://user-mode-linux.sourceforge.net
The UML Community site : http://usermodelinux.org
Jeff
reply other threads:[~2002-08-13 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200208131727.MAA02464@ccure.karaya.com \
--to=jdike@karaya.com \
--cc=linux-kernel@vger.kernel.org \
--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