3 ms·

Ok that’s a bit much. Why is SystemD encroaching on the fstab??

• jcelerier 5y ago
  Because systemd services can depend on mount points or cause mountpoints to come up dynamically, in a way that pure fstab does not support, e.g. for containers. So (as far as I understand) fstab is now simply an input to the actual mount system.
• Denvercoder9 5y ago
  It's not encroaching on fstab, it's using it as input during boot, because mounting is intimately coupled with service ordering. Think about services that reside on a network filesystem: the network has to be up to mount the filesystem, but the network in turn can require arbitrary services to run, which can require other local filesystems to be mounted. You can't get configurations like these to work without coupling mounting and service ordering. It's fundamentally not that different from sysvinit, with its various init scripts that mounted filesystems according to the fstab.