From owner-freebsd-hackers  Thu May 23 00:50:15 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id AAA04972
          for hackers-outgoing; Thu, 23 May 1996 00:50:15 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA04965
          for <freebsd-hackers@FreeBSD.org>; Thu, 23 May 1996 00:50:12 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id RAA05274; Thu, 23 May 1996 17:47:40 +1000
Date: Thu, 23 May 1996 17:47:40 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199605230747.RAA05274@godzilla.zeta.org.au>
To: garya@ics.com, jkh@time.cdrom.com, sef@kithrup.com
Subject: Re: stty -- not
Cc: freebsd-hackers@FreeBSD.org
Sender: owner-hackers@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>I did manage to get a <cr> inserted, but only by manually configuring
>the printer using:

>	stty -f /dev/ttyid1 opost onlcr
>	stty -f /dev/ttyld1 opost onlcr

>Attempting to manually configure the device using the locked device
>alone, or the initialization device alone, did not work.

>One can specifically set the initialization and locked state using stty.  
>Does using the - version of a flag lock them off, or simply return them
>to their default, unlocked, condition?

Using the - version on the lock state device returns the lock bits to
their default, zero (no-lock), condition.

You needed to lock the state because lpd always changes it to the wrong
value.  Then you needed to set the initial state because the default is
wrong too.

Bruce