Okay....
I'm trying to setup a system with a serial console and mostly everything has
worked as expected.
With minicom running at 9600 and using software flow control I can see and
control the lilo prompt. I see the kernel messages and the SysV init
messages. In multiuser mode getty starts up fine and I can log in via the
serial port.
All of that is good.
But when I go to single user mode init shows me the "bash#" prompt but thats
it. I can't use the bash prompt or anything.
I'm fairly certain it can't be a terminal settings issue (relating to
/etc/ioctl.save) or anything becuase the magic sysrq still works over the
serial port. Also if go straight to S instead of via runlevel 1 (so I keep
the rest of my processes) I still echo out to the serial port and I
faitfully see it in my minicom session.
lsof shows that /bin/bash has its stdio mapped to /dev/console as expected.
strace shows that bash is blocking on a read(0, ...) operation.
If i use other shells like /sbin/sash, /bin/ash, or even /bin/cat the same
behavior is seen.
Ditto if i force bash to use /dev/ttyS0 isntead of /dev/console for it's
stdio.
If I tell init to stary getty in runlevel S instead of /bin/bash then
everything works just as well as it does in multi-user mode. Of course...
that does rather reduce the usefulness of acutally having a single user
mode.:)
This is on a stock redhat 2.2.16-3 kernel except with the 5.05 serial
drivers installed.
Anyone who's struck this problem or knows what's going on.. I'd love to hear
from you. :) A serial console that doens't work in single user mode is
rather pointless.
Cheers.
M.
--
WebCentral Pty Ltd Australia's #1 Internet Web Hosting Company
Level 1, 96 Lytton Road. Network Operations - Systems Engineer
PO Box 4169, East Brisbane. phone: +61 7 3249 2583
Queensland, Australia. pgp key id: 0x900E515F
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
