automount NTFS in Redhat 8.0

mhearn · 02-01-2003, 03:29 PM

Indeed, the problem may be the umask. Set it to 777 rather than 222 and see if that helps.

MasterC · 02-01-2003, 05:41 PM

umask 777 will leave them with absolutely no rights. a umask of 777 is equal to a chmod 000

So, if you mean a umask=000 then that'd be equal to a chmod 777 (which is probably more likely what you mean).

Cool

manub · 02-02-2003, 03:55 AM

I've tried with a mix of your tips and I get it work !

/dev/hdc1 /mnt/data ntfs umask=000,defaults 1 0

I used that line ... now I'm not sure about the security of this settings ... for me it's good that any user can read the partition ... of course noone could write

how about this ?

MasterC · 02-02-2003, 04:05 AM

Should be fine, however, I think you should change that last 1 to a zero.

The umask of 000 will work fine since NTFS is unwriteable anyway (for arguments sake I'll say that you could enable write, but normally it's off for safety).

Cool

manub · 02-02-2003, 04:10 AM

did it

thanks a lot !

MasterC · 02-02-2003, 04:11 AM

You're welcome, I am glad you got it working!

lynch · 02-02-2003, 04:50 AM

I was wondering when someone was going to mention "umask=000".

lynch

MasterC · 02-02-2003, 05:06 AM

Lynch, why? Why does it have to be a umask of 000 when all one needs is execution and read permissions (umask=000)? Just curious, I know write isn't necessarily a bad thing for this instance since NTFS doesn't allow it anyway, but I still am curious as to why? Thanks

Cool

mhearn · 02-02-2003, 06:04 AM

Thanks MasterC, didn't realise umasks were inverted like that...

MasterC · 02-02-2003, 06:19 AM

You're welcome

Any ideas on my above question? I'm quite confused on it...

Cool

Darin · 02-02-2003, 06:59 AM

in kernel config:

Code:

[*] prompt for development and/or bla bla bla...

opens up:

Code:

[*]NTFS write support (DANGEROUS)

and umask 000 means anyone can read/write,
umask 007 means owner and group can read/write, everyone else no touchie.

lynch · 02-02-2003, 08:21 AM

Quote:

...Any ideas on my above question? I'm quite confused on it...

Oh,so am I.

It's just how I've always got it to work for me.Actually,I just add "umask=0"to the fstab line and leave it at that.

Sorry I dont have a good answer.
lynch

MasterC · 02-02-2003, 11:47 AM

Quote:

Originally posted by Darin
in kernel config:

Code:

[*] prompt for development and/or bla bla bla...

opens up:

Code:

[*]NTFS write support (DANGEROUS)

and umask 000 means anyone can read/write,
umask 007 means owner and group can read/write, everyone else no touchie.

Thank Darin, but my question more applies to why a read/execute priviledge doesn't allow reading if the write bit isn't set as well.

Cool

candyman123 · 07-04-2003, 11:42 AM

I know this is really old...but I think I found the problem as to why "umask 222" didn't work.

I haven't looked into why it works...but it does

/dev/hdd3 /home/tom/storage2 ntfs auto,umask=0222 0 0

That works perfect. Everyone gets read and execute access.

When I did it with just 222, I had major problems. The user has read, the group and everyone else has none.

Whaddya think?

mike-hell · 07-19-2003, 01:05 PM

ok wierd sense of linux still sucking and sticking with freebsd

problem: can not mount ntfs in redhat 9
sygnosis: when tried to create in fstab (/dev/hda1 /win ntfs umask=007,gid=201,defaults 1 0 )
error: mount: fs type ntfs not supported by kernel
(all i want to do is mount my gf's winxp partition to my linux to get files off it and burn on cd)