Paul Goyette wrote:
> 
> Well, _I_ don't like calling these things the "printer" port or the
> "modem" port.  Why can't we be consistent and call them tty00 and tty01?
> And then we could rather easily pass an optional parameter to a generic
> script to select the port to use.

I don't like calling them that either.  However, I think that the ppp kits
were meant to make it easier to set up PPP for the average NetBSD/mac68k
user.  Does the average use know offhand which port is tty00 and which is
tty01?  I don't think that this is documented in the INSTALL document
anywhere, and that's about all I can hope that someone has read before
they decide to go setup PPP.  So, although I don't like the name
ppp-printer, etc. for the scripts, it might be nice to be able to pass
that (or the tty name) to a script to select which one you want.

> But then, we're going to get pretty complicated/messy, since we'll need to
> worry about whether there's a file called /etc/ppp/options.tty00 or
> /etc/ppp/options.tty01 out there.  We'd need to look for these in
> deference to the default /etc/ppp/options if we're going to set up the
> ppp-debug script to be able to turn on debugging for the proper port.

Have both and let the startup script pick which one it needs to choose
based on a default or on a command line option.

> And of course, how can we be sure whether tty00 is associated with ppp0
> when we try to shut things down?  IIRC, the ppp0 or ppp1 will get chosen
> based on the first unit number that's available, even if we run pppd on
> tty01 first - it would get associated with ppp0.
> 
> Things do get messy...

Yes, they do... ;-)

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.