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!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The reason is simple FAT partition being a propriatery toy from a well known company isn't aware of linux permissions. To set it up you need to edit
put the line there
/dev/hdb1 /mnt/windows vfat noauto,user,owner,umask=0770,rw 0 0
P.S. Assuming your windows fat partition is on /dev/hdb1 and the mount point is /mnt/windows
don't use the umask=0770. that yields a mount permissions of:
--- - --- - rwx
where the owner of the partition (default is root) and group owner of the partition (default again root) have no access.
if you don't want to make groups to have certain users have full access to your partitions and just want to have everyone under the sun be able to troll around your windows partitions, use umask=0000. this yields a mount permissions of:
edit: if it were me, i'd do something like this in fstab:
/dev/hda1 = windows C:\
/dev/hda5 = windows D:\
umask=0007 -> mount permissions of rwx - rwx - ---
umask=0002 -> mount permissions of rwx - rwx - r-x
basically for windows, i have it set for other to have no permissions due to the fact that allowing others to have read/exec access can constitute a security hole in that other user's can grab password files from windows, windows apps, and 3rd party apps that use passwords when logged into linux. but i would then create a windows group and put in users that i want to have full permissions on windows partitions, like your user account for convenience. setting a umask to 0002 will still let other users read/exec files/directories on that partition. anyway, for me mounting windows partitions should be thought out on what kind of permissions you wish to set. it also helps to figure out where 3rd party apps that do use passwords where they store those passwords so you can secure that partition accordingly. after all, you spend all that time to secure windows when you boot into windows, it doesn't make sense to leave windows open when booted in linux. of course this depends how you're going to use your computer. if you're the only one going to use this computer then, all this is pretty overkill. if going to allow multiple users like i do, then you might want to take into consideration such things. also take into account what might happen if one of your accounts gets hacked and owned. just my 2 cents.
Actually, you can change the permissions of mount point itself (because it's a normal Linux directory), but you can't change them while a Windows filesystem is mounted there. It won't do the trick anyway though, because when the Win filesystem gets mounted the default mask (write permissions for root only) will be applied. That's where the "umask" option comes into play- it overrides the default.
Originally posted by DMR Actually, you can change the permissions of mount point itself (because it's a normal Linux directory), but you can't change them while a Windows filesystem is mounted there. It won't do the trick anyway though, because when the Win filesystem gets mounted the default mask (write permissions for root only) will be applied. That's where the "umask" option comes into play- it overrides the default.