All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goffredo Baroncelli <kreijack@libero.it>
To: Chris Mason <clm@fb.com>, Lennart Poettering <lennart@poettering.net>
Cc: systemd-devel@lists.freedesktop.org,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [systemd-devel] [HEADS-UP] Discoverable Partitions Spec
Date: Mon, 10 Mar 2014 23:44:37 +0100	[thread overview]
Message-ID: <531E4055.7010207@libero.it> (raw)
In-Reply-To: <531E1EBA.1090404@fb.com>

On 03/10/2014 09:21 PM, Chris Mason wrote:
> On 03/10/2014 04:02 PM, Lennart Poettering wrote:
>> On Mon, 10.03.14 19:34, Goffredo Baroncelli (kreijack@libero.it) wrote:
[...]
>> I am pretty sure automatic discovery of mount points should not cover
>> the usecase where people install multiple distributions into the same
>> btrfs volume. THe automatic logic should cover the simple cases only,
>> and it sounds way over the top to support installing multiple OSes into
>> the same btrfs... I mean, people can do that, if they want to, they just
>> have to write a proper fstab, which I think is not too much too ask...
> 
> Thinking more about this, using the UUIDs does make it harder for the
> admin to roll back and forth between snapshots. This is similar to
> the multiple install idea, but the goal would be easily jumping back
> to the old one if an update failed.
> 
> I'm not against anything that makes us more flexible here, just
> trying to nail down the use case a little bit more.>

We can store the mount point in a xattr. Also we can store the snapshots relation (parent/child or real/rollback) in a xattr. During the boot a "systemd-btrfs-fstab-generator" could generate on the fly the right mounts list.



 
> -chris
> 
> -- 
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it>
Key fingerprint BBF5 1610 0B64 DAC6 5F7D  17B2 0EDA 9B37 8B82 E0B5

  parent reply	other threads:[~2014-03-10 22:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140307182603.GA22874@tango.0pointer.de>
2014-03-10 18:34 ` [systemd-devel] [HEADS-UP] Discoverable Partitions Spec Goffredo Baroncelli
2014-03-10 18:53   ` Kay Sievers
2014-03-10 18:59     ` Goffredo Baroncelli
2014-03-10 19:43   ` Chris Murphy
2014-03-10 20:02   ` Lennart Poettering
2014-03-10 20:21     ` Chris Mason
2014-03-10 20:53       ` Chris Murphy
2014-03-10 21:09         ` Lennart Poettering
2014-03-10 22:44       ` Goffredo Baroncelli [this message]
2014-03-10 22:39     ` Goffredo Baroncelli
2014-03-10 23:45       ` Lennart Poettering
2014-03-10 23:59         ` Alex Elsayed
2014-03-11 14:30         ` [systemd-devel] " Calvin Walton
2014-03-12 17:24         ` Chris Mason
2014-03-12 19:12           ` Goffredo Baroncelli
2014-03-12 19:31             ` Chris Murphy
2014-03-12 19:55               ` Goffredo Baroncelli
2014-03-12 23:22               ` Brendan Hide
2014-03-12 22:18             ` Goffredo Baroncelli

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=531E4055.7010207@libero.it \
    --to=kreijack@libero.it \
    --cc=clm@fb.com \
    --cc=kreijack@inwind.it \
    --cc=lennart@poettering.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=systemd-devel@lists.freedesktop.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.