Mike Smith wrote to Ryan Thompson:

> > "Don't have a keyboard" != "No keyboard detected" != "Serial Console".  
> 
> No keyboard detected -> local console won't be used -> use serial console

Yes, that would seem to sum up the current behavior quite well. :-)


> > Ok, so they can't be probed.  However, I HAVE thought about it for a
> > minute, and, to be honest, I still don't see why my proposal is entirely
> > nonsensical. :-)  Would you mind explaning your argument?  For clarity,
> > I'll explain mine again... Perhapas we're just not on the same wavelength:
> > 
> > >From boot(8):
> > 
> >        -P   probe the keyboard.  If no keyboard is found, the -D and
> >             -h options are automatically set.
> > 
> > Instead of that behaviour, I am suggesting a more forgiving behaviour:
> > 
> > 1. Probe for a keyboard.
> > 2. Is there a keyboard? 
> >  Yes - Boot from the local console
> >  No  - Display "Keyboard not found.  Using serial console in 10 seconds,
> >             press any key to abort"
> 
> This is as stupid as the "Keyboard error - Press F1 to continue" message 
> that several BIOS vendors are so fond of.  If there's no keyboard 
> attached, you can't hit a key.  Not very smart.

:-)  I just mentioned that in another (now closely related) thread.


> > 3. Was a key pressed in 10 seconds?
> >  Yes - Boot from the local console
> >  No  - Display "Booting from serial console"
> >        Boot from the serial console
> 
> There's also not enough code space in the bootstrap for this frippery.  
> If you want to use a local keyboard, make sure it's plugged in.  We don't 
> have a diagnostic for when you forget eg. to install your disk drive 
> either...

That's a concern that I stated in my previous post.  If it's not feasable,
then it's not feasable.  (And I can infer from your responses that you
wouldn't be the one to commit such frippery to the codebase, anyway :-)

It was but an idle query from someone mildly inconvenienced by -P.

Thanks for the input.

- Ryan

-- 
  Ryan Thompson <[EMAIL PROTECTED]>
  Systems Administrator, Accounts
  Phone: +1 (306) 664-1161

  SaskNow Technologies     http://www.sasknow.com
  #106-380 3120 8th St E   Saskatoon, SK  S7H 0W2



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to