On Fri, Jul 01, 2011 at 04:04:28PM -0400, Steve Dickson wrote: > On 06/30/2011 01:40 PM, J. Bruce Fields wrote: > > Dumb question, as I haven't been following the libmount stuff, but: how > > soon before we can throw out the non-libmount code? > The switch has been throw in Fedora Rawhide/Fedora 16. > > > > > Looks like patching and maintaining both is a pain. > Likes like?? Boy, you have 20/20 8-) > > > > > Could we get away with saying "if you want a non-libmount-based mount, > > feel free to go checkout 1.2.4 or earlier, and backport security fixes > > to it yourself if you want", and just rip it out now? > Well we would not rip it out the code, we would just change the default to > always use the libmount code and have a --disable-libmount config flag > for people that don't have the libmount code.... I'm thinking that > patch would fairly trivial... Yeah, understood, that's why I was asking when we could actually rip out all the code. As long as it's still there, people may be tempted to use it, which means you're stuck maintaining it. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
