"quiet" mount option to VFAT

[Behdad Esfahbod]

On Sat, 29 Jan 2005, Alexey Morozov wrote:

> It's clearly that UTF-8 is a vendor specific option. Just because so
> many (console) apps have significant problems when utf-8 really becomes
> multibyte. Thus certain distributions prefer old-style single-byte
> encodings as system default. As far as I checked last time some of GNU
> textutils/coreutils still aren't multibyte clean, zsh behaves strangely
> when _certain_ two+-bytes letters are typed (and/or _cleared_ w/
> backspace), text labels in Midnight Commander and entire ncurses apps
> family sometimes looks weird when multibyte strings are in use etc etc.
> Most of Western (American and European) speakers usually don't notice
> this because they usually work w/ single byte letters (us-ascii), but
> those [unluckies :-)] w/ non-Latin based alphabets can see such bugs
> regularly...

Well, first, GNOME and KDE at least work UTF-8.  Second, HAL
doesn't really have to worry about console and legacy
applications.  Next, ncurses supports UTF-8 for quite a while
now.  Well, I'm sure I don't need to argue about why UTF-8 or
not...

> 'quiet' I think is even a more general requirement just because it's
> independent of a user's language environment and it always makes sense
> when dealing w/ filesystems which don't support unix-style attributes.

That this warning is generated each and every time and basically
there is no solution to it, makes it so useless that can be
'quiet'ed safely.  Isn't HAL's basic idea making access to
hardware easier?  Choosing sane defaults is towards that goal,
isn't it?  And to answer another reply in this thread:  Whatever
kernel's default is, is not necessarily the best option.  Kernel
people just provide the functionality, they don't try to make the
better option the default.

Just my couple cents,

--behdad
http://behdad.org/
_______________________________________________
hal mailing list
hal at lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/hal