Subject: Re: tty0?
To: Ken Hornstein <firstname.lastname@example.org>
From: NetBSD <email@example.com.UnB.br>
Date: 06/21/1996 15:19:38
Thanks for the replies, but that is exactly the point. We have some BSDi
boxes hanging around and setting the clocal flag on a port
keeps it set until you unset it, even after the port is closed, that is,
the state of the control flags is kept and not reset after every close.
Isn't that how things should be set up? What's the point of using stty on
a device other the the controlling terminal if as soon as the command is
finished everything comes back to its defaults?
Is this the reason of the ttyflags command? If it is, how does it
permanently changes the state of a serial port? It probably opens and
closes the port to issue the ioctl commands, right? Wouldn't that last
close reset things back to normal.
How does one redirect the output of some commands to the serial port? The
shell doesn't know anything about it (I presume) and blocks when trying
to open the device.
Could someone please comment on this?
On Fri, 21 Jun 1996, Ken Hornstein wrote:
> >I can't seem to make my serial ports work. If I do an 'stty -f /dev/tty00
> >clocal' and then a 'stty -f /dev/tty00' the clocal flag is not set.
> The serial ports reset their state upon each close.
> >If I launch an getty on the port, the stty command above works. As soon
> >as I kill the getty process, stty doesn't work again.
> That's why this happens.
> >Tip doesn't work either. Ttyflags, on the other hand does work.
> >I'm running the i386 port.
> I've found that I have better luck with "cu", but you might need something
> like this in /etc/uucp/port
> port tty01
> type modem
> device /dev/tty01
> speed 57600
> port tty02
> type direct
> device /dev/tty02
> speed 9600
> One of those should work fine.
> Either that, or adding the ttyflags for "local" or "softcar".