Given the device and filesystem on the drive, I'll guess that this is a removable drive usb or firewire drive. If that is the case, you may want to use the "noauto" option instead. Also, for fat32 mass storage drives, it is best not to have execute permissions on files. But you need the "x" bit set for directories to be able to enter them. To do this you need to use the "fmask" and "dmask" options instead of "umask".
Another problem is that if you were to add another usb drive, the next time you boot up the same partition might be assigned to another device. So, instead of using a device entry in fstab, use either "LABEL=alabel
" or "UUID=fs_uuid
I'll do it myself right now to walk you through the process:
I just inserted a USB Cruzer mini pendrive into the laptop. Let's see what the FS_UUID number is:
> udevinfo -q env -n /dev/sda1
Cheating a little, I automounted it and borrowed some of the options used in mounting it:
UUID=3B69-1AFD /mnt/cr256 vfat rw,nosuid,nodev,noatime,noauto,flush,user,uid=jschiwal,utf8,shortname=lower,fmask=177,dmask=077
I added the uid=, and user option to allow me to mount it as a regular user. The fsmask and dmask options I chose will give the mounted partition r/w permissions for user "jschiwal" but if another user "gest" were to mount it, he wouldn't be able to enter the directory without using sudo ( or another computer).
Also, reinserting two pendrives, the device used was /dev/sdd1 instead. Entering "mount /mnt/cr256" mounted it anyway.