msdos/vfat defaults are annoying

[John Richard Moser <nigelenki@comcast.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So I've noticed, again, much annoyed, that if I rely on -t auto,
horrible horrible things happen.

I have had floppies and compact flash cards that I've done mkfs.vfat to
make fat32 filesystems on (not fat16), and mounting them brings the
thing on as msdos by default (autodetect).  Furthermore, I build msdos
out, and mount says the msdos FS isn't supported.  In either case I need
to use -t vfat.

Vfat is much more common and should be backwards compatible with msdos.
  When there's a ton of foo~1 files around after mounting, something's
wrong.

Shouldn't vfat be the automatic default?  Or at least, if only vfat and
not msdos is available, use vfat.  For that matter, can msdos and vfat
be collapsed?  As I recall, the difference is that vfat makes more
inodes to store long file names, one for each 13 characters (in reverse?)

I dunno.  I can never understand the innards of the kernel devs' minds.

- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCBaw3hDd4aOud5P8RAtBGAJsE8I1510nLSNqM6MRwPFGnl9l2UQCfSaGy
HPGDuNVPvMZq8nkI34DlfPI=
=uNx9
-----END PGP SIGNATURE-----