Re: What I should do for official ruby backport?

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

Johan Deneux wrote:

>I indeed backport the force-feedback related drivers to 2.4. The reason
>for this are:
>1. I use 2.4 (2.5+ide used to be a bad combination)
>2. Users are mainly gamers. Gamers use NVidia cards. NVidida drivers are
>for 2.4. -> users probably want 2.4.

Me to is gamer. I use 3 Nvidia cards in my local system. This one
allow me emulate net gaming in my home. Triple Quake3Arena and triple
UnrealTournament works for me fine. Game may be sametimes choppy, but my
users never complain.
IMHO any bugget restricted gamer dream.

>> I will heard veteran hints. I hope You don't recommend stop it.
>
>I am not sure what your patch exactly does.

backstreet-ruby split /dev/tty's into separate range, same in ruby CVS.
8 /dev/tty's per keyboard/console pair.User can choose keyboard for
X server with X server paramether vtXX. And run several X
simultaneos with independ keyboard,mouse,monitor.

>But if it's a full ruby
>back-port, I am not sure it is really worth the pain (IMHO).

No full. Framebuffer devices removed. No real text based
multiheaded console. Only multiple X supported. X server
do not need console, but only tty drivers. I emulate additional
console for 2nd, 3rd X with dummy console.

>As far as I
>know, ruby is not going to make it into 2.4. It must be quite hard and
>time-comsuming to track the console+input thing, isn't it ?

IMHO vt-handling is complete in ruby CVS. Seems James mean similar,
because no vt.c real changes since DEC-2001.

>Are there many users out there *needing* ruby in 2.4 ? If it's only for
>testing purposes, I guess they can use 2.5.

Current 3-6 patchers, any has 2-3 X terminal (end-users unknow count).
My system use 6 peoples(gamers).
I will popularize this , but current version is buggy.
Rather I flunk.

Thanks
Aivils Stoss