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.