From: Matt Zimmerman <mdz@debian.org>
To: user-mode-linux-user@lists.sourceforge.net,
user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Dynamic remount with variable COW stacking/merging needed, support for snapshot repilication
Date: Sun, 18 Jan 2004 19:59:24 -0800 [thread overview]
Message-ID: <20040119035924.GE16181@alcor.net> (raw)
In-Reply-To: <200401181517.52700.blaisorblade_spam@yahoo.it>
On Sun, Jan 18, 2004 at 05:13:57PM +0100, BlaisorBlade wrote:
> Alle 09:20, domenica 18 gennaio 2004, James W McMechan ha scritto:
> > Oh yes as a side note 2.6.0 and 2.4.25pre
> > have the fix for Oops on the host kernel
> > when reading /dev/shm with hostfs so if
> > that was bothering you the 2.6 or next
> > 2.4 kernel should help.
>
> Yes, I saw it. Thanks!
Ooh, good. I stopped using hostfs-on-tmpfs for a number of things due to
this bug, having sent the oops to linux-kernel and having received no
response. I'm glad it's fixed.
--
- mdz
-------------------------------------------------------
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 prev parent reply other threads:[~2004-01-19 3:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 8:20 [uml-devel] Dynamic remount with variable COW stacking/merging needed, support for snapshot repilication James W McMechan
2004-01-18 16:13 ` BlaisorBlade
2004-01-19 3:59 ` Matt Zimmerman [this message]
2004-01-19 4:10 ` [uml-user] " Jeff Dike
2004-01-19 18:26 ` Adam Heath
2004-01-19 19:40 ` Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2004-01-17 21:13 Stephen D. Williams
2004-01-18 11:04 ` BlaisorBlade
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=20040119035924.GE16181@alcor.net \
--to=mdz@debian.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--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