I've been using Linux for over a quarter of a century. Initially I spent hours attempting to come up with the best partitioning scheme but these days I pick LVM and use the defaults.

If I run out of space, I add a drive (or grow the virtual one) and grow the filesystem into the extra space.

Sometimes I need temporary space and use sshfs to mount a directory from another machine.

In other words, today you have infinite options to adjust according to need, partition schemes are not nearly as important.

Even swap space can live as a file on a normal partition if required.

That said. If you have specific use cases, check what's required. Specifically because different uses need different attributes, it pays to check.

with the majority here, I just use distro default / automatic setup in installer

LONG ago, I did the whole hand-crafted thing, obsessing over exactly how large each partition had to be, but with increasing speed and lowering prices of storage, this attention to detail now seems pretty irrelevant:
- hda split into /boot, /tmp, (swap), /, /opt, /usr, /var
- hdb split into (swap) and /home

• 180 MB /efi (if needed)
• 384 MB /boot (for LUKS compatibility)
• Remainder / (usually btrfs)

• 550MiB /boot (also used as esp)
• Rest for / (btrfs)
• Subvols for /home, /var/log, /var/cache, /.snapshots (snapper snaps), /swap

I've tried some weird and wonderful partition schemes in the past, but I think I've settled down and just go for simplicity. Half a gig for /boot, and the rest for / (in ext4). I've tried btrfs, but I've never been in the position where I needed snapshots, and ext4 is a lot more simple.

I also like having the flexibility of not having a separate home partition. I back up my super important files, so it doesn't matter if I lose home (not that I distrohop much anymore, anyway). And I don't have to stress about whether I've made my root partition big enough. For the same reason I use a swapfile rather than a swap partition (though I do need to look in to zram and zswap) - I like knowing that I can resize it easily, even if I don't really plan on doing so.

Just recently repartitioned my MacBook:

1 GB for EFI (vfat)
2 GB for /boot (ext4)
11 GB for swap
224 GB for / (bcachefs)

Grub cannot load a kernel off bcachefs so I need ext4 to bridge the gap. Once the kernel is loaded, it has no problem using bcachefs as root.

fabien@debian2080ti:~$ df -h
Filesystem                         Size  Used Avail Use% Mounted on
udev                                16G     0   16G   0% /dev
tmpfs                              3.2G  1.9M  3.2G   1% /run
/dev/mapper/debian2080ti--vg-root   28G   25G  1.8G  94% /
tmpfs                               16G  168K   16G   1% /dev/shm
tmpfs                              5.0M   24K  5.0M   1% /run/lock
/dev/nvme0n1p2                     456M  222M  210M  52% /boot
/dev/nvme0n1p1                     511M  5.9M  506M   2% /boot/efi
/dev/mapper/debian2080ti--vg-home  439G  390G   27G  94% /home
tmpfs                              3.2G  2.6M  3.2G   1% /run/user/1000
/dev/sda3                          1.7T  1.6T   62G  97% /media/fabien/a77cf81e-fb2c-44a7-99a3-6ca9f15815091

EFI
83:boot(e4fs)
8e:lvm(e4fs)
bf:zfs

This is just for /dev/sda or so, and implies non-redundant root disks because mirroring is done by the hypervisor. I've been 20 years doing virtualization, and I'm really starting to forget the last vestiges of my mdadm fdisk layout.

So many people in this thread have no idea why you'd want separate allocation for /home and /tmp and others. Are we missing proper mentorship?