On Tue, Sep 29, 2020 at 11:04 AM Manfred Hollstein firstname.lastname@example.org wrote:
On Tue, 29 Sep 2020, 16:25:13 +0200, Thorsten Kukuk wrote:
On Tue, Sep 29, Richard Brown wrote:
There are some configuration files not owned by any package, such as /etc/fstab
In such an example, it might be advantageous to have YaST produce an /usr/etc/fstab at installation time, to provide the 'default filesystem layout', but then have modifications present in /etc.
I would propose to drop /etc/fstab and only use systemd.mounts. Don't know why upstream systemd thinks mount units should not be used instead of /etc/fstab.
just to be sure I get this right... /etc/fstab is for the local admin to add stuff which otherwise is defined by systemd.mounts? To be honest, this will drive away lots of admins coming from a real UNIX background! I always thought of systemd was a bad thing, but some/a lot of parts really work OK in the meantime, and most admins got used to it. But removing /etc/fstab? No way!
Upstream systemd does not recommend getting rid of /etc/fstab. Mount units were designed to express dependencies on mounts and to support *transient* mounts via a reasonable API.