On 2020-01-26 7:11 p.m., Carlos E. R. wrote:
Now, put /boot on different partition, and the feature can not work.
It depends on the 'whatever' that got updated. What gets updated when you get a kernel update is not the same as an update for anything else. I'm not running BtrFS but when I get a new kernel, an update via kernel_Stable, the earlier version stays around and the update to the grub config just alters the menu so that the new one becomes the default. I can still boot from the old one EVEN THOUGH I"M NOT USING BTRFS. # ls /boot/vmlinuz* /boot/vmlinuz /boot/vmlinuz-5.4.13-1.g5cf5394-default /boot/vmlinuz-5.4.11-1.g2d02eb4-default /boot/vmlinuz-5.4.14-1.gfc4ea7a-default /boot/vmlinuz-5.4.12-2.gcea1843-default Just as with BtrFS snapshots you can 'purge' old ones btrfs subvolume delete ..... The old kernels stay around until I 'purge-kernel'. How many kernels I keep at a purge is set in '/etc/zypp/zypp.conf' by the parameter 'multiversion.kernels' Because of this, you don't want the snapshot feature of BtrFS to snapshot the kernel updates & history (and that includes the corresponding kernel kernel modules). Yes, you could list them in the BtrFS configuration file as excluded directories. Yes, you could put up with the waste and pointlessness of the duplication. But please, the revision history mechanisms for the kernel exist quite independently from BtrFS. I don't use BtrFS but I do have the ability to boot from previous kernels for testing or if there is a problem with an update (as sometimes happens). -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org