Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
What I'm wondering now is about what I'm expected to do in case of system failure. For what I read there are two possibilities: - If snapshots are writable, I can boot in any snapshot and start using it normally, right?. It would be like forking from a previous snapshot, but I read that writable snapshots are dangerous because I could break things again and because snapshots should be inmutable, so readonly snapshots are recommended. Also I found that if done wrong snapshots may not work after restoring (https://www.reddit.com/r/btrfs/comments/aj0o83/why_do_you_need_to_add_snapshots_mountpoint_to/), that's way I feel so afraid to miss a step, haha - So if snapshots are readonly and I boot in them like a live-cd (https://github.com/Antynea/grub-btrfs/blob/master/initramfs/readme.md), how do I "fork" from a readonly snapshot in a persistent way so I can just continue to use the system normally from that "fork" and still preserve the readonly snapshot in case I need to rollback to it again?
Take a look at snap-pac-grub for grub menu snapshot integration. It's in the AUR.
I've also written (at length) about why the flat layout is better and less confusing on (this GH issue tracker)[https://github.com/archlinux/archinstall/issues/781], and I recommend that you read it and draw your own conclusions.