Re: New Linux Development Model

[Bernd Petrovitsch]

On Sat, 2005-11-05 at 14:19 +0100, Edgar Hucek wrote:
[...]
> Maybe you don't understand what i wanted to say or it's my bad english.
> The ipw2200 driver was only an example. I had also problems with, vmware,
> unionfs...
> What i mean ist, that kernel developers make incompatible changes to the 
> header

ACK. The reason is the improve the kernel and drivers.

> files, change structures, interfaces and so on. Which makes the kernel 
> releases incompatible.

ACK. It needs (a lot of) work to keep backwards compatibility and who
wants can do it (probably).
At what to do at the point where you actually have to break it?

> There are several reasons why modules are not in the mainline kernel and 
> will never
> get there. So saying, bring modules to the kernel is wrong.

The last conclusion doesn't hold. Especially not in this general form.
You have to list the "various reaons" and then we can discuss each of
them.

> The right way would be to take care of defined interfaces, header files, 
> and so on.

The only defined interface of the kernel can be found in POSIX, SUSv3
and similar documents.

> Otherwise you could only say the kernel 2.6.14 is only compatible to 
> 2.6.14.X and
> you there is no stable 2.6 mainline kernel.

Compatible in what way? Source? Object? User-space binary interface?

> I think it's also no task for the user, to search the net why external 

Then don't do it.

> driver xyz not
> works with a new kernel ( because of incompatibilties ). Basicly in new 
> kernel there

Who is interested in the new driver/kernel/..?
The user. So guess who's job is to do it (or find someone to do it -
paid or unpaid).

> could be a chance for the user a driver works better, because a bug was 
> fixed in the kernel.
> Hopefully this time it's more clear why i blame the development process 
> and i'm a so frustrated linux user.

Who do you mean with "user"? 
A typical "user" just installs $DISTRIBUTION (be it a free or commercial
one) and that's it. *If* the bug is severe enough (and the relevant
maintainers does it) there will be a new rpm/deb/... with the newest
kernel release or a backport.
If not, you can do it on your own anyways.
But then you are half a programmer and more like a sys-admin and no
longer a "user". Voila.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services



-
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/