Wrap root in <username>.
PR: docs/37532 Submitted by: Martin Heinen <martin@sumuk.de> Approved by: murray
This commit is contained in:
parent
459ac1baba
commit
35716bf6ec
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12907
14 changed files with 37 additions and 37 deletions
|
@ -2386,7 +2386,7 @@ ISDN BRI line</literallayout>
|
|||
<filename>/etc</filename> directory of the NIS master, with one
|
||||
exception: the <filename>/etc/master.passwd</filename> file.
|
||||
This is for a good reason; you do not want to propagate
|
||||
passwords to your root and other administrative accounts to
|
||||
passwords to your <username>root</username> and other administrative accounts to
|
||||
all the servers in the NIS domain. Therefore, before we
|
||||
initialize the NIS maps, you should:</para>
|
||||
|
||||
|
@ -2398,7 +2398,7 @@ ISDN BRI line</literallayout>
|
|||
(<username>bin</username>, <username>tty</username>, <username>kmem</username>,
|
||||
<username>games</username>, etc), as well as any accounts that you
|
||||
do not want to be propagated to the NIS clients (for example
|
||||
root and any other UID 0 (superuser) accounts).</para>
|
||||
<username>root</username> and any other UID 0 (superuser) accounts).</para>
|
||||
|
||||
<note><para>Make sure the
|
||||
<filename>/var/yp/master.passwd</filename> is neither group
|
||||
|
@ -3413,7 +3413,7 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 libscrypt.so@ -> libscrypt.so.2
|
|||
you should be warned that <devicename>bpf</devicename>
|
||||
is also the device that allows packet sniffers to work
|
||||
correctly (although they still have to be run as
|
||||
root). <devicename>bpf</devicename>
|
||||
<username>root</username>). <devicename>bpf</devicename>
|
||||
<emphasis>is</emphasis> required to use DHCP, but if
|
||||
you are very sensitive about security, you probably
|
||||
should not add <devicename>bpf</devicename> to your
|
||||
|
@ -4478,7 +4478,7 @@ www IN CNAME @</programlisting>
|
|||
following checklist, it is assumed that the path to the sandbox
|
||||
is <filename>/etc/namedb</filename> and that you have made no
|
||||
prior modifications to the contents of this directory. Perform
|
||||
the following steps as root.</para>
|
||||
the following steps as <username>root</username>.</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
@ -5832,7 +5832,7 @@ lp0: TCP/IP capable interface</screen>
|
|||
both computers.</para>
|
||||
|
||||
<para>Configure the network interface parameters for lp0 on both
|
||||
sites as root. For example, if you want connect the host host1
|
||||
sites as <username>root</username>. For example, if you want connect the host host1
|
||||
with host2</para>
|
||||
|
||||
<programlisting> host1 <-----> host2
|
||||
|
|
|
@ -793,7 +793,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
|
|||
floppies.</para>
|
||||
|
||||
<para>To backup all the files in the current directory and sub-directory
|
||||
use this (as root):</para>
|
||||
use this (as <username>root</username>):</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>tar Mcvf /dev/fd0 *</userinput></screen>
|
||||
|
||||
|
|
|
@ -607,7 +607,7 @@ boot:</screen>
|
|||
<para>If the system <literal>console</literal> is set
|
||||
to <literal>insecure</literal> in
|
||||
<filename>/etc/ttys</filename>, then the system prompts for
|
||||
the root password before initiating single-user mode.</para>
|
||||
the <username>root</username> password before initiating single-user mode.</para>
|
||||
|
||||
<example id="boot-insecure-console">
|
||||
<title>An Insecure Console in /etc/ttys</title>
|
||||
|
@ -623,7 +623,7 @@ console none unknown off insecure</programlisting>
|
|||
<para>An <literal>insecure</literal> console means that you
|
||||
consider your physical security to the console to be
|
||||
insecure, and want to make sure only someone who knows the
|
||||
root password may use single-user mode, and it does not
|
||||
<username>root</username> password may use single-user mode, and it does not
|
||||
mean that you want to run your console insecurely. Thus,
|
||||
if you want security, choose <literal>insecure</literal>,
|
||||
not <literal>secure</literal>.</para>
|
||||
|
|
|
@ -381,7 +381,7 @@ exit 0
|
|||
|
||||
<para>The startup scripts of FreeBSD will look in
|
||||
<filename>/usr/local/etc/rc.d</filename> for scripts that have an
|
||||
<literal>.sh</literal> extension and are executable by root. Those
|
||||
<literal>.sh</literal> extension and are executable by <username>root</username>. Those
|
||||
scripts that are found are called with an option <option>start</option>
|
||||
at startup, and <option>stop</option> at shutdown to allow them to carry
|
||||
out their purpose. So if you wanted the above sample script to be
|
||||
|
|
|
@ -1786,7 +1786,7 @@ Building everything..
|
|||
then set up <filename>/etc/make.conf</filename> properly to share
|
||||
distfiles. You should set <makevar>DISTDIR</makevar> to a
|
||||
common shared directory that is writable by whichever user
|
||||
root is mapped to by your NFS mounts. Each
|
||||
<username>root</username> is mapped to by your NFS mounts. Each
|
||||
machine should set <makevar>WRKDIRPREFIX</makevar> to a
|
||||
local build directory. Finally, if you are going to be
|
||||
building and distributing packages, you should set
|
||||
|
|
|
@ -4096,9 +4096,9 @@ when you've finished.</screen>
|
|||
<title>Add User/Groups</title>
|
||||
|
||||
<para>You should add at least one user during the installation so
|
||||
that you can use the system without being logged in as root. The
|
||||
that you can use the system without being logged in as <username>root</username>. The
|
||||
root partition is generally small and running applications as
|
||||
root can quickly fill it. A bigger danger is noted below:</para>
|
||||
<username>root</username> can quickly fill it. A bigger danger is noted below:</para>
|
||||
|
||||
<screen> User Confirmation Requested
|
||||
Would you like to add any initial user accounts to the system? Adding
|
||||
|
@ -4218,7 +4218,7 @@ when you've finished.</screen>
|
|||
login.</para>
|
||||
|
||||
<para>The user was also added to the group <groupname>wheel</groupname> to be able to
|
||||
become a superuser with root privileges.</para>
|
||||
become a superuser with <username>root</username> privileges.</para>
|
||||
|
||||
<para>When you are satisfied, press &gui.ok; and
|
||||
the User and Group Management menu will redisplay.</para>
|
||||
|
@ -4254,7 +4254,7 @@ when you've finished.</screen>
|
|||
|
||||
[ Press enter to continue ]</screen>
|
||||
|
||||
<para>Press <keycap>Enter</keycap> to set the root password.</para>
|
||||
<para>Press <keycap>Enter</keycap> to set the <username>root</username> password.</para>
|
||||
|
||||
<para>The password will need to be typed in twice
|
||||
correctly. Needless to say, make sure you have a way of finding
|
||||
|
@ -4332,7 +4332,7 @@ when you've finished.</screen>
|
|||
<command>dmesg</command> at the prompt.</para>
|
||||
|
||||
<para>Login using the username/password you set during installation
|
||||
(rpratt, in this example). Avoid logging in as root except when
|
||||
(rpratt, in this example). Avoid logging in as <username>root</username> except when
|
||||
necessary.</para>
|
||||
|
||||
<para>Typical boot messages:</para>
|
||||
|
@ -4506,8 +4506,8 @@ Password:</screen>
|
|||
<para>It is important to properly shutdown the operating
|
||||
system. Do not just turn off power. First, become a superuser by
|
||||
typing <command>su</command> at the command line and entering the
|
||||
root password. This will work only if the user is a member of the
|
||||
group wheel. Otherwise, login as root and use
|
||||
<username>root</username> password. This will work only if the user is a member of the
|
||||
group wheel. Otherwise, login as <username>root</username> and use
|
||||
<command>shutdown -h now</command>.</para>
|
||||
|
||||
<screen>The operating system has halted.
|
||||
|
|
|
@ -209,7 +209,7 @@ Id Refs Address Size Name
|
|||
libraries? How do you know which shared libraries Linux
|
||||
binaries need, and where to get them? Basically, there are 2
|
||||
possibilities (when following these instructions you will need
|
||||
to be root on your FreeBSD system).</para>
|
||||
to be <username>root</username> on your FreeBSD system).</para>
|
||||
|
||||
<para>If you have access to a Linux system, see what shared
|
||||
libraries the application needs, and copy them to your FreeBSD
|
||||
|
@ -1261,7 +1261,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
<title><command>make world</command> and a New Kernel</title>
|
||||
|
||||
<para>The first thing to do is to install the sources.
|
||||
As user root, do the following:</para>
|
||||
As user <username>root</username>, do the following:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/src</userinput>
|
||||
&prompt.root; <userinput>make world</userinput> </screen>
|
||||
|
@ -1314,7 +1314,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
|
||||
<sect3 id="installinglinuxbase-system">
|
||||
<title>Installing Linux Base-system</title>
|
||||
<para>First the Linux base-system needs to be installed (as root):</para>
|
||||
<para>First the Linux base-system needs to be installed (as <username>root</username>):</para>
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base</userinput>
|
||||
&prompt.root; <userinput>make package</userinput> </screen>
|
||||
</sect3>
|
||||
|
@ -1706,7 +1706,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
|
|||
|
||||
<screen>&prompt.root; <userinput>export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib</userinput> </screen>
|
||||
|
||||
<para>Start R3SETUP as user root from installation
|
||||
<para>Start R3SETUP as user <username>root</username> from installation
|
||||
directory:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /oracle/IDS/sapreorg/install</userinput>
|
||||
|
|
|
@ -599,7 +599,7 @@ postmaster@example.com postmaster@noc.example.net
|
|||
<para>Add a script to
|
||||
<filename>/usr/local/etc/rc.d/</filename> that
|
||||
ends in <filename>.sh</filename> and is executable by
|
||||
root. The script should also accept the parameters 'start'
|
||||
<username>root</username>. The script should also accept the parameters 'start'
|
||||
and 'stop'. So that you could, for example, execute
|
||||
<filename>/usr/local/etc/rc.d/supermailer.sh start</filename>
|
||||
or <filename>/usr/local/etc/rc.d/supermailer.sh stop</filename>.
|
||||
|
|
|
@ -2125,7 +2125,7 @@ doc/zh_TW.Big5</screen>
|
|||
directory status files untouched when run this way. The new
|
||||
versions of those files will be written into the specified
|
||||
directory. As long as you have read access to
|
||||
<filename>/usr/src</filename>, you do not even need to be root
|
||||
<filename>/usr/src</filename>, you do not even need to be <username>root</username>
|
||||
to perform this kind of trial run.</para>
|
||||
|
||||
<para>If you are not running X11 or if you just do not like GUIs,
|
||||
|
|
|
@ -236,7 +236,7 @@ pcm0: <SB16 DSP 4.11> on sbc0</screen>
|
|||
|
||||
<para>If the previous command returned
|
||||
<devicename>pcm0</devicename>, you will have to run the
|
||||
following as root:</para>
|
||||
following as <username>root</username>:</para>
|
||||
|
||||
<screen>&prompt.root; cd /dev
|
||||
&prompt.root; sh MAKEDEV snd0</screen>
|
||||
|
|
|
@ -2003,7 +2003,7 @@ name_of_service_provider:
|
|||
<sect2>
|
||||
<title>Running <application>PPP</application></title>
|
||||
|
||||
<para>As root, you can run:</para>
|
||||
<para>As <username>root</username>, you can run:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>ppp -ddial name_of_service_provider</userinput></screen>
|
||||
|
||||
|
@ -2378,7 +2378,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
|
|||
<keycombo>
|
||||
<keycap>Ctrl</keycap>
|
||||
<keycap>z</keycap>
|
||||
</keycombo>) and as root, type:</para>
|
||||
</keycombo>) and as <username>root</username>, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>slattach -h -c -s 115200 /dev/modem</userinput></screen>
|
||||
|
||||
|
|
|
@ -514,8 +514,8 @@ sio2: type 16550A</screen>
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Become root with the &man.su.1; command. Enter the
|
||||
root password when prompted.</para>
|
||||
<para>Become <username>root</username> with the &man.su.1; command. Enter the
|
||||
<username>root</username> password when prompted.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
@ -706,7 +706,7 @@ showpage</programlisting>
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Become root with &man.su.1;.</para>
|
||||
<para>Become <username>root</username> with &man.su.1;.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
@ -771,7 +771,7 @@ showpage</programlisting>
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Become root with &man.su.1;.</para>
|
||||
<para>Become <username>root</username> with &man.su.1;.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
@ -3293,7 +3293,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
|||
to have access to a printer in a certain group, and then name that
|
||||
group in the <literal>rg</literal> capability.</para>
|
||||
|
||||
<para>Users outside the group (including root) will be greeted with
|
||||
<para>Users outside the group (including <username>root</username>) will be greeted with
|
||||
|
||||
<errorname>lpr: Not a member of the restricted group</errorname>
|
||||
|
||||
|
@ -4378,14 +4378,14 @@ cfA013rose dequeued
|
|||
printer is <emphasis>started</emphasis> or the queue is
|
||||
cleared.</para>
|
||||
|
||||
<para>If a queue is <emphasis>disabled</emphasis>, no user (except root)
|
||||
<para>If a queue is <emphasis>disabled</emphasis>, no user (except <username>root</username>)
|
||||
can submit jobs for the printer. An <emphasis>enabled</emphasis>
|
||||
queue allows jobs to be submitted. A printer can be
|
||||
<emphasis>started</emphasis> for a disabled queue, in which case it
|
||||
will continue to print jobs in the queue until the queue is
|
||||
empty.</para>
|
||||
|
||||
<para>In general, you have to have root privileges to use the
|
||||
<para>In general, you have to have <username>root</username> privileges to use the
|
||||
&man.lpc.8; command. Ordinary users can use the &man.lpc.8; command
|
||||
to get printer status and to restart a hung printer only.</para>
|
||||
|
||||
|
@ -4428,12 +4428,12 @@ cfA013rose dequeued
|
|||
<listitem>
|
||||
<para>Disable queuing of new jobs. If the printer is running, it
|
||||
will continue to print any jobs remaining in the queue. The
|
||||
superuser (root) can always submit jobs, even to a disabled
|
||||
superuser (<username>root</username>) can always submit jobs, even to a disabled
|
||||
queue.</para>
|
||||
|
||||
<para>This command is useful while you are testing a new printer
|
||||
or filter installation: disable the queue and submit jobs as
|
||||
root. Other users will not be able to submit jobs until you
|
||||
<username>root</username>. Other users will not be able to submit jobs until you
|
||||
complete your testing and re-enable the queue with the
|
||||
<command>enable</command> command.</para>
|
||||
</listitem>
|
||||
|
|
|
@ -1642,7 +1642,7 @@ AT&B2&W</programlisting>
|
|||
<screen>&prompt.root; <userinput>cd /dev</userinput>
|
||||
&prompt.root; <userinput>sh MAKEDEV cuaa0</userinput></screen>
|
||||
|
||||
<para>Or use <command>cu</command> as root with the following
|
||||
<para>Or use <command>cu</command> as <username>root</username> with the following
|
||||
command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
|
||||
|
|
|
@ -236,7 +236,7 @@ pcm0: <SB16 DSP 4.11> on sbc0</screen>
|
|||
|
||||
<para>If the previous command returned
|
||||
<devicename>pcm0</devicename>, you will have to run the
|
||||
following as root:</para>
|
||||
following as <username>root</username>:</para>
|
||||
|
||||
<screen>&prompt.root; cd /dev
|
||||
&prompt.root; sh MAKEDEV snd0</screen>
|
||||
|
|
Loading…
Reference in a new issue