I remember using a command to force the system to re-read /etc/fstab after edits to it:

"systemctl daemon-reload".

I remember using this when switching USB drives from using block devices to UUIDs for mounting, and I remember it working. Not sure if it was on THIS install of slackware or one of the other distros that I was testing (and not liking, thus back to Slackware). And after forgetting to save this to a file in ~/systems, I found it again at

https://unix.stackexchange.com/quest...eload-of-fstab

Anyways, where is systemctl? The system is refusing to see updates to
/etc/fstab without it, but as root, I get

-su: systemctl: command not found

And why am I suddenly seeing this -su: crap that I've never seen before? Yes, I have a password for root, and no, I don't use it for ANYTHING that doesn't absolutely require root, especially if I'll be doing more than one command. I've known better for decades ... simple mistakes can result in immediate disaster.
If I run "zsh -l" (login shell), it goes away, but it still doesn't find systemctl.

Anyways, if not "systemctl daemon-reload", how do you force the system to reload /etc/fstab without restarting? I just restored a long-dead 4 TB drive (was as simple as lsblk, fdisk, and mkfs) and lost another one (same process fails).

Thanks

is one way to do it in SysVinit there are other similar commands also... but systemctl is for systemd systems...

1 members found this post helpful.

Guess what? Slackware does NOT use systemd, so there is no systemctl for you.

Yes, I know, I know. You learned Slackware, you learned Linux. BUT that was 30 years ago. Go figure!

1 members found this post helpful.

-su means you are currently used su to change to root (to open a shell).
systemctl should be available in your PATH, so either it is set incorrectly or the command does not exist at all.

1 members found this post helpful.

NOT in Slackware! This systemctl simply does NOT exists here.

1 members found this post helpful.

yes, that's what I wrote

1 members found this post helpful.

Yeah, got that. :-) Ok, so how DO I force a re-read of /etc/fstab without a restart? For some unknown reason, the newly restored 4 TB drive's UUID changed (confirmed by blkid). and while I corrected it in fstab, the system is still trying to mount the one that no longer exists.

I'm not about to restart just to force the system to update its view of fstab. That creates far too much stuff to restore (tiled tabs in Firefox that, while session manager is SUPPOSED to restore those, it doesn't. VLC windows for media in one virtual desktop, for music in the next one, re-starting pcloud (trivial, but yet another thing to do), and so on. The tiled tabs in Firefox are the major PITA to restore, but great once it's done.

So now the only question is, how do I get the system to re-read the actual file, /etc/fstab, instead of its version in memory?

Thanks

I'm surprised that you have UUIDs in your fstab. AFAIR slackware still uses old-fashioned device names.

30 years ago? Yeah, that's about right. :-) 1992, to be exact.

But it wasn't Slackware for me, it was my own custom-build BSD 4.2 Linux (using bits and pieces from sunsite.org). Was a screamer on the old 486 I'd loaded it on ... but then, Linux has always been resource friendly.

Thanks

I was advised, in this forum, to use UUIDs, and they're FAR better than device names. No more ... ummm, where is this drive mounted this time, where's this one mounted, and so on. They just mount correctly and that's that.

Thanks

If command mount -av is not working then, from the link you gave: https://unix.stackexchange.com/a/671664

1 members found this post helpful.

Thanks. Hopefully that will solve it. Just sitting down to breakfast now, but will try later.

Thanks

1 members found this post helpful.

... wrong post

Ok, I got the new drive mounted. And the old 4 TB drive is mounted, too (error in fstab---somehow, "defaults" got clobbered with a few letters in the middle of it, and my cancer tumor/surgery/chemo damaged left occipital lobe ignored it for weeks until just a minute ago when it finally let me see it. And hen I did see that, the solution for that drive was obvious...remove the noise. No idea how it got there, but it's cleaned up now.

Now all three 4 TB drives are mounted using their UUIDs (and the newly-repaired drive is using its second UUID after changing somehoe from its first one)..

Thanks everyone for the assistance in getting this all working again.

Edit: FOUR 4 TB drives, not three:

1) Media
2) Media (mirror)
3) /home
4) /backups