On Tue, May 20 2014, Krzysztof Opasiak wrote: > I found out that kernel returns -ENODEV error which when file system > type has not been found. I look into code of ffs and found out that > ffs_fs_mount() also returns this error if it was unable to acquire given > device. I know that this error looks really suitable in this place but > it really hurts discoverability in userspace because you don't know > where did you make your typo in file system name or in dev name. I have > run through few other fs implementations and found out that they all > return -ENOENT if given device has not been found. > > Maybe FFS should follow this convention Probably, patches welcome. :) -- Best regards, _ _ .o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o ..o | Computer Science, Michał “mina86” Nazarewicz (o o) ooo +--<mpn@xxxxxxxxxx>--<xmpp:mina86@xxxxxxxxxx>--ooO--(_)--Ooo--
Attachment:
signature.asc
Description: PGP signature