[EMAIL PROTECTED] wrote:\ > 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, ..." Yes, but often dmesg has information about the error details - could perhaps printk (or what it's called?) be used in aufs to show information about what error occured? :)
Kindest regards, Jørgen P. Tjernø. ------------------------------------------------------------------------- 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/
