Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

RE: mount and linux

> >
> > > This is wrong in case of fully modular system (75% of users) since
> > > only register to /proc/filesystems at module insertion.
> > >
> > > The best way would be to combine that with /etc/filesystems..
> >
> > On up-to-date cooker:
> >
> > [root@cooker root]# cat /etc/filesystems
> > ext2
> > nodev proc
> > nodev devpts
> > iso9660
> > reiserfs
> > vfat
> >
> > not overly usesful (ext3, xfs, supermount, jfs, nfs ...).
> On slightly out-of-date Debian /etc/filesystems doesn't exist at all.
> isn't Mandrake specific is it? What is the purpose of it and where
> it come from? Certainly it is a fair point about /proc/filesystems
> limitations though so if /etc/filesystems allows us to correctly add
> more supported filesystems, it should be used.

man mount:
              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
              (minix,  ext, ext2, ext3, xiafs, iso9660, reiserfs,
              romfs, ufs, ntfs,  qnx4,  bfs,  xfs,  cramfs,  hfs,
              hpfs,  adfs,  vxfs  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).

[root@cooker root]# rpm -q mount

of course, man page for mount is in different RPM so it may apply to
totally different command altogether :-)


Messages sorted by: Reverse Date, Date, Thread, Author