problem with fstab

From: The Illien (theillien_at_yahoo.com)
Date: 08/28/03

  • Next message: SINNER: "Re: [Help] Dual boot system WindowsME & Linux RedHat 9.0" 
    Date: Thu, 28 Aug 2003 18:24:10 GMT

    I had my fstab set up so that it would automatically mount a vfat
    partion when loaded. However, it has never allowed me to write to it
    from within Linux. I did a brief search and found that I should not set
    it up to auto mount. I then edited it to look like this:

    LABEL=/ / ext3 defaults
    1 1
    none /dev/pts devpts gid=5,mode=620
    0 0
    none /proc proc defaults 0 0
    LABEL=/home /home ext3 defaults 1 2
    none /dev/shm tmpfs defaults 0 0
    /dev/hdb3 swap swap defaults 0 0
    /dev/cdrom /mnt/cdrom auto,owner,kudzu,ro 0 0
    /dev/hda5 /mnt/data noauto,user,kudzu,rw 0 0
    /dev/fd0 /mnt/floppy noauto,owner,kudzu 0 0
    /dev/cdrom1 /mnt/cdrom1 auto,owner,kudzu,ro 0 0

    The device in question is /dev/hda5. I'm not sure if I should have it
    set up as user or owner though. I havent' reached that problem yet.

    Now, I have an even bigger problem. When I run the command 'mount -a'
    to reload the fstab without rebooting I get this:

    mount: fs type ro not supported by kernel
    mount: fs type noauto,user,kudzu,rw not supported by kernel
    mount: fs type noauto,owner,kudzu not supported by kernel
    mount: fs type ro not supported by kernel

    I've never got this before. So now I actually have two questions:

    1. How do I solve the problem with the unsupported fs types, and
    2. How do I configure my fstab to mount a vfat partion in a way that
         allows me to write to it?

    I guess a third question could be should I set up the mount as 'user' or
    'owner'?

    I'm running a dual boot RH9/win2k (if I ever get it working again, go
    figure).

    Thanks for the help
    The Illien

  • Next message: SINNER: "Re: [Help] Dual boot system WindowsME & Linux RedHat 9.0"

    Relevant Pages

    • Re: Cant mount cdrom (Fixed)
      ... I also have the proper entry in fstab. ... just hangs and does nothing. ... Doing that not only solved my mount ... Well then something else must have been bad in my kernel. ...
      (freebsd-current)
    • RE: Machine not Booting - Continued
      ... The fstab is not to blame for this issue as i have just run mkraid /dev/md0 ... and then a mount -a and the area mounted straight away. ... it has no proper file system to mount. ...
      (RedHat)
    • Re: How to set /etc/fstab again after system has started
      ... That is the incorrect statement. ... With an appropriate entry in fstab, it takes very little, ... but without it the mount command needs more information. ... The previous poster went off on a tangent, ...
      (comp.os.linux.misc)
    • Re: DVD Recorder on FC3
      ... Apparently, mount is not ... even though it's included on fstab. ... You don't need ide-scsi with a 2.6 kernel :-) ...
      (Fedora)
    • Re: nfs bug & df: Can I lock up my kernel and overflow this buffer?
      ... > mount_nfs commandline switches I needed. ... You are not restricted to only the -o option with fstab. ... Since mount wasn't able to understand those switches on ...
      (freebsd-stable)