Re: option to mount read-only subvolume with read-write access

[Eric Levy <contact@ericlevy.name>]

On Mon, Nov 14 2022 at 09:33:31 PM +0100, David Sterba 
<dsterba@suse.cz> wrote
>> This sounds like the transaction update that is in openSUSE,
> https://github.com/openSUSE/transactional-update . The difference is
> that you would like it to work on the same subvolume and that all the
> work is done on the filesystem level, not completely managed by
> userspace utilities.


My understanding of the TU framework is that the tools create a 
snapshot to be selected for the next boot session, and that while that 
snapshot is being prepared, its read-only property is disabled. Once 
some modification operation concludes, the read-only property is 
toggled back to true. A file-system feature would make it easier to 
alter the snapshot in some staging environment, without changing the 
snapshot properties, or the location of the snapshot in the full file 
system.

My current understanding of TU is based on some amount of 
extrapolation, however, which may be inaccurate.