It doesn't seem right that installing kexec-tools would change the semantics of the "reboot" command.
It was finally decided enabling kexec reboot by default was the reasonable > thing to do since one needs o install kexec-tools explicitly and one would > install it primarily when they want to enable kexec reboots. If I write an app that depends on kexec-tools to do what debathena does or something similar, I should explicitly call on kexec -l. Such apps do exist (as evidenced by this report) and many other possible ones come to mind. In such a scenario, the user may not have explicitly installed kexec-tools or even know that it exists. She would would experience an unexpected change in behaviour. How about if I leave the default to be enabled but make the debconfquestion > high priority (it is medium priority at this time). Making such a question "high" priority means that there is no reasonable default. It seems to me that the reasonable default for kexec is to not automatically modify the behaviour and intent of "reboot". -- Luke Faraone;; Debian & Ubuntu Developer; Sugar Labs, Systems lfaraone on irc.[freenode,oftc].net -- http://luke.faraone.cc PGP fprint: 5189 2A7D 16D0 49BB 046B DC77 9732 5DD8 F9FD D506
