From: Jeff Dike <jdike@addtoit.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] uml-patch-2.4.23-2
Date: Sat, 17 Jan 2004 10:47:25 -0500 [thread overview]
Message-ID: <200401171547.i0HFlPtk009266@uml.user-mode-linux.org> (raw)
This patch fixes a number of bugs including
with ubd-mmap in force, device data remaining mapped after the device
was closed - this should fix the EBADF errors some people were seeing on UML
shutdown, it allows 2.6 to boot with ubd-mmap, and there's some potential that
it fixed file corruption. Anyone who has been seeing ubd-mmap problems should
test this and let me know one way or the other.
/dev/anon is now correctly checked for and used if it's available
fixed the linker script to get rid of the segfaults seen with RH and
Fedora
mhz is now a long long, so UML again will stop hanging on fast hosts
lots of small changes to fix minor bugs, compilation problems, and
to reduce the number of diffs between the 2.4 and 2.6 trees
CVS hasn't been updated yet because SF is broken again. I'll check everything
in when the CVS server is back up.
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 reply other threads:[~2004-01-19 17:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 15:47 Jeff Dike [this message]
2004-01-20 9:20 ` [uml-devel] uml-patch-2.4.23-2 Nick Craig-Wood
2004-01-20 15:00 ` Jeff Dike
2004-01-20 17:35 ` Nick Craig-Wood
2004-01-20 20:40 ` Jeff Dike
2004-01-21 7:41 ` Nick Craig-Wood
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=200401171547.i0HFlPtk009266@uml.user-mode-linux.org \
--to=jdike@addtoit.com \
--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