From: Goetz Bock <bock+uml@blacknet.de>
To: "'user-mode-linux-devel@lists.sourceforge.net'"
<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Separate COW patch.
Date: Sat, 27 Sep 2003 01:14:41 +0200 [thread overview]
Message-ID: <20030926231441.GB15465@shell.blacknet.de> (raw)
In-Reply-To: <2D4B6CD74137D4119A1100104BC6BCBF0BC585FC@dubntex006.qwest.net>
On Fri, Sep 26 '03 at 18:45, Montgomery, Kendal L wrote:
> I was wondering if there was anyone who is trying to use the COW
> filesystem in a normal linux kernel? [ ... ]
The COW is not a filesystem, it is a block level thingy.
If you only have a small number of changes, the LVM / DM snapshot
feature might be usefill. OTOH it is designed to be merged afterwards,
not discarded.
--
/"\ Goetz Bock at blacknet dot de -- secure mobile Linux everNETting
\ / (c) 2003 as GNU FDL 1.1
X [ 1. Use descriptive subjects - 2. Edit a reply for brevity - ]
/ \ [ 3. Reply to the list - 4. Read the archive *before* you post ]
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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:[~2003-09-27 0:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-26 22:45 [uml-devel] Separate COW patch Montgomery, Kendal L
2003-09-26 23:14 ` Goetz Bock [this message]
2003-09-27 0:02 ` Jeff Dike
2003-09-27 22:56 ` Michael Richardson
2003-09-28 0:00 ` Paul Sladen
2003-09-28 1:44 ` Matt Zimmerman
-- strict thread matches above, loose matches on Subject: below --
2003-09-29 16:53 Montgomery, Kendal L
2003-10-06 21:23 ` Jeff Dike
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=20030926231441.GB15465@shell.blacknet.de \
--to=bock+uml@blacknet.de \
--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