Peter Bloomfield suggested minicom (thanks) and Tom Patton wrote:
On Wed, 2008-01-09 at 12:46 -0800, Linda Walsh wrote:
I have 3 machines in this setup. The setup being: --- Linda, load the "lessons for Lizards" documentation, and look at How-To Access COM Port (RS-232 client/server)
??lessons for Lizards" documentation? *blink* Say wah? What's a "lessons for Lizards?"...wait...suse? Lizard? still unclear...what or which document are you talking about? (sorry)
This uses the "screen" command, and is really perfect for you to get a console over the serial port. Or minicom.
ahh...screen or minicom I can probably find documentation on...but the lessons for lizard thing's got me stumped. :-)
..or why not a network connection, and tie them together with a hub or switch?
They are tied together with a gigabit switch...but when the kernel first boots, the network isn't available until later. I need to use the serial port (AFAIK), if I want access to the console. Have you ever done that over the network?...where you see all the bootup messages come over the serial line and then it leaves you at the login prompt on /dev/console (but over a serial port). Two reasons 1) monitor that was shared by these machines died (being replaced, but that doesn't help in the short term). 2) I want remote access to the console startup messages so I can monitor a boot to see if it goes ok and if not, what died. The computers I want to use the serial port for are in another room from where I'm sitting -- even when they had a working monitor, it was only for monitoring bootups or doing machine maintenance (the systems I want to access the serial port console on don't even run a desktop). Thanks.. Linda -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org