KDE-Forum.org

Windows filesystems doesn't support the same access rights as traditional UNIX filesystems and can't be changed with chmod/chown. Instead they are set when mounting the filesystem with mount or in the /etc/fstab file. For more informaion see manual pages for mount and fstab.

here's a copy of my etc/fstab file:

devpts /dev/pts devpts gid=5,mode=620 0 0
/proc /proc proc defaults 0 0
none /proc/bus/usb usbdevfs defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,exec 0 0
/dev/fd0 /mnt/floppy auto defaults,user,noauto 0 0
/dev/hda8 / ext3 defaults 1 1
/dev/hda5 /mnt/hda5 vfat umask=0,quiet,defaults 0 0
/dev/hda5 /home/patrick/Shared vfat umask=0,quiet,defaults 0 0
/dev/hda2 /mnt/hda2 ntfs umask=022,ro,defaults 0 0
/dev/hda1 /mnt/hda1 vfat umask=0,quiet,defaults 0 0
/dev/hda6 swap swap defaults 0 0

as you can see, /dev/hda5 is a fat32 partition, and much like yourself I set it up for storage of files, tunes, whatever, so I can share them seemlessly between differnt OS.

as a neat little side trick, I also mount hda5 in my users home directory for super easy access.

the way it's laid out gives full read write access to all users, though there are also many different ways of setting it up. this is a very simplistic option, which is why I like it.

Like per said, check your man pages and search the net for fstab...you'll find many resources.

good luck!

If a non linux filesystem is mounted at boottime, it becomes owned by root. So only root has write acces.
To avoid this, you can either try not mounting at boot time, but later on as user, or change the umask of the filesystem.
Last one is wat I prefer.
To this, add the following line in /etc/fstab for your Windows-partition:

[code:1]
/dev/hda5 /mnt/hda5 vfat users,gid=users,umask=0002,iocharset=iso8859-15,code=437 0 0
[/code:1]

(string should be on 1 line..)

The trick over here is the umask=0002

This only works with vfat, ntfs is not good supported, and therefore even as root write protected.

Rinse

Writing to NTFS drives is experimental and can damage your NTFS-filesystem.

Rinse

Quoted

Original von seb

My fourth reinstallation, now Fat32

Well, it keeps you off the street

Keep also in mind that Linux kernel 2.6 will have full support for NTFS

Rinse

I have nbeen having the same problem, I have two win2k partitions on my system that I want to access to pull down data. I originall had the group and owner set up as root for both. I was told on another site that I should change the owners ro user which I did. But every time I tried to mount the NTFS partitians using the user mount tool they ownership changed back to root. at that point my fstab file looked like:

/dev/hdb1 /mnt/drive_f ntfs noauto,user,ro 0 0
/dev/hda1 /mnt/drive_c ntfs noauto,user,ro 0 0

However after reading this post I changed my fstab to read:

dev/hdb1 /mnt/drive_f ntfs users,gid=users,umask=022,ro,defaults 0 0
/dev/hda1 /mnt/drive_c ntfs users,gid=users,umask=022,ro,defaults 0 0

This now lets me mount the partitians as the user and read the data in the folders. Problem is, I am not sure what I have just done can someone explain all after the ntfs part?

Thanks
:?

users - users can mount the partition
gid=users - the group identity of the files is set to users
umask=022 - reverses the file permissions, see man umask for details.
ro - readonly
defaults - this one has no function in this string, it tells fstab that the default settings apply.
But the other options overrule defaults..

Rinse