On Tue, 2020-09-29 at 13:56 +0000, Frederic Crozat wrote:
With /usr/etc providing a pristine reference point, it should always be easy for users to evaluate their custom configurations for things that can be removed or optimised.
So what about YaST? Where would YaST bootloader module write its configuration?
To /usr/etc/default/grub? No, that's package's domain to /etc/default/grub? No, that's my (user's) domain to /var/adm/default/grub?
I'd say /etc/default/grub : YaST is working on behalf on the user.
It is "just" a nicer UI to /etc/default/grub than vi/emacs ;)
I'd agree, with the following theoretical caveat: 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. Of course such a option would need some magic done to handle such a split-fstab, so this is just in theory, presented as an idea to consider to see if we feel like going down that road. In practice, the simple straightforward "YaST does /etc, cuz its a tool used by the user" is a good assumption IMHO. Regards, -- Richard Brown Linux Distribution Engineer - Future Technology Team Phone +4991174053-361 SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, D-90409 Nuernberg (HRB 36809, AG Nürnberg) Geschäftsführer: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org