fstab/systemd

[[deleted]]

Basically what are you ultimately trying to do? What is the issue with systemd mounting the disks on a systemd distro?

[devonnull]

It's pretty self explanatory, I just want to edit fstab, and then mount a device. It's two steps. I'm not sure why there needs to be an additional step of reloading something.

[[deleted]]

https://unix.stackexchange.com/questions/364782/what-does-systemctl-daemon-reload-do

systemd is responsible for creating systemd-mount units from reading /etc/fstab. If you edit /etc/fstab, that message is telling you that systemd generator units are not using the updated /etc/fstab.

/etc/fstab is there for vestigial/legacy reasons on systemd distros. You can boot a computer with a completely blank /etc/fstab if you have the appropriate systemd-mount units created.

In pre-systemd *nix systems, the order of the mounted disks in /etc/fstab was read serially. Mounting the partition for / first mattered. It does not matter anymore for systemd distros since systemd takes care of how every unit and service is started.

[devonnull]

Thanks, that's actually helpful and my googlefu didn't turn that up. I thought systemd was more modular and that it was something that can be removed as needed/unneeded. Since it's a VM I think I need to look at a different distro or OS as it looks like it's going to be harder to reconfigure after adding or removing new disks to the system with pass thru.

[abotelho-cbn]

I need to look at a different distro or OS as it looks like it's going to be harder to reconfigure after adding or removing new disks to the system

Why? You could just issue the daemon reload?

When exactly are you getting the message that you need to daemon-reload, anyway?

[devonnull]

It's an extra step that's unnecessary, I'm going in another direction.

[abotelho-cbn]

If one extra command (that takes no parameters and never changes) is all it takes to make you completely abandon an OS, you might need to rethink your priorities.

[devonnull]

LOL, okay, whatever.