From: Jeff Dike <jdike@addtoit.com>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: tim doyle <tim@unclewebster.com>,
UML <user-mode-linux-user@lists.sourceforge.net>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [uml-user] one drawback to using cows commercially...
Date: Tue, 13 Apr 2004 00:58:20 -0400 [thread overview]
Message-ID: <200404130458.i3D4wKsf024793@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Sun, 11 Apr 2004 16:51:20 +0200." <200404111651.20256.blaisorblade_spam@yahoo.it>
blaisorblade_spam@yahoo.it said:
> Have you heard of the discussion about COWlinks? I.e. creating a Copy
> - On - Write functionality for hard links? Or do you want to rewrite
> files one page at a time (i.e. if I change one byte inside a file,
> only the "page" containing that byte is copied and changed)?
COWlinks sound like they would be useful for doing file-level COWing for
UML.
I'm considering that, plus block-level COWing within a file, using the standard
COW format we have today. This would be necessary if we do block devices
by loop-mounting a rootfs from humfs and using that as the root device.
Jeff
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-04-13 4:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40686E7D.2080600@unclewebster.com>
[not found] ` <200403300217.i2U2HKxc026892@ccure.user-mode-linux.org>
2004-04-01 17:53 ` [uml-devel] Hostfs and Humfs BlaisorBlade
2004-04-01 19:54 ` [uml-devel] Re: [uml-user] " Jeff Dike
[not found] ` <200404051840.i35IeHhZ029055@ccure.user-mode-linux.org>
2004-04-09 17:54 ` [uml-devel] " BlaisorBlade
2004-04-11 14:51 ` [uml-devel] Re: [uml-user] one drawback to using cows commercially BlaisorBlade
2004-04-13 4:58 ` Jeff Dike [this message]
2004-05-26 23:57 ` update on cowlinks - was: " roland
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=200404130458.i3D4wKsf024793@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=tim@unclewebster.com \
--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