At 04 Sep 2002 12:41:06 +1000, Ken Foskey wrote:
> Why would this be happening on debian:
because you are typing it at a keyboard connected to a debian system?
(couldn't resist)
> gandalf: ~
> $ mount /floppy/
> mount: I could not determine the filesystem type, and none was specified
> from fstab:
> /dev/fd0 /floppy auto defaults,user,noauto 0 0
quoting from mount(8):
-t vfstype
[...]
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, ufs, vxfs,
xfs, xiafs are supported).
note that neither "vfat" nor "msdos" are listed.
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).
/etc/filesystems is probably empty, /proc/filesystems will list all
filesystems that the kernel currently knows about. if you have vfat
autoloaded (and you probably do), then it probably isn't listed in
/proc/filesystems at the moment, so "mount -t auto" never knows about
it.
Note that 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 filesystem type.
as hinted at here, the fix is to simply create an /etc/filesystems
containing something like:
vfat
msdos
then they will be attempted regardless of whether the vfat.o kernel
module is currently loaded.
--
- Gus
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
