Re: Stop the Linux kernel madness

[Andrew Morton]

4Front Technologies <dev@xxxxxxxxxxxxx> wrote:
>
> This is absolutely not our problem and we don't know who to contact at SuSE to fix
> this problem. Our software works perfectly with Fedora/Debian/Gentoo/Mandrake/Redhat/etc.

Are you referring to userspace applications which fail under Suse's kernel,
or are you referring to kernel code?

If the former then yes, this may well be a bug in the Suse kernel - please
provide the means to reproduce it.

If the latter (your drivers don't work in Suse's kernel) then this too
could be a bug in the Suse changes, or in your driver.  Again, more details
would be needed to diagnose it.


I expect your distress is a little misplaced - someone somewhere has a
silly little bug and once that's found and fixed, things will be OK.


As to your broader point - yes, I too am disturbed by *any* divergence from
a kernel.org kernel.  Because it means that there is some feature which the
mainstream kernel is missing, or some problem which remains unresolved. 
Especially if there are variations in user-visible features - that would be
very bad for everyone.

Either way, each unmerged patch is a little failing which costs the users
of the patched kernel as well as the users of the unpatched kernels.

I don't have a lot of substantiation for this, but I think the reason why
suse are sitting on 1500 patches is a combination of:

a) They're on 2.6.5 and have included a lot of patches which are already in
   2.6.6 and 2.6.7

b) They shipped the kitchen sink with 2.4 and their customers still want
   to wash the dishes in 2.6.

c) Maybe they haven't been terribly stern about throwing things away.


I would like to see a little more all-round effort to reduce the variation
between kernels, and perhaps Suse moved onto 2.6 a little later than they
should and have a resourcing problem.  Hopefully we'll be seeing more
patches from them soon.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/