linux-um archives
 help / color / mirror / Atom feed
From: greg <greg@lonnon.org>
To: roland <for_spam@gmx.de>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] mounting COW on HOST?
Date: Mon, 08 Dec 2003 19:10:08 -0700	[thread overview]
Message-ID: <1070935808.4256.25.camel@profx.lonnon.org> (raw)
In-Reply-To: <009701c3bded$d0efef70$2000000a@schlepptopp>

Roland,

It wouldn't be that tough to write a COW block device for the standard
kernel.  In fact, if we did that, we could get rid of the COW hack in
the ubd device.  

The basic idea of COW is a bitmap to represent all the sectors of the
block device, a backing block device and a cow block device.  Any
blocking device should work.  

I have also thought of changing the index to be a 4 byte offset, this
would useful for live CD distros with a floppy device.  The floppy
device becomes the COW disk while the backing file is the CDROM.  I
haven't done the math on the usability of 1.4MB floppy or the recovery
mechanism in case of a kernel panic, etc...  But having a live CD in
which any sector could be changed might be interesting, at least make it
easier for the live CD people.

See ya,
Greg

On Mon, 2003-12-08 at 17:45, roland wrote:
> hi!
> one thing came to my mind today: why not porting the COW feature of UML to 
> the "mainstream" linuxkernel itself?
> i would find this useful - not only in relation to UML.
> maybe there is already something like this? don`t know....
> what would we need? modifying loopdevice(mount -o loop...) code? perhaps using 
> lufs for that? (btw: long awaited read/write support for ntfs partitions has 
> been implemented via lufs and native windows ntfs.sys driver!) 
> maybe this has been discussed already?
> 
> regards
> roland
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
> Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&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
-- 



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&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:[~2003-12-09  2:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09  0:45 [uml-devel] mounting COW on HOST? roland
2003-12-09  2:10 ` greg [this message]
2003-12-09  3:58   ` Russell Coker
2003-12-09  2:18 ` Matt Zimmerman

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=1070935808.4256.25.camel@profx.lonnon.org \
    --to=greg@lonnon.org \
    --cc=for_spam@gmx.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