this post was submitted on 04 May 2024
122 points (96.9% liked)
Linux
48310 readers
645 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
BTRFS for the OS partitions, ext4 for /home, tmpfs for /tmp. I rarely need to use snapshots, but I do use a rolling release. It's one of those things you don't need until you really fucking NEED it. Tumbleweed support is great - I can roll back a bad update in about as long as it takes to reboot.
This is exactly how and what Im using.
Home and other ext4 are backed up one form or another on by NAS.
Seeing that user Flatpaks are installed in the home folder, I see this as an interesting strategy. EXT4 still beats BTRFS in certain read/write benchmarks. My only problem being that you lose provisioning.
I don't see a lot of people talking about this here, but BTRFS subvolume provisioning is probably the best reason to use BTRFS - and BCacheFS - not just CoW or snapshotting.
The old way, of having a set beginning and end of a partition, is like caveman technology to me now. Subvolumes are here to stay and I am happy about that.
If I need to do a little distrohop now, even though I wouldn't (rpm-ostree rebase go brrrr), all I'd do is delete an recreate the "@" subvolume (or the root subvolume) without touching another partition or subvolume. All storage space is shared between subvolumes, basically, removing that boundary distinction between them, so I get to keep the files, permissions and meta data in my "@home" and my "@var" subvolumes, even though I get rid of the old "@" to replace it with a new one.
Therefore the idea of having storage that is reliant upon partitioning, ordering sectors one after another, having to defragment and keep strict separations between them is absolutely archaic to me. I'll gladly take a slight performance hit just for the convenience of avoiding all that.