Allan,
I'm already doing that (although I use /dev/tty2 rather than the serial port
since a modem may be out there). This removes the normal kernel diagnostic
spew, though if I press a key on the keyboard while any of the init scripts
are running that key will still be echoed to the display. I seem to have
been able to reduce the problem somewhat by adding the command "stty -echo"
at the beginning of all of my scripts, but that simply prevents the keyboard
characters from being echoed during the lifetime of that script file. When
another application is run (init or mingetty for example) then all of the
characters that were suppressed while the script file was running are now
displayed.
How can I clear out the contents of stdin in a bash script? Using read
isn't quite good enough since it still depends on line $IFS variable.
David Christensen
> -----Original Message-----
> From: Allan Jones [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 24, 2001 7:21 PM
> To: David Christensen; [EMAIL PROTECTED]
> Subject: Re: Hiding keyboard input
>
>
> This works for me (if you use LILO):
>
> Add the following line to your /etc/lilo.conf file
> append="CONSOLE=/dev/ttyS2"
>
>
> Make sure to run lilo afterwards!
> --Allan
>
>
>
>
> On Tue, 24 Jul 2001, David Christensen wrote:
> >I have a Linux system running with the Linux Progress Patch
> (which displays
> >a nice bitmap instead of the normal kernel messages). This
> works well, but
> >when Linux starts running the init process, any keys a user
> might press will
> >be displayed over the bitmap. How can I prevent this?
> >
> >David Christensen
--
To unsubscribe from this list, send a message to [EMAIL PROTECTED]
with the command "unsubscribe linux-embedded" in the message body.
For more information, see <http://waste.org/mail/linux-embedded>.
