I want change the file "/mnt/work" permission, I used "chmod 777 /mnt/work" ,

it's useless.

But if I setup a new file in the "/mnt", I could change its permission.

By the way, "work" is a directory which I mounted a section of my windows part.

Thank you for you guys help.

i think u missed -R option, this is for directories
ie chmod -R 777 /dir......... for ur case it is /mnt/work/

be sure to run this as root

if u simply type chmod 777 /dir/dir1 it will take as dir1 one as a file

please do a search n chmod changing permission in google

Welcome to LQ!

I'm not sure I understand your question. Perhaps if you read this Quick and Dirty Guide to File Permissions first, then if you have any more questions, please post back. That guide was instrumental in helping me understand permissions, and I believe it will help you.

Windows does not have UNIX permissions. Therefore, you must set the permissions when mounting the partition (either through the fstab entry, or using -o with the mount command).

now only i saw tht ur partition was mounted on thth dir

so plz send the fstab entry how u entered it
if so i donthtink that u can change the permission by chmod it is there in the fstab entry 10, 00 like things
plz reply back

and keep in mind NTFS is read only
i dont think its possible to write to a NTFS partition

You want the option "umask=000"

Or put it in your fstab if you use that.

This is my fstab:

/dev/hda11 swap swap defaults 0 0
/dev/hda10 / ext3 defaults 1 1
/dev/cdrom /mnt/cdrom iso9660 noauto,owner,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,owner 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
/dev/hda8 /mnt/work vfat auto 0 0


So far I used all the method but I cannot change the permission "/mnt/work " to

777.

help!!!

Try: or

/mnt/work vfat auto,gid=100,user,umask=007 1 0 % 0 0 is ok
what about 0 0 and 0 1 entries i think both should be zeros here no dumb option, no need to backup tht partition

and also u didint mention which file sysem u have on /dev/hda fat32 or ntfs ?

is it possible to change permisssion through chmod to an fstab entry ? nope

uncomment that line in fstab and try manually mounting to some where (directory) in ur home directory and
check wether this works or not % or else it will tell it is already mounted

it is similar to making a file in ur home dir ...

what windows part .........here it looks like a winblows drive (c:, d: etc) is it fat32 or ntfs

do root can change the files in /mnt/work

%%%%%%%%%%comment on cd drive and floppy
i hopw u also have some problem with cd drive too %cant mount write etc...

Thanks all, I fixed the problem. But I don't understand it

means. (gid=100,user,umask=000 1 0) Can someone explain

it?

You can find more info about it on fstab and mount man pages. To reach them type: and: Basically the options means:
- gid=100 - Make the mounted device to be owned by group id 100 (users).
- user - Allow any user to mount the device and allow him to umount it.
- umask=000 - Give permissions for read,write,execute to owner,group and others.
- 1 means that the filesystem should be dumped by some backup/restore programs. Set that to 0, my mistake as stated by rkrishna
- 0 (in the last field) means that the filesystem shouldn't be checked by fsck.

how? what have u done let us also know

regards

Many thanks to all of you.

According to gbonvehi's method, I modified the fstab. Then I

use the command "chmond 777 /mnt/work". The permission is

become to "rwxrwxrwx".

I change the directory's permission because I want to use

samba to share my linux. So if I donot change the directory

"work" permission, it couldnot be access by others. And now

I could do it sccessfully.

SLack 10.1
115GB IBM /dev/hda (windoze) ntfs
160GB WD /dev/hdb (Slack) Linux partition
40GB Maxtor /dev/hde (personal) ntfs

my problem is writing to the Maxtor; not even a text file will write to it! I use it to share my files between the operating systems.
I cannot reset the permissions on this drive;
tells me the location is read only. Then I found the "no write" to ntfs info.
Would making it FAT32 fix this and still act right in BOTH operating systems?

THanks. I had to scour the 'net to find that little trinket of info.
Dyn0myt3