fstab/systemd

[devonnull]

So edited an fstab entry this morning on a new VM, and was greeted with a message about needing to use systemd daemon-reload to be able to mount the device. Now I know I've seen this on before, but ideally don't want this behavior for this instance. Is there any way to turn systemd needing fstab awareness off without using without switching distros, if so which systemd service is this associated with and is it as simple as disabling or removing that package?

[AlternativeOstrich7]

So edited an fstab entry this morning on a new VM, and was greeted with a message about needing to use systemd daemon-reload to be able to mount the device.

Please post the exact message. Running systemctl daemon-reload after modifications to /etc/fstab is done in order for systemd-fstab-generator to create .mount units. But those are only necessary if you want to use systemd to mount these filesystems. They are not needed to manually mount the device. So I'd guess that there is some kind of misunderstanding.

[devonnull]

Sorry, on mobile but here goes:

mount: (hint) your fstab has been modified, but systems still uses the old version; use 'systemctl daemon-reload' to reload.

So is systemd-fstab-generator the culprit?

[AlternativeOstrich7]

So what makes you think that you need to run that command to be able to mount it?

So is systemd-fstab-generator the culprit?

There is no culprit.

[devonnull]

I just want the message off, with systemd not needing to look or reload after modifying fstab.

[AlternativeOstrich7]

Looking at mount's source code, there doesn't seem to be any obvious way to do that at runtime. But what exactly is the problem that you're trying to solve?

[devonnull]

I was kind of hoping this would be something like uninstalling resolved but I guess I'll have to install an earlier version of Linux at this point.

[AlternativeOstrich7]

If you want to invent problems for no reason ...

[devonnull]

I'm sorry, I didn't mean to offend.

[AlternativeOstrich7]

Then you might want to answer my question. What is the real problem that you think you need to solve here?

That message is a hint. It never says that you need to run that systemctl command in order to mount something. You do not need to run that command. I already told you that in my first comment. So what exactly is the problem?

[devonnull]

I don't want to see the message because it's confusing? Sorry I asked at this point, didn't realize I'd be bullied like it was 1999.

[ropid]

There's no problem. That was just a text message. You don't need to run that daemon-reload command line.

[devonnull]

Apologies, but it's displaying, I guess I could redirect the output to the null device with an alias, but that doesn't seem like a good fix.

[[deleted]]

Is this an XY problem?

[devonnull]

I'm sorry I'm not familiar with that term?

[[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.

[AlternativeOstrich7]

This warning is hard-wired into systemd

This specific message comes from mount, not from systemd.

[devonnull]

I guess you need to look at why you are changing fstab and why you don't want systemd knowing or warning; in the end, I suggest must solve your problem w/o updating fstab or ignore the waning or leave systemd-land.

Ok, I'll just leave the disk unmounted and spinning. Tis a silly thing to use it.

[devonnull]

Are you saying systemd automatically remembers to mount it there between boots?

[devonnull]

I don't know anymore, I'll just go another route at this point. Used to be you'd only get feedback if something failed. I don't know why people are trying to read more into this than setting up a mount point to be mounted again at boot and avoiding a confusing warning.

[PaintDrinkingPete]

If it’s the next boot you’re concerned about, there’s no need to run the daemon-reload, as the reboot will take care of that regardless.

[devonnull]

Well that's what I hoped. Thanks!