linuxconsole-dev

What I should do for official ruby backport?

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

Hi, folks

Motivation:
1. James Simons will not keep clear code in ruby CVS.
2. Nobody use Linux in my home , if can't start triple Freeciv,
Quake3Arena, and so on.

     Sametimes I can find small bugs in one-two month time period. It's
good enough
for me, but my be abnormality in public area.

     Johan alwways made backport. So next time I wait for it, then release
my
package.

I will heard veteran hints. I hope You don't recommend stop it.

Thanks
Aivils Stoss

Re: What I should do for official ruby backport?

[Johann D. <joh...@it...>]

Aivils Stoss wrote:
> Hi, folks
> 
> Motivation:
> 1. James Simons will not keep clear code in ruby CVS.
> 2. Nobody use Linux in my home , if can't start triple Freeciv,
> Quake3Arena, and so on.
> 
>      Sametimes I can find small bugs in one-two month time period. It's
> good enough
> for me, but my be abnormality in public area.
> 
>      Johan alwways made backport. So next time I wait for it, then release
> my
> package.
> 

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.

Now, this is not a complete backport of ruby at all. It only included 
small pieces of the input layer, plus the iforce and hid drivers.

I was planning to wait until Brad's patches would be included into 
2.4.20-preX to send iforce to Alan Cox (and later hid).

> I will heard veteran hints. I hope You don't recommend stop it.

I am not sure what your patch exactly does. But if it's a full ruby 
back-port, I am not sure it is really worth the pain (IMHO). 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 ?
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.

-- 
Johann Deneux

Re: What I should do for official ruby backport?

[James S. <jsi...@in...>]

> I am not sure what your patch exactly does. But if it's a full ruby
> back-port, I am not sure it is really worth the pain (IMHO). 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 ?
> 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.

I agree. That is way I never worked on a 2.4 port. There are just to
many changes to severly subsystem layers to deal with.

Re: What I should do for official ruby backport?

[Andreas S. <an...@sc...>]

* Aivils Stoss (Aiv...@un...) [020916 11:35]:
> Motivation:
> 1. James Simons will not keep clear code in ruby CVS.

> 2. Nobody use Linux in my home , if can't start triple Freeciv,
> Quake3Arena, and so on.
I do not understand what you wanted to express with this. 

>      Sametimes I can find small bugs in one-two month time period. It's
> good enough
> for me, but my be abnormality in public area.

I have tried to get this to work for a few days now, and it seems
that there is lots of clean up to be done. 

what I notice is that the interoperation with the rest of the
kernel is suboptimal. eg: if one activates magic sysrequest keys
the serial subsytem brakes. 
Other general problems are in the area of corner cases: what
happens if you have more keyboards then vts? So the robustness in
general is not very high.

I would encourage you to work together with others (like me :-)
to improve both your documentation and patch quality. I volunteer
to go over your webpages and try to straighten out some issues in
grammar. I could also mirror the site on a box with better
connectivity or on a debian server.

I have run into several people who would be very interested in
your setup to work reliably, and once this is packaged and
it went into debian, i expect that the number of users to
mulitply.

> I will heard veteran hints. I hope You don't recommend stop it.

i certainly hope you keep up your work. i do not believe this
goes into mainline 2.4 at anytime, but i think this has the
potental to become an independent kernel patch, which provides
something many want in a stable kernel (like alsa for sound?).

Re: What I should do for official ruby backport?

[James S. <jsi...@in...>]

> * Aivils Stoss (Aiv...@un...) [020916 11:35]:
> > Motivation:
> > 1. James Simons will not keep clear code in ruby CVS.

> what I notice is that the interoperation with the rest of the
> kernel is suboptimal. eg: if one activates magic sysrequest keys
> the serial subsytem brakes.

Actually this has been fixed in the latest 2.5.X kernels. I haven't had
the time to back port the fixes into ruby. The plan was to push huge
amount of ruby into 2.5.X then update ruby since I woudn't have much to
do.

> Other general problems are in the area of corner cases: what
> happens if you have more keyboards then vts? So the robustness in
> general is not very high.

If you have more keyboards they are registered but not attached to any
VTs. Once you add a video card then it will attach the keyboard.

> I would encourage you to work together with others (like me :-)
> to improve both your documentation and patch quality. I volunteer
> to go over your webpages and try to straighten out some issues in
> grammar. I could also mirror the site on a box with better
> connectivity or on a debian server.
>
> I have run into several people who would be very interested in
> your setup to work reliably, and once this is packaged and
> it went into debian, i expect that the number of users to
> mulitply.

Really:-) Cool!!!

> i certainly hope you keep up your work. i do not believe this
> goes into mainline 2.4 at anytime, but i think this has the
> potental to become an independent kernel patch, which provides
> something many want in a stable kernel (like alsa for sound?).

True.