On Sun, Apr 20, 2014 at 09:27:55PM -0500, Bruce Dubbs wrote:
> Ken Moffat wrote:
> > I'm just looking in more detail at the set-systemd and set-sysv
> > scripts in section 7.1.
> >
> > Two questions:
> >
> > 1. set-systemd ends with
> > echo "Now reboot with /sbin/reboot-sysv"
> > and set-sysv ends with
> > echo "Now reboot with /sbin/reboot-systemd"
>
> > Are these swapped, i.e. set-systemd should instruct
> > people to run "reboot-systemd" ?
>
> When you change the symlinks, you need to reboot with the program for
> the existing system, not the new one. After the symlinks are changed,
> the reboot program points to the wrong version.
>
> If you booted into a sysv init, reboot normally calls that init. You
> need to use the sysv reboot.
>
> > 2. does a plain reboot not do whatever is necessary to change from
> > sysv to systemd, or vice-versa ?
>
> No. After a symlink change, a plain reboot would use the wrong version.
>
> -- Bruce
OK, I take your point that a previous-style reboot is recommended
after changing between the init systems.
For those of us who enable MagicSysRQ in our kernel builds
(Alt-PrintScreen-letter) I imagine that Alt-PrintScreen-{S,U,B}
(sync, umount, boot) will do the job, and that if we have to go back
to the old init version this will be no worse than any other unclean
shutdown ?
ĸen
--
das eine Mal als Tragödie, dieses Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
