Summary: | Problem with reboot.sh script and /sbin/reboot (kexec-related) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Slycord <cslycord> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chris Slycord
2006-04-04 17:38:06 UTC
Now I am even more confused. With reboot.sh looking like this: # Copyright 1999-2005 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 /sbin/reboot -idpk # hmm, if the above failed, that's kind of odd ... # so let's force a reboot /sbin/reboot -f I then entered (as root) "/sbin/reboot -idp" and it restarted using kexec. Then I removed the "k" in reboot.sh and again entered "/sbin/reboot -idp" and was rebooted to bios. This makes absolutely no sense to me. The way a command responds shouldn't be effected by another script that can be used to call that command. if you look at the source code of sysvinit you'll see that the behavior of running reboot depends largely on what init level you're currently in i mentioned this user-unfriendliness upstream with the kexec project but i dont recall them being able to come to a solution ... iirc, i pushed for something like `reboot -k` to use kexec but `reboot -K` to not use kexec what i do is add the kexec init.d script to my default run level so that the kernel gets tagged automatically at boot for use with kexec ... but if i want to reboot into the bios, i stop the kexec script before rebooting so try changing your alias to something like: alias reboot='sudo /etc/init.d/kexec stop ; sudo reboot' |