On Tue, Mar 16, 2010 at 10:23:38AM +0100, Miklos Szeredi wrote: > > I would strongly suggest to drop this hack, it's really no problem for > > the user to add -o loop for loop mounts. Especially as we might replace > > the current loop driver with a more flexible one with a different name > > in the future, so mount hardcoding loop is not a good thing. > > That argument is bogus, the kernel will need to provide the old loop > API anyway. We'd probably keep the old loop driver forever, but might switch to using dm-loop or similar for preference. Hardcoding this as assumption inside mount might not be a good idea. Then again mount -o loop already does that anyway. -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
