Re: hijacled q

[Aivils S. <ai...@un...>]

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.

Aivils