-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 16.12.2011 22:37, schrieb Cristian Rodríguez:
Supporting 2 different init systems comes with a large increase of possible usecases and scenarios that are very difficult to support correctly, specially in the long term.
This RFC proposes steps to permanently phase out sysvinit from future openSUSE releases.
- Fix all *currently* outstanding bugs of systemd
https://bugzilla.novell.com/show_bug.cgi?id=696902 tracks several systemd-related bugs in the "Depends On" section and there are currently 32 open bugs at: https://bugzilla.novell.com/buglist.cgi?quicksearch=systemd
note that this step only deals with problems in systemd itself, not in service files installed by other packages, udev, kernel, networkmanager or whatever other thing.
We need to address bugs in other components (that did not occur with sysvinit) to avoid regressions.
- Determine which services currently lack of native systemd units.
As I understood it, native unit files are not needed for the goal of fully switching to systemd and dropping sysvinit - so this step (and all other steps about /etc/init.d/ replacement) should be optional.
Add documentation, HowTos etc. for developers and users of systemd and its service files so that they can tweak and extend their system as easily as with sysvinit. This might be inherently hard, because some things that used to be in easily changeable /etc/init.d/boot.* scripts were hardcoded into systemd's C code.
test, test, test.
remove sysvinit and all the relevant bootloader options and from
This step will ideally still be some years ahead, so that as many use-cases as possible will be known to work with systemd. People don't like being forced into something that does not work properly.
-- Profit. :-)
Ciao Bernhard M.