01234567890123456789012345678901234567890123456789012345678901234567890123456789
I have 3 machines in this setup.  The setup being:

- Room "big closet" (where I sit) contains "mDesktop".
- Room "small closet" contains machines "mTest" and "mControl".

- Machines  mControl and  mTest have a serial "crossover" cable (null
  modem) connecting their /dev/ttyS0 (COM1) ports.

- I am using 'ssh' from  mDesktop to connect into  mControl.

- I've setup  mTest to listen on it's serial port for a login with the
  line in its "/etc/inittab":

    S0:12345:respawn:/sbin/agetty -L 38400,19200,9600 ttyS0 linux

I sent -HUP to init on mTest to signal rereading its inittab.

mTest appears to be spawning "agetty" on ttyS0 as expected/desired.

*** my problem(s):
    - How do I use mControl's ttyS0 port to connect to  mTest?
    - What program do I use on  mControl to connect me to  mTest?

Notes/thoughts:

I remember doing this with 'cu' in the past, but I've never felt
entirely comfortable with this due to a comment in the 'cu' manpage:

  BUGS
         "This program does not work very well"

Is there a preferred alternative?  I vaguely remember using some
sort of 'call device' like 'cua0' in cu that corresponded to ttyS0
with an invocation like:
  cu -l /dev/cua0

I've tried the above and "cu -l /dev/ttyS0" and neither work:

mDesktop > cu -l /dev/ttyS0
cu: open (/dev/ttyS0): No such device or address
cu: /dev/ttyS0: Line in use
mDesktop > cu -l /dev/cua0
cu: open (/dev/cua0): No such file or directory
cu: /dev/cua0: Line in use

------
    The different error messages, in some part, have to do
with the fact that under the new udev-managed /dev directory
"cua0" no longer exists. Don't even remember, offhand, what
it's Major-Minor device numbers were, but don't think that
would necessarily help since the numbers under udev are
allocated differently.  Also, there doesn't seem to be any
"default" config files setup for uucp anymore (I think it had
some commented-out line that, commented-in, enabled cua0, but
it has been a while.  Is there a better way to do this these
days?

    I also need to know how to do this to be able to connect
to local devices that provide a serial port for management (when
managing them sans-network).

    Eventually, I'd like to be able to use the serial port as
mTest's console (as it's not always convenient to find a 'head'
to attach it to (esp. right now with the VGA-monitor in that room
having died recently :-))...

TIA...
Linda
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to