On Fri, Apr 02, 2010 at 04:50:32PM +0200, Toni Mueller wrote:
| Hi,
|
| On Fri, 02.04.2010 at 15:50:36 +0200, Paul de Weerd <[email protected]> wrote:
| > What do you mean "the new kernel won't boot" ?
|
| I mean that, for whatever reason, the kernel does not reach full
| multi-user capabilities within some timeout (say, 5 minutes).
Your timeout idea is interesting. The bootloader loads the kernel
image and then starts executing it. After this, the bootloader is no
longer active, who will do this timing out ? The kernel (or the
garbage that was loaded in its place) is the only code running at this
point.
| > May seem like a nice idea at first, but it doesn't sound very portable
| > to me.
|
| Ok... then I should probably try to figure out how to boot OpenBSD by
| non-BSD-supplied boot loaders (eg. grub).
I don't think they will offer you the option of timing out the kernel
booting.
Now you may of course be doing the time out yourself (looking at your
watch and pinging the remote host). In this case, clearing a flag from
userland like I suggested in my previous mail becomes possible. But
consider this .. after your proposed 5 minutes (or whatever time you
deem sufficient) you decide something is wonky and do a remote power
reset. What if it was a typo in your /etc/hostname.if or
/etc/pf.conf ? The system was multiuser (the proper flags were cleared
from userland) and waiting for you to log in, but you couldn't reach
it...
You seem to have a valid issue, but a proper solution does not appear
to be obvious to me. I take it you don't have two machines under your
control in these remote locations so you could exchange serial console
between the two ? (a USB to serial adapter on one machine connected to
the serial port of the other and vice versa)
Cheers,
Paul 'WEiRD' de Weerd
--
>++++++++[<++++++++++>-]<+++++++.>+++[<------>-]<.>+++[<+
+++++++++++>-]<.>++[<------------>-]<+.--------------.[-]
http://www.weirdnet.nl/
