Date: Sun, 29 Jan 2012 23:24:16 +0100 From: Uffe Jakobsen <uffe@uffe.org> To: freebsd-fs@freebsd.org Subject: Re: kern/164516: [ext2fs] unable to mount EXT2 filesystem Message-ID: <4F25C710.6000806@uffe.org> In-Reply-To: <20120129042647.GJ2726@deviant.kiev.zoral.com.ua> References: <201201272310.q0RNABvZ065758@freefall.freebsd.org> <20120128004755.GA89980@icarus.home.lan> <4F246CA9.30803@uffe.org> <CADLo83_jMpKK60gu%2BVyejTudGicyHiqbGnP5JBpZ8d20pjndsg@mail.gmail.com> <4F248B44.1090304@uffe.org> <20120129042647.GJ2726@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2012-01-29 05:26, Kostik Belousov wrote: > On Sun, Jan 29, 2012 at 12:56:52AM +0100, Uffe Jakobsen wrote: >>> Question is if there exists a scenario >>> where the requested filesystem type would/could not be found by >>> getvfsbyname() ? >>>> >> Anyway - would you accept a patch that checked the fstype using >> getvfsbyname() before calling nmount() ? > > Kernel tries to load the named module if it is not registered in the > list of know VFSes. Your proposal would break this functionality. Thanks that was exactly the info I asked for - I had a feeling that there was some sort of catch. I was not aware of that functionality in nmount - it is not mentioned in the manpage and I admit that i did not look deep into its source. Well that settles the question - it is a no go - thx for your answer. /Uffe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F25C710.6000806>