I recently (re) installed NetBSD 1.0 from scratch, and discovered what I 
consider to be an annoying "feature":  since there is no separate device
for COM ports, you must use tty00.   But tty00, by default, blocks when
you try to use "cu" on it.

Now, I know all -real- men have Ethernet direct to their house, but some
of us out here use SLIP or PPP, and I think it's totally reasonable for
someone to say "Well, I'll just get the install floppie and base10 and FTP
everything else."  But the way things are set up now, that is very
difficult.

The eventual solution I used was to go to DOS, enter my terminal program,
assert carrier with AT&C0 and then re-enter BSD and FTP kermit, which
works just fine.

Before I did that, however, I tried to change the characteristics of the
serial port by doing:

stty clocal </dev/tty00

Nothing.  The machine hangs forever.

Read the man page.  Ok, how about:

stty -f /dev/tty00 clocal

True to the man page's promise, it doesn't block.  But it doesn't work,
either.

What am I missing here?  How does one fix this problem in a suitably
guru-like fashion?

As a data point, stty clocal < /dev/tty00 worked just fine under BSDI.

-- 
......................................................................
  Peter G. Berger, Esq.  Telerama Public Access Internet, Pittsburgh
Internet: peterb@telerama.lm.com Phone: 412/481-3505 Fax: 412/481-8568
	   	 	http://www.lm.com/~peterb