I don't see how it could be useful. If you don't want someone to see
the message (because he doesn't understand what this means), you
should set the timeout to zero. Then GRUB will show nothing.
Okuji
___
Bug-grub mailing list
[EMAIL PROTECTED]
seems to me that the default for almost any of these situations is to be
silent and force a verbose option via the menu.lst file. This would allow
you to explicitly control what is said and when it is said. Since you have
to have a menu.lst in order to boot anything anyway, then this should be
Have you thought about the side effects ?
Think, you have a mouse on COM1, which also is your secondary console...
then
*1* GRUB reinitializes the COM1 to the selected baud rate or mode
(at this moment not the problem, as the mouse drive is not
active
Christoph Plattner wrote:
Have you thought about the side effects ?
Yes.
Think, you have a mouse on COM1, which also is your secondary console...
Bad example. I do not have a screen, so connecting a mouse is useless.
What is with other things connected to the RS232 as multi meter with
