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.
This is probably easy to fix, I have installed the slackware 9.0 experience now.
I was installing from the cd-rom , and I just installed it over yhe old 8.1.
When prompted if I wanted to formating my / partition , I choosed NO .
Everything seems to work ok , exept from one thing:
this is the problem:
When logging in as an ordinary user, I can't access my mounted FAT32 partitions, I can howewer access them as root.
I did not have any problems accessing partitions, with the 8.1 release.
I discovered yesterday that Slack 9.0 does not use the default umask setting from /etc/profile the way it should and the way it has been in the past. You need to mount the vfat partitions using a mount option to set the umask to 022 or 000. It is now mounting the partitions with a umask of 033 unless it is instructed otherwise. If you use the /etc/fstab to mount the partition at boot, then add it to the options as umask=000. If you mount manually or through rc.local then use "-o umask=000" in the mount command. Perhaps it will help with your problem.
In my tests the umask setting was 033 instead of the set default umask. Now, 033 should produce rwxr--r-- permissions that should allow read for all users. However, if some programs have problems with it then add the umask setting of 022 and that would be using the Slack default (rwxr-xr-x). Also, there are two new settings available, fmask and dmask. You can review the man page (man mount) for more info regarding the use.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.