On Mon, Jul 20, 2015 at 10:33 PM, Michael Chang
On Mon, Jul 20, 2015 at 01:26:56PM -0600, Chris Murphy wrote:
On Mon, Jul 20, 2015 at 12:20 PM, Chris Murphy
wrote: It's so esoteric and hidden I can't imagine on what basis someone could describe it as being obvious and found in plain sight.
That basically means you have to update those self contained grub.cfg whenever it's in new created snapshots and also reinstalling bootloader for pointing prefix to new rollback subvolume. We want to avoid that as the requirement is snapshot and rollback operations to be atomic and as plain file system operations.
OSTree manages to do atomic updates and rollbacks on ext4 and XFS, without any of the negatives you list. There is no need to recreate or modify grub.cfg from scratch, it becomes a static configuration file, augmented by a drop-in snippet per boot entry. These are human readable, and easier to understand than grub.cfg. Updates and rollbacks are completely atomic operations, even on non-COW file systems. And ostree/rpm-ostree aren't the only way to do this correctly. However that project proves it's possible to: - use BLS snippets to augment grub.cfg, obviating the need to replace or modify grub.cfg; - avoid reinstalling the bootloader; - maintain subvol set-default as the user feature it was intended to be; - provide clarity of what fs tree will be booted, is booted, and has been booted; - present an explicit way forward for better dual boot cooperation among the distros. None of those things are true with the current implementation. None are addressed by your response. I think these things should be requirements too, not just atomicity of updates and rollbacks. -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org