August 2019 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Decission: configuration files in /etc and /usr/etc
by Thorsten Kukuk 21 Aug '19

21 Aug '19

Hi, after many months and many discussions, we decided to go with my Proposal for a better configuration file management on openSUSE (https://github.com/thkukuk/atomic-updates_and_etc/) and use /usr/etc as the directory below /usr for distribution provided configuration files. While there is a small risk in using this directory, the feedback was nearly unanimously to go with this directory, as this is well known to people. Having the by-in from so many people is in our opinion really important. If we choose a name nobody likes, we can declare it already as failed. So, what do we plan? -------------------- The plan is, to make updating of configuration files a lot of easier and solve the problems of configuration file updates with atomic updates (transactional-update on openSUSE). Longterm, /etc should only contain the host specific and by the admin modified configuration, all distribution provided configuration files should be in /usr/etc. Additional, the distribution provided configuration files should be moved from /usr/lib and consolidated in /usr/etc. Configuration files in /usr/etc should not be modified by the admin, as /usr/etc can be read-only. Instead, the applications needs to be enhanced, as far as possible and necessary, to read the configuration files from several locations. Take the systemd configuration as example: https://www.freedesktop.org/software/systemd/man/systemd.unit.html#Examples What needs to be done? ---------------------- In the first place, you need to adopt your packages. What you need to do and what you can do depends on your package. It's not possible to implement this with every kind of configuration file, but on the other side, there are many applications which supports this already, and it is only a question of the right configuration and maybe a little bit of tweaking it. We develop currently an universal, really flexible config file parser for config files more or less compatible with the ini file format, it's libeconf: https://github.com/parlt91/libeconf This should make it much easier to port some applications to the new schema. Roadmap: -------- We will start with adding the directory to the filesystem RPM and adjust the scripts to not throw an error if you use this directory. Afterwards we will go through the files in /etc and move the easy ones and continue until we are done. At some point in time we will create new tests which forbids to deliver files in /etc, so that this will really finish at some point in time and we don't add more files to /etc then others remove. Open Questions: --------------- If you read the github document, you will see, that we don't have a solution for everything yet. I hope we can improve here over the time. Second, the big question for packagers: configuration files in /usr/etc, should we mark them as %config or not? As no customer should touch them, %config is not really necessary. On the other side, if we mark them as %config and the user modifies them by accident, the next update would not overwrite the changes, but save them as *.rpmsave file. %config(noreplace) is no option, this would lead again to big problems with not updated configuration files and thus not working services. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

3 8

[opensuse-packaging] Re: [opensuse-factory] Update on configuration location below /usr
by Jan Engelhardt 18 Aug '19

18 Aug '19

On Monday 2019-07-29 18:54, Manfred Hollstein wrote: > > everyone coming from a *NIX background *knows* what /etc is and > probably can deduct, what /usr/etc is. Even if you believe it was a > terrible name, it *is* a name known to a lot of people, at least from > a generation before 2019 or maybe more ;) Even M$ adopted it... (do > you know where their /etc/hosts equivalent lives ;) ? ) Technically speaking, today's equivalent of the hosts file lives in one or more unspecified databases. In case of Windows, there is a program called "DNS Manager" to edit it (this is probably already outdated information, looks like they have something new in Windows 2016 again). As is common with Microsoft products, the data is stored in binary form in some arcane location somewhere (the registry, an AD, ... needless to say, the data _will_ end up on an actual storage device at some point). -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

1 0

[opensuse-packaging] AMD SEV sev-tool
by Larry Dewey 07 Aug '19

07 Aug '19

Hey everyone, I was hoping to receive some direction as to what group this application should be placed in. The primary usage of this tool is for provisioning an AMD Secure Encrypted Virtualization (SEV) guest, test the SEV hardware, and perform host introspection to determine if the host is ready to provide SEV access for guests. Thanks, Larry Dewey

2 1