I sent this to questions a couple of weeks ago, but didn't receive any 
helpful replies.  Anyone doing this - two machines connected by a null-modem
cable with the ability to create a serial terminal session from either
side, with suitable juggling of getty processes?

John


Hi,

I have two FreeBSD boxes, one runs headless and uses a serial console.
This serial console is provided by the second machine, via a null-modem 
cable:

  +------------+                       +------------+
  | machine 1  |                       | machine 2  |
  | 3.5-STABLE |                       | 4.1-STABLE |
  | HEADLESS   |   Null-modem cable    |            |
  | port sio0  |=======================| port sio1  |
  +------------+                       +------------+

The serial console works perfectly. I can use cu / tip on machine 2 to
watch boot messages and log in (I have configured /etc/ttys to provide
a getty on /dev/ttyd0 on machine 1).

I would like to be able to do the reverse - log in to machine 1 through
a network connection, and use it to control machine 2.

My steps to accomplish this were:

        on Machine 1:
        change /etc/ttys to remove the getty on /dev/ttyd0
        kill -HUP 1

        on Machine 2:
        change /etc/ttys to run a getty on /dev/ttyd1
        kill -HUP 1

        on Machine 1:
        cu -l cuaa0

Doesn't work.
'cu' tells me I am connected, but no login prompt appears.  No characters 
I type are echoed.

I then removed the getty on machine 2 and tried some simpler experiments:

        Machine 1                       Machine 2
        cu -l cuaa0                     cu -l cuaa1
        type                            characters echoed
        characters echoed               type

So the cable is OK.  The connection _can_ work.

        Machine 1                       Machine 2
        cat < /dev/ttyd0                cu -l cuaa1
        lines echoed                    type then Enter key

So the line-discipline is different, but there is no problem using the
ttyd0 device on machine1.

        Machine 1                       Machine 2
        cu -l cuaa0                     cat < /dev/ttyd1
        type (no echo on terminal)      NO ECHO

This does not work.

It appears that the tty device on machine 2 is my problem.  Any ideas how
I can make it work?

There are no permissions problems, the devices on both machines have been
re-built (so they are not stale device files).

Please reply directly (and thank you if you've read this far!) since I'm not
on the questions list.

John


-- 
        Unreal City,
     Under the brown fog of a winter dawn,

finger [EMAIL PROTECTED] for pgp public key


Reply via email to