On 9/14/07, Trash Compactor  wrote:

quoted text
> Greg Thomas wrote:

> > On 9/14/07, Craig Skinner  wrote:

> >

> >> Darren Spruell wrote:

> >>

> >>> For the scenario where you have two openbsd hosts, one connected to

> >>> the second with a serial null modem cable, what is the right device to

> >>> use when connecting using tip(1) from the first to a console on the

> >>> second?

> >>>

> >> This works very well for me on i386;

> >>

> >> 2 null modem serial cables, cross connected thusly:

> >>

> >> box-a pccom0 connected to box-b pccom1

> >> box-b pccom0 connected to box-a pccom1

> >>

> >> This on both:

> >>

> >> $ cat /etc/boot.conf

> >> stty com0 9600

> >> set tty com0

> >>

> >> And this too on both boxes:

> >>

> >> $ rcsdiff -r1.1 /etc/remote

> >> ===================================================================

> >> RCS file: /etc/RCS/remote,v

> >> retrieving revision 1.1

> >> diff -r1.1 /etc/remote

> >> 67a68,70

> >>  > tty01|For hp300,i386,mac68k,macppc,mvmeppc,vax:\

> >>  >       :dv=/dev/tty01:tc=direct:tc=unixhost:

> >>  >

> >>

> >> Then, on either box, I can do this to get to the console on its neighbour:

> >>

> >> $ sudo tip tty01

> >>

> >

> > Is this just for boot messages?  It's my understanding (minimal, at

> > that) that you can't do this for logins both directions because getty

> > will tie up the port?

> >

> > Greg

> >

> But he has hostA:tty01 connected to hostB:tty00 and hostB:tty01

> connected to hostA:tty00.

> Each system has two com ports, one for console and one for connecting to

> the the system's console.

>

Ah, bueno, thanks for pointing that out.  I missed the 1s.
Greg

--

Ticketmaster and Ticketweb suck, but everyone knows that:

http://ticketmastersucks.org
Dethink to survive - Mclusky