Mike McMullin wrote:
On Sun, 2006-02-26 at 12:00 +0100, Clayton wrote:
Please leave some of the top of the message. It makes it easier to figure out if your responding to what I wrote or a quote from someone else.
Ha... some people hate too much quoting... others like loads of it :-) I'm a minimalist I guess <grin>
/dev/hda1 /mnt/ME vfat users,gid=users,umask=0002,iocharset=utf8 0 0 Hmmm was tied to the umask=002.... as in... I added users,gid=users and no change, but added umask=002 and it all started working. Hmmmm... I wonder why the YAST tools didn't set this up right on install? Oh well.. setting the umask gave the results I wanted.
Setting it up right is a relative thing. I've never had SuSE set my ?fat based partitions as read\write outside of root. I've always had to edit fstab.
Interesting. I had similar results as Kevan mentioned... it worked fine in 9.1, stopped working in 9.2 (I forget what I did back then to get it working) worked fine in 9.3 (no tinkering needed), worked fine in my first install of 10.0 (no tinkering.. had full rw access to a fat32 partition). Then I reinstalled 10.0 after a major drive failure... and no more fat32 rw access. To me, setting it up right is to allow rw access to partitions Linux can reliably rw to. I never pay much attention though to what is in my fstab since - at least in the last couple releases - it's always worked as expected. No matter in the long run... adding umask=002 worked. C.