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

Whitespace cleanup from last commit.

Browse source 
No content changes.

Approved by:	murray
This commit is contained in:
Ceri Davies 2002-04-29 12:22:30 +00:00
parent 35716bf6ec
commit 5693e26a0d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12908
9 changed files with 62 additions and 54 deletions
Download patch file Download diff file Expand all files Collapse all files

19
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -2386,19 +2386,20 @@ 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 <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>
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>
<screen>&prompt.root; <userinput>cp /etc/master.passwd /var/yp/master.passwd</userinput>
&prompt.root; <userinput>cd /var/yp</userinput>
&prompt.root; <userinput>vi master.passwd</userinput></screen>
<para>You should remove all entries regarding system accounts
(<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
<username>root</username> and any other UID 0 (superuser) accounts).</para>
(<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 <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
@ -5832,8 +5833,8 @@ lp0: TCP/IP capable interface</screen>
both computers.</para>
<para>Configure the network interface parameters for lp0 on both
sites as <username>root</username>. For example, if you want connect the host host1
with host2</para>
sites as <username>root</username>. For example, if you want connect
the host host1 with host2</para>
<programlisting> host1 &lt;-----&gt; host2
IP Address 10.0.0.1 10.0.0.2</programlisting>

10
en_US.ISO8859-1/books/handbook/boot/chapter.sgml
View file

@ -605,9 +605,9 @@ boot:</screen>
mode</link>.</para>
<para>If the system <literal>console</literal> is set
to <literal>insecure</literal> in
<filename>/etc/ttys</filename>, then the system prompts for
the <username>root</username> password before initiating single-user mode.</para>
to <literal>insecure</literal> in <filename>/etc/ttys</filename>,
then the system prompts for 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,8 +623,8 @@ 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
<username>root</username> password may use single-user mode, and it does not
mean that you want to run your console insecurely. Thus,
<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>
</note>

13
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -381,12 +381,13 @@ 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 <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
picked up and run at the proper time during system startup, you should
save it to a file called <filename>FooBar.sh</filename> in
<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 picked up and run at the proper time during
system startup, you should save it to a file called
<filename>FooBar.sh</filename> in
<filename>/usr/local/etc/rc.d</filename> and make sure it's
executable. You can make a shell script executable with &man.chmod.1;
as shown below:</para>

24
en_US.ISO8859-1/books/handbook/install/chapter.sgml
View file

@ -4096,9 +4096,10 @@ 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 <username>root</username>. The
root partition is generally small and running applications as
<username>root</username> can quickly fill it. A bigger danger is noted below:</para>
that you can use the system without being logged in as
<username>root</username>. The root partition is generally small
and running applications as <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
@ -4217,8 +4218,9 @@ when you've finished.</screen>
use a shell that does not exist or you will not be able to
login.</para>
<para>The user was also added to the group <groupname>wheel</groupname> to be able to
become a superuser with <username>root</username> privileges.</para>
<para>The user was also added to the group <groupname>wheel</groupname>
to be able to 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 +4256,8 @@ when you've finished.</screen>
[ Press enter to continue ]</screen>
<para>Press <keycap>Enter</keycap> to set the <username>root</username> 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,8 +4335,8 @@ 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 <username>root</username> except when
necessary.</para>
(rpratt, in this example). Avoid logging in as
<username>root</username> except when necessary.</para>
<para>Typical boot messages:</para>
@ -4506,8 +4509,9 @@ 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
<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
<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.

3
en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml
View file

@ -1314,7 +1314,8 @@ 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 <username>root</username>):</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>

4
en_US.ISO8859-1/books/handbook/mail/chapter.sgml
View file

@ -599,8 +599,8 @@ 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
<username>root</username>. The script should also accept the parameters 'start'
and 'stop'. So that you could, for example, execute
<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>.
The system will call your script using 'start' when the it

4
en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml
View file

@ -2125,8 +2125,8 @@ 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 <username>root</username>
to perform this kind of trial run.</para>
<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,
you should add a couple of options to the command line when you

35
en_US.ISO8859-1/books/handbook/printing/chapter.sgml
View file

@ -514,8 +514,8 @@ sio2: type 16550A</screen>
<procedure>
<step>
<para>Become <username>root</username> with the &man.su.1; command. Enter the
<username>root</username> 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>
@ -3293,7 +3293,8 @@ 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 <username>root</username>) 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,16 +4379,16 @@ cfA013rose dequeued
printer is <emphasis>started</emphasis> or the queue is
cleared.</para>
<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>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 <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>
<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>
<para>Here is a summary of the &man.lpc.8; commands. Most of the
commands take a <replaceable>printer-name</replaceable> argument to
@ -4428,14 +4429,14 @@ 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 (<username>root</username>) can always submit jobs, even to a disabled
queue.</para>
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
<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>
<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>
</varlistentry>

4
en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml
View file

@ -1642,8 +1642,8 @@ AT&amp;B2&amp;W</programlisting>
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>sh MAKEDEV cuaa0</userinput></screen>
<para>Or use <command>cu</command> as <username>root</username> with the following
command:</para>
<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>