On Tue, 30 Mar 2004, CW Harris wrote:
> -t vfstype
> <snip>
>
> The type iso9660 is the default. If no -t option is given, or
> if the auto type is specified, the superblock is probed for the
> filesystem type (adfs, bfs, cramfs, ext, ext2, ext3, hfs, hpfs,
> iso9660, jfs, minix, ntfs, qnx4, reiserfs, romfs, udf, ufs,
> vxfs, xfs, xiafs are supported). If this probe fails, mount
> will try to read the file /etc/filesystems, or, if that does not
> exist, /proc/filesystems. All of the filesystem types listed
> there will be tried, except for those that are labeled "nodev"
> (e.g., devpts, proc and nfs). If /etc/filesystems ends in a
> line with a single * only, mount will read /proc/filesystems
> afterwards.
That is very interesting. I checked my /proc/filesystems and it contains:
ext2
minix
msdos
nodev proc
iso9660
nodev devpts
vfat
nodev usbdevfs
nodev nfs
ufs
With fstab
/dev/fd0 /floppy auto user,noauto 0 0
and 'mount floppy' - where the floppy is a vfat formated one - I never could
use the long name support of vfat (I think "auto" probes the floppy to
msdos). But creating additionally a /etc/filesystems with
vfat
ext2
minix
msdos
nodev proc
iso9660
nodev devpts
nodev usbdevfs
nodev nfs
ufs
gives me the long-name-possibility.
I did not know that "auto" uses a heuristic probing and that
/etc/filesystems could change this order.
I would like to know what exactly determines the order in /proc/filesystems?
Oliver
--
... don't touch the bang bang fruit
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
