linux-um archives
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Alasdair G Kergon <agk@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	user-mode-linux-devel@lists.sourceforge.net,
	user-mode-linux-user@lists.sourceforge.net
Subject: [uml-devel] Writing on DM snapshots, and having no "mainstream" device (was: Re: Fw: [PATCH 1/7] Add dm-snapshot tutorial in Documentation)
Date: Fri, 23 Sep 2005 22:11:31 +0200	[thread overview]
Message-ID: <200509232211.32238.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050921154846.GW18976@agk.surrey.redhat.com>

On Wednesday 21 September 2005 17:48, Alasdair G Kergon wrote:
> On Tue, Sep 20, 2005 at 04:34:33PM -0700, Andrew Morton wrote:
> > ack?
>
> Applied some quick corrections to this.
I'm now looking at this, but you've done an error. You say that 

You must create the snapshot-origin device before you can create snapshots.

This is totally wrong. The whole point of my document is to show that you can 
create snapshots *WITHOUT* having a snapshot-origin device (yes, I did it).

And while the LVM setup (with snapshot-origin) is often used and well known, 
the possibility to do without the snapshot-origin, and more important to 
write on the snapshots, is something which is not widely known at all.

In fact, UML community has been using an in-house version of the same feature, 
which cannot be mounted on the host due to missing code.
> See also http://people.redhat.com/agk/talks/FOSDEM_2005/
> (slides 15-27)
Not yet had time to look at those, sorry.
> You might like to convert some of those diagrams to ASCII
> and include them?
If you feel like doing this, ok, but I'm not normally a documentor.
> Alasdair

-- 
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it



-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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:[~2005-09-23 20:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050920163433.6081be3b.akpm@osdl.org>
     [not found] ` <20050921154846.GW18976@agk.surrey.redhat.com>
2005-09-23 20:11   ` Blaisorblade [this message]
2005-09-23 21:19     ` [uml-devel] Re: Writing on DM snapshots, and having no "mainstream" device (was: Re: Fw: [PATCH 1/7] Add dm-snapshot tutorial in Documentation) Alasdair G Kergon
2005-09-26 15:03       ` Blaisorblade
2005-09-27 18:34         ` Alasdair G Kergon

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=200509232211.32238.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=agk@redhat.com \
    --cc=linux-kernel@vger.kernel.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