Svetoslav Slavtchev wrote:
>> FEATURE
>> Alt-Fx uses James Simons's special layout, don't wonder.
>
> and that means ?
> what special layout ?
I check out it. This is big, deep trouble.
linus-tree kernel uses two TTY drivers. 1st for /dev/tty0
and 2nd /dev/tty1-63. So VC console count for VT begins from 1.
Linux-ruby uses one TTY diver for /dev/tty0-63. This is practical solution,
because it is pretty stable. Stability as well not guaranted correct work
of
code. Under linux-ruby /dev/tty0 is just another TTY from VT0 pool. Since
James remove tty0 handling from tty_open(), I understand James has no plans
for tty0. I has no plans to, because don't understand how works TTY driver.
In curreent ruby state tty0 works almost correct for VT0.
If process spawned from VT1 tty pool, then process can get wrong data
about VT1, if that use /dev/tty0 (VT_GETSTATE,VT_OPENQRY).
Why trouble is so deep?
IMHO we cannot serve multiple opens of /dev/tty0 correct, if processes,
which uses /dev/tty0, are spawned from different VT.
Seems making /dev/tty0 as current for all VTs is not so easy.
Alt-Fx is shifted because under linux-ruby console count begins from 0.
This one is easy fixable for VT0.
Aivils
|
