Re: hijacled q

[Hugo V. <hvw...@ya...>]

--- Aivils Stoss <ai...@un...> wrote:

> On Piektdiena, 9. Septembris 2005 13:23, you wrote:
> > Hi,
> >
> > I have an app that writes procfs status to
> keyboard
> > leds. Like:
> >
> > ...
> > ioctl ( ttys[i].fd, KDSETLED, savedleds|led );
> > ...
> >
> > WITH hijacled it does not work.
> >
> > WITHOUT hijacled it does work. And capslock
> numlock
> > and scrolllock still work on both keyboards.
> 
> But hijacled was intentionally created for that.
> hijacled isolate keyboards LED's from old /dev/ttyXX
> ioctl's. If Your 1st X/console don't use faketty,
> then code above works fine.
> 
> Normal kernel: You plug in 12 keyboards and press
> CapsLock on 1st - remaider 11 keyboards switch LED's
> as 1st one. You press key on twelfth and it goes to
> console.
> 
> hijacled: You plug in 12 keyboards and start single
> X
> on /dev/fttyXX as secondary head. Now You press
> CapsLock on 1st - remaider 10 keyboards switch LED's
> as 1st one, but twelfth was opened by X via faketty
> does not respond to 1st keyboard keypress. That
> twelfth
> is grabed by faketty. You press key on twelfth and
> it
> goes to X instead console. While /dev/fttyXX is not
> opened every keyboard is ordinary. Just close all
> /dev/fttyXX and check out Your code.
> 

So in writing "info" to the leds I override what the
users do anyway.

Writing to the leds "works" (in this case network
activity NumLock=RX and ScrollLock=TX) when the
keyboard patch is NOT added and hijacled is NOT
active.

At this point for my setup I have everything Ruby did
"positively" (not its foibles) minus the bell for the
secondary keyboards!

Hugo






	
		
______________________________________________________ 
Yahoo! for Good 
Watch the Hurricane Katrina Shelter From The Storm concert 
http://advision.webevents.yahoo.com/shelter