Accessing Win98 partition

[Jeffrey Wong]

The umask=0 tells mount what permissions to remove from the partition (0
means don't remove any permissions).  Generally speaking, umask is an
inverse bitmask that should be applied to files, so a umask of 0 applied
to any file will keep the original permissions, while a umask of 777 would
remove all permissions.

Jeff

On Tue, 2 Oct 2001, Rodney Kanno wrote:

> Hi Brian,
> 
> Yeah I am using wine, and I do store unix binaries on there hehee. That drive 
> is pretty much a storage drive for both windows and linux as well as fir 
> running a few programs. what's umask=0 do? I just copied my old fstab file 
> that's why.
> 
> Thanks,
> Rodney
> 
> On Tuesday 02 October 2001 06:23 am, you wrote:
> > On Mon, Oct 01, 2001 at 08:43:55PM -0400, Rodney Kanno wrote:
> > > instead of being like this:
> > >
> > > /dev/hdb1 /mnt/win_c2 vfat
> > > user,exec,umask=0,iocharset=iso8859-1,codepage=850 0 0
> > >
> > > it was like this:
> > >
> > > /dev/hdb1 /mnt/win_c2 vfat iocharset=iso8859-1,codepage=850 0 0
> > >
> > > is this okay? I mean I can write to the drive now, but is the the
> > > "correct" way it is supposed to be set up?
> >
> > Are you sure you want exec as an option? I'd probably make it noexec
> > and nosuid, looks fine apart from that though. Again, I don't have
> > any vfat partitions lying around though..
> >
> > Only reason you might want to make it exec is if you're using wine,
> > or if you have unix binaries on there.. which would be a bit odd
> > frankly.
> 
> ---
> You are currently subscribed to luau as: jmwong at hoku.net
> To unsubscribe send a blank email to $subst('Email.Unsub')
>