From 90b9e3f1996c214f95987b685530d449eb5efeb2 Mon Sep 17 00:00:00 2001 From: Robert Watson Date: Fri, 26 Mar 2004 03:26:15 +0000 Subject: [PATCH] Correct the definition of the multilabel flag: it enables multilabel MAC support on the file system, if supported, which causes MAC to treat each object as having its own label, rather than using a single label for all objects on the file system. This doesn't have to be used in combination with the tunefs/newfs flags -- it's an alternative. --- sbin/mount/mount.8 | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/sbin/mount/mount.8 b/sbin/mount/mount.8 index 4d99ddd4ecb5..af164db616c3 100644 --- a/sbin/mount/mount.8 +++ b/sbin/mount/mount.8 @@ -147,14 +147,19 @@ flag, this is the same as specifying all the options listed in the .Xr fstab 5 file for the file system. .It Cm multilabel -Enable Mandatory Access Control, or MAC. -Must be used in conjunction with the +Enable multi-label Mandatory Access Control, or MAC, on the specified file +system. +If the file system supports multilabel operation, individual labels will +be maintained for each object in the file system, rather than using a +single label for all obejcts. +An alternative to .Em -l flag in .Xr tunefs 8 . See .Xr mac 4 -for more information. +for more information, which cause the multilabel mount flag to be set +automatically at mount-time. .It Cm noasync Metadata I/O should be done synchronously, while data I/O should be done asynchronously.