l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 Feb 17 14:09

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] FSTAB Questions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] FSTAB Questions

Gee. What else could be said on this topic?

Heh heh heh...
(comments below)

Robert G. Scofield said:
> 1)  Does this order look okay?  Is /dev/hda1 in the right place?  Man
> fstab
> says that order is important.

Other answered this well enough in this thread.

> 2)  Instead of "umask=0" I originally tried "defaults", and then
> "rw,user."
> But with these, Open Office couldn't write to the Windows files.  (I've
> haven't tried backing up yet.)  Umask=0 is working fine.  But here's the
> question.  I've come across an old Mandrake 9.0 fstab and here's the entry
> for the Windows partition:
> /dev/hda1   /mnt/windows   vfat   iocharset=iso8859-1,codepage=850,umask=0
> 0 0
> Is there some advantage to having this sort of complicated entry?  Will I
> screw something up with my simple umask=0?  Should I copy the Mandrake
> entry
> into my SuSE system?


I did not see any mention of this so I'll comment on it.

On a multi-user system with a mounted windows filesystem, you may have
desire for everyone to have read access, but only a few to have write
access to the mounted windows volume. Here is what I have found to work:

/dev/hda1  /mnt/dosc vfat     defaults,user,auto,uid=win,gid=win,umask=002
 0  0

Focus on the options "uid=" and "gid=" and the "umask" otion discussed by

Of couse your mount point and your device will differ, and you may have
other options to add, the above is very useful.

First, create a user named "win" (example) and set its shell to be
/bin/false and set the password to be invalid for any crypt (! or * for
example in password field)

Also, create a group called "win".

Then, when the above options are read during the mount, the mount has a
directory tree of files chmod 775 , owned by "win" and group "win".

As a result, you can locate anyone into the "win" group and they can all
read and write to the windows share. This permits all of these users to
have write access at the same time and makes the volume always available
on boot.

By alternative, you can set the mount option to 007 and then nobody can
read unless they are amember of the win group.

I use this on a few systems that have multiple users and a mounted windows
filesystem.( umask 007 )

If you have users on your system that you do not completely trust, you
probably do not want to expose a bootable windows filesystsm to read
access. Files can be copied off the volume for cracking purposes to use
the next time the windows system is "booted" (this assumes that the
windows volume can be booted and would be.)

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Sunset Systems
Who graciously hosts our website & mailing lists!