Thanks Steve, this makes sense. Pleased to report that again this
morning things appear to be working "normally".
steve wrote:
Roger Searle wrote:
I have umask=0. Is this the same as umask=0 0 0
umask = 0 means that you're making no restrictions at all on who can
access files that you create. Not that I think you can on a vfat
formatted partition anyway. This is the same as umask 000 ( or 0000 ),
but umask 0 0 0 has no extra meaning.
/dev/hda5 /mnt/win_d vfat codepage=850,umask=0,iocharset=iso8859-1 0 0
Also a couple of lines I thought were interesting:
none /mnt/cdrom supermount
dev=/dev/hdd,fs=udf:iso9660,ro,--,iocharset=iso8859-1 0 0
none /mnt/floppy supermount
Why do they start with "none"? The drive is mounted - at least I can
view files on the CD. As you can see, I'm still confused by most
things linux, but hanging in there and learning slowly.
This is because you're using a 'third party' or 'external' routing to
actually perform the mount for removable devices. In this case, the
program is supermount ( Mandrake is the only distro I've seen it in,
but then I've not been looking ). You can use an entry like
/dev/cdrom /mnt/cdrom udf,iso9660
noauto,owner,kudzu,ro 0 0
which will mount your cdrom and make the contents available to you
under the mount point /mnt/cdrom, but you have to manually mount
first, and, of course, there are options in between where it's
automounted. It's the physical pressing of the eject button that
screws things up in the old world.
The real conceptual difference between linux and windoze here is that
when you mount a cd, floppy, disk partition, or anything else, it
becomes a seamless part of the hierarchical directory ( folder )
structure that starts at /, and works on down. There are no real
restrictions on where you put it ( one of the numbers at the end of
the line tells you which pass to mount it on, so if you want to mount
separate partitions/CD's... below each other, eg /, /usr, /usr/local,
/usr/local/cdrom, you can organise it so that the parent is available
before the child ), and you can move them around, replace one with
another ( if a directory that is populated is used as a mount point,
then the original population disappears - can be very useful in
testing software! ), and so on. There is no equivalent of a c:, d:,
etc drive... a concept that M$ are only slowly warming to.
Hopefully I made some sense (:
Steve
Roger
Alasdair Tennant wrote:
On Wed, 28 Jul 2004 18:14:51 +1200
Roger Searle <[EMAIL PROTECTED]> wrote:
Hi, I seem to have lost write access to my folders (has been fine up
to now).
Looking in Konqueror the permissions for all the folders on the
partition are shown as rwxrwxrwx, which I thought would be OK? (I
don't know the command to show this). So it seems the
permissions themselves are good, something else is going on.
My drive is mounted thus:
/dev/hda6 on /winshare type vfat (rw,umask=007,gid=1003)
My fstab reads:
/dev/hda6 /winshare vfat
umask=007,gid=famten 0 0
N.B. the umask=007. I had the same problem till I sussed this one.
I'm told that this is specific to FAT mounts, to spoof enough
permissions that aren't possible with FAT. The umask=007 combined
with gid=1003 gives the owner and any member of group 1003 full
access, rest-of-the world none. use umask=000 for all access to
everyone. Thanks go to the kind soul who helped me out with a
super-clear description.
