diff options
Diffstat (limited to 'pl_PL.ISO8859-2/books/handbook/config/chapter.xml')
| -rw-r--r-- | pl_PL.ISO8859-2/books/handbook/config/chapter.xml | 368 |
1 files changed, 153 insertions, 215 deletions
diff --git a/pl_PL.ISO8859-2/books/handbook/config/chapter.xml b/pl_PL.ISO8859-2/books/handbook/config/chapter.xml index 4825f473e0..0b9b5894ef 100644 --- a/pl_PL.ISO8859-2/books/handbook/config/chapter.xml +++ b/pl_PL.ISO8859-2/books/handbook/config/chapter.xml @@ -4,35 +4,22 @@ $FreeBSD$ --> - -<chapter id="config-tuning"> - <chapterinfo> +<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="config-tuning"> + <info><title>Configuration and Tuning</title> <authorgroup> - <author> - <firstname>Chern</firstname> - <surname>Lee</surname> - <contrib>Written by </contrib> - </author> + <author><personname><firstname>Chern</firstname><surname>Lee</surname></personname><contrib>Written by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Mike</firstname> - <surname>Smith</surname> - <contrib>Based on a tutorial written by </contrib> - </author> + <author><personname><firstname>Mike</firstname><surname>Smith</surname></personname><contrib>Based on a tutorial written by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Matt</firstname> - <surname>Dillon</surname> - <contrib>Also based on tuning(7) written by </contrib> - </author> + <author><personname><firstname>Matt</firstname><surname>Dillon</surname></personname><contrib>Also based on tuning(7) written by </contrib></author> </authorgroup> - </chapterinfo> + </info> - <title>Configuration and Tuning</title> + - <sect1 id="config-synopsis"> + <sect1 xml:id="config-synopsis"> <title>Synopsis</title> <indexterm><primary>system configuration</primary></indexterm> @@ -80,8 +67,7 @@ <itemizedlist> <listitem> - <para>Understand &unix; and &os; basics (<xref - linkend="basics"/>).</para> + <para>Understand &unix; and &os; basics (<xref linkend="basics"/>).</para> </listitem> <listitem> <para>Be familiar with the basics of kernel configuration/compilation @@ -90,7 +76,7 @@ </itemizedlist> </sect1> - <sect1 id="configtuning-initial"> + <sect1 xml:id="configtuning-initial"> <title>Initial Configuration</title> <sect2> @@ -151,7 +137,7 @@ </sect3> - <sect3 id="swap-design"> + <sect3 xml:id="swap-design"> <title>Swap Partition</title> <indexterm><primary>swap sizing</primary></indexterm> @@ -217,7 +203,7 @@ </sect1> - <sect1 id="configtuning-core-configuration"> + <sect1 xml:id="configtuning-core-configuration"> <title>Core Configuration</title> <indexterm> @@ -277,7 +263,7 @@ </sect1> - <sect1 id="configtuning-appconfig"> + <sect1 xml:id="configtuning-appconfig"> <title>Application Configuration</title> <para>Typically, installed applications have their own @@ -320,18 +306,14 @@ </sect1> - <sect1 id="configtuning-starting-services"> - <sect1info> + <sect1 xml:id="configtuning-starting-services"> + <info><title>Starting Services</title> <authorgroup> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> + </info> - <title>Starting Services</title> + <indexterm><primary>services</primary></indexterm> @@ -339,8 +321,8 @@ from the Ports Collection. In many of these situations it may be necessary to configure the software in a manner which will allow it to be started upon system initialization. Services, - such as <filename role="package">mail/postfix</filename> or - <filename role="package">www/apache13</filename> are just two + such as <package>mail/postfix</package> or + <package>www/apache13</package> are just two of the many software packages which may be started during system initialization. This section explains the procedures available for starting third party software.</para> @@ -353,7 +335,7 @@ <para>Before the advent of <filename>rc.d</filename>, applications would drop a simple start up script into the - <filename class="directory">/usr/local/etc/rc.d</filename> + <filename>/usr/local/etc/rc.d</filename> directory which would be read by the system initialization scripts. These scripts would then be executed during the latter stages of system start up.</para> @@ -404,7 +386,7 @@ exit 0</programlisting> <para>Could be started manually with:</para> - <screen>&prompt.root; <userinput><filename>/usr/local/etc/rc.d/utility.sh</filename> start</userinput></screen> + <screen>&prompt.root; <userinput>/usr/local/etc/rc.d/utility.sh start</userinput></screen> <para>While not all third party software requires the line in <filename>rc.conf</filename>, almost every day a new port will @@ -498,18 +480,13 @@ run_rc_command "$1"</programlisting> </sect2> </sect1> - <sect1 id="configtuning-cron"> - <sect1info> + <sect1 xml:id="configtuning-cron"> + <info><title>Configuring the <command>cron</command> Utility</title> <authorgroup> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - <contrib>Contributed by </contrib> - <!-- 20 May 2003 --> - </author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> - <title>Configuring the <command>cron</command> Utility</title> + </info> + <indexterm><primary>cron</primary> <secondary>configuration</secondary></indexterm> @@ -534,14 +511,14 @@ run_rc_command "$1"</programlisting> <note> <para>User crontabs allow individual users to schedule tasks without the - need for <username>root</username> privileges. Commands in a user's crontab run with the + need for <systemitem class="username">root</systemitem> privileges. Commands in a user's crontab run with the permissions of the user who owns the crontab.</para> - <para>The <username>root</username> user can have a user crontab just like + <para>The <systemitem class="username">root</systemitem> user can have a user crontab just like any other user. This one is different from <filename>/etc/crontab</filename> (the system crontab). Because of the system crontab, there is usually no need to create a user crontab - for <username>root</username>.</para> + for <systemitem class="username">root</systemitem>.</para> </note> <para>Let us take a look at the <filename>/etc/crontab</filename> file @@ -551,17 +528,17 @@ run_rc_command "$1"</programlisting> <programlisting># /etc/crontab - root's crontab for &os; # # $&os;: src/etc/crontab,v 1.32 2002/11/22 16:13:39 tom Exp $ -# <co id="co-comments"/> +# <co xml:id="co-comments"/> # SHELL=/bin/sh -PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <co id="co-env"/> +PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin <co xml:id="co-env"/> HOME=/var/log # # -#minute hour mday month wday who command <co id="co-field-descr"/> +#minute hour mday month wday who command <co xml:id="co-field-descr"/> # # -*/5 * * * * root /usr/libexec/atrun <co id="co-main"/> +*/5 * * * * root /usr/libexec/atrun <co xml:id="co-main"/> </programlisting> <calloutlist> @@ -612,7 +589,7 @@ HOME=/var/log mean <quote>first-last</quote>, and can be interpreted as <emphasis>every</emphasis> time. So, judging by this line, it is apparent that the <command>atrun</command> command is to be invoked by - <username>root</username> every five minutes regardless of what + <systemitem class="username">root</systemitem> every five minutes regardless of what day or month it is. For more information on the <command>atrun</command> command, see the &man.atrun.8; manual page.</para> @@ -631,7 +608,7 @@ HOME=/var/log files.</para> - <sect2 id="configtuning-installcrontab"> + <sect2 xml:id="configtuning-installcrontab"> <title>Installing a Crontab</title> <important> @@ -640,8 +617,8 @@ HOME=/var/log editor: the <command>cron</command> utility will notice that the file has changed and immediately begin using the updated version. See - <ulink url="&url.books.faq;/admin.html#ROOT-NOT-FOUND-CRON-ERRORS"> - this FAQ entry </ulink> for more information.</para> + <link xlink:href="&url.books.faq;/admin.html#ROOT-NOT-FOUND-CRON-ERRORS"> + this FAQ entry </link> for more information.</para> </important> <para>To install a freshly written user @@ -675,19 +652,14 @@ HOME=/var/log </sect2> </sect1> - <sect1 id="configtuning-rcd"> - <sect1info> + <sect1 xml:id="configtuning-rcd"> + <info><title>Using rc under &os;</title> <authorgroup> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - <contrib>Contributed by </contrib> - <!-- 16 May 2003 --> - </author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> + </info> - <title>Using rc under &os;</title> + <para>In 2002 &os; integrated the NetBSD <filename>rc.d</filename> system for system initialization. @@ -747,7 +719,7 @@ $sshd_enable=YES</screen> <note> <para>The second line (<literal># sshd</literal>) is the output - from the <command>sshd</command> command, not a <username>root</username> + from the <command>sshd</command> command, not a <systemitem class="username">root</systemitem> console.</para> </note> @@ -814,19 +786,14 @@ sshd is running as pid 433.</screen> and &man.rc.subr.8; manual pages.</para> </sect1> - <sect1 id="config-network-setup"> - <sect1info> + <sect1 xml:id="config-network-setup"> + <info><title>Setting Up Network Interface Cards</title> <authorgroup> - <author> - <firstname>Marc</firstname> - <surname>Fonvieille</surname> - <contrib>Contributed by </contrib> - <!-- 6 October 2002 --> - </author> + <author><personname><firstname>Marc</firstname><surname>Fonvieille</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> + </info> - <title>Setting Up Network Interface Cards</title> + <indexterm> <primary>network cards</primary> @@ -854,7 +821,7 @@ sshd is running as pid 433.</screen> <para>Once you are sure your card is supported, you need to determine the proper driver for the card. <filename>/usr/src/sys/conf/NOTES</filename> and - <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> will give you + <filename>/usr/src/sys/arch/conf/NOTES</filename> will give you the list of network interface drivers with some information about the supported chipsets/cards. If you have doubts about which driver is the correct one, read the manual page of the @@ -900,17 +867,16 @@ ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto</screen> <para>Alternatively, you may statically compile the support for your card into your kernel. Check <filename>/usr/src/sys/conf/NOTES</filename>, - <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> + <filename>/usr/src/sys/arch/conf/NOTES</filename> and the manual page of the driver to know what to add in your kernel configuration file. For more information - about recompiling your kernel, please see <xref - linkend="kernelconfig"/>. If your card was detected at + about recompiling your kernel, please see <xref linkend="kernelconfig"/>. If your card was detected at boot by your kernel (<filename>GENERIC</filename>) you do not have to build a new kernel.</para> </listitem> </itemizedlist> - <sect3 id="config-network-ndis"> + <sect3 xml:id="config-network-ndis"> <title>Using &windows; NDIS Drivers</title> <indexterm><primary>NDIS</primary></indexterm> @@ -982,16 +948,16 @@ linuxemu/chapter.xml --> <para>The next step is to compile the driver binary into a loadable kernel module. To accomplish this, as - <username>root</username>, use &man.ndisgen.8;:</para> + <systemitem class="username">root</systemitem>, use &man.ndisgen.8;:</para> - <screen>&prompt.root; <userinput>ndisgen <replaceable>/path/to/W32DRIVER.INF</replaceable> <replaceable>/path/to/W32DRIVER.SYS</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>ndisgen /path/to/W32DRIVER.INF /path/to/W32DRIVER.SYS</userinput></screen> <para>The &man.ndisgen.8; utility is interactive and will prompt for any extra information it requires; it will produce a kernel module in the current directory which can be loaded as follows:</para> - <screen>&prompt.root; <userinput>kldload <replaceable>./W32DRIVER.ko</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>kldload ./W32DRIVER.ko</userinput></screen> <para>In addition to the generated kernel module, you must load the <filename>ndis.ko</filename> and @@ -1018,14 +984,13 @@ ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps</screen> <para>From here you can treat the - <devicename>ndis0</devicename> device like any other network - interface (e.g., <devicename>dc0</devicename>).</para> + <filename>ndis0</filename> device like any other network + interface (e.g., <filename>dc0</filename>).</para> <para>You can configure the system to load the NDIS modules at boot time in the same way as with any other module. First, copy the generated module, - <filename>W32DRIVER.ko</filename>, to the <filename - class="directory">/boot/modules</filename> directory. Then, + <filename>W32DRIVER.ko</filename>, to the <filename>/boot/modules</filename> directory. Then, add the following line to <filename>/boot/loader.conf</filename>:</para> @@ -1079,37 +1044,37 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen> <itemizedlist> <listitem> - <para><devicename>dc0</devicename>: The first Ethernet + <para><filename>dc0</filename>: The first Ethernet interface</para> </listitem> <listitem> - <para><devicename>dc1</devicename>: The second Ethernet + <para><filename>dc1</filename>: The second Ethernet interface</para> </listitem> <listitem> - <para><devicename>lp0</devicename>: The parallel port + <para><filename>lp0</filename>: The parallel port interface</para> </listitem> <listitem> - <para><devicename>lo0</devicename>: The loopback device</para> + <para><filename>lo0</filename>: The loopback device</para> </listitem> <listitem> - <para><devicename>tun0</devicename>: The tunnel device used by + <para><filename>tun0</filename>: The tunnel device used by <application>ppp</application></para> </listitem> </itemizedlist> <para>&os; uses the driver name followed by the order in which one the card is detected at the kernel boot to name the - network card. For example <devicename>sis2</devicename> would + network card. For example <filename>sis2</filename> would be the third network card on the system using the &man.sis.4; driver.</para> - <para>In this example, the <devicename>dc0</devicename> device is + <para>In this example, the <filename>dc0</filename> device is up and running. The key indicators are:</para> <orderedlist> @@ -1121,30 +1086,30 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen> <listitem> <para>The card has an Internet (<literal>inet</literal>) address (in this case - <hostid role="ipaddr">192.168.1.3</hostid>).</para> + <systemitem class="ipaddress">192.168.1.3</systemitem>).</para> </listitem> <listitem> <para>It has a valid subnet mask (<literal>netmask</literal>; - <hostid role="netmask">0xffffff00</hostid> is the same as - <hostid role="netmask">255.255.255.0</hostid>).</para> + <systemitem class="netmask">0xffffff00</systemitem> is the same as + <systemitem class="netmask">255.255.255.0</systemitem>).</para> </listitem> <listitem> <para>It has a valid broadcast address (in this case, - <hostid role="ipaddr">192.168.1.255</hostid>).</para> + <systemitem class="ipaddress">192.168.1.255</systemitem>).</para> </listitem> <listitem> <para>The MAC address of the card (<literal>ether</literal>) - is <hostid role="mac">00:a0:cc:da:da:da</hostid></para> + is <systemitem class="etheraddress">00:a0:cc:da:da:da</systemitem></para> </listitem> <listitem> <para>The physical media selection is on autoselection mode (<literal>media: Ethernet autoselect (100baseTX <full-duplex>)</literal>). We see that - <devicename>dc1</devicename> was configured to run with + <filename>dc1</filename> was configured to run with <literal>10baseT/UTP</literal> media. For more information on available media types for a driver, please refer to its manual page.</para> @@ -1153,7 +1118,7 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen> <listitem> <para>The status of the link (<literal>status</literal>) is <literal>active</literal>, i.e. the carrier is detected. - For <devicename>dc1</devicename>, we see + For <filename>dc1</filename>, we see <literal>status: no carrier</literal>. This is normal when an Ethernet cable is not plugged into the card.</para> </listitem> @@ -1167,7 +1132,7 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen> <para>it would indicate the card has not been configured.</para> - <para>To configure your card, you need <username>root</username> + <para>To configure your card, you need <systemitem class="username">root</systemitem> privileges. The network card configuration can be done from the command line with &man.ifconfig.8; but you would have to do it after each reboot of the system. The file @@ -1181,8 +1146,8 @@ tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen> <programlisting>ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0" ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP"</programlisting> - <para>You have to replace <devicename>dc0</devicename>, - <devicename>dc1</devicename>, and so on, with + <para>You have to replace <filename>dc0</filename>, + <filename>dc1</filename>, and so on, with the correct device for your cards, and the addresses with the proper ones. You should read the card driver and &man.ifconfig.8; manual pages for more details about the allowed @@ -1255,7 +1220,7 @@ PING 192.168.1.2 (192.168.1.2): 56 data bytes round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen> <para>You could also use the machine name instead of - <hostid role="ipaddr">192.168.1.2</hostid> if you have set up the + <systemitem class="ipaddress">192.168.1.2</systemitem> if you have set up the <filename>/etc/hosts</filename> file.</para> </sect3> @@ -1301,15 +1266,13 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen> This can happen if no default route is specified, or if a cable is unplugged. Check the output of <command>netstat -rn</command> and make sure there is a valid route to the host - you are trying to reach. If there is not, read on to <xref - linkend="advanced-networking"/>.</para> + you are trying to reach. If there is not, read on to <xref linkend="advanced-networking"/>.</para> <para><errorname>ping: sendto: Permission denied</errorname> error messages are often caused by a misconfigured firewall. If <command>ipfw</command> is enabled in the kernel but no rules have been defined, then the default policy is to deny all - traffic, even ping requests! Read on to <xref - linkend="firewalls"/> for more information.</para> + traffic, even ping requests! Read on to <xref linkend="firewalls"/> for more information.</para> <para>Sometimes performance of the card is poor, or below average. In these cases it is best to set the media selection mode @@ -1322,7 +1285,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen> </sect2> </sect1> - <sect1 id="configtuning-virtual-hosts"> + <sect1 xml:id="configtuning-virtual-hosts"> <title>Virtual Hosts</title> <indexterm><primary>virtual hosts</primary></indexterm> @@ -1339,7 +1302,7 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen> normally added by placing alias entries in <filename>/etc/rc.conf</filename>.</para> - <para>An alias entry for the interface <devicename>fxp0</devicename> + <para>An alias entry for the interface <filename>fxp0</filename> looks like:</para> <programlisting>ifconfig_fxp0_alias0="inet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx"</programlisting> @@ -1354,27 +1317,27 @@ round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms</screen> one address which correctly represents the network's netmask. Any other addresses which fall within this network must have a netmask of all <literal>1</literal>s (expressed as either - <hostid role="netmask">255.255.255.255</hostid> or <hostid role="netmask">0xffffffff</hostid>). + <systemitem class="netmask">255.255.255.255</systemitem> or <systemitem class="netmask">0xffffffff</systemitem>). </para> <para>For example, consider the case where the - <devicename>fxp0</devicename> interface is - connected to two networks, the <hostid role="ipaddr">10.1.1.0</hostid> - network with a netmask of <hostid role="netmask">255.255.255.0</hostid> - and the <hostid role="ipaddr">202.0.75.16</hostid> network with - a netmask of <hostid role="netmask">255.255.255.240</hostid>. - We want the system to appear at <hostid role="ipaddr">10.1.1.1</hostid> - through <hostid role="ipaddr">10.1.1.5</hostid> and at - <hostid role="ipaddr">202.0.75.17</hostid> through - <hostid role="ipaddr">202.0.75.20</hostid>. As noted above, only the + <filename>fxp0</filename> interface is + connected to two networks, the <systemitem class="ipaddress">10.1.1.0</systemitem> + network with a netmask of <systemitem class="netmask">255.255.255.0</systemitem> + and the <systemitem class="ipaddress">202.0.75.16</systemitem> network with + a netmask of <systemitem class="netmask">255.255.255.240</systemitem>. + We want the system to appear at <systemitem class="ipaddress">10.1.1.1</systemitem> + through <systemitem class="ipaddress">10.1.1.5</systemitem> and at + <systemitem class="ipaddress">202.0.75.17</systemitem> through + <systemitem class="ipaddress">202.0.75.20</systemitem>. As noted above, only the first address in a given network range (in this case, - <hostid role="ipaddr">10.0.1.1</hostid> and - <hostid role="ipaddr">202.0.75.17</hostid>) should have a real - netmask; all the rest (<hostid role="ipaddr">10.1.1.2</hostid> - through <hostid role="ipaddr">10.1.1.5</hostid> and - <hostid role="ipaddr">202.0.75.18</hostid> through - <hostid role="ipaddr">202.0.75.20</hostid>) must be configured with a - netmask of <hostid role="netmask">255.255.255.255</hostid>.</para> + <systemitem class="ipaddress">10.0.1.1</systemitem> and + <systemitem class="ipaddress">202.0.75.17</systemitem>) should have a real + netmask; all the rest (<systemitem class="ipaddress">10.1.1.2</systemitem> + through <systemitem class="ipaddress">10.1.1.5</systemitem> and + <systemitem class="ipaddress">202.0.75.18</systemitem> through + <systemitem class="ipaddress">202.0.75.20</systemitem>) must be configured with a + netmask of <systemitem class="netmask">255.255.255.255</systemitem>.</para> <para>The following <filename>/etc/rc.conf</filename> entries configure the adapter correctly for this arrangement:</para> @@ -1391,7 +1354,7 @@ ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255"</programlisting> </sect1> - <sect1 id="configtuning-configfiles"> + <sect1 xml:id="configtuning-configfiles"> <title>Configuration Files</title> <sect2> @@ -1667,7 +1630,7 @@ cron.* /var/log/cron </sect3> </sect2> - <sect2 id="configtuning-sysctlconf"> + <sect2 xml:id="configtuning-sysctlconf"> <title><filename>sysctl.conf</filename></title> <indexterm><primary>sysctl.conf</primary></indexterm> @@ -1689,7 +1652,7 @@ compat.linux.osrelease=4.3-STABLE</programlisting> </sect2> </sect1> - <sect1 id="configtuning-sysctl"> + <sect1 xml:id="configtuning-sysctl"> <title>Tuning with sysctl</title> <indexterm><primary>sysctl</primary></indexterm> @@ -1735,18 +1698,13 @@ kern.maxfiles: 2088 -> 5000</screen> see the &man.sysctl.conf.5; manual page and the <xref linkend="configtuning-sysctlconf"/>.</para> - <sect2 id="sysctl-readonly"> - <sect2info> + <sect2 xml:id="sysctl-readonly"> + <info><title>&man.sysctl.8; Read-only</title> <authorgroup> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - <contrib>Contributed by </contrib> - <!-- 31 January 2003 --> - </author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect2info> - <title>&man.sysctl.8; Read-only</title> + </info> + <para>In some cases it may be desirable to modify read-only &man.sysctl.8; values. While this is sometimes unavoidable, it can only be done @@ -1772,7 +1730,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen> </sect2> </sect1> - <sect1 id="configtuning-disk"> + <sect1 xml:id="configtuning-disk"> <title>Tuning Disks</title> <sect2> @@ -1928,7 +1886,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen> </sect3> </sect2> - <sect2 id="soft-updates"> + <sect2 xml:id="soft-updates"> <title>Soft Updates</title> <indexterm><primary>Soft Updates</primary></indexterm> @@ -2110,7 +2068,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen> </sect2> </sect1> - <sect1 id="configtuning-kernel-limits"> + <sect1 xml:id="configtuning-kernel-limits"> <title>Tuning Kernel Limits</title> <indexterm> @@ -2118,10 +2076,10 @@ device_probe_and_attach: cbb0 attach returned 12</screen> <secondary>kernel limits</secondary> </indexterm> - <sect2 id="file-process-limits"> + <sect2 xml:id="file-process-limits"> <title>File/Process Limits</title> - <sect3 id="kern-maxfiles"> + <sect3 xml:id="kern-maxfiles"> <title><varname>kern.maxfiles</varname></title> <indexterm> @@ -2191,7 +2149,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen> If, however, you see the dreaded <errortype>proc table full</errortype> error when trying to start another program, or are running a server with a large number of simultaneous users (like - <hostid role="fqdn">ftp.FreeBSD.org</hostid>), you can always + <systemitem class="fqdomainname">ftp.FreeBSD.org</systemitem>), you can always increase the number and rebuild.</para> <note> @@ -2201,8 +2159,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen> the maximum number of users you will likely have on your system and how many processes each of them will be running. One keyword which <emphasis>does</emphasis> limit the number of simultaneous - remote logins and X terminal windows is <link - linkend="kernelconfig-ptys"><literal>pseudo-device pty + remote logins and X terminal windows is <link linkend="kernelconfig-ptys"><literal>pseudo-device pty 16</literal></link>. With &os; 5.X, you do not have to worry about this number since the &man.pty.4; driver is <quote>auto-cloning</quote>; you simply use the line @@ -2232,7 +2189,7 @@ device_probe_and_attach: cbb0 attach returned 12</screen> </sect3> </sect2> - <sect2 id="nmbclusters"> + <sect2 xml:id="nmbclusters"> <title>Network Limits</title> <para>The <literal>NMBCLUSTERS</literal> kernel configuration @@ -2401,7 +2358,7 @@ kern.maxvnodes: 100000</programlisting> </sect2> </sect1> - <sect1 id="adding-swap-space"> + <sect1 xml:id="adding-swap-space"> <title>Adding Swap Space</title> <para>No matter how well you plan, sometimes a system does not run @@ -2414,7 +2371,7 @@ kern.maxvnodes: 100000</programlisting> for this task exist and why it should be done, please refer to <xref linkend="swap-encrypting"/> of the Handbook.</para> - <sect2 id="new-drive-swap"> + <sect2 xml:id="new-drive-swap"> <title>Swap on a New Hard Drive</title> <para>The best way to add swap, of course, is to use this as an @@ -2426,7 +2383,7 @@ kern.maxvnodes: 100000</programlisting> arrange your swap.</para> </sect2> - <sect2 id="nfs-swap"> + <sect2 xml:id="nfs-swap"> <title>Swapping over NFS</title> <para>Swapping over NFS is only recommended if you do not have a @@ -2435,7 +2392,7 @@ kern.maxvnodes: 100000</programlisting> burden on the NFS server.</para> </sect2> - <sect2 id="create-swapfile"> + <sect2 xml:id="create-swapfile"> <title>Swapfiles</title> <para>You can create a file of a specified size to use as a swap @@ -2486,22 +2443,15 @@ kern.maxvnodes: 100000</programlisting> </sect2> </sect1> - <sect1 id="acpi-overview"> - <sect1info> + <sect1 xml:id="acpi-overview"> + <info><title>Power and Resource Management</title> <authorgroup> - <author> - <firstname>Hiten</firstname> - <surname>Pandya</surname> - <contrib>Written by </contrib> - </author> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - </author> + <author><personname><firstname>Hiten</firstname><surname>Pandya</surname></personname><contrib>Written by </contrib></author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname></author> </authorgroup> - </sect1info> + </info> - <title>Power and Resource Management</title> + <para>It is very important to utilize hardware resources in an efficient manner. Before <acronym>ACPI</acronym> was introduced, @@ -2519,7 +2469,7 @@ kern.maxvnodes: 100000</programlisting> comprehensive information about <acronym>ACPI</acronym>. References will be provided for further reading at the end.</para> - <sect2 id="acpi-intro"> + <sect2 xml:id="acpi-intro"> <title>What Is ACPI?</title> <indexterm> @@ -2545,7 +2495,7 @@ kern.maxvnodes: 100000</programlisting> (Advanced Power Management).</para> </sect2> - <sect2 id="acpi-old-spec"> + <sect2 xml:id="acpi-old-spec"> <title>Shortcomings of Advanced Power Management (APM)</title> <para>The <emphasis>Advanced Power Management (APM)</emphasis> @@ -2582,7 +2532,7 @@ kern.maxvnodes: 100000</programlisting> the &man.apm.4; manual page.</para> </sect2> - <sect2 id="acpi-config"> + <sect2 xml:id="acpi-config"> <title>Configuring <acronym>ACPI</acronym></title> <para>The <filename>acpi.ko</filename> driver is loaded by default @@ -2616,29 +2566,18 @@ kern.maxvnodes: 100000</programlisting> </sect2> </sect1> - <sect1 id="ACPI-debug"> - <sect1info> + <sect1 xml:id="ACPI-debug"> + <info><title>Using and Debugging &os; <acronym>ACPI</acronym></title> <authorgroup> - <author> - <firstname>Nate</firstname> - <surname>Lawson</surname> - <contrib>Written by </contrib> - </author> + <author><personname><firstname>Nate</firstname><surname>Lawson</surname></personname><contrib>Written by </contrib></author> </authorgroup> <authorgroup> - <author> - <firstname>Peter</firstname> - <surname>Schultz</surname> - <contrib>With contributions from </contrib> - </author> - <author> - <firstname>Tom</firstname> - <surname>Rhodes</surname> - </author> + <author><personname><firstname>Peter</firstname><surname>Schultz</surname></personname><contrib>With contributions from </contrib></author> + <author><personname><firstname>Tom</firstname><surname>Rhodes</surname></personname></author> </authorgroup> - </sect1info> + </info> - <title>Using and Debugging &os; <acronym>ACPI</acronym></title> + <indexterm> <primary>ACPI</primary> @@ -2661,7 +2600,7 @@ kern.maxvnodes: 100000</programlisting> Thanks for reading this and we hope we can solve your system's problems.</para> - <sect2 id="ACPI-submitdebug"> + <sect2 xml:id="ACPI-submitdebug"> <title>Submitting Debugging Information</title> <note> @@ -2672,8 +2611,8 @@ kern.maxvnodes: 100000</programlisting> <para>For those of you that want to submit a problem right away, please send the following information to - <ulink url="mailto:freebsd-acpi@FreeBSD.org"> - freebsd-acpi@FreeBSD.org</ulink>:</para> + <link xlink:href="mailto:freebsd-acpi@FreeBSD.org"> + freebsd-acpi@FreeBSD.org</link>:</para> <itemizedlist> <listitem> @@ -2710,7 +2649,7 @@ kern.maxvnodes: 100000</programlisting> very large. Generate a copy of your <acronym>ASL</acronym> by running this command:</para> - <screen>&prompt.root; <userinput>acpidump -t -d > <replaceable>name</replaceable>-<replaceable>system</replaceable>.asl</userinput></screen> + <screen>&prompt.root; <userinput>acpidump -t -d > name-system.asl</userinput></screen> <para>(Substitute your login name for <replaceable>name</replaceable> and manufacturer/model for @@ -2733,7 +2672,7 @@ kern.maxvnodes: 100000</programlisting> reported by someone before.</para> </sect2> - <sect2 id="ACPI-background"> + <sect2 xml:id="ACPI-background"> <title>Background</title> <indexterm> @@ -2769,16 +2708,16 @@ kern.maxvnodes: 100000</programlisting> provided an interpreter (<acronym>ACPI-CA</acronym>) that is shared with Linux and NetBSD. The path to the <acronym>ACPI-CA</acronym> source code is - <filename class="directory">src/sys/contrib/dev/acpica</filename>. + <filename>src/sys/contrib/dev/acpica</filename>. The glue code that allows <acronym>ACPI-CA</acronym> to work on &os; is in <filename>src/sys/dev/acpica/Osd</filename>. Finally, drivers that implement various <acronym>ACPI</acronym> devices are found in - <filename class="directory">src/sys/dev/acpica</filename>.</para> + <filename>src/sys/dev/acpica</filename>.</para> </sect2> - <sect2 id="ACPI-comprob"> + <sect2 xml:id="ACPI-comprob"> <title>Common Problems</title> <indexterm> @@ -2971,7 +2910,7 @@ hw.acpi.s4bios: 0</screen> </sect3> </sect2> - <sect2 id="ACPI-aslanddump"> + <sect2 xml:id="ACPI-aslanddump"> <title><acronym>ASL</acronym>, <command>acpidump</command>, and <acronym>IASL</acronym></title> @@ -3013,7 +2952,7 @@ hw.acpi.s4bios: 0</screen> <screen>&prompt.root; <userinput>iasl your.asl</userinput></screen> </sect2> - <sect2 id="ACPI-fixasl"> + <sect2 xml:id="ACPI-fixasl"> <title>Fixing Your <acronym>ASL</acronym></title> <indexterm> @@ -3098,11 +3037,11 @@ hw.acpi.s4bios: 0</screen> acpi_dsdt_name="/boot/DSDT.aml"</programlisting> <para>Be sure to copy your <filename>DSDT.aml</filename> to the - <filename class="directory">/boot</filename> directory.</para> + <filename>/boot</filename> directory.</para> </sect3> </sect2> - <sect2 id="ACPI-debugoutput"> + <sect2 xml:id="ACPI-debugoutput"> <title>Getting Debugging Output From <acronym>ACPI</acronym></title> @@ -3145,7 +3084,7 @@ acpi_dsdt_name="/boot/DSDT.aml"</programlisting> make ACPI_DEBUG=1</userinput></screen> <para>Install <filename>acpi.ko</filename> in - <filename class="directory">/boot/kernel</filename> and add your + <filename>/boot/kernel</filename> and add your desired level and layer to <filename>loader.conf</filename>. This example enables debug messages for all <acronym>ACPI-CA</acronym> components and all @@ -3165,7 +3104,7 @@ debug.acpi.level="ACPI_LV_ERROR"</programlisting> in <filename>loader.conf</filename>.</para> </sect2> - <sect2 id="ACPI-References"> + <sect2 xml:id="ACPI-References"> <title>References</title> <para>More information about <acronym>ACPI</acronym> may be found @@ -3178,17 +3117,17 @@ debug.acpi.level="ACPI_LV_ERROR"</programlisting> <listitem> <para>The <acronym>ACPI</acronym> Mailing List Archives - <ulink url="http://lists.freebsd.org/pipermail/freebsd-acpi/"></ulink></para> + <uri xlink:href="http://lists.freebsd.org/pipermail/freebsd-acpi/">http://lists.freebsd.org/pipermail/freebsd-acpi/</uri></para> </listitem> <listitem> <para>The old <acronym>ACPI</acronym> Mailing List Archives - <ulink url="http://home.jp.FreeBSD.org/mail-list/acpi-jp/"></ulink></para> + <uri xlink:href="http://home.jp.FreeBSD.org/mail-list/acpi-jp/">http://home.jp.FreeBSD.org/mail-list/acpi-jp/</uri></para> </listitem> <listitem> <para>The <acronym>ACPI</acronym> 2.0 Specification - <ulink url="http://acpi.info/spec.htm"></ulink></para> + <uri xlink:href="http://acpi.info/spec.htm">http://acpi.info/spec.htm</uri></para> </listitem> <listitem> @@ -3198,9 +3137,8 @@ debug.acpi.level="ACPI_LV_ERROR"</programlisting> </listitem> <listitem> - <para><ulink - url="http://www.cpqlinux.com/acpi-howto.html#fix_broken_dsdt"> - <acronym>DSDT</acronym> debugging resource</ulink>. + <para><link xlink:href="http://www.cpqlinux.com/acpi-howto.html#fix_broken_dsdt"> + <acronym>DSDT</acronym> debugging resource</link>. (Uses Compaq as an example but generally useful.)</para> </listitem> </itemizedlist> |