so all i need to do is edit /etc/filesystems to get it to check for vfat before checking for msdos. now i just need to get round to setting that autofs thing up and i'm laughing...-t vfstype
The argument following the -t is used to indicate the file sys-
tem type. The file system types which are currently supported
are: adfs, affs, autofs, coda, coherent, cramfs, devpts, efs,
ext, ext2, ext3, hfs, hpfs, iso9660, jfs, minix, msdos, ncpfs,
nfs, ntfs, proc, qnx4, reiserfs, romfs, smbfs, sysv, tmpfs, udf,
ufs, umsdos, vfat, xenix, xfs, xiafs. Note that coherent, sysv
and xenix are equivalent and that xenix and coherent will be
removed at some point in the future -- use sysv instead. Since
kernel version 2.1.21 the types ext and xiafs do not exist any-
For most types all the mount program has to do is issue a simple
mount(2) system call, and no detailed knowledge of the filesys-
tem type is required. For a few types however (like nfs, smbfs,
ncpfs) ad hoc code is necessary. The nfs ad hoc code is built
in, but smbfs and ncpfs have a separate mount program. In order
to make it possible to treat all types in a uniform way, mount
will execute the program /sbin/mount.TYPE (if that exists) when
called with type TYPE. Since various versions of the smbmount
program have different calling conventions, /sbin/mount.smb may
have to be a shell script that sets up the desired call.
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
The auto type may be useful for user-mounted floppies. Creating
a file /etc/filesystems can be useful to change the probe order
(e.g., to try vfat before msdos) or if you use a kernel module
autoloader. Warning: the probing uses a heuristic (the presence
of appropriate `magic'), and could recognize the wrong filesys-
tem type, possibly with catastrophic consequences. If your data
is valuable, don't ask mount to guess.
More than one type may be specified in a comma separated list.
The list of file system types can be prefixed with no to specify
the file system types on which no action should be taken. (This
can be meaningful with the -a option.)
For example, the command:
mount -a -t nomsdos,ext
mounts all file systems except those of type msdos and ext.
as an aside, void main, does that phpman thing interact with the actual man command on the host machine, or is it static man pages in files that get called up as required, or what is it?