You should have in your /etc/ttys file, something that looks like this:

console "/usr/libexec/getty Pc"         pc3     off secure
ttyv0   "/usr/libexec/getty Pc"         pc3      on secure
tty00   "/usr/libexec/getty std.9600"   unknown off secure
tty01   "/usr/libexec/getty std.38400"  vt100    on secure
tty02   "/usr/libexec/getty std.9600"   unknown off secure
tty03   "/usr/libexec/getty std.9600"   unknown off secure
tty04   "/usr/libexec/getty std.9600"   unknown off secure
tty05   "/usr/libexec/getty std.9600"   unknown off secure
tty06   "/usr/libexec/getty std.9600"   unknown off secure
tty07   "/usr/libexec/getty std.9600"   unknown off secure

in this example, tty01 (com2) has been set to be a DCE port at
38400 anticipating be connected to by a vt100 terminal.  Just reboot
after changing /etc/tty01 and it should work.  Best way to verify is
to connect a terminal or PC running a terminal emulation package to
the BSD box via a null modem supporting CD (carrier detect), without
CD NetBSD wont respond.  Set the terminal to 38400 E-7-1 (even parity,
7 bits, 1 stop bit) and it should work.  If your modem is failing, you
John Maier special BSD modem hack that was posted about two days ago
(notice I didn't say fix, I'm working on it ;-).  Some don't like it,
but if you're just after results it will do...
(e-mail me if you didn't get in on it and want a copy)

And no, after you set up the port via /etc/ttys, cu -l /dev/tty01 will
fail until you turn getty off in /etc/ttys and reboot (at least I
don't know how to do it).

jam

**********************************************************************
*       John A. Maier          * Research Assistant For Datastorm    *
* E-mail: johnam@datastorm.com * Technologies Inc. (Procomm Plus)    *
*                              * (314) 443-3283                      *
**********************************************************************