Who still partitions like that???
Anyone using ZFS should!
Since ZFS partitions are all taking from the available space of the pool, you can have as many partitions as you need, which is very practical for snapshots and diffs, or if you want to use the same pool for different hosts (=> use a different etc along with a few others like var/lib )
Look at the set of partitions I recommend on https://github.com/csdvrx/zfs-autosnapshot (this is for the host 7275 on the pool nvme)
zfs create -o mountpoint=/ nvme/7275
zfs create -o mountpoint=/etc nvme/7275/etc
zfs create -o mountpoint=/opt nvme/7275/opt
zfs create -o mountpoint=/usr nvme/7275/usr
# for optimization
zfs create -o mountpoint=/img recordsize=1M primarycache=metadata secondarycache=none nvme/7275/img
zfs create -o mountpoint=/img/qcow2 recordsize=64k nvme/7275/images/qcow2
# for safety
zfs create -o mountpoint=/var nvme/7275/var
zfs create -o mountpoint=/var/tmp nvme/7275/var/tmp
zfs create -o mountpoint=/tmp nvme/7275/tmp
zfs set exec=off nvme/7275/var
zfs set setuid=on nvme/7275/var/tmp
zfs set setuid=off devices=off sync=disabled nvme/7275/tmp
# for systemd-journald
zfs create -o mountpoint=/var/log nvme/7275/var/log
zfs set acltype=posixacl nvme/7275/var/log
# for postgresql optimization
zfs create -o mountpoint=/var/lib nvme/7275/var/lib
zfs create -o mountpoint=/var/lib/postgresql nvme/7275/var/lib/postgresql
zfs set recordsize=8K primarycache=metadata logbias=throughput nvme/7275/var/lib/postgresql