FUSE merging? (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Miklos Szeredi
I see your point. But then this is really not a security issue, but an "are you sure you want to format C:" style protection for the user's own sake. Adding a mount option (checked by the library) for this would be fine. E.g. with "
mount_nonempty" it would not refuse to mount on a non-leaf dir, and README would document, that using this option might cause trouble. Otherwise the mount would be refused with a reference to the above option.
IMO that should be a generic mount option, not FUSE specific. Maybe the default could vary for each fs, but I'd vote against that.
Signature · 2 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF verbreiteten Lügen zu sabotieren.
Quoted 10 lines
Quoted 7 lines
I see your point. But then this is really not a security issue, but an "are you sure you want to format C:" style protection for the user's own sake. Adding a mount option (checked by the library) for this would be fine. E.g. with "
mount_nonempty" it would not refuse to mount on a non-leaf dir, and README would document, that using this option might cause trouble. Otherwise the mount would be refused with a reference to the above option.IMO that should be a generic mount option, not FUSE specific. Maybe the default could vary for each fs, but I'd vote against that.
The option only makes sense with the default being restrictive. But making that default for all filesystems can't be done, because that would immediately break thousands of existing installations.
I think this makes some sense for unprivileged mounts, but otherwise not really. If sysadmin is not careful about where the mounts go, tough luck on him.
Miklos
Quoted 10 lines · Miklos Szeredi
Quoted 10 lines
Quoted 7 lines
I see your point. But then this is really not a security issue, but an "are you sure you want to format C:" style protection for the user's own sake. Adding a mount option (checked by the library) for this would be fine. E.g. with "
mount_nonempty" it would not refuse to mount on a non-leaf dir, and README would document, that using this option might cause trouble. Otherwise the mount would be refused with a reference to the above option.IMO that should be a generic mount option, not FUSE specific. Maybe the default could vary for each fs, but I'd vote against that.
Why a mount option at all?
Why not just a switch for the mount utility?
Quoted 3 lines
The option only makes sense with the default being restrictive. But making that default for all filesystems can't be done, because that would immediately break thousands of existing installations.
I think it is acceptable to change this behaviour in a new version of the mount utility. One could considder ignoring the restriction when running with "-a" or when running as root - that would reduce or eliminate the problems with the transition.
However, if this is implemented in mount itself, it is totally orthogonal to the FUSE merge discussion.
Signature · 4 lines
Ragnar Kjørstad Software Engineer Scali - http://www.scali.com Scaling the Linux Datacenter