Re: Coercing sane file permissions -- site specific
On 11/20/2016 6:33 AM, Nicolas George wrote:
Le decadi 30 brumaire, an CCXXV, Richard Owlett a écrit :
Not as I read them.
Then you did not read correctly.
https://manned.org/fstab.5 states
"
The first field (fs_spec).
This field describes the block special device or remote
filesystem
to be mounted.
...
LABEL=<label> or UUID=<uuid> may be given instead of a device
name. This is the recommended method, as device names are
often a
coincidence of hardware detection order, and can change
when other
disks are added or removed. For example, `LABEL=Boot' or
UUID=3e6be9de-8139-11d1-9106-a43f08d823a6'. (Use a
filesystem-
specific tool like e2label(8), xfs_admin(8), or
fatlabel(8) to set
LABELs on filesystems).
It's also possible to use PARTUUID= and PARTLABEL=. These
partitions identifiers are supported for example for GUID
Partition Table (GPT).
"
They give methods of handling an explicitly specified device.
Tomas' answer contains the solution to your problem: the umask mount
option. This it, no more no less.
On 11/19/2016 2:33 PM, tomas@tuxteam.de wrote:
Use the "umask" option when mounting the file system. Umask is
supposed to be the bits *not* to set in the file permissions.
That would be
mount /dev/foo mnt -oumask=000
That works for an explicit value of "foo".
Maybe the problem is D.E. specific? I'm using MATE and thus Caja
as file-manager.
On top menu-bar Places will list identifiers for mountable devices.
Clicking the "identifier" will "mount" the identified device.
It will use information available from /etc/fstab and/or
pmount.allow .
Neither appears to have an entry equivalent to "any FAT
filesystem on plugable device".
To know how to actually use it, re-read Tomas' answer, RTFM, RTFW or
hire a consultant. But you have your answer.
Reply to: