On Wed, 2007-04-04 at 13:29 -0700, Andrew Morton wrote: > On Wed, 04 Apr 2007 14:17:13 -0400 > Dave Dillow <[EMAIL PROTECTED]> wrote: > > The thing is, it's been broken for a long time -- this change just > > highlighted it. This isn't the first time that device-mapper has moved > > -- the introduction of mdp (before git, so haven't tracked down > > timeframe) also moved it around. The dynamic major is not stable, so > > should we be concerned if it moves for 2.6.21? > > > > I don't like the effect it has on the backups, but I don't think we > > should hand out LOCAL/EXP majors to dynamic devices, either. There is a > > module option to make the device-mapper and mdp majors stable, so > > perhaps a compromise is possible? Revert for 2.6.21, and schedule the > > patch for later addition, which gives distros time to use the DM major > > option? > > hm, good points. > > Overall, the patch helps kernel developers and hurts the userbase. I tend > to prefer to hurt kernel developers than our users ;) > > I don't think the protect-lanana-numbers thing is very important, really. > If some kernel developer or someone who is maintaining an unofficial > out-of-tree driver hits the problem, they are presumably able to handle > it. Preferably by switching to a dynamically-assigned major.
Works for me; I don't really have a dog in the fight. - 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/
