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?).