From: C Anthony Risinger <anthony@extof.me>
To: Chris Mason <chris.mason@oracle.com>,
Sage Weil <sage@newdream.net>,
linux-btrfs@vger.kernel.org
Subject: Replacing the top-level root
Date: Mon, 25 Oct 2010 15:20:58 -0500 [thread overview]
Message-ID: <AANLkTiktaR6ipbH-i=kTdRvHqBdTAAcYYsdVamogifm1@mail.gmail.com> (raw)
On Mon, Oct 25, 2010 at 2:58 PM, Chris Mason <chris.mason@oracle.com> wrote:
>
> Oh, and it shouldn't work on the root of the FS either ;)
>
> -chris
This is not 100% related but...
Will removing [replacing] the top-level root be something that
can/will be supported? I've asked in the past about this regarding an
initramfs hook i maintain implementing system rollbacks, but I never
really got a solid answer.
For example, right now extlinux support booting btrfs, but _only_ from
the top-level root. if i just had a way to "swap" the top-level root
with a different subvol, i could overcome several problems i have with
users all at once:
) users install their system to the top-level root, which means it is
no longer manageable by snapshot scripts [currently]
) if the top-level root could be swapped, extlinux could then boot my
snapshot? (i'm probably wrong here)
"set-default" is not enough; i'm looking for a way to gain control
over the system state when the system has been installed into the
top-level root. currently, i have no way to manipulate/move/change
it, because the top-level is essentially "immutable", or so it seems.
thus it's not possible to support kernel rollbacks without manually
syncing <snapshot>/boot to /boot.
is there a solution to this that i'm missing?
C Anthony
next reply other threads:[~2010-10-25 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 20:20 C Anthony Risinger [this message]
2010-10-27 5:53 ` Replacing the top-level root David Brown
2010-10-27 16:52 ` C Anthony Risinger
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='AANLkTiktaR6ipbH-i=kTdRvHqBdTAAcYYsdVamogifm1@mail.gmail.com' \
--to=anthony@extof.me \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sage@newdream.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;
as well as URLs for NNTP newsgroup(s).