Thorsten Kukuk wrote:
On Tue, Sep 29, Richard Brown wrote:
There are some configuration files not owned by
any package, such as
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.
On a _default_ installation neither should be needed for operating
system components. The system can discover what goes where if we follow
some common pattern. For partitions there's the discoverable partitions
spec¹ from systemd for example. Our btrfs subvolume layout also follows
some pretty predictable scheme so it's actually redundant to explicitly
spell out what goes where. A generator could be used instead.
Admin overrides could of course still go into fstab but we wouldn't
clutter it by default anymore.
(o_ Ludwig Nussel
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer
HRB 36809 (AG Nürnberg)
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org