On Sat, 24.07.10 00:14, Casey Dahlin (cdahlin@xxxxxxxxxx) wrote: > > On Fri, Jul 23, 2010 at 10:54:50PM -0500, Garrett Holmstrom wrote: > > On 7/23/2010 20:26, Lennart Poettering wrote: > > > - You can boot into either of them by setting the "init=" kernel cmdline > > > option according to your wishes. If you pass "init=/bin/systemd" you > > > will boot into systemd, if you pass "init=/sbin/upstart" you will boot > > > into upstart (note the /sbin vs. /bin!) > > > > Why is the systemd executable in /bin instead of /sbin? > > Without looking too closely I believe systemd eventually seeks to replace > things like gnome-session daemon. It has session management in mind as well as > system. Yes, this is the case. Normal users can and should start it and it might even be invoked by scripts such as gnomerc or suchlike. On most distributions (with the exception of Fedora) /sbin/ is not in $PATH and hence the right place for the systemd binary is /bin/ and nothing else. Lennart -- Lennart Poettering - Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
