Vfat Conflicts...rw

[XciterKid]

I have 3 fat32 drives(my windows partitions) which i've mounted into linux at points /c,/e,/f. I ran into the all-to- familiar "chmod dilemma". With a little research I found an article on how to allow read/write access to vfat drives for normal users. It had to do w/ umsdos and optionaly uid,gid settings. After using umsdos and it totally ****ing up mp3 titles names when viewed in windows, i switched to the second option. The uid,gid fstab attempt worked occasionally. For some reason it chose not to work sometimes, but worked perfect other times. Well now it doesn't work at all and I can't figure out how to get it to work. If anyone understands and can response helpfully to what I'm saying I would be most gracious.

[7]

Do the lines in /etc/fstab relating to these vfat filesystems have the word 'user' in the options field?

[Linuxcool]

I use /dev/hda1 /mnt/windows vfat noauto,ro,user 0 0 to mount my windows partition. You can change it to mount your partitions. The ' noauto ' means that it will not mount the partition automatically on boot up. You have to use the mount command to mount it. The ' ro ' means read-only. Change that to ' rw ' for read/write.

[XciterKid]

Kinda enjoyed having it mount it self and set permissions, but your suggestion seems to be more reliable. Thanks.

[Pras]

I had the same problem. When it mounts on bootup, it does it as root and doesn't allow other users to access it. What I did was to add a simple 'umount /mnt/windows' followed immediately by 'mount /mnt/windows' in my .bashrc file and that did the trick. When I login, it will automatically unmount and remount and I'm ok.

[XciterKid]

Thanks Pras. I'm still pretty new to linux and I still haven't learned all the names of the startup scripts. I had the idea for what you've explained b/ wasnt sure how to execute it. I wasn't aware of a script which was run as the actual user and not as root.