On 31/01/2019 22.52, Jeff Mahoney wrote:
On 1/31/19 4:05 PM, Carlos E. R. wrote:
On 31/01/2019 21.50, Jim Henderson wrote:
...
Ideally, the mount command would print information, or where to read more.
The mount command doesn't have that context. It calls mount(2) and the kernel requests that userspace load the module. Then mount(2) returns -ENODEV, which is documented in the mount(2) man page as "file system type not configured in the kernel." If the module isn't loaded, the module doesn't register as a file system type, and then there's no difference between "mount -t sadlksjadlk" and "mount -t jfs".
mount(8) can't attempt to load the module itself since it may not have privileges to do that even if it weren't blacklisted.
Understood.
We can definitely document the blacklisting case in the mount(8) man page, though. It's probably possible to link with libkmod and check if the module was blacklisted, too.
That would be nice, thanks :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)