From: David Coulson <david@davidcoulson.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Stability of /dev/anon patch
Date: Sat, 13 Mar 2004 22:54:44 -0500 [thread overview]
Message-ID: <4053D784.7020803@davidcoulson.net> (raw)
I'm finally caught up with the current UML patches, but I wanted to see
if it was worth rebuilding my host with the devanon stuff - From what I
understand, as long as I don't enable mmaped I/O, it should not cause
corruption?
Does anyone us this patch in production and what has the end result been?
David
--
David Coulson email: d@vidcoulson.com
Linux Developer / web: http://davidcoulson.net/
Network Engineer phone: (216) 533-6967
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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
reply other threads:[~2004-03-14 3:54 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=4053D784.7020803@davidcoulson.net \
--to=david@davidcoulson.net \
--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