floppy fstab entry for vfat and ext

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I'm trying to create an fstab entry for /dev/fd0 so that user can mount a floppy formatted either with VFAT or ext32. The simple fstab entry



/dev/fd0 /mnt/floppy auto noauto,user,sync,gid=users,umask=000 0 2


can only mount DOS floppies. If I change the entry to



/dev/fd0 /mnt/floppy ext2 noauto,user,sync 0 2


then I can only mount a floppy with ext2 filesystem.
Obviously, I can issue a root mount command with appropriate -t option and mount either floppies. Is there a way to mount floppy as user with the simple command



mount /mnt/floppy


for floppies with either VFAT or ext2 filesystem?










share|improve this question













migrated from stackoverflow.com Oct 11 '17 at 13:45


This question came from our site for professional and enthusiast programmers.


















    up vote
    1
    down vote

    favorite












    I'm trying to create an fstab entry for /dev/fd0 so that user can mount a floppy formatted either with VFAT or ext32. The simple fstab entry



    /dev/fd0 /mnt/floppy auto noauto,user,sync,gid=users,umask=000 0 2


    can only mount DOS floppies. If I change the entry to



    /dev/fd0 /mnt/floppy ext2 noauto,user,sync 0 2


    then I can only mount a floppy with ext2 filesystem.
    Obviously, I can issue a root mount command with appropriate -t option and mount either floppies. Is there a way to mount floppy as user with the simple command



    mount /mnt/floppy


    for floppies with either VFAT or ext2 filesystem?










    share|improve this question













    migrated from stackoverflow.com Oct 11 '17 at 13:45


    This question came from our site for professional and enthusiast programmers.
















      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I'm trying to create an fstab entry for /dev/fd0 so that user can mount a floppy formatted either with VFAT or ext32. The simple fstab entry



      /dev/fd0 /mnt/floppy auto noauto,user,sync,gid=users,umask=000 0 2


      can only mount DOS floppies. If I change the entry to



      /dev/fd0 /mnt/floppy ext2 noauto,user,sync 0 2


      then I can only mount a floppy with ext2 filesystem.
      Obviously, I can issue a root mount command with appropriate -t option and mount either floppies. Is there a way to mount floppy as user with the simple command



      mount /mnt/floppy


      for floppies with either VFAT or ext2 filesystem?










      share|improve this question













      I'm trying to create an fstab entry for /dev/fd0 so that user can mount a floppy formatted either with VFAT or ext32. The simple fstab entry



      /dev/fd0 /mnt/floppy auto noauto,user,sync,gid=users,umask=000 0 2


      can only mount DOS floppies. If I change the entry to



      /dev/fd0 /mnt/floppy ext2 noauto,user,sync 0 2


      then I can only mount a floppy with ext2 filesystem.
      Obviously, I can issue a root mount command with appropriate -t option and mount either floppies. Is there a way to mount floppy as user with the simple command



      mount /mnt/floppy


      for floppies with either VFAT or ext2 filesystem?







      linux mount floppy fstab






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 10 '17 at 3:09









      Janos

      84




      84




      migrated from stackoverflow.com Oct 11 '17 at 13:45


      This question came from our site for professional and enthusiast programmers.






      migrated from stackoverflow.com Oct 11 '17 at 13:45


      This question came from our site for professional and enthusiast programmers.






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          0
          down vote



          accepted










          From man 8 mount on Linux:




          If no -t option is given, or if the auto type is specified,
          mount will try to guess the desired type. Mount uses the blkid
          library for guessing the filesystem type; if that does not turn
          up anything that looks familiar, 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 *, mount will
          read /proc/filesystems afterwards. While trying, all filesystem
          types will be mounted with the mount option silent.




          So just create a file /etc/filesystems containing something like this:



          ext4
          ext3
          ext2
          vfat
          msdos
          ntfs
          iso9660
          ufs
          xfs


          Add more filetypes if you need. Then you can use type auto in fstab.






          share|improve this answer






















          • @Sato Katsura - thanks for your interest in responding to my question. I do have the /etc/filesystems file that contains ext2 and vfat entries, yet fstab with auto entry gives error suach as "bad superblock..." if using mount command without -t option. The cat /proc/filesystem shows only filesystems currently used by mounted devices. This problem happens only with /dev/fd0; I can mount auto sda devices (usb sticks formatted either vfat or ext2). Strange behavior for fd0?
            – Janos
            Oct 18 '17 at 15:19










          • @Janos The order is important, the entries are tried in order. If msdos comes before vfat and you try to mount a vfat filesystem you'll get an error, because the filesystems are similar enough for msdos to match.
            – Satō Katsura
            Oct 18 '17 at 15:31










          • @sato Katsura - it works now! Thanks again, Janos
            – Janos
            Oct 20 '17 at 2:14










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "106"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f397465%2ffloppy-fstab-entry-for-vfat-and-ext%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          0
          down vote



          accepted










          From man 8 mount on Linux:




          If no -t option is given, or if the auto type is specified,
          mount will try to guess the desired type. Mount uses the blkid
          library for guessing the filesystem type; if that does not turn
          up anything that looks familiar, 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 *, mount will
          read /proc/filesystems afterwards. While trying, all filesystem
          types will be mounted with the mount option silent.




          So just create a file /etc/filesystems containing something like this:



          ext4
          ext3
          ext2
          vfat
          msdos
          ntfs
          iso9660
          ufs
          xfs


          Add more filetypes if you need. Then you can use type auto in fstab.






          share|improve this answer






















          • @Sato Katsura - thanks for your interest in responding to my question. I do have the /etc/filesystems file that contains ext2 and vfat entries, yet fstab with auto entry gives error suach as "bad superblock..." if using mount command without -t option. The cat /proc/filesystem shows only filesystems currently used by mounted devices. This problem happens only with /dev/fd0; I can mount auto sda devices (usb sticks formatted either vfat or ext2). Strange behavior for fd0?
            – Janos
            Oct 18 '17 at 15:19










          • @Janos The order is important, the entries are tried in order. If msdos comes before vfat and you try to mount a vfat filesystem you'll get an error, because the filesystems are similar enough for msdos to match.
            – Satō Katsura
            Oct 18 '17 at 15:31










          • @sato Katsura - it works now! Thanks again, Janos
            – Janos
            Oct 20 '17 at 2:14














          up vote
          0
          down vote



          accepted










          From man 8 mount on Linux:




          If no -t option is given, or if the auto type is specified,
          mount will try to guess the desired type. Mount uses the blkid
          library for guessing the filesystem type; if that does not turn
          up anything that looks familiar, 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 *, mount will
          read /proc/filesystems afterwards. While trying, all filesystem
          types will be mounted with the mount option silent.




          So just create a file /etc/filesystems containing something like this:



          ext4
          ext3
          ext2
          vfat
          msdos
          ntfs
          iso9660
          ufs
          xfs


          Add more filetypes if you need. Then you can use type auto in fstab.






          share|improve this answer






















          • @Sato Katsura - thanks for your interest in responding to my question. I do have the /etc/filesystems file that contains ext2 and vfat entries, yet fstab with auto entry gives error suach as "bad superblock..." if using mount command without -t option. The cat /proc/filesystem shows only filesystems currently used by mounted devices. This problem happens only with /dev/fd0; I can mount auto sda devices (usb sticks formatted either vfat or ext2). Strange behavior for fd0?
            – Janos
            Oct 18 '17 at 15:19










          • @Janos The order is important, the entries are tried in order. If msdos comes before vfat and you try to mount a vfat filesystem you'll get an error, because the filesystems are similar enough for msdos to match.
            – Satō Katsura
            Oct 18 '17 at 15:31










          • @sato Katsura - it works now! Thanks again, Janos
            – Janos
            Oct 20 '17 at 2:14












          up vote
          0
          down vote



          accepted







          up vote
          0
          down vote



          accepted






          From man 8 mount on Linux:




          If no -t option is given, or if the auto type is specified,
          mount will try to guess the desired type. Mount uses the blkid
          library for guessing the filesystem type; if that does not turn
          up anything that looks familiar, 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 *, mount will
          read /proc/filesystems afterwards. While trying, all filesystem
          types will be mounted with the mount option silent.




          So just create a file /etc/filesystems containing something like this:



          ext4
          ext3
          ext2
          vfat
          msdos
          ntfs
          iso9660
          ufs
          xfs


          Add more filetypes if you need. Then you can use type auto in fstab.






          share|improve this answer














          From man 8 mount on Linux:




          If no -t option is given, or if the auto type is specified,
          mount will try to guess the desired type. Mount uses the blkid
          library for guessing the filesystem type; if that does not turn
          up anything that looks familiar, 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 *, mount will
          read /proc/filesystems afterwards. While trying, all filesystem
          types will be mounted with the mount option silent.




          So just create a file /etc/filesystems containing something like this:



          ext4
          ext3
          ext2
          vfat
          msdos
          ntfs
          iso9660
          ufs
          xfs


          Add more filetypes if you need. Then you can use type auto in fstab.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Oct 11 '17 at 14:24

























          answered Oct 11 '17 at 13:54









          Satō Katsura

          10.7k11533




          10.7k11533











          • @Sato Katsura - thanks for your interest in responding to my question. I do have the /etc/filesystems file that contains ext2 and vfat entries, yet fstab with auto entry gives error suach as "bad superblock..." if using mount command without -t option. The cat /proc/filesystem shows only filesystems currently used by mounted devices. This problem happens only with /dev/fd0; I can mount auto sda devices (usb sticks formatted either vfat or ext2). Strange behavior for fd0?
            – Janos
            Oct 18 '17 at 15:19










          • @Janos The order is important, the entries are tried in order. If msdos comes before vfat and you try to mount a vfat filesystem you'll get an error, because the filesystems are similar enough for msdos to match.
            – Satō Katsura
            Oct 18 '17 at 15:31










          • @sato Katsura - it works now! Thanks again, Janos
            – Janos
            Oct 20 '17 at 2:14
















          • @Sato Katsura - thanks for your interest in responding to my question. I do have the /etc/filesystems file that contains ext2 and vfat entries, yet fstab with auto entry gives error suach as "bad superblock..." if using mount command without -t option. The cat /proc/filesystem shows only filesystems currently used by mounted devices. This problem happens only with /dev/fd0; I can mount auto sda devices (usb sticks formatted either vfat or ext2). Strange behavior for fd0?
            – Janos
            Oct 18 '17 at 15:19










          • @Janos The order is important, the entries are tried in order. If msdos comes before vfat and you try to mount a vfat filesystem you'll get an error, because the filesystems are similar enough for msdos to match.
            – Satō Katsura
            Oct 18 '17 at 15:31










          • @sato Katsura - it works now! Thanks again, Janos
            – Janos
            Oct 20 '17 at 2:14















          @Sato Katsura - thanks for your interest in responding to my question. I do have the /etc/filesystems file that contains ext2 and vfat entries, yet fstab with auto entry gives error suach as "bad superblock..." if using mount command without -t option. The cat /proc/filesystem shows only filesystems currently used by mounted devices. This problem happens only with /dev/fd0; I can mount auto sda devices (usb sticks formatted either vfat or ext2). Strange behavior for fd0?
          – Janos
          Oct 18 '17 at 15:19




          @Sato Katsura - thanks for your interest in responding to my question. I do have the /etc/filesystems file that contains ext2 and vfat entries, yet fstab with auto entry gives error suach as "bad superblock..." if using mount command without -t option. The cat /proc/filesystem shows only filesystems currently used by mounted devices. This problem happens only with /dev/fd0; I can mount auto sda devices (usb sticks formatted either vfat or ext2). Strange behavior for fd0?
          – Janos
          Oct 18 '17 at 15:19












          @Janos The order is important, the entries are tried in order. If msdos comes before vfat and you try to mount a vfat filesystem you'll get an error, because the filesystems are similar enough for msdos to match.
          – Satō Katsura
          Oct 18 '17 at 15:31




          @Janos The order is important, the entries are tried in order. If msdos comes before vfat and you try to mount a vfat filesystem you'll get an error, because the filesystems are similar enough for msdos to match.
          – Satō Katsura
          Oct 18 '17 at 15:31












          @sato Katsura - it works now! Thanks again, Janos
          – Janos
          Oct 20 '17 at 2:14




          @sato Katsura - it works now! Thanks again, Janos
          – Janos
          Oct 20 '17 at 2:14

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f397465%2ffloppy-fstab-entry-for-vfat-and-ext%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Displaying single band from multi-band raster using QGIS

          How many registers does an x86_64 CPU actually have?