6 ms·

Partition autodiscovery is pretty neat. I did my archlinux install with it using this guide[0]. I have never touched /etc/fstab and I have had zero to worry abo

Partition autodiscovery is pretty neat. I did my archlinux install with it using this guide[0]. I have never touched /etc/fstab and I have had zero to worry about corrupting a boot with wrong fstab entries. [0] https://walian.co.uk/arch-install-with-secure-boot-btrfs-tpm2-luks-encryption-unified-kernel-images.html https://walian.co.uk/arch-install-with-secure-boot-btrfs-tpm...

nubinetwork 3mo ago
Btrfs and zfs don't need an fstab at all, they manage their mountable filesystems internally.
- s_ting765 3mo ago
  Sure. After you have located root and the boot partition which is what this addresses.
simoncion 3mo ago
My searches for "systemd partition autodiscovery" lead me to [0]. In the table labeled "Table 1. Partition Type GUIDs", we find this in the Explanation section for 'SD_GPT_HOME' The first partition with this type UUID on the same disk as the root partition is mounted to /home/. ...you can't spread your /home and / partitions on separate disks and use this? In fact, it looks like you can't use this autodetection unless all of the partitions of interest (including your /boot/) are on the same disk? Seriously? There's also no indication that this works with LVM... which is -if true- is extremely inconvenient. The document at [1] only mentions LVM in passing, and [2] is Poettering saying "Fuck off, I don't want to support doing this with LVM". Did I misread a document or fail to find a relevant one? If not, is this really limited to single-disk, "legacy" [3] configurations? [0] <https://www.freedesktop.org/software/systemd/man/latest/systemd-gpt-auto-generator.html https://www.freedesktop.org/software/systemd/man/latest/syst...> [1] <https://uapi-group.org/specifications/specs/discoverable_partitions_specification/ https://uapi-group.org/specifications/specs/discoverable_par...> [2] <https://github.com/systemd/systemd/issues/1727 https://github.com/systemd/systemd/issues/1727> [3] Yes, I'm considering any fixed-partition mechanism, whether MBR or GPT to be "legacy". The flexibility you get from LVM is sooooo nice.
- jeroenhd 3mo ago
  > you can't spread your /home and / partitions on separate disks and use this No, you'll need to add a line to your fstab manually if you want something autodiscovery cannot do, like multi-disk setups, LVM, and FDE with unsupported configurations. It's great if it works for you and a very minor change if it doesn't. I don't recall ever installing a system with / and /home on separate partitions, though.
  - simoncion 3mo ago
    > No, you'll need to add a line to your fstab manually if you want something autodiscovery cannot do... It's just shocking that autodiscovery is so extremely limited. I'm aware that if you want to do something that autodiscovery can't do, then you cant use autodiscovery for that thing... I'm pretty sure that was covered in a recent Tautology Club meeting. > I don't recall ever installing a system with / and /home on separate partitions, though. I'd wager that that's the configuration of vast majority of the consumer systems out there... which makes it even more confusing how anemic partition autodetection is. Its target user is one who bothers to partition out space for subdirectories, but doesn't use either multiple disks or LVM? That's a very particular sort of user.
    - jeroenhd 3mo ago
      > I'd wager that that's the configuration of vast majority of the consumer systems out there... I'm not so sure. Most people I know, including developers, only have one SSD, maybe a hard drive for photos or whatever that's not mounted inside /home. The most popular mainstream Linux distributions (Android, ChromeOS, SteamOS) all default to a single disk setup, as do most virtual machines (which must exceed the number of home installs by at least a thousandfold). For a particular brand of enthusiasts, running multi-disk is definitely more popular (I have 4 in my desktop), but I don't think those are the majority, and even among those splitting partitions across disks rather than just using a /media (or equivalent) to access the larger disk like you would an external drive is quite popular. Multi-disk detection would be nice, but I can already imagine the absolute mess that would happen if you were to try to boot on a multi-distro PC, or even just a recovery flash drive on an existing Linux image. My recovery boot drive only has a root partition so auto-detecting the drive will work fine, but auto-mounting my home directory to /home would mess up the entire system. The code would be so full of edge cases and weird guards that it'll inevitably just break without configuration, making the entire thing pretty damn useless.

nubinetwork 3mo ago

Btrfs and zfs don't need an fstab at all, they manage their mountable filesystems internally.

s_ting765 3mo ago
Sure. After you have located root and the boot partition which is what this addresses.

simoncion 3mo ago

My searches for "systemd partition autodiscovery" lead me to [0]. In the table labeled "Table 1. Partition Type GUIDs", we find this in the Explanation section for 'SD_GPT_HOME' The first partition with this type UUID on the same disk as the root partition is mounted to /home/. ...you can't spread your /home and / partitions on separate disks and use this? In fact, it looks like you can't use this autodetection unless all of the partitions of interest (including your /boot/) are on the same disk? Seriously? There's also no indication that this works with LVM... which is -if true- is extremely inconvenient. The document at [1] only mentions LVM in passing, and [2] is Poettering saying "Fuck off, I don't want to support doing this with LVM". Did I misread a document or fail to find a relevant one? If not, is this really limited to single-disk, "legacy" [3] configurations? [0] <https://www.freedesktop.org/software/systemd/man/latest/systemd-gpt-auto-generator.html https://www.freedesktop.org/software/systemd/man/latest/syst...> [1] <https://uapi-group.org/specifications/specs/discoverable_partitions_specification/ https://uapi-group.org/specifications/specs/discoverable_par...> [2] <https://github.com/systemd/systemd/issues/1727 https://github.com/systemd/systemd/issues/1727> [3] Yes, I'm considering any fixed-partition mechanism, whether MBR or GPT to be "legacy". The flexibility you get from LVM is sooooo nice.

jeroenhd 3mo ago
> you can't spread your /home and / partitions on separate disks and use this No, you'll need to add a line to your fstab manually if you want something autodiscovery cannot do, like multi-disk setups, LVM, and FDE with unsupported configurations. It's great if it works for you and a very minor change if it doesn't. I don't recall ever installing a system with / and /home on separate partitions, though.
- simoncion 3mo ago
  > No, you'll need to add a line to your fstab manually if you want something autodiscovery cannot do... It's just shocking that autodiscovery is so extremely limited. I'm aware that if you want to do something that autodiscovery can't do, then you cant use autodiscovery for that thing... I'm pretty sure that was covered in a recent Tautology Club meeting. > I don't recall ever installing a system with / and /home on separate partitions, though. I'd wager that that's the configuration of vast majority of the consumer systems out there... which makes it even more confusing how anemic partition autodetection is. Its target user is one who bothers to partition out space for subdirectories, but doesn't use either multiple disks or LVM? That's a very particular sort of user.
  - jeroenhd 3mo ago
    > I'd wager that that's the configuration of vast majority of the consumer systems out there... I'm not so sure. Most people I know, including developers, only have one SSD, maybe a hard drive for photos or whatever that's not mounted inside /home. The most popular mainstream Linux distributions (Android, ChromeOS, SteamOS) all default to a single disk setup, as do most virtual machines (which must exceed the number of home installs by at least a thousandfold). For a particular brand of enthusiasts, running multi-disk is definitely more popular (I have 4 in my desktop), but I don't think those are the majority, and even among those splitting partitions across disks rather than just using a /media (or equivalent) to access the larger disk like you would an external drive is quite popular. Multi-disk detection would be nice, but I can already imagine the absolute mess that would happen if you were to try to boot on a multi-distro PC, or even just a recovery flash drive on an existing Linux image. My recovery boot drive only has a root partition so auto-detecting the drive will work fine, but auto-mounting my home directory to /home would mess up the entire system. The code would be so full of edge cases and weird guards that it'll inevitably just break without configuration, making the entire thing pretty damn useless.