Linux

Shrug. To me this is like arguing over how to fold your underwear.

Well technically, if you're using BTRFS, you might want to check out subvolumes. Here's my subvolume setup:

• Subvolume 1, named @ (root subvol)
• Subvolume 2, named @home (/home subvol)
• Subvolume 3, named @srv (/srv subvol)
• Subvolume 4, named @opt (/opt subvol)
• Subvolume 5, named @swap (which is - you guessed it - the swap subvol)

You then set up fstab to reflect each of the subvolumes, using the subvol= option. Here's the kicker: they are all in one partition. Yes, even the swap. Though caveat, swap still has to be a swapfile, but in its own separate subvolume. Don't ask me why, it's just the way to do it.

The great thing about subvolumes is that it doesn't do any size provisioning, unless specified by the user. All subvolumes share the space available within the partition. This means you won't have to do any soul searching when setting up the partitions regarding use of space.

This also means that if I want to nuke and pave, I only need run a BTRFS command on my @ subvolume (which contains /usr, /share, /bin), because it won't be touching the contents of @home, @srv, or @opt. What's extra cool here is that I'll lose 0% FS metadata or permission setup, since you're technically just disassociating some blocks from a subvolume. You're not really "formatting"... which is neat as hell.

The only extra partitions I have is the EFI partition and an EXT4 partition for the /boot folder since I use LUKS2.

It's fine for most uses.

For server or enterprise cases you want to separate /usr, /var and /tmp to prevent a rogue process from filling the / volume and crashing the machine.

I don't like wasting space or having to predict how much space I'll be using two years from now, so I prefer the minimum of partitions: efi, boot, and system(luks), with a btrfs subvol for /, home, and swapfile.

What you're doing is perfectly fine.

It is however more of a mitigation for bad distro installers than general good practice. If the distro installers preserved /home, you could keep it all in one partition. Because such "bad" distro installers still exist, it is good practice if you know that you might install such a distro.

If you were installing "manually" and had full control over this, I'd advocate for a single partition because it simplifies storage. Especially with the likes of btrfs you can have multiple storage locations inside one partition with decent separation between them.

All fine though I would recommend you look into lvm, gives you easier control over sizing and resizing, even online.

what you're doing is perfectly fine. if it's what your comfortable with, there's no 'need' to change.

If you reinstall often a separate /home makes some sense. Otherwise it's probably pointless. I'd try to get to a point where I don't have to reinstall my base OS and invest in an automatic backup solution.

That's the standard way. It's how (most) distros partition by default.

I set it up this way so that if I need to reinstall Linux, I can just overwrite / while preserving /home and just keep working after a new install with very few hiccups.

Even with a single partition for / and /home you can keep the contents of /home during a reinstall by simple not formatting the partitions again. I know when I tried years ago with Ubuntu years ago the installed asked if I wanted to remove the system folders for you. But even if the installer does not you can delete them manually before hand. Installers wont touch /home contents if you don't format the drive (or any files outside the system folders they care about).

Though I would still backup everything inside /home before any attempt at a reinstall as mistakes do happen no matter what process you decide to go with.

Why do you have a btrfs volume and an ext4 volume? I went btrfs and used sub volumes to split up my root and home but I’m not sure if that’s the best way to do it or not

Why would you put home on ext4 instead of btrfs?

You're using it well. Nothing wrong at all.

Butterface excels at keeping data safe-ish or at least lets you know when to throw in the towel, and which bits you've lost. It's also write intensive if you open a file with write permissions, which is harder on your drives.

Btrfs is great for the data you want to keep long term.

Also UEFI has some nice advantages if your computer isn't a dino that can't handle it.

Do what works for you, and keep on keeping on.

I just use /

I don't think having a swap partition or file would be all that useful because I have plenty of memory. I've never had to reinstall Linux so I'm not sure why I would need a separate home. If I did bork my OS somehow I'm fairly confident I could repair it from a live distro. And even if I did end up having to save my home I could just copy the files I want to another drive if it really came to that.

It's a good way to do it for your use case.

It's not outdated, just less necessary now. With SSD's, you can just copy your /home back from your daily backup after reinstallation, which takes all of 5 minutes.

When I started with Linux, I was happy to learn that I didn't need a bunch of separate partitions, and have installed all-in-one (except for boot of course!) since. Whatever works fine for you (-and- is easiest) is the right way! (What you're doing was once common practice, and serves just as well. No disadvantage in staying with the familiar.)

After I got up to 8GB memory, stopped using swap ... easier on the hard drive -and- the SSD. (I move most data to the HD ... including TimeShift ... except what I use regularly.)

I use Mint as well; for me this keeps things as simple as possible. When I install a new OS version (always with the same XFCE DE) I do put THAT on a new partition (rather than try the upgrade route and risk damaging my daily driver) using the same UserName. A new Home is created within the install partition (does nothing but hold the User folder.)

To keep from having to reconfig -almost everthing- in the new OS all over again I evolved a system. First I verify that the new install boots properly, I then use a Live USB to copy the old User .config file (and the apps and their support folders I keep in user) to the new User folder. Saves hours of reconfiguring most things. The new up-to-date OS mostly resembles and works like the old one ... without the upgrade risks.

This is the way

They are probably using timeshift or some advanced feature in btrfs to auto-generate snapshots so they can go back to a working state using one of them.

The way you do it is probably getting old. I say this because I do the same, but to use several distros with a shared home partition, provided I have the same GID and UID for the users. This is not recommended but only once I've had a problem and it was easy to solve, so I kept doing it. Installed Fedora recently with defaults in one partition and they use one fat partition (EFI), and one btrfs partition with a logical volume and some unfamiliar partitioning. I think we are maybe missing some new technologies.

I think that's a pretty common partition layout