Slack 9: mounted FAT32 partitions cannot be accessed by normal user
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When a partition type of vfat is mounted, the system will mask the full permision set 777 with the umask setting, thus producing the the permisions for the mount point. So the umask is an inverse of the desired settings. For example; full permisions are rwxrwxrwx or 777. If you desire, rwxr--r-- or 744, then a umask of 033 would be correct. For rwxr-xr-x or 755, a umask of 022 would be correct. Notice the numbers will add up to 7 in each column.
Now for the problem or change in Slack 9.0. The system default umask setting is 022 and that is set in /etc/profile. This setting has not changed. However, the mount command has been modified to include some new options, fmask and dmask, and in the process the system umask setting is not being used. The mount command is defaulting to a umask setting of 033, producing 744 permisions (rwxr--r--). Even if the default umask is set to 000, it continues to use a 033 setting. However, if you force the command by providing the option for the umask setting then it will use it properly.
To manually mount with rwxr-xr-x;
mount -t vfat -o umask=022 /dev/hd?? /mnt/point
To mount from /etc/fstab with rwxrwxrwx;
/dev/hd?? /mnt/point vfat defaults,umask=000 0 0
quiet => it won't complaint if you try to chmod a file there, or
use midnight commander to copy file to it.
shortname=mixed => it can consistently store upper/lower case filename.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.