On Mon, 2013-12-23 at 22:34 -0500, Phillip Susi wrote: > I thought that these days module autoprobe was pretty much taken care > of and that in the case of filesystems, an attempt to mount a > filesystem for which a module had not yet been loaded would result in > the kernel forking a modprobe on fs-xxx, which would use the module > aliases to match up an appropriate module and load it. So why is it > that when I try to mount an ext2 filesystem mount complains that > there's no such filesystem until I modprobe ext2? If you're expecting mount /dev/sda1 /mnt to insert all the available filesystem modules and discover that /dev/sda1 is ext2, this is a case of mismatched user expectations (because we won't). If mount -t ext2 /dev/sda1 /mnt isn't autoprobing, that's either a bug or a distribution problem. James -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
