On Tue, 14 Mar 2000, you wrote:
> You can leave them on at boot, just change the umask to 0. The umask
> permissions are exactly inverted from the normal chmod permissions,
> which throws most people off. For instance, if you want to allow no
> writes or reads to the drive (don't know why you would), the umask
> would be 777. If you want anyone to have access to read and write and
> execute, the umask is 000. Backwards, but it works.
>
> No need to get cranky at the default fstab, although putting things
> under /mnt/DOS_hda1 was odd. I prefer a bit SHORTER mount point myself.
> :-)
Well, since it is a nice desktop icon in KDE, you can rename it right there.
My users see a "windows" drive on their desktops (without any change in
mount point) though all network functions are now disabled for their windows
boots, the icon is there for porting their files and occasionally for storing
the odd *.exe file sent as an email attachment.
Civileme
> > On 15 Mar, Ron Stodden wrote: > > Andrew,
> >
> > Write permission for vfat file systems at mount time is only provided
> > to the user that does the mount. So that is what you should do -
> > have the user who wants to write be the one that does the mount and
> > eventual umount.
> >
> > But first as root alter /etc/fstab to make all the vfat mounts noauto
> > (as the installer should have done), then reboot.
>
> --
>
> -----------
> Nil Carborundum Illegitimi
> http://andysocial.com
