I think I have found an oddness that I had not seen before either in
the system or in the mailing list...

When I fire up kermit, the systems waits for something to happen right
before it connects to the /dev/tty02 port.  The sure fire way to make
it connect is to ^Z and then 'fg' the job.  When the 'fg' restarts the
process, the port is connected and the SLIP connection script (user-id
stuff notwithstanding) to establish my SLIP connection runs.

I have tried several other signals (^C for example) and they all have
the same effect.  Whatever event kermit seems to be waiting for is
suddenly satisfied and the program jaunts of merrily connecting my to
the outside world.  

I find it just the least bit spooky.

I am running a kernel with -current from about the 15th (although my
sources are actaully up to about the minute).  Here is the compile info
banner:

NetBSD 1.0-ALPHA (CYNJUT.TEST) #3: Mon Jul 18 23:25:37 PDT 1994
    root@:/usr/src/sys/arch/i386/compile/CYNJUT.TEST
CPU: i386DX (386-class CPU)

The kermit is from the last time that kermit was in 'othersrc'.  BTW, I
haven't looked real hard, but I thought I saw kermit getting deleted
and not replaced in the sup mail I got....

------------------------------------------------------------------------------