Andrei Borzenkov wrote:
01.12.2016 01:51, Carlos E. R. пишет:
/etc/fstab is read once when systemd is started. Editing it after that has no effect unless you reload systemd (systemctl daemon-reload) and even then previous units may be carried over.
---- So they only way to get it to respect a new run-time change to fstab, is to restart systemd, which forces a reboot of the machine to ensure a new copy of systemd? It also sounds like /etc/fstab has become "/etc/fsinittab", in practice, and that a new file-system mount table, "/etc/fsruntab", needs to be created to restore the original usage and intent of /etc/fstab?
Seems things are getting worse in this respect in 42.2 than in 13.1 :-(
Well, systemd author believes it's a feature. If you can find arguments to convince him in the contrary ... I could not.
Lovely. Still reminds me of the M5 computer evolving beyond its original purpose. Still seems like this is emphasizing the need for a new run-time-fstab... ;-( It's a bit worrisome how things continue to change in lack of a roadmap. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org