Subject: stty flags in printcap (was: Re: defaults for tty open)
To: Ken Hornstein <firstname.lastname@example.org>
From: Scott Bartram <email@example.com>
Date: 02/02/1996 13:29:26
> >> You fix the program. In the case of lpd, in particular, this is quite
> >> trivial.
> >I haven't hacked on lpd, so I'm at the base of the learning curve.
> >How do I fix it?
> >I think the real fix would be to add a new entry to printcap. If this
> >field's present, stty gets forked on the output port & sent the flags in
> >this element. Some form of unix (Linux?) does this; Ghostscript's
> >default printcap entry contains such a field. So instead of cryptic
> >bit settings which require perusal of header files, we say something
> >like "57600 raw crtscts clocal".
> You mean, like the SunOS printcap entry that lets you specify stty-like
> settings (but doesn't actually _invoke_ stty)? You know, there are patches
> laying around on the net for BSD lpr that _do_ this. I wish I knew where
> I saw them.
The changes to support stty(1) flags in printcap(5) were added when lpr
was modified to use termios (pre-1.1). It's the "ms" flag. Unfortunately,
I just noticed that the man page was not updated to reflect this (though I
did submit a patch for it).