Lennart Poettering <mzerqung(a)0pointer.de> wrote:
I have just uploaded a new systemd and a new upstart package which
make
systemd the default init system for Rawhide. The scheme I followed makes
sure that in case systemd actually breaks systems there is an easy path
back to upstart. And here's how it works:
[...]
- Since there can only be one implementation providing the
/sbin/init
file name, I have split off -sysvinit packages from both packages
which symlink this to either /bin/systemd (in the systemd-sysvinit
pkg) or /sbin/upstart (in the upstart-sysvinit pkg). Something similar
is done for /sbin/reboot and the other well-known SysV client
utilities. That basically means you can choose which init system to
use by default simply by installing either of these two packages. By
default systemd-sysvinit will now be installed. As mentioned the
"upstart" and "systemd" packages do not conflict -- but
"upstart-sysvinit" and "systemd-sysvinit" do. The former two
packages
include all the actual code, and the latter then install them under
the well-known names via symlinks.
Can't be installed. yum wants to install _both_ *-sysvinit (even on freshly
installed machines: F13 --> rawhide), they conflict, and thus systemd isn't
updated at all.
--
Dr. Horst H. von Brand User #22616
counter.li.org
Departamento de Informatica Fono: +56 32 2654431
Universidad Tecnica Federico Santa Maria +56 32 2654239
Casilla 110-V, Valparaiso, Chile 2340000 Fax: +56 32 2797513