Hi,
On Wed, 11 Jun 2003 11:59:04 +0200, I wrote:
> > > mount: wrong fs type, bad option, bad superblock on
> > > //some.machine/mountpoint,
> > > or too many mounted file systems
> > >
> > > Whereas the real error was revealed only by strace:
> > >
> > > stat64("/sbin/mount.smbfs", 0xbffff5ac) = -1 ENOENT (No such file or
> > > directory)
> > >
> > > Surely it doesn't _have_ to obfuscate the error like that? :P
> > >
> > > Note that it did recognize smbfs as a valid file system type because the
> > > kernel supports it. If it can do that, it could also tell me clearly that
> > > I don't have the userland program for it.
> > >
> > > Please fix this. TIA.
On Sun, Dec 19, 2004 at 08:46:06PM +0100, Thomas Hood wrote:
> > #197004: cretinous error reporting when /sbin/mount.$fstype isn't found
On Sun, 19 Dec 2004 22:13:58 +0100 Andries Brouwer wrote:
> Clueless submitter
I'm sorry? How exactly am I clueless? You think it's normal for
mount to ignore the fact that mount.$fstype is ENOENT when mount()
returned EINVAL?
Or do I live in some sort of a parallel universe, where useful error
and warning messages are only for the clueless?
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
