[Vmdebootstrap-devel] Bug#741223: Simplifying the patch

[Sunil Mohan Adapa]

On Monday 11 January 2016 07:50 PM, Petter Reinholdtsen wrote:
> 
> I do no longer remember the details, but the goal when I went with this
> approach to picking the btrfs root was to be able to snapshot the
> current system (assuing / contain /etc/, /var/, /usr/ and everything
> else needed to run the system), upgrade it, boot into the new system and
> conclude that the upgraded system is broken, boot it again and change
> the boot parameter to get back to the old system by changing subvol=@ to
> subvol=<oldsnapshot>.
> 
> Will this use case still work with your new approach, is is the only way
> to change the root to have a working system to boot into to change the
> default subvolume?
> 

With the proposed approach, we will have both the ways to mount and use,
that is, revert to an older snapshot.

1) Use 'btrfs set-default' to set the default subvolume and reboot.

2) Change the arguments to mount in fstab and kernel boot parmeters like
before using 'subvol=' and 'subvolid='.

Both methods will have the same result of mounting the desired
subvolume.  The latter appoarch is harder for automated tools to handle.
 Snapper (possibly most other tools) use the first method.

-- 
Sunil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/vmdebootstrap-devel/attachments/20160111/bac5d594/attachment.sig>