On Fri, 20 Jan 2006 09:36:35 -0700
Michael Loftis <[email protected]> wrote:
> Yes I realise this change isn't out of the blue or anything, but it's in a
> 'stable' kernel. Why bother calling 2.6 stable? We may as well have
> stayed at 2.5 if this sort of thing is going to continue to be pulled.
>
Most of your message seems to boil down to complaining that devfs has been removed.
Unfortunately your frustration is pointed in the wrong direction; you should be
asking yourself why you ignored all those warnings about devfs removal for so long.
If you really need it, just use the 2.4 kernel; it's very stable.
If you want to complain about the current tree being called "stable", then just
don't call it stable. Call it the development tree because in the end that's what
it is. No need to get hung up on a name; it is what it is. Anyone, is free to fork
a real stable tree just like some distributions do. But such "stable" trees just
aren't going to be maintained by the same people who develop the mainline; they have
enough to do already.
If you can think of an idea to solve your problem without demanding that other people
(ie. the mainline developers) do extra work, then speak up. But just demanding that
the developers patch a stable tree while working on the development branch as well,
has other _real_ costs that precipitated the shift to the current model.
Sean
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
