From: Jeff Dike <jdike@karaya.com>
To: user-mode-linux-user@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: user-mode port 0.47-2.4.10
Date: Tue, 25 Sep 2001 23:51:09 -0500 [thread overview]
Message-ID: <200109260451.XAA04821@ccure.karaya.com> (raw)
The user-mode port of 2.4.10 is available.
The highlights:
UML can now communicate with the host networking via TUN/TAP.
libc's allocation routines (malloc, calloc, free) are intercepted and
converted into kmalloc whenever possible. This fixes problems with gprof
and gcov, and closes a potential security hole.
UML loads itself into the top of the address space (0xa0000000-0xc0000000 on
1G/3G hosts), giving its processes everything below that. This fixes a bug
which caused nasty-looking complaints when UML was given 256M of physical
memory or more. I've run it with up to 464M. This also fixes the hang
caused by mlockall.
The mconsole client has been enhanced, so it now had command history and
command recall, it can control multiple UMLs, and can attached to a UML by
its name rather than the full filename of its control socket.
uml_net does complete setup of TUN/TAP interfaces. It also insmods netlink_dev
for the benefit of ethertap.
The ubd COW header now has room for MAXPATHLEN-sized filenames, it contains
absolute paths only, and is in network byte order. The ubd driver handles
IO errors better now, and should be 64-bit clean.
The process segfaults seen on a swapping system are gone.
The project's home page is http://user-mode-linux.sourceforge.net
Downloads are available at
http://user-mode-linux.sourceforge.net/dl-sf.html
Jeff
reply other threads:[~2001-09-26 3:33 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=200109260451.XAA04821@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