os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Typos fixing

Browse source 
- Remove contractions
- s/I/we
This commit is contained in:
Marc Fonvieille 2003-01-01 15:37:54 +00:00
parent d2a14426bc
commit b341d7163f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=15497
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -258,15 +258,15 @@
<listitem>
<para>The mount-time <acronym>ACLs</acronym> flag cannot be changed by a
remount (&man.mount.8; <option>-u</option>), only by means of a complete
<command>unmount</command> and fresh &man.mount.8;. This means that
&man.umount.8; and fresh &man.mount.8;. This means that
<acronym>ACLs</acronym> cannot be enabled on the root file system after boot.
It also means that you cannot change the disposition of a file system once
it's in use.</para>
it is in use.</para>
</listitem>
<listitem>
<para>Setting the superblock flag will cause the file system to always be
mounted with <acronym>ACLs</acronym> enabled even if there isn't an
mounted with <acronym>ACLs</acronym> enabled even if there is not an
<filename>fstab</filename> entry or if the devices re-order. This prevents
accidental mounting of the file system without <acronym>ACLs</acronym>
enabled, which can result in <acronym>ACLs</acronym> being improperly enforced,
@ -274,12 +274,12 @@
</listitem>
</itemizedlist>
<note><para>We may change the <acronym>ACL</acronym> behavior to allow the flag to
be enabled without a complete fresh &man.mount.8;, but I consider it desirable to
<note><para>We may change the <acronym>ACLs</acronym> behavior to allow the flag to
be enabled without a complete fresh &man.mount.8;, but we consider it desirable to
discourage accidental mounting without <acronym>ACLs</acronym> enabled, because you
can shoot your feet quite nastily if you enable <acronym>ACLs</acronym>, then disable
them, then re-enable them without flushing the extended attributes. In general, once
ou have enabled <acronym>ACLs</acronym> on a file system, they should not be disabled,
you have enabled <acronym>ACLs</acronym> on a file system, they should not be disabled,
as the resulting file protections may not be compatible with those intended by the
users of the system, and re-enabling <acronym>ACLs</acronym> may re-attach the previous
<acronym>ACLs</acronym> to files that have since had their permissions changed,