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.
Whenever I boot my machine and go into root i have full permissions. Whenever I log in as a user however I cannot get write mode working. Logging into root will let me save files as root.
I tried swtting up my user as a sudoer. This was actually a challenge as I have never used vi and or visudo, but i conquered that issue. Short story long, sudo works but again no rwx for user.
So what I am guessing is take the solution from the thread I posted and insert it into the appropriate startup script.
Is this correct or is there an easier solution I skimmed over in slackbook?
If I understand correctly, you have a VFAT partition and you wish to have regular users provided with write access to it. You have found that the following command sets things up properly and therefore wish to have this "autoconfigured" at bootup.
Quote:
mount -t vfat /dev/sda1 /media/hdd -o rw,uid=0,gid=104,umask=000
The "proper" way to accomplish this at bootup is to edit the /etc/fstab file and add the following line:
Ah, it is my storage drive I am talking about, although I have 3 drives that mount at bootup to the /drives/ directory I created specificly for that durning instalation.
So I have no problem re-mounting the drive(s) with proper permissions and getting the correct access mode. I don't quite know where in the bootup process the script is that mounts those drives, I just want to alter it slightly so I dont have to do this every time i log in.
If I understand correctly, you have a VFAT partition and you wish to have regular users provided with write access to it. You have found that the following command sets things up properly and therefore wish to have this "autoconfigured" at bootup.
The "proper" way to accomplish this at bootup is to edit the /etc/fstab file and add the following line:
It was in that example (fat32). Its NTFS in this one. Looks like we were replying at the same time.
one more question, how do I find or assign group ID to each user. In the example from the previous thread i was running fedora and gid 104 worked fine. It does not apply here i dont think as i cannot save, however the folder is green which means it worked, now i just have to make it work for the correct user.
Once I figure that out I can edit those lines into my /etc/fstab. I completely forgot about that file because i was reading slackbook and it mentions several scripts that it loads and this one
Quote:
rc.local
Contains any specific startup commands for your system. This is empty after a fresh install, as it is reserved for local administrators. This script is run after all other initialization has taken place.
looked like it would work, but didnt have the command in it. I didnt want to tell my drives to mount here if something that was loading before it already told them to mount a certain way.
**
reading is fundamental. its in /etc/passwd
shows me my gid and uid so i can use either.**
Last edited by linuxpokernut; 11-24-2008 at 02:40 AM.
Gets me in there but when I go to save a file, access denied. I am stumped.
*Problem solved, thank you*
If anyone wants to explain what the 2 numbers after the umask in the fstab file signify however i would like to understand better. Thank you for the help.
The fifth field of an fstab entry indicates how often the partition should be backed up (1=every day, 2=every other day, etc). I believe it is ignored in modern GNU/Linux systems but Patrick seems to put a "1" there and I trust his judgment.
The sixth field indicates the order in which 'fsck' is to be executed during bootup. The root partition should be checked first and so the sixth field for its entry should "1". The order of other partitions should not matter and their entries should contain a "2" (unless 'fsck' is never to be run for the partition, in which case the sixth field should contain "0").
Perhaps for a VFAT partition, the sixth field should be set to "0" -- I don't use Microsoft partitions so I'm not sure.
mount -t ntfs /dev/hdb1 /drives/storage -o rw,uid=your_uid,gig=your_gid
and
mount -t ntfs /dev/hdb1 /drives/storage -o rw,umask=000
Yes, I tried both of those before I edited my fstab, neither method worked, once i did that (edited fstab) everything works fine. I was just asking about the 5th and 6th fields as I wanted to know what i was doing, not just cut/paste/forget.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.