minicom [non-] bug and linux kernel 2.6.25.4

[Adam Lackorzynski]

On Fri Jun 20, 2008 at 02:29:16 -0500, R.L. Horn wrote:
> On Wed, 18 Jun 2008, Adam Lackorzynski wrote:
>
>> Now, what to do about minicom itself? Just leave it as is and tell
>> people to use .25.8 (if it will be in there) or apply a fix? What do you
>> think?
>
> Well, there are already eight buggy (stable) versions of the kernel, at 
> least one of which has found its way into a distribution.  In light of the 
> fact that there's been no major outcry over this, I think the bug's 
> probably going to have to be accommodated for awhile, if only as a courtesy 
> to the relatively small legacy hardware/minicom "community."
>
> Perhaps more importantly, as always, the sooner you release an updated 
> version, the less likely it is that your work will be mangled by 
> distributors (somehow, I suspect that that's one of the reasons linux 
> releases are so darn rushed).
>
> I favor checking that the kernel is behaving as it should, and logging a 
> warning if not (while putting things right).  Something like the enclosed 
> patch.
>
> If you release, say, a 2.3.1 now, it will probably have blown over by the 
> time there's a 2.4 or 2.5 (you know, when gcc 5 refuses to compile the 
> older version :-)), and the check can be removed.

Well, I don't really like adding such code if not really needed. I'm
also trying to remove all those old code for now old systems that
probably nobody has used in ages. And now that 2.6.25.8 has the fix
we'll hope for the best. If there are major complaints I might
rethink...



Adam
-- 
Adam                 adam at os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/