Re: [HEADS-UP] systemd for F14 - the next steps

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 2010-07-14 at 19:32 +0200, Lennart Poettering wrote:

> 
> Well, that doesn't really work, since upstart and systemd would fight
> for the /sbin/init name. If we want the system to boot into systemd by
> default /sbin/init must be linekd to /bin/systemd.
> 
> systemd provides compatibility with those sysv tools like
> reboot/shutdown/runlevel and init itself via symlinks to native
> binaries. The package "systemd" currently includes the native binaries
> and "systemd-sysvinit" adds in those symlinks. Only "systemd-sysvinit"
> conflicts with upstart, and only that package is what makes systemd the
> default init system. And that is the package which I want to make
> obsolete upstart.
> 
> To achieve what you want to do upstart would need to support something
> similar: make it possible to install it without insisting on the
> /sbin/init file name and related ones, and then add in those names via
> symlinks only by a an upstart-sysvinit package or so. But upstart
> doesn't support something like that. Sorry.

Would alternatives work here ?

-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux