Documentation/filesystems/sharedsubtree.txt needs updating because the mount command in util-linux package is well aware of shared subtree features now. The patch also fixes two typos in sharedsubtree.txt. Signed-off-by: Peng Tao <bergwolf@xxxxxxxxx> --- Documentation/filesystems/sharedsubtree.txt | 37 ++++++++++++++++----------- 1 files changed, 22 insertions(+), 15 deletions(-) diff --git a/Documentation/filesystems/sharedsubtree.txt b/Documentation/filesystems/sharedsubtree.txt index 7365400..b07f377 100644 --- a/Documentation/filesystems/sharedsubtree.txt +++ b/Documentation/filesystems/sharedsubtree.txt @@ -4,7 +4,7 @@ Shared Subtrees Contents: 1) Overview 2) Features - 3) smount command + 3) Setting mount states 4) Use-case 5) Detailed semantics 6) Quiz @@ -137,11 +137,18 @@ replicas continue to be exactly same. Binding a unbindable mount is a invalid operation. -3) smount command +3) Setting mount states + + The mount command ( util-linux package ) can be used to set mount + states: + + mount --make-shared mountpoint + mount --make-slave mountpoint + mount --make-private mountpoint + mount --make-unbindable mountpoint + + Also, the following smount program can be used to set mount states. - Currently the mount command is not aware of shared subtree features. - Work is in progress to add the support in mount ( util-linux package ). - Till then use the following program. ------------------------------------------------------------------------ // @@ -227,13 +234,13 @@ replicas continue to be exactly same. command: smount /mnt rshared - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-rshared /mnt just to mark a mount /mnt as shared, execute the following command: smount /mnt shared - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-shared /mnt (ii) To mark all the shared mounts under /mnt as slave execute the @@ -241,26 +248,26 @@ replicas continue to be exactly same. command: smount /mnt rslave - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-rslave /mnt just to mark a mount /mnt as slave, execute the following command: smount /mnt slave - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-slave /mnt (iii) To mark all the mounts under /mnt as private execute the following command: smount /mnt rprivate - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-rprivate /mnt just to mark a mount /mnt as private, execute the following command: smount /mnt private - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-private /mnt NOTE: by default all the mounts are created as private. But if @@ -272,13 +279,13 @@ replicas continue to be exactly same. command: smount /mnt runbindable - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-runbindable /mnt just to mark a mount /mnt as unbindable, execute the following command: smount /mnt unbindable - the corresponding syntax planned for mount command is + the corresponding syntax for mount command is mount --make-unbindable /mnt @@ -350,7 +357,7 @@ replicas continue to be exactly same. mount --rbind / /view/v3 mount --rbind / /view/v4 - and if /usr has a versioning filesystem mounted, than that + and if /usr has a versioning filesystem mounted, then that mount appears at /view/v1/usr, /view/v2/usr, /view/v3/usr and /view/v4/usr too @@ -390,7 +397,7 @@ replicas continue to be exactly same. For example: mount --make-shared /mnt - mount --bin /mnt /tmp + mount --bind /mnt /tmp The mount at /mnt and that at /tmp are both shared and belong to the same peer group. Anything mounted or unmounted under -- 1.6.2.GIT -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
