Date: Wed, 22 May 1996 22:45:55 -0600 From: Gary Aitken <garya@ics.com> To: Sean Eric Fagan <sef@kithrup.com> Cc: freebsd-hackers@freebsd.org Subject: Re: stty -- not Message-ID: <31A3ED83.730@ics.com> References: <199605230335.UAA13414@kithrup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Looking at the source, decimal and octal numbers are allowed. Hex numbers > are apparantly not allowed. > > I have not looked at the handbook, so I don't know what it would have. #ifdef ASIDE Given that the handbook shows use of hex numbers, is there a chance that historical usage allowed hex numbers, and any mods should continue to allow hex numbers? Or was the handbook just plain wrong? #endif /* ASIDE */ > >How the heck *do* you turn those bits on, and what are the right > >ones? > > I have NO IDEA. I believe you :-) Can you tell me this: do you know if setting -opost and -onlcr on the init and/or lock devices will prevent their having any effect when specified in the printcap file? In particular, will the sequence: stty -f /dev/ttyld1 opost onlcr stty -f /dev/ttyld1 -opost -onlcr which *looks* like a noop (to illiterates like me), in fact still allow printcap to override the opost and onlcr values when lpd attempts to configure the device? If not, is the only way to get back to "normal" to reboot? -- Gary Aitken garya@ics.com (business) garya@dreamchaser.org (personal)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?31A3ED83.730>