Re: A users thoughts on the new dev. model

[Adrian Bunk]

On Fri, Jul 23, 2004 at 04:04:32PM -0700, hpa@xxxxxxxxx wrote:
> >
> > One problem from a user's point of view is that removal of obsolete code
> > that works sufficiently for some users.
> >
> > Andrew said explicitely in a mail to linux-kernel that he'd consider
> > removing devfs "mid-2005" - and it didn't sound as if this would only be
> > a -mm "feature".
> >
> > Even if 2.7 is started this doesn't has to imply that it has to be
> > flooded with big changes - a short 2.7 with relativley few invasive
> > changes might also be an option.
> >
> 
> There is no difference from a user's point of view between a "short 2.7"
> and "a close -mm tree."  Either way devfs is on death row, because it's

You missed one important difference:

With a "short 2.7", 2.6 stays unchanged. This way, users have a 2.6 tree 
which will continue to stay unchanged regarding such user-visible 
changes but still gets lots of fixes for several years.

For many users I know it's an important difference whether upgrading 
from 2.6.X to 2.6.Y (with Y > X) has a low risk of breaking anything 
working with 2.6.X or not.

Many people complained after USB_SCANNER was removed in 2.6.3, and the 
only excuse (besides that it had several bugs and was for most users  
inferior to SANE) is that this was very early in the 2.6 series.

> buggy and unmaintained.  Any piece of code, *especially* one as invasive
> as devfs, which is buggy and unmaintained is a hassle to for *all* kernel
> development, and have to be extricated at some point.

I don't disagree with this statement. But IMHO "some point" shouldn't 
be in 2.6 .

> 	-hpa

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

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