On Thu, 2010-11-25 at 11:23 +0100, Ludwig Nussel wrote:
Kay Sievers wrote:
- systemd/SYSV service management - the init scripts should call systemd if systemd is used, e.g. /etc/init.d/cups start" should either print a warning or call "systemctl start cups.service" directly
I'd suggest to turn the {/usr,}/sbin/rcfoo -> /etc/init/foo symlinks to links to /sbin/service. That script can then decide whether to talk to systemd or run the initscript. The conversion could be done automatically via brp script.
Lots of things don't do the rcfoo stuff, just /etc/init.d/foo, right? Other distros are doing it by adding stuff to /etc/rc.status, which is sourced-in by every file.
- replace SUSE-specific config files to new cross-distro configs: /etc/os-release (like /etc/SuSE-release)
Why not call it /etc/linux? :-)
Yeah, no reason. :)
- some of the old SUSE-specific config files are read by systemd, but we should start using the new "Linux default"
Ah, that reveals the real intentions.
- sort out NetworkManager vs. sysconfig mess - starting NetworkManager from a the sysconfig init script, depending on a config variable is just weird
Isn't that just the logical consequence of the usual freedesktop.org "There can be only one" philosophy we see a lot nowadays?
Why? NM on Fedora works fine running at the same time as the old network scripts stuff. If there is an old config, NM ignores the device/ I think that's much better than what we do. And it allows us to have proper D-Bus activation of NM, to be able to ignore dependencies, and NM service files to manage if NM is used. Kay -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org