Undo previous commit
In case it isn't already obvious the following are not the same: dcvs ci -F install/chapter.sgml dcvs ci -F log install/chapter.sgml
This commit is contained in:
Eitan Adler
parent
4740eff281
commit
13e629bb88
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=38463
14 changed files with 2102 additions and 1730 deletions
en_US.ISO8859-1/books/handbook
install
jails
kernelconfig
l10n
linuxemu
mac
mail
mirrors
ports
security
serialcomms
users
virtualization
x11
File diff suppressed because it is too large
Load diff
|
|
@ -394,7 +394,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
</itemizedlist>
|
||||
|
||||
<sect2 id="jails-tuning-utilities">
|
||||
<title>System Tools for Jail Tuning in &os;</title>
|
||||
<title>System tools for jail tuning in &os;</title>
|
||||
|
||||
<para>Fine tuning of a jail's configuration is mostly done by
|
||||
setting &man.sysctl.8; variables. A special subtree of sysctl
|
||||
|
|
@ -483,7 +483,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
</sect2>
|
||||
|
||||
<sect2 id="jails-tuning-admintools">
|
||||
<title>High-Level Administrative Tools in &os; Ports
|
||||
<title>High-level administrative tools in &os; Ports
|
||||
Collection</title>
|
||||
|
||||
<para>Among the many third-party utilities for jail administration,
|
||||
|
|
@ -546,7 +546,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<para>This idea has been presented to resolve such issues by
|
||||
sharing as much as is possible between jails, in a safe way
|
||||
— using read-only &man.mount.nullfs.8; mounts, so that
|
||||
updating will be simpler, and putting single services into
|
||||
updating will be be simpler, and putting single services into
|
||||
individual jails will become more attractive. Additionally,
|
||||
it provides a simple way to add or remove jails as well as a
|
||||
way to upgrade them.</para>
|
||||
|
|
@ -626,7 +626,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
<listitem>
|
||||
<para>Each jailspace (read-write portion of each jail) shall
|
||||
be created in <filename
|
||||
class="directory">/home/js</filename>.</para>
|
||||
class="directory">/home/js</filename>.<para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
@ -645,7 +645,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
|
||||
<para>This section will describe the steps needed to create the
|
||||
master template that will be the read-only portion for the
|
||||
jails to use.</para>
|
||||
jails to use.<para>
|
||||
|
||||
<para>It is always a good idea to update the &os; system to the
|
||||
latest -RELEASE branch. Check the corresponding Handbook
|
||||
|
|
@ -746,7 +746,7 @@ jail_<replaceable>www</replaceable>_devfs_ruleset="<replaceable>www_ruleset</rep
|
|||
setup and configure the jails in
|
||||
<filename>/etc/rc.conf</filename>. This example demonstrates
|
||||
the creation of 3 jails: <quote>NS</quote>,
|
||||
<quote>MAIL</quote> and <quote>WWW</quote>.</para>
|
||||
<quote>MAIL</quote> and <quote>WWW</quote>.<para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
|
|
|
|||
|
|
@ -579,7 +579,7 @@ cpu I686_CPU</programlisting>
|
|||
|
||||
<para>This is the identification of the kernel. You should change
|
||||
this to whatever you named your kernel,
|
||||
i.e., <literal><replaceable>MYKERNEL</replaceable></literal> if you have
|
||||
i.e. <literal><replaceable>MYKERNEL</replaceable></literal> if you have
|
||||
followed the instructions of the previous examples. The value you put
|
||||
in the <literal>ident</literal> string will print when you boot up the
|
||||
kernel, so it is useful to give the new kernel a different name if you
|
||||
|
|
@ -605,7 +605,7 @@ cpu I686_CPU</programlisting>
|
|||
|
||||
<para>The normal build process of &os; includes
|
||||
debugging information when building the kernel with the
|
||||
<option>-g</option> option, which enables debugging
|
||||
the <option>-g</option> option, which enables debugging
|
||||
information when passed to &man.gcc.1;.</para>
|
||||
|
||||
<programlisting>options SCHED_ULE # ULE scheduler</programlisting>
|
||||
|
|
@ -1242,7 +1242,7 @@ device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs.
|
|||
device loop # Network loopback</programlisting>
|
||||
|
||||
<para>This is the generic loopback device for TCP/IP. If you telnet
|
||||
or FTP to <hostid>localhost</hostid> (aka <hostid
|
||||
or FTP to <hostid>localhost</hostid> (a.k.a. <hostid
|
||||
role="ipaddr">127.0.0.1</hostid>) it will come back at you through
|
||||
this device. This is <emphasis>mandatory</emphasis>.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -187,7 +187,7 @@
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Wide or multibyte encodings, e.g., EUC, Big5.</para>
|
||||
<para>Wide or multibyte encodings, e.g. EUC, Big5.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
|
|||
|
|
@ -155,7 +155,8 @@ Id Refs Address Size Name
|
|||
|
||||
<para>This is by far the easiest method to use when installing the
|
||||
runtime libraries. It is just like installing any other port
|
||||
from the <ulink type="html" url="file://localhost/usr/ports/">Ports Collection</ulink>:
|
||||
from the <ulink type="html" url="file://localhost/usr/ports/">Ports Collection</ulink>.
|
||||
Simply do the following:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base-f10</userinput>
|
||||
&prompt.root; <userinput>make install distclean</userinput></screen>
|
||||
|
|
|
|||
|
|
@ -140,7 +140,7 @@
|
|||
</sect1>
|
||||
|
||||
<sect1 id="mac-inline-glossary">
|
||||
<title>Key Terms in This Chapter</title>
|
||||
<title>Key Terms in this Chapter</title>
|
||||
|
||||
<para>Before reading this chapter, a few key terms must be
|
||||
explained. This will hopefully clear up any confusion that
|
||||
|
|
@ -260,7 +260,7 @@
|
|||
<listitem>
|
||||
<para><emphasis>subject</emphasis>: a subject is any
|
||||
active entity that causes information to flow between
|
||||
<emphasis>objects</emphasis>; e.g., a user, user processor,
|
||||
<emphasis>objects</emphasis>; e.g. a user, user processor,
|
||||
system process, etc. On &os;, this is almost always a thread
|
||||
acting in a process on behalf of a user.</para>
|
||||
</listitem>
|
||||
|
|
@ -1065,7 +1065,7 @@ test: biba/high</screen>
|
|||
using a variety of <command>sysctl</command> variables. In
|
||||
essence &man.mac.portacl.4; makes it possible to allow
|
||||
non-<username>root</username> users to bind to specified
|
||||
privileged ports, i.e., ports fewer than 1024.</para>
|
||||
privileged ports, i.e. ports fewer than 1024.</para>
|
||||
|
||||
<para>Once loaded, this module will enable the
|
||||
<acronym>MAC</acronym> policy on all sockets. The following
|
||||
|
|
@ -1115,13 +1115,13 @@ test: biba/high</screen>
|
|||
<note>
|
||||
<para>Since the ruleset is interpreted directly by the kernel
|
||||
only numeric values can be used for the user ID, group ID, and
|
||||
port parameters. User, group, and port service names
|
||||
port parameters. I.e. user, group, and port service names
|
||||
cannot be used.</para>
|
||||
</note>
|
||||
|
||||
<para>By default, on &unix;-like systems, ports fewer than 1024
|
||||
can only be used by/bound to privileged processes,
|
||||
i.e., those run as <username>root</username>. For
|
||||
i.e. those run as <username>root</username>. For
|
||||
&man.mac.portacl.4; to allow non-privileged processes to bind
|
||||
to ports below 1024 this standard &unix; restriction has to be
|
||||
disabled. This can be accomplished by setting the &man.sysctl.8;
|
||||
|
|
@ -1880,8 +1880,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
|
||||
<para>For this scenario, the &man.mac.bsdextended.4; mixed with
|
||||
&man.mac.seeotheruids.4; could co-exist and block access not
|
||||
only to system objects, but to hide user processes as
|
||||
well.</para>
|
||||
only to system objects but to hide user processes as well.
|
||||
|
||||
<para>Begin by adding the following line to
|
||||
<filename>/boot/loader.conf</filename>:</para>
|
||||
|
|
@ -1984,7 +1983,7 @@ setpmac biba/10\(10-10\) /usr/local/etc/rc.d/nagios.sh forcestart</userinput></s
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Cannot Start a X11 Server After <acronym>MAC</acronym></title>
|
||||
<title>Cannot start a X11 server after <acronym>MAC</acronym></title>
|
||||
|
||||
<para>After establishing a secure environment with
|
||||
<acronym>MAC</acronym>, I am no longer able to start
|
||||
|
|
|
|||
|
|
@ -356,7 +356,7 @@ FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="local">
|
||||
<title>Accessing Local Mailboxes</title>
|
||||
<title>Accessing local mailboxes</title>
|
||||
|
||||
<para>Mailboxes may be accessed locally by directly utilizing
|
||||
<acronym>MUA</acronym>s on the server on which the mailbox
|
||||
|
|
@ -550,7 +550,7 @@ procmail: "|/usr/local/bin/procmail"</programlisting>
|
|||
<para>The file format is simple; the mailbox name on the left
|
||||
side of the colon is expanded to the target(s) on the right.
|
||||
The
|
||||
first example expands the mailbox <username>root</username>
|
||||
first example simply expands the mailbox <username>root</username>
|
||||
to the mailbox <username>localuser</username>, which is then
|
||||
looked up again in the aliases database. If no match is found,
|
||||
then the message is delivered to the local user
|
||||
|
|
@ -673,7 +673,7 @@ postmaster@example.com postmaster@noc.example.net
|
|||
|
||||
<para>However, for a variety of reasons, some system
|
||||
administrators want to change their system's MTA. These
|
||||
reasons range from merely wanting to try out another MTA to
|
||||
reasons range from simply wanting to try out another MTA to
|
||||
needing a specific feature or package which relies on another
|
||||
mailer. Fortunately, whatever the reason, FreeBSD makes it
|
||||
easy to make the change.</para>
|
||||
|
|
@ -818,7 +818,7 @@ purgestat /usr/local/supermailer/bin/purgestat-compat</programlisting>
|
|||
<para>Once you have everything configured the way you want it, you should
|
||||
either kill the <application>sendmail</application> processes that
|
||||
you no longer need and start the processes belonging to your new
|
||||
software, or merely reboot. Rebooting will also
|
||||
software, or simply reboot. Rebooting will also
|
||||
give you the opportunity to ensure that you have correctly
|
||||
configured your system to start your new MTA automatically on boot.</para>
|
||||
|
||||
|
|
@ -952,7 +952,7 @@ to /etc/mail/sendmail.cf.</programlisting>
|
|||
deliver the mail it will try to connect to you (<hostid role="domainname">example.com</hostid>) over the modem
|
||||
link. It will most likely time out because you are not online.
|
||||
The program <application>sendmail</application> will automatically deliver it to the
|
||||
secondary MX site, i.e., your Internet provider (<hostid role="domainname">example.net</hostid>). The secondary MX
|
||||
secondary MX site, i.e. your Internet provider (<hostid role="domainname">example.net</hostid>). The secondary MX
|
||||
site will then periodically try to connect to
|
||||
your host and deliver the mail to the primary MX host (<hostid role="domainname">example.com</hostid>).</para>
|
||||
|
||||
|
|
@ -1037,8 +1037,8 @@ the DNS for <quote>customer.com</quote>.</programlisting>
|
|||
locally, or would like to use a point and click
|
||||
client/system on another machine or even another ISP. It
|
||||
is also very useful if you only have one or two email
|
||||
accounts set up. If there are a large number of addresses
|
||||
to add, open this file in your favorite
|
||||
accounts set up. If there is a large number of addresses
|
||||
to add, you can simply open this file in your favorite
|
||||
text editor and then add the domains, one per line:</para>
|
||||
|
||||
<programlisting>your.isp.example.com
|
||||
|
|
@ -1355,7 +1355,7 @@ if-bus.UUCP uucp-dom:if-bus
|
|||
<para>Final hint: if you are uncertain whether some particular
|
||||
mail routing would work, remember the <option>-bt</option>
|
||||
option to <application>sendmail</application>. It starts <application>sendmail</application> in <emphasis>address test
|
||||
mode</emphasis>; enter <literal>3,0</literal>, followed
|
||||
mode</emphasis>; simply enter <literal>3,0</literal>, followed
|
||||
by the address you wish to test for the mail routing. The last
|
||||
line tells you the used internal mail agent, the destination
|
||||
host this agent will be called with, and the (possibly
|
||||
|
|
@ -1727,7 +1727,7 @@ define(`confAUTH_MECHANISMS', `GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl</programlis
|
|||
will be discussed later in this chapter (<xref
|
||||
linkend="mail-fetchmail">).</para>
|
||||
|
||||
<para>In order to send and receive email, invoke the
|
||||
<para>In order to send and receive email, simply invoke the
|
||||
<command>mail</command> command as per the following
|
||||
example:</para>
|
||||
|
||||
|
|
@ -1884,7 +1884,7 @@ EOT</screen>
|
|||
</imageobject>
|
||||
</mediaobject>
|
||||
|
||||
<para>In order to read an email, select it using the cursor
|
||||
<para>In order to read an email, simply select it using the cursor
|
||||
keys, and press the <keycap>Enter</keycap> key. An example of
|
||||
<application>mutt</application> displaying email can be seen
|
||||
below:</para>
|
||||
|
|
|
|||
|
|
@ -422,7 +422,7 @@ SSH2 HostKey: 1024 e8:3b:29:7b:ca:9f:ac:e9:45:cb:c8:17:ae:9b:eb:55 /etc/ssh/ssh_
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Using SSH to Check out the <filename>src/</filename>
|
||||
<title>Using SSH to check out the <filename>src/</filename>
|
||||
tree:</title>
|
||||
<screen>&prompt.user; <userinput>cvs -d anoncvs@anoncvs1.FreeBSD.org:/home/ncvs co src</userinput>
|
||||
The authenticity of host 'anoncvs1.freebsd.org (216.87.78.137)' can't be established.
|
||||
|
|
|
|||
|
|
@ -1183,7 +1183,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="portupgrade">
|
||||
<title>Upgrading Ports Using Portupgrade</title>
|
||||
<title>Upgrading Ports using Portupgrade</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>portupgrade</primary>
|
||||
|
|
@ -1237,7 +1237,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="portmanager">
|
||||
<title>Upgrading Ports Using Portmanager</title>
|
||||
<title>Upgrading Ports using Portmanager</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>portmanager</primary>
|
||||
|
|
@ -1277,7 +1277,7 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="portmaster">
|
||||
<title>Upgrading Ports Using Portmaster</title>
|
||||
<title>Upgrading Ports using Portmaster</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>portmaster</primary>
|
||||
|
|
|
|||
|
|
@ -588,7 +588,7 @@
|
|||
|
||||
<sect2>
|
||||
<title>Securing the Kernel Core, Raw Devices, and
|
||||
File Systems</title>
|
||||
File systems</title>
|
||||
|
||||
<para>If an attacker breaks <username>root</username> he can do
|
||||
just about anything, but there are certain conveniences. For
|
||||
|
|
@ -1879,8 +1879,8 @@ Aug 27 15:37:58 Aug 28 01:37:58 krbtgt/EXAMPLE.ORG@EXAMPLE.ORG</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title><application>Kerberos</application> Enabling a Server
|
||||
with Heimdal Services</title>
|
||||
<title><application>Kerberos</application> enabling a server
|
||||
with Heimdal services</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>Kerberos5</primary>
|
||||
|
|
@ -1989,7 +1989,7 @@ kadmin><userinput> exit</userinput></screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title><application>Kerberos</application> Enabling a Client
|
||||
<title><application>Kerberos</application> enabling a client
|
||||
with Heimdal</title>
|
||||
|
||||
<indexterm>
|
||||
|
|
@ -2040,7 +2040,7 @@ kadmin><userinput> exit</userinput></screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>User Configuration Files: <filename>.k5login</filename>
|
||||
<title>User configuration files: <filename>.k5login</filename>
|
||||
and <filename>.k5users</filename></title>
|
||||
|
||||
<indexterm>
|
||||
|
|
@ -2237,7 +2237,7 @@ jdoe@example.org</screen>
|
|||
|
||||
<sect2>
|
||||
<title>Differences with the <acronym>MIT</acronym>
|
||||
Port</title>
|
||||
port</title>
|
||||
|
||||
<para>The major difference between the <acronym>MIT</acronym>
|
||||
and Heimdal installs relates to the
|
||||
|
|
@ -2292,7 +2292,7 @@ kadmind5_server_enable="YES"</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Mitigating Limitations Found in
|
||||
<title>Mitigating limitations found in
|
||||
<application>Kerberos</application></title>
|
||||
|
||||
<indexterm>
|
||||
|
|
@ -2316,8 +2316,8 @@ kadmind5_server_enable="YES"</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title><application>Kerberos</application> is Intended for
|
||||
Single-User Workstations</title>
|
||||
<title><application>Kerberos</application> is intended for
|
||||
single-user workstations</title>
|
||||
|
||||
<para>In a multi-user environment,
|
||||
<application>Kerberos</application> is less secure.
|
||||
|
|
@ -2337,7 +2337,7 @@ kadmind5_server_enable="YES"</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>The KDC is a Single Point of Failure</title>
|
||||
<title>The KDC is a single point of failure</title>
|
||||
|
||||
<para>By design, the <acronym>KDC</acronym> must be as
|
||||
secure as the master password database is contained on it.
|
||||
|
|
@ -3185,7 +3185,7 @@ racoon_enable="yes"</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Enabling <application>sshd</application></title>
|
||||
<title>Enabling sshd</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>OpenSSH</primary>
|
||||
|
|
@ -3307,7 +3307,7 @@ COPYRIGHT 100% |*****************************| 4735
|
|||
</sect2>
|
||||
|
||||
<sect2 id="security-ssh-keygen">
|
||||
<title><application>ssh-keygen</application></title>
|
||||
<title>ssh-keygen</title>
|
||||
|
||||
<para>Instead of using passwords, &man.ssh-keygen.1; can
|
||||
be used to generate DSA or RSA keys to authenticate a
|
||||
|
|
@ -3356,7 +3356,7 @@ bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8f:79:17 user@host.example.com</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="security-ssh-agent">
|
||||
<title><application>ssh-agent</application> and <application>ssh-add</application></title>
|
||||
<title>ssh-agent and ssh-add</title>
|
||||
|
||||
<para>The &man.ssh-agent.1; and &man.ssh-add.1; utilities
|
||||
provide methods for <application>SSH</application> keys to
|
||||
|
|
@ -3887,7 +3887,7 @@ You are advised to update or deinstall the affected package(s) immediately.</pro
|
|||
to patch a system.</para>
|
||||
|
||||
<sect2>
|
||||
<title>What Does an Advisory Look Like?</title>
|
||||
<title>What does an advisory look like?</title>
|
||||
|
||||
<para>The &os; security advisories look similar to the one
|
||||
below, taken from the &a.security-notifications.name;
|
||||
|
|
|
|||
|
|
@ -810,7 +810,7 @@ sio3: type 16550A</screen>
|
|||
through the Ports Collection. The Ports include quite a few
|
||||
utilities which can work in ways similar to &man.cu.1; and
|
||||
&man.tip.1;,
|
||||
i.e., <filename role="package">comms/minicom</filename>.</para>
|
||||
i.e. <filename role="package">comms/minicom</filename>.</para>
|
||||
</note>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -1173,7 +1173,7 @@ ttyu5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
modems instead of terminals.</para>
|
||||
|
||||
<sect2>
|
||||
<title>External Versus Internal Modems</title>
|
||||
<title>External vs. Internal Modems</title>
|
||||
|
||||
<para>External modems seem to be more convenient for dial-up, because
|
||||
external modems often can be semi-permanently configured via
|
||||
|
|
@ -1881,7 +1881,7 @@ AT&B2&W</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="direct-at">
|
||||
<title>How Am I Expected to Enter These <literal>AT</literal> Commands?</title>
|
||||
<title>How Am I Expected to Enter These AT Commands?</title>
|
||||
|
||||
<indexterm>
|
||||
<primary><filename>/etc/remote</filename></primary>
|
||||
|
|
@ -1895,7 +1895,7 @@ AT&B2&W</programlisting>
|
|||
|
||||
<para>Use the highest bps rate your modem supports in the br capability.
|
||||
Then, type <command>tip cuau0</command> and you will be connected to
|
||||
your modem.</para >
|
||||
your modem.</para>
|
||||
|
||||
<para>Or use <command>cu</command> as <username>root</username> with the
|
||||
following command:</para>
|
||||
|
|
@ -1903,9 +1903,9 @@ AT&B2&W</programlisting>
|
|||
<screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
|
||||
|
||||
<para><replaceable>line</replaceable> is the serial port
|
||||
(e.g., <filename>/dev/cuau0</filename>) and
|
||||
(e.g.<filename>/dev/cuau0</filename>) and
|
||||
<replaceable>speed</replaceable> is the speed
|
||||
(e.g., <literal>57600</literal>). When you are done entering the AT
|
||||
(e.g.<literal>57600</literal>). When you are done entering the AT
|
||||
commands type <command>~.</command> to exit.</para>
|
||||
</sect2>
|
||||
|
||||
|
|
@ -2117,7 +2117,7 @@ raisechar=^^</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="zmodem-tip">
|
||||
<title>How Can I Run <application>zmodem</application> with <command>tip</command>?</title>
|
||||
<title>How Can I Run zmodem with <command>tip</command>?</title>
|
||||
|
||||
<para>To receive files, start the sending program on the remote end.
|
||||
Then, type <command>~C rz</command> to begin receiving them
|
||||
|
|
@ -2829,7 +2829,7 @@ ttyu3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
|||
Change <literal>off</literal> to <literal>on</literal> for the
|
||||
desired port. If you have changed the speed of the serial port,
|
||||
you need to change <literal>std.9600</literal> to match the current
|
||||
setting, e.g., <literal>std.19200</literal>.</para>
|
||||
setting, e.g. <literal>std.19200</literal>.</para>
|
||||
|
||||
<para>You may also want to change the terminal type from
|
||||
<literal>unknown</literal> to the actual type of your serial
|
||||
|
|
@ -2907,7 +2907,7 @@ ttyu3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
|||
while most systems will let you boot without a keyboard, there
|
||||
are quite a few that will not let you boot without a graphics adapter.
|
||||
Machines with AMI BIOSes can be configured to boot with no graphics
|
||||
adapter installed by changing the
|
||||
adapter installed simply by changing the
|
||||
<quote>graphics adapter</quote> setting in the CMOS configuration to
|
||||
<quote>Not installed.</quote></para>
|
||||
|
||||
|
|
|
|||
|
|
@ -392,7 +392,7 @@
|
|||
the new user a welcome message.</para>
|
||||
|
||||
<example>
|
||||
<title>Adding a User on &os;</title>
|
||||
<title>Adding a user on &os;</title>
|
||||
|
||||
<screen>&prompt.root; <userinput>adduser</userinput>
|
||||
Username: <userinput>jru</userinput>
|
||||
|
|
|
|||
|
|
@ -231,7 +231,7 @@
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<title>Set Boot Loader Variables</title>
|
||||
<title>Set boot loader variables</title>
|
||||
|
||||
<para>The most important step is to reduce the
|
||||
<option>kern.hz</option> tunable to reduce the CPU utilization
|
||||
|
|
@ -249,7 +249,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Create a New Kernel Configuration File</title>
|
||||
<title>Create a new kernel configuration file</title>
|
||||
|
||||
<para>You can remove all of the SCSI, FireWire, and USB
|
||||
device drivers. <application>Parallels</application>
|
||||
|
|
@ -261,7 +261,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Setup Networking</title>
|
||||
<title>Setup networking</title>
|
||||
|
||||
<para>The most basic networking setup involves simply
|
||||
using DHCP to connect your virtual machine to the same
|
||||
|
|
@ -731,7 +731,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<title>Set Boot Loader Variables</title>
|
||||
<title>Set boot loader variables</title>
|
||||
|
||||
<para>The most important step is to reduce the
|
||||
<option>kern.hz</option> tunable to reduce the CPU utilization
|
||||
|
|
@ -749,7 +749,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Create a New Kernel Configuration File</title>
|
||||
<title>Create a new kernel configuration file</title>
|
||||
|
||||
<para>You can remove all of the SCSI, FireWire, and USB
|
||||
device drivers. <application>Virtual PC</application>
|
||||
|
|
@ -761,7 +761,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Setup Networking</title>
|
||||
<title>Setup networking</title>
|
||||
|
||||
<para>The most basic networking setup involves simply
|
||||
using DHCP to connect your virtual machine to the same
|
||||
|
|
@ -926,7 +926,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<title>Set Boot Loader Variables</title>
|
||||
<title>Set boot loader variables</title>
|
||||
|
||||
<para>The most important step is to reduce the
|
||||
<option>kern.hz</option> tunable to reduce the CPU utilization
|
||||
|
|
@ -944,7 +944,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Create a New Kernel Configuration file</title>
|
||||
<title>Create a new kernel configuration file</title>
|
||||
|
||||
<para>You can remove all of the FireWire, and USB device
|
||||
drivers. <application>VMware</application> provides a
|
||||
|
|
@ -954,7 +954,7 @@ xenbr1 8000.feffffffffff no vif0.1
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Setup Networking</title>
|
||||
<title>Setup networking</title>
|
||||
|
||||
<para>The most basic networking setup involves simply
|
||||
using DHCP to connect your virtual machine to the same
|
||||
|
|
@ -1051,7 +1051,7 @@ EndSection</programlisting>
|
|||
<!--
|
||||
# Sun VirtualBox
|
||||
# Hal driver description for the vboxmouse driver
|
||||
# $Id: chapter.sgml,v 1.28 2012-02-15 18:14:17 eadler Exp $
|
||||
# $Id: chapter.sgml,v 1.29 2012-02-15 18:37:26 eadler Exp $
|
||||
|
||||
Copyright (C) 2008-2009 Sun Microsystems, Inc.
|
||||
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@
|
|||
<quote>X server</quote> runs on the computer that has the keyboard,
|
||||
monitor, and mouse attached. The server's responsibility includes tasks such as managing
|
||||
the display, handling input from the keyboard and mouse, and other
|
||||
input or output devices (i.e., a <quote>tablet</quote> can be used as
|
||||
input or output devices (i.e. a <quote>tablet</quote> can be used as
|
||||
an input device, and a video projector may be an alternative output
|
||||
device).
|
||||
Each X application (such as <application>XTerm</application>, or
|
||||
|
|
@ -530,7 +530,7 @@ dbus_enable="YES"</programlisting>
|
|||
<programlisting>Option "AutoAddDevices" "false"</programlisting>
|
||||
|
||||
<para>Input devices may then be configured as in previous versions,
|
||||
along with any other options needed (e.g., keyboard layout
|
||||
along with any other options needed (e.g. keyboard layout
|
||||
switching).</para>
|
||||
|
||||
<note>
|
||||
|
|
|
|||
Loading…
Reference in a new issue