mounting hard drive as executable
Hi, OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used: #UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 #xavier #UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2 They are mounted with me as a user owning them but I cannot write to them. So how should I mount them. Is it a root problem or do I need to change the permissions or something else. Thanks for any help, mike spartana
Le 04/02/2021 à 17:56, Michael Spartana a écrit :
I need to change the permissions or something else.
give your user all permissions on disk mount point (as root) jdd -- http://dodin.org
* Michael Spartana <furryllama@comcast.net> [02-04-21 11:57]:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the
Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 #xavier #UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them. So how should I mount them. Is it a root problem or do
I need to change the permissions or something else.
I use "uid=1000,gid=100,file_mode=0777,dir_mode=0777" and have rwx access by <user> and <root> -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
* Michael Spartana <furryllama@comcast.net> [02-04-21 11:57]:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the
Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 #xavier #UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them. So how should I mount them. Is it a root problem or do
I need to change the permissions or something else.
I use "uid=1000,gid=100,file_mode=0777,dir_mode=0777" and have rwx access by <user> and <root> note: as I am currently under censorship, I have cc'd you as many of my posts experience "extended" wait time for *approval*, sometimes >26 hours. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On 2/4/21 12:26 PM, Patrick Shanahan wrote:
* Michael Spartana <furryllama@comcast.net> [02-04-21 11:57]:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the
Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 #xavier #UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them. So how should I mount them. Is it a root problem or do
I need to change the permissions or something else. I use "uid=1000,gid=100,file_mode=0777,dir_mode=0777" and have rwx access by <user> and <root>
OK thanks, .....It didn't work for me. I cannot even create a directory... Andrei says that fuse only mounts with root (they are on fuseblk)..... I have to check that out....Thanks anyways, mike
note: as I am currently under censorship, I have cc'd you as many of my posts experience "extended" wait time for *approval*, sometimes >26 hours.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday, 2021-02-04 at 14:36 -0500, Michael Spartana wrote:
On 2/4/21 12:26 PM, Patrick Shanahan wrote:
* Michael Spartana <> [02-04-21 11:57]:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 # xavier # UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them. So how should I mount them. Is it a root problem or do
I need to change the permissions or something else. I use "uid=1000,gid=100,file_mode=0777,dir_mode=0777" and have rwx access by <user> and <root>
OK thanks, .....It didn't work for me. I cannot even create a directory...
You have to check that the mask is correct, that the gid is correct, the uid is correct. Ie, in your example above, user number 1000 and group number 1000 will have access, not others. I use (single line): LABEL=Windows /windows/C ntfs nofail,noauto,users,gid=users,fmask=133,dmask=022 0 0 and this results in: egolas:~ # mount | grep wind /dev/sda3 on /windows/C type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) Legolas:~ # which does not work: cer@Legolas:/windows/C/Documents and Settings/cer/Documents> touch p touch: cannot touch 'p': Permission denied cer@Legolas:/windows/C/Documents and Settings/cer/Documents> su - Password: Legolas:~ # touch p Legolas:~ # Now, this is curious, because I think it worked in the past. Legolas:~ # logout cer@Legolas:/windows/C/Documents and Settings/cer/Documents> l total 25 drwxr-xr-x 1 root users 4096 Oct 17 2019 ./ drwxr-xr-x 1 root users 8192 Oct 17 2019 ../ drwxr-xr-x 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ drwxr-xr-x 1 root users 4096 Aug 6 2018 Biblioteca exd/ - -rw-r--r-- 1 root users 402 Oct 17 2019 desktop.ini Well, I see the group permission is wrong, it does not permit the group to write. I have "fmask=133,dmask=022". I change to "fmask=0117,dmask=0007", and now it works: cer@Legolas:~> cd /windows/C/Users/cer/Documents/ cer@Legolas:/windows/C/Users/cer/Documents> touch p cer@Legolas:/windows/C/Users/cer/Documents> l total 25 drwxrwx--- 1 root users 4096 Feb 4 22:22 ./ drwxrwx--- 1 root users 8192 Oct 17 2019 ../ drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ - -rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini ... - -rw-rw---- 1 root users 0 Feb 4 22:22 p cer@Legolas:/windows/C/Users/cer/Documents> Note that it is mounted noexec, so not possible to run things. You can change that if you wish :-) - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYBxm4Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVmVEAnRBVbIoCiAS+9PKhh5i3 CyZG0vqOAKCH23AbS7tqsJV+ujpeQ7JDPhtXoQ== =RS6J -----END PGP SIGNATURE-----
On 2/4/21 4:28 PM, Carlos E. R. wrote:
On 2/4/21 12:26 PM, Patrick Shanahan wrote:
* Michael Spartana <> [02-04-21 11:57]:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the Hard Drives for the installations. These are the 2 drives and
On Thursday, 2021-02-04 at 14:36 -0500, Michael Spartana wrote: this is
the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 # xavier # UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them. So how should I mount them. Is it a root problem or do
I need to change the permissions or something else. I use "uid=1000,gid=100,file_mode=0777,dir_mode=0777" and have rwx access by <user> and <root>
OK thanks, .....It didn't work for me. I cannot even create a directory...
You have to check that the mask is correct, that the gid is correct, the uid is correct.
Ie, in your example above, user number 1000 and group number 1000 will have access, not others.
I use (single line):
LABEL=Windows /windows/C ntfs nofail,noauto,users,gid=users,fmask=133,dmask=022 0 0
and this results in:
egolas:~ # mount | grep wind /dev/sda3 on /windows/C type fuseblk (rw,nosuid,nodev,noexec,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096) Legolas:~ #
which does not work:
ok this follows what I was told about fuseblk...I think I need allow_others. I need to know where to put it . I'm reading about this with fuse.
cer@Legolas:/windows/C/Documents and Settings/cer/Documents> touch p touch: cannot touch 'p': Permission denied cer@Legolas:/windows/C/Documents and Settings/cer/Documents> su - Password: Legolas:~ # touch p Legolas:~ #
Now, this is curious, because I think it worked in the past.
I used to use usb drives but I'm trying to cut down on the power draw from the main box....I thought this would be the best way...although apparently not the easiest.....
Legolas:~ # logout cer@Legolas:/windows/C/Documents and Settings/cer/Documents> l total 25 drwxr-xr-x 1 root users 4096 Oct 17 2019 ./ drwxr-xr-x 1 root users 8192 Oct 17 2019 ../ drwxr-xr-x 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ drwxr-xr-x 1 root users 4096 Aug 6 2018 Biblioteca exd/ -rw-r--r-- 1 root users 402 Oct 17 2019 desktop.ini
Well, I see the group permission is wrong, it does not permit the group to write.
I have "fmask=133,dmask=022". I change to "fmask=0117,dmask=0007", and now it works:
cer@Legolas:~> cd /windows/C/Users/cer/Documents/ cer@Legolas:/windows/C/Users/cer/Documents> touch p cer@Legolas:/windows/C/Users/cer/Documents> l total 25 drwxrwx--- 1 root users 4096 Feb 4 22:22 ./ drwxrwx--- 1 root users 8192 Oct 17 2019 ../ drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ -rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini ... -rw-rw---- 1 root users 0 Feb 4 22:22 p
I see you have write privileges....does it matter that it was root created. Problem is that I don't do this changing file permissions enough to know it as well as I should ....thanks mike
cer@Legolas:/windows/C/Users/cer/Documents>
Note that it is mounted noexec, so not possible to run things. You can change that if you wish :-)
-- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar)
On 04/02/2021 22.50, Michael Spartana wrote:
On 2/4/21 4:28 PM, Carlos E. R. wrote:
On Thursday, 2021-02-04 at 14:36 -0500, Michael Spartana wrote:
On 2/4/21 12:26 PM, Patrick Shanahan wrote:
...
Well, I see the group permission is wrong, it does not permit the group to write.
I have "fmask=133,dmask=022". I change to "fmask=0117,dmask=0007", and now it works:
cer@Legolas:~> cd /windows/C/Users/cer/Documents/ cer@Legolas:/windows/C/Users/cer/Documents> touch p cer@Legolas:/windows/C/Users/cer/Documents> l total 25 drwxrwx--- 1 root users 4096 Feb 4 22:22 ./ drwxrwx--- 1 root users 8192 Oct 17 2019 ../ drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ -rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini ... -rw-rw---- 1 root users 0 Feb 4 22:22 p
I see you have write privileges....does it matter that it was root created. Problem is
that I don't do this changing file permissions enough to know it as well as I should
Notice that for ntfs you can not change file permissions: you change fstab instead, which is what I did, successfully. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2/4/21 6:21 PM, Carlos E.R. wrote:
On 04/02/2021 22.50, Michael Spartana wrote:
On 2/4/21 4:28 PM, Carlos E. R. wrote:
On Thursday, 2021-02-04 at 14:36 -0500, Michael Spartana wrote:
On 2/4/21 12:26 PM, Patrick Shanahan wrote: ...
Well, I see the group permission is wrong, it does not permit the group to write.
I have "fmask=133,dmask=022". I change to "fmask=0117,dmask=0007", and now it works:
cer@Legolas:~> cd /windows/C/Users/cer/Documents/ cer@Legolas:/windows/C/Users/cer/Documents> touch p cer@Legolas:/windows/C/Users/cer/Documents> l total 25 drwxrwx--- 1 root users 4096 Feb 4 22:22 ./ drwxrwx--- 1 root users 8192 Oct 17 2019 ../ drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ -rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini ... -rw-rw---- 1 root users 0 Feb 4 22:22 p I see you have write privileges....does it matter that it was root created. Problem is
that I don't do this changing file permissions enough to know it as well as I should
Notice that for ntfs you can not change file permissions: you change fstab instead, which is what I did, successfully.
Yes, Carlos...all posts I read where someone tried changing file permissions created many problems when returning to windows... mike
On 05/02/2021 00.47, Michael Spartana wrote:
On 2/4/21 6:21 PM, Carlos E.R. wrote:
On 04/02/2021 22.50, Michael Spartana wrote:
On 2/4/21 4:28 PM, Carlos E. R. wrote:
On Thursday, 2021-02-04 at 14:36 -0500, Michael Spartana wrote:
On 2/4/21 12:26 PM, Patrick Shanahan wrote: ...
Well, I see the group permission is wrong, it does not permit the group to write.
I have "fmask=133,dmask=022". I change to "fmask=0117,dmask=0007", and now it works:
cer@Legolas:~> cd /windows/C/Users/cer/Documents/ cer@Legolas:/windows/C/Users/cer/Documents> touch p cer@Legolas:/windows/C/Users/cer/Documents> l total 25 drwxrwx--- 1 root users 4096 Feb 4 22:22 ./ drwxrwx--- 1 root users 8192 Oct 17 2019 ../ drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ -rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini ... -rw-rw---- 1 root users 0 Feb 4 22:22 p I see you have write privileges....does it matter that it was root created. Problem is
that I don't do this changing file permissions enough to know it as well as I should
Notice that for ntfs you can not change file permissions: you change fstab instead, which is what I did, successfully.
Yes, Carlos...all posts I read where someone tried changing file
permissions created many problems when returning to windows...
That's not what I'm saying. Linux doesn't use the actual permissions of Windows filesystems: it /fakes/ them. So, when I first had: drwxr-xr-x 1 root users 4096 Aug 6 2018 Biblioteca exd/ --rw-r--r-- 1 root users 402 Oct 17 2019 desktop.ini And later I had: drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ --rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini I did not change any of the files permissions (or anything whatsoever in the files or their metadata). I told Linux to fake different permissions, by changing the appropriate option in fstab. Now, you do that and you get access to your files as user. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2/4/21 4:29 PM, Carlos E.R. wrote:
drwxr-xr-x 1 root users 4096 Aug 6 2018 Biblioteca exd/ --rw-r--r-- 1 root users 402 Oct 17 2019 desktop.ini
And later I had:
drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ --rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini
I did not change any of the files permissions (or anything whatsoever in the files or their metadata). I told Linux to fake different permissions, by changing the appropriate option in fstab
im confused. it appears that permissions for owner, group and everyone else. were actually changed?
On 05/02/2021 01.42, edward wrote:
On 2/4/21 4:29 PM, Carlos E.R. wrote:
drwxr-xr-x 1 root users 4096 Aug 6 2018 Biblioteca exd/ --rw-r--r-- 1 root users 402 Oct 17 2019 desktop.ini
And later I had:
drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ --rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini
I did not change any of the files permissions (or anything whatsoever in the files or their metadata). I told Linux to fake different permissions, by changing the appropriate option in fstab
im confused. it appears that permissions for owner, group and everyone else.
were actually changed?
Yes and no. Nothing was changed on the disk. What was changed is what Linux allows. It is a Windows filesystem, its real attributes and permissions are not supported. Instead, you tell via mount options what permissions you want, and Linux does it, for every single file on the windows partition. Every file gets the exact same permissions. Faked, so to speak. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2/4/21 7:29 PM, Carlos E.R. wrote:
On 05/02/2021 00.47, Michael Spartana wrote:
On 2/4/21 6:21 PM, Carlos E.R. wrote:
On 04/02/2021 22.50, Michael Spartana wrote:
On 2/4/21 4:28 PM, Carlos E. R. wrote:
On Thursday, 2021-02-04 at 14:36 -0500, Michael Spartana wrote:
On 2/4/21 12:26 PM, Patrick Shanahan wrote: ...
Well, I see the group permission is wrong, it does not permit the group to write.
I have "fmask=133,dmask=022". I change to "fmask=0117,dmask=0007", and now it works:
cer@Legolas:~> cd /windows/C/Users/cer/Documents/ cer@Legolas:/windows/C/Users/cer/Documents> touch p cer@Legolas:/windows/C/Users/cer/Documents> l total 25 drwxrwx--- 1 root users 4096 Feb 4 22:22 ./ drwxrwx--- 1 root users 8192 Oct 17 2019 ../ drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ -rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini ... -rw-rw---- 1 root users 0 Feb 4 22:22 p I see you have write privileges....does it matter that it was root created. Problem is
that I don't do this changing file permissions enough to know it as well as I should Notice that for ntfs you can not change file permissions: you change fstab instead, which is what I did, successfully. Yes, Carlos...all posts I read where someone tried changing file
permissions created many problems when returning to windows... That's not what I'm saying.
Linux doesn't use the actual permissions of Windows filesystems: it /fakes/ them. So, when I first had:
drwxr-xr-x 1 root users 4096 Aug 6 2018 Biblioteca exd/ --rw-r--r-- 1 root users 402 Oct 17 2019 desktop.ini
And later I had:
drwxrwx--- 1 root users 4096 Oct 17 2019 Biblioteca de calibre/ --rw-rw---- 1 root users 402 Oct 17 2019 desktop.ini
I did not change any of the files permissions (or anything whatsoever in the files or their metadata). I told Linux to fake different permissions, by changing the appropriate option in fstab.
Now, you do that and you get access to your files as user.
You know what, I think I'm going to reformat the 1 gig drive as EXT4. The 5 GB drive would be for windows. There really isn't much on the small drive. Thanks for all the advice. Then I can do anything without hurting the system and find easier solutions to problems.....mike
On 05/02/2021 02.14, Michael Spartana wrote:
On 2/4/21 7:29 PM, Carlos E.R. wrote:
On 05/02/2021 00.47, Michael Spartana wrote:
You know what, I think I'm going to reformat the 1 gig drive as
EXT4. The 5 GB drive would be for windows. There really isn't
much on the small drive. Thanks for all the advice. Then I can
do anything without hurting the system and find easier solutions
to problems.....mike
There is nothing complicated about what we discussed here, only that you are not familiar with the handling of Windows filesystems in Linux. If you want a filesystem that can be used nicely in both Linux and Windows, you should format as exfat, which is used by big usb sticks or flash cards. It is also understood by TV sets and cameras. Still, the permissions work using the same system as described here, via mount options. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
On 2021/02/04 09:26, Patrick Shanahan wrote:
note: as I am currently under censorship, I have cc'd you as many of my posts experience "extended" wait time for *approval*, sometimes >26 hours.
I don't think this is the case, since your post to the list arrived 9 minutes before the Cc you sent to the OP. There have been times in the past where I had high delays, but I think it was problems with the list SW (though, depending on "when", not saying thoughts similar to yours didn't cross my mind :^) ). Cheers!
04.02.2021 19:56, Michael Spartana пишет:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the
Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 #xavier #UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them.
Are you using kernel ntfs driver or ntfs-3g?
So how should I mount them. Is it a root problem or do
I need to change the permissions or something else.
Thanks for any help, mike spartana
On 2/4/21 1:42 PM, Andrei Borzenkov wrote:
04.02.2021 19:56, Michael Spartana пишет:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the
Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 #xavier #UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them. Are you using kernel ntfs driver or ntfs-3g?
well, they're mounted fuseblk so that would be ntfs-3g right?. I have the ntfs-3g in my rpm list of installed packages....I still have to try Patrick Shanahan' s method of entries
So how should I mount them. Is it a root problem or do
I need to change the permissions or something else.
Thanks for any help, mike spartana
04.02.2021 22:16, Michael Spartana пишет:
On 2/4/21 1:42 PM, Andrei Borzenkov wrote:
04.02.2021 19:56, Michael Spartana пишет:
Hi,
OK trying to mount a hard drive so I can install steam games (I have a 512 GB SSD with the OS -Tumbleweed-on it) and so I want the
Hard Drives for the installations. These are the 2 drives and this is the fstab entries I used:
#UUID=E4S46B88D46B5BB4 /home/ekim/mrmike ntfs defaults PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2 #xavier #UUID=D892118892116BEE /home/ekim/xavier ntfs defaults PARTUUID=5ae7b70a-f359-4bc6-9420-ab1913fd040c /home/ekim/xavier ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them. Are you using kernel ntfs driver or ntfs-3g?
well, they're mounted fuseblk so that would be ntfs-3g right?. I
By default FUSE restricts access to user who mounted filesystem, which in case of /etc/fstab entries is root. Try adding allow_other (see man fuse).
have the ntfs-3g
in my rpm list of installed packages....I still have to try Patrick Shanahan' s
method of entries
So how should I mount them. Is it a root problem or do
I need to change the permissions or something else.
Thanks for any help, mike spartana
On 2021/02/04 08:56, Michael Spartana wrote:
Hi,
OK trying to mount a hard drive ... PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them.
You say it is an ntfs drive which you are mounting locally on linux -- which will use the ntfs driver to interpret it. If you are root, the driver likely equates that to Admin on the drive and gives override capabilities on the drive, however a normal user wouldn't have those abilities, so I'm a bit surprised that there is even an option to specify a uid+mask and gid. It seems it might be viewed as a bit of a security issue to allow someone to ignore/override ntfs permissions just by mounting it on linux with directions to ignore access control. For the items you are trying to access, are the directories open to 'all' to write? Since you are specifying a uid for that is not the owner of the files, it seems a umask of 022 would lock out that user, but I'm not sure how much of the security functionality in ntfs the driver uses or understands.
On 05/02/2021 02.46, L A Walsh wrote:
On 2021/02/04 08:56, Michael Spartana wrote:
Hi,
OK trying to mount a hard drive ... PARTUUID=9ef08689-2e85-4ada-9b22-cf4533e076d0 /home/ekim/mrmike ntfs permissions,uid=1000,umask=022,gid=1000 0 2
They are mounted with me as a user owning them but I cannot write to them.
You say it is an ntfs drive which you are mounting locally on linux -- which will use the ntfs driver to interpret it. If you are root, the driver likely equates that to Admin on the drive and gives override capabilities on the drive, however a normal user wouldn't have those abilities, so I'm a bit surprised that there is even an option to specify a uid+mask and gid.
Why? It is in the man since ages. It is the same method than for fat and the old ntfs kernel driver. man mount.ntfs-3g OPTIONS Below is a summary of the options that ntfs-3g accepts. uid=value and gid=value Set the owner and the group of files and direc- tories. The values are numerical. The defaults are the uid and gid of the current process. umask=value Set the bitmask of the file and directory per- missions that are not present. The value is given in octal. The default value is 0 which means full access to everybody. fmask=value Set the bitmask of the file permissions that are not present. The value is given in octal. The default value is 0 which means full access to everybody. dmask=value Set the bitmask of the directory permissions that are not present. The value is given in octal. The default value is 0 which means full access to everybody.
It seems it might be viewed as a bit of a security issue to allow someone to ignore/override ntfs permissions just by mounting it on linux with directions to ignore access control.
Happens.
For the items you are trying to access, are the directories open to 'all' to write? Since you are specifying a uid for that is not the owner of the files, it seems a umask of 022 would lock out that user, but I'm not sure how much of the security functionality in ntfs the driver uses or understands.
If you look at the man page, you will see there is some support for acls. I have not studied it, but it seems rather complicated. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
participants (8)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E.R. -
edward -
jdd＠dodin.org -
L A Walsh -
Michael Spartana -
Patrick Shanahan