I see here https://wiki.archlinux.org/index.php/NTFS-3G that dmask allows user write. I’m still a little unsure how to proceed from here.
My next step is sleep first though
Thanks for all your help.
On 2012-09-13 14:46, asarge wrote:
> I see here https://wiki.archlinux.org/index.php/NTFS-3G that dmask
> allows user write. I’m still a little unsure how to proceed from here.
dmask adjusts who can read and/or write to directories. You still need to adjust fmask for
access to the files in those same directories. Or you may use instead umask, which applies to
both at the same time.
If you use “defaults” you set uid, gid to the user running the mount process, and set umask to
zero, which means full access to everybody. This is, of course, dangerous if other people than
you use your machine. Also opens the system to accidents writing there, but it is safe if you
are the only user.
All this is explained in “man ntfs-3g”.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
So far everything that I have tried has resulted in no one being able to read anything on the shared ntfs partition or everyone having full access to it.
I assume that the best way to deal this is to set up a group that is able to access and others that can’t.
Is this heading in the right direction?
Well, I did try defaults. But that just gave everybody access to everything
But I suspect I might be missing something in my sleep deprived state.
(I do have a knack of doing things the hard way when the simple solution is sitting right in front of me)
Then when it is only for one user, where is the* uid=…*. clause?
And of course the mount point itself must be owned by the user and (s)he should set the permission of it in a way that (s)he denies other users. And when it is for one user, why then mounting so high in the directory tree? Why not inside his/her home directory. Mabe (s)he will then feel more responsible for it’s pertmissions and have his/her own data where (s)he expects it: somewhere inside her/his home directory.
On 2012-09-14 12:06, asarge wrote:
>
> So far everything that I have tried has resulted in no one being able to
> read anything on the shared ntfs partition or everyone having full
> access to it.
> I assume that the best way to deal this is to set up a group that is
> able to access and others that can’t.
For that you simply have to use the GID word in the fstab line and assign it to an adequate
group. Then the dmask and fmask must also be applied so that the group has r/w access, but not
others.
> Is this heading in the right direction?
It is what I do.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
I have been trying to set up a group permission on the partitions that I want to be able to share. But each time I reboot, I get a text login for root in an emergency mode.
I am only changing the line that relates to the ntfs file system.
Would this be happening because the “group” I’m attempting to allow does not currently exist?
Which brings me to my next question. How do I create a new group?
1.165270] pnp 00:01: can't evaluate _CRS: 12311
doing fast boot
Creating device nodes with udev
Welcome to emergency mode. Use "systemctl default" or D to enter default mode.
Give root password for login: systemd-fsck[504]: /dev/sda7: clean, 58456/33120256 files
Is this helpful? Or should I be looking in a log file somewhere?
> Code:
> --------------------
> 1.165270] pnp 00:01: can’t evaluate _CRS: 12311
> doing fast boot
> Creating device nodes with udev
> Welcome to emergency mode. Use “systemctl default” or D to enter default mode.
> Give root password for login: systemd-fsck[504]: /dev/sda7: clean, 58456/33120256 files
> --------------------
>
> Is this helpful? Or should I be looking in a log file somewhere?
The error should be several lines above and you have to look carefully. I’m not that familiar
with systemd to be sure of that. However, a bad line in fstab will certainly dump you into
emergency mode.
You should not reboot to try a change in fstab, just umount before the change, mount after the
change. Of course, a non existing group in a line that request use of that group could do that.
Comment out that line, boot normally, add the group, edit fstab, mount and check. Do not reboot.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
