- Fix up FAQ entry on chmod(1)'s behavior regarding symlinks

PR:		docs/143926
Submitted by:	Franklin Pierce <14th.president@gmail.com>
This commit is contained in:
Gabor Pali 2010-07-15 20:39:57 +00:00
parent 13169bb986
commit 224fbcff07
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=36021

View file

@ -10137,8 +10137,8 @@ hint.sio.7.irq="12"</programlisting>
<answer>
<para>Symlinks do not have permissions, and by default,
&man.chmod.1; will not follow symlinks to change the
permissions on the target file. So if you have a file,
&man.chmod.1; will follow symlinks to change the
permissions on the source file, if possible. So if you have a file,
<filename>foo</filename>, and a symlink to that file,
<filename>bar</filename>, then this command will always
succeed.</para>
@ -10148,7 +10148,9 @@ hint.sio.7.irq="12"</programlisting>
<para>However, the permissions on <filename>foo</filename>
will not have changed.</para>
<para>You have to use either <option>-H</option> or
<para>When changing modes of the file hiearchies rooted in the
files instead of the files themselves,
you have to use either <option>-H</option> or
<option>-L</option> together with the <option>-R</option>
option to make this work. See the &man.chmod.1; and
&man.symlink.7; manual pages for more info.</para>