Comments below.
On Wed, 6 Jul 2011 09:00, Andreas Jaeger
I'd like to hear some feedback on the proposal below so that we can pass it on to the systemd developers,
Andreas
---------- Forwarded Message ----------
Subject: [systemd-devel] [RFC] Preset Files Date: Tuesday, July 05, 2011, 21:21:03 From: Lennart Poettering
To: systemd Mailing List
<snip>
More specifically this is how it should work: We'd have a directory /lib/systemd/system.preset/. By default it would be empty (or not even exist), which for simplicity reasons would mean "enable everything installed" (i.e. the Debian policy). Then, if distros or spins want to change what is enabled by default, they'd drop in a file (or multiple, which might be useful for a desktop spin and a graphical design spin where the latter is a superset of the former) in that directory. The file would be a trivial text file with lines like this: <snip> A few more things to note:
- systemd would not ship any preset file by default (and probably not even the directory), this is left to distributions. Most likely the distributions would ship a preset file in some spin-specific RPM, which would conflict with the the RPMs for other spins.
To NOT include the preset dir (/lib/systemd/system.preset/) in the systemd-package is not a good decision in terms of foresight. If you include the dir in systemd, you make it clear where it belongs to, and make sure it has the needed ownership and rights. In rpm-terms: mark it as config-dir. That way package-management can check for existence, ownership, rights. AND close a potential security hole (symlink-dir), before it even exists. Those that do not learn from the errors past are damned to repeat them. (original in Latin, spoken in early Rome, wrt the Greek, still true) Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org