Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Well, I got so far: Root mounts the NTFS-Drives and can read them. But when the user tries to open the folder (e.g. /Windows/E), Linux says he doesn't have the necessary rights to open the folder.
I tried to use chmod 777 before mounting the drive, but it didn't work.
fstab looks like this:
/dev/hdb7 /windows/E ntfs auto,user 0 0
Thanks for your answers, and please forgive my English, I'm from Germany.
Well.... at least the user can open the folder now
When the drives get mounted on startup, they appear as /windows/E and /windows/F, before I changed fstab the user wasn't able to open the folder at all (it had a lock as icon) and root could read the files in it, and now the user can open the folder, but it's empty. Root can read the folders nevertheless.
Originally posted by Fred Affe Well.... at least the user can open the folder now
When the drives get mounted on startup, they appear as /windows/E and /windows/F, before I changed fstab the user wasn't able to open the folder at all (it had a lock as icon) and root could read the files in it, and now the user can open the folder, but it's empty. Root can read the folders nevertheless.
What does "umask" do?
This is what I have, edit it to fit yours:
/dev/hda1 /mnt/windows ntfs ro,umask=0222 0 0
Works fine, all users with read only permission
Quote:
umask is a filter of permissions, so it works in the opposite way to chmod. Full permissions are equivalent to 777 (rwxrwxrwx). A umask of 0222 (-w--w--w-) leaves 555 (r-xr-xr-x).
You havent answered my question - I pointed out that Fred would need an auto option in his fstab entry to have his Windows partition automatically mounted on boot up.
To that you replied
Quote:
Hmm, strange, mine does, lol.
implying that you have your Windows partition automatically mounted on boot up without an auto option
So I'll ask you again - is it possible to have your Windows partition automatically mounted on boot up without an auto option?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.