On Mon, 11 Dec 2000, Eric Seppanen wrote:
> On Mon, Dec 11, 2000 at 03:53:26PM -0700, Ronald G Minnich wrote:
> > it's easy to fix as soon as I can figure out the interface between linux
> > and linuxbios. Any suggestions? I was actually thinking of having a
> > /proc/chipset, with entries like
> > reboot
> > reset
>
> Isn't that over-engineering the problem a little bit? I mean, you could
> probably add less than ten lines of code to machine_restart() that would
> cover all the motherboards linuxbios can boot. And if that doesn't work,
> it's pretty easy for a user to add their own.
yeah, it might be. On the other hand, we're fooling around with seeing how
much stuff we can yank into linux user commands, such as over-clocking,
watching fans, and so on.
Also, some kind of less ad-hoc way to get into reboot would be nice. I
spent a lot of time looking at the linux reboot code, and at some point I
realized what a hack it is. Also, it for the most part barely works. All
my cluster nodes appear to reboot via the triple-fault path. yuck.
> And wouldn't access to reboot from /proc mean that the system would
> shutdown prematurely? Since init will call the reboot syscall when
> it's time to reboot, why would you want to add an alternate mechanism?
actually, it's useful. It's pretty much a nicer version of the "Magic
SysReq key". If you're running ext3 then an instantaneous reboot is kind
of handy, and you're not going to be hurt by doing it.
ron
