On Sun, Jan 22, 2006 at 02:35:42PM +0100, Andries Brouwer wrote:
> > And besides, how hard is it to cache a warning message about non-existent
> > mount.$fstype and display it a few lines below if the EINVAL happens?
>
> You see, it would not be an improvement at all.
> Someone tries to mount a CDROM and gets "mount.iso9660 not found".
> She will be very confused. Do I need that?
> Such an error message will point people to something that almost
> certainly is not the cause of the problem.
Well, you already have a very confusing error message:
mount: wrong fs type, bad option, bad superblock on //smbserver/foo,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
That's 4 options, neither of which apply, only "other", and there is nothing
about it in dmesg. How much worse would it be to (conditionally) print this
for e.g. unmountable CDs:
mount: wrong fs type, bad option, bad superblock on /mnt/cdrom,
missing codepage, missing mount.iso9660, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
I don't think this would be that much worse - 5 options, of which the third
is accurate, while the fifth is extra and just as ignorable as the others.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
