Poettering: Revisiting how we put together Linux systems
Poettering: Revisiting how we put together Linux systems
Posted Sep 2, 2014 7:53 UTC (Tue) by suckfish (guest, #69919)Parent article: Poettering: Revisiting how we put together Linux systems
I rely heavily on maintaining various parts of my systems in subvols that are regularly cloned & manipulated in various ways (chroots/containerisation, backups, major upgrades). I believe I am far from unique here.
This relies on me being able to decide what constitutes a subvolume. As soon as a different idea gets imposed on my system (e.g., fragmenting my OS install into multiple subvols) my ability to use subvols to manage my system will be impeded (e.g., I could no longer create a standalone environment just by "btrfs subvol clone"ing my OS).
OTOH a stow (remember that?) like system of isolating packages into their own directories sounds great to me, not least because I can choose to put a package into it's own subvol if I wish.
Posted Sep 2, 2014 18:49 UTC (Tue)
by mezcalero (subscriber, #45103)
[Link] (1 responses)
Posted Sep 3, 2014 6:37 UTC (Wed)
by suckfish (guest, #69919)
[Link]
If upstream packaging imposes a decision on how the filesystem is split into subvolumes, then the sysadmin no longer gets to choose.
This makes it much harder for the sysadmin to subvolumes to maintain their system.
The bottom line is sysadmins want to choose what 'btrfs subvol clone ...' clones, not have that choice imposed by upstream.
Poettering: Revisiting how we put together Linux systems
Poettering: Revisiting how we put together Linux systems