"Jrgen_P._Tjern": > >> mount: wrong fs type, bad option, bad superblock on none, > >> missing codepage or helper program, or other error > >> (for several filesystems (e.g. nfs, cifs) you might > >> need a /sbin/mount.<type> helper program) > >> In some cases useful info is found in syslog - try > >> dmesg | tail or so > > = > > > Is CONFIG_AUFS_HINOTIFY enabled?
> I guess not, if I removed udba=3Dinotify it worked. The error messages = > > were not dechiperable at _ALL_, I think this is something that should be = > > changed? How is a user supposed to figure out that this is the issue = > > with prebuilt packages? :( Maybe you are right. But it might be a nature of mount(2) systemcall. When the systemcall meets an illegal option, it just returns an error with EINVAL error code. It should be mount(8) command that prints the error message. But there is no way for the systemcall to tell userspace which option is wrong. I guess every filesystem returns EINVAL simply in this situation and mount(8) prints "mount: wrong fs type, bad option, ..." Junjiro Okajima ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
