Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!ames!lll-winken!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: Why is stty behaving differantly with Ultrix 3.0 ?
Message-ID: <6432@cbmvax.UUCP>
Date: 29 Mar 89 07:31:05 GMT
References: <20471@prls.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Distribution: usa
Organization: Commodore Technology, West Chester, PA
Lines: 27

In article <20471@prls.UUCP> gordon@prls.UUCP (Gordon Vickers) writes:
> 
>      Does anyone know why stty(1) may be behaving differantly in Ultrix 3.0 ?
>    I normally use something like:
>      stty 9600 >/dev/tty07
>    to change selected parameters on a given port and this method has always
>    worked until I installed Ultrix 3.0  .
>       Changing port parameters now, seems to work only on login ports.
>       I've retreived stty from Ultrix 2.0 but it seems ineffectual as well.

The general notion is the stty parameters only stick as long as something
has the file open.  When it is closed, the parameters will be set back
to the default.  Could it be that when you re-installed Ultrix that the
port you were accustomed to doing this on no longer has something floating
about that was holding it open in your old setup?  Either a login or the
task that you were setting the parameters for?

On the other hand, perhaps DEC has broken something...

you can always try (stty xxxx; sleep 99999) > /dev/ttyx



-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)