summaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/udf.txt
diff options
context:
space:
mode:
authorPhillip Susi <psusi@cfl.rr.com>2006-03-25 03:08:14 -0800
committerLinus Torvalds <torvalds@g5.osdl.org>2006-03-25 08:23:00 -0800
commit0e6b3e5e97e2e8a25bcfc528dad94edf5220dfeb (patch)
treede537ca068cd7fc2a1d20a47f16c9091cf4c64ff /Documentation/filesystems/udf.txt
parent11b0b5abb2097a63c1081d9b7e825b987b227972 (diff)
downloadkernel-crypto-0e6b3e5e97e2e8a25bcfc528dad94edf5220dfeb.tar.gz
kernel-crypto-0e6b3e5e97e2e8a25bcfc528dad94edf5220dfeb.tar.xz
kernel-crypto-0e6b3e5e97e2e8a25bcfc528dad94edf5220dfeb.zip
[PATCH] udf: fix uid/gid options and add uid/gid=ignore and forget options
As Pekka Enberg pointed out, with the if still following the else, you can still get a null uid written to the disk if you specify a default uid= without uid=forget. In other words, if the desktop user is uid=1000 and the mount option uid=1000 is given ( which is done on ubuntu automatically and probably other distributions that use hal ), then if any other user besides uid 1000 owns a file then a 0 will be written to the media as the owning uid instead. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'Documentation/filesystems/udf.txt')
-rw-r--r--Documentation/filesystems/udf.txt14
1 files changed, 14 insertions, 0 deletions
diff --git a/Documentation/filesystems/udf.txt b/Documentation/filesystems/udf.txt
index e5213bc301f..511b4230c05 100644
--- a/Documentation/filesystems/udf.txt
+++ b/Documentation/filesystems/udf.txt
@@ -26,6 +26,20 @@ The following mount options are supported:
nostrict Unset strict conformance
iocharset= Set the NLS character set
+The uid= and gid= options need a bit more explaining. They will accept a
+decimal numeric value which will be used as the default ID for that mount.
+They will also accept the string "ignore" and "forget". For files on the disk
+that are owned by nobody ( -1 ), they will instead look as if they are owned
+by the default ID. The ignore option causes the default ID to override all
+IDs on the disk, not just -1. The forget option causes all IDs to be written
+to disk as -1, so when the media is later remounted, they will appear to be
+owned by whatever default ID it is mounted with at that time.
+
+For typical desktop use of removable media, you should set the ID to that
+of the interactively logged on user, and also specify both the forget and
+ignore options. This way the interactive user will always see the files
+on the disk as belonging to him.
+
The remaining are for debugging and disaster recovery:
novrs Skip volume sequence recognition