[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]

Re: Re: High-bit strip?

Aaron Burt aaron@osdlab.org
Fri, 23 Feb 2001 12:39:30 -0800 (PST)

On Fri, 23 Feb 2001, Bryan Stansell wrote:
> On Thu, Feb 22, 2001 at 01:45:16PM -0800, Aaron Burt wrote:
>> So, does Conserver strip bit 7?  My terminal server is set to pass
>> chars raw, but line-drawing chars come out as "MMMM" etc. on a Linux
>> console.
> Yep, by default it does.  You can change it by using the --enable-8bit
> configure option with 7.0.0 or editing conserver/cons.h in pre-7.0.0
> versions (option CPARITY - set to 0).  If that doesn't do it for you,
> let me know ("conserver -V" should tell you your current policy with
> recent versions).

Well, it still draws MMMM with TERM=linux but things look great with
TERM=vt220 or xterm.  I tried a stock 6.1.7 client connecting to a 8-bit
7.0.0 server, too.  Worked fine.

>> Also, is there any info on how keycodes are passed on?

To amplify, it'd be nice to understand the mechanism well enough to ensure
Fn keys and suchlike are sent properly, and perhaps even to remap <BREAK>
to something like, say, SysRQ (for Linux kernel hackers, y'see).
Also, no matter what the terminal-type is set to in the inittab for getty
on the machine being controlled, backspace and delete don't work when
logging in.  Though ^H does.  Arrow keys move the cursor but seem to
invisibly mess up the username/password.

And yes, I'm trynta look at the source, too.