diff options
Diffstat (limited to 'pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.xml')
| -rw-r--r-- | pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.xml | 205 |
1 files changed, 85 insertions, 120 deletions
diff --git a/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.xml b/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.xml index c0f83bd4fd..9fe1caf318 100644 --- a/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.xml +++ b/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.xml @@ -4,42 +4,24 @@ $FreeBSD$ --> - -<chapter id="cutting-edge"> - <chapterinfo> +<chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="cutting-edge"> + <info><title>The Cutting Edge</title> <authorgroup> - <author> - <firstname>Jim</firstname> - <surname>Mock</surname> - <contrib>Restructured, reorganized, and parts updated by </contrib> - </author> + <author><personname><firstname>Jim</firstname><surname>Mock</surname></personname><contrib>Restructured, reorganized, and parts updated by </contrib></author> <!-- Mar 2000 --> </authorgroup> <authorgroup> - <author> - <firstname>Jordan</firstname> - <surname>Hubbard</surname> - <contrib>Original work by </contrib> - </author> - <author> - <firstname>Poul-Henning</firstname> - <surname>Kamp</surname> - </author> - <author> - <firstname>John</firstname> - <surname>Polstra</surname> - </author> - <author> - <firstname>Nik</firstname> - <surname>Clayton</surname> - </author> + <author><personname><firstname>Jordan</firstname><surname>Hubbard</surname></personname><contrib>Original work by </contrib></author> + <author><personname><firstname>Poul-Henning</firstname><surname>Kamp</surname></personname></author> + <author><personname><firstname>John</firstname><surname>Polstra</surname></personname></author> + <author><personname><firstname>Nik</firstname><surname>Clayton</surname></personname></author> </authorgroup> - <!-- with feedback from various others --> - </chapterinfo> + + </info> - <title>The Cutting Edge</title> + - <sect1 id="cutting-edge-synopsis"> + <sect1 xml:id="cutting-edge-synopsis"> <title>Synopsis</title> <para>&os; is under constant development between releases. For @@ -70,15 +52,14 @@ <para>Before reading this chapter, you should:</para> <itemizedlist> - <listitem><para>Properly set up your network connection (<xref - linkend="advanced-networking"/>).</para> + <listitem><para>Properly set up your network connection (<xref linkend="advanced-networking"/>).</para> </listitem> <listitem><para>Know how to install additional third-party software (<xref linkend="ports"/>).</para></listitem> </itemizedlist> </sect1> - <sect1 id="current-stable"> + <sect1 xml:id="current-stable"> <title>&os.current; vs. &os.stable;</title> <indexterm><primary>-CURRENT</primary></indexterm> <indexterm><primary>-STABLE</primary></indexterm> @@ -88,7 +69,7 @@ how to keep your system up-to-date with each respective tree. &os.current; will be discussed first, then &os.stable;.</para> - <sect2 id="current"> + <sect2 xml:id="current"> <title>Staying Current with &os;</title> <para>As you read this, keep in mind that &os.current; is the @@ -228,15 +209,14 @@ </listitem> <listitem> - <para>Use the <application><link - linkend="ctm">CTM</link></application><indexterm><primary>-CURRENT</primary><secondary>Syncing with CTM</secondary></indexterm> facility. If you + <para>Use the <application>CTM</application><indexterm><primary>-CURRENT</primary><secondary>Syncing with CTM</secondary></indexterm> facility. If you have very bad connectivity (high price connections or only email access) <application>CTM</application> is an option. However, it is a lot of hassle and can give you broken files. This leads to it being rarely used, which again increases the chance of it not working for fairly long periods of time. We recommend using - <application><link linkend="cvsup">CVSup</link></application> + <application>CVSup</application> for anybody with a 9600 bps modem or faster connection. </para> </listitem> @@ -253,8 +233,7 @@ <para>Before compiling &os.current;<indexterm><primary>-CURRENT</primary><secondary>compiling</secondary></indexterm>, read the <filename>Makefile</filename> in <filename>/usr/src</filename> - carefully. You should at least <link - linkend="makeworld">install a new kernel and rebuild the world</link> the first time through + carefully. You should at least <link linkend="makeworld">install a new kernel and rebuild the world</link> the first time through as part of the upgrading process. Reading the &a.current; and <filename>/usr/src/UPDATING</filename> will keep you up-to-date on other bootstrapping procedures that sometimes become necessary as we move toward the next @@ -272,7 +251,7 @@ </sect3> </sect2> - <sect2 id="stable"> + <sect2 xml:id="stable"> <title>Staying Stable with &os;</title> <sect3> @@ -306,8 +285,7 @@ support old releases of FreeBSD forever, although we do support them for many years. For a complete description of the current security policy for old releases of - FreeBSD, please see <ulink - url="&url.base;/security/">http://www.FreeBSD.org/security/</ulink>.</para> + FreeBSD, please see <link xlink:href="&url.base;/security/">http://www.FreeBSD.org/security/</link>.</para> </footnote> , and tracking an entire development branch just for security reasons is likely to bring in a lot of unwanted @@ -358,8 +336,8 @@ <listitem> <para>If you are going to install a new system and want it to run monthly snapshot built from &os.stable;, please - check the <ulink url="&url.base;/snapshots/"> - Snapshots</ulink> web page for more information. + check the <link xlink:href="&url.base;/snapshots/"> + Snapshots</link> web page for more information. Alternatively, it is possible to install the most recent &os.stable; release from the <link linkend="mirrors">mirror sites</link> and follow @@ -389,8 +367,7 @@ </listitem> <listitem> - <para>Use the <application><link - linkend="ctm">CTM</link></application><indexterm><primary>-STABLE</primary><secondary>syncing with CTM</secondary></indexterm> facility. If + <para>Use the <application>CTM</application><indexterm><primary>-STABLE</primary><secondary>syncing with CTM</secondary></indexterm> facility. If you do not have a fast and inexpensive connection to the Internet, this is the method you should consider using. @@ -409,8 +386,7 @@ <listitem> <para>Before compiling &os.stable;<indexterm><primary>-STABLE</primary><secondary>compiling</secondary></indexterm>, read the <filename>Makefile</filename> in <filename>/usr/src</filename> - carefully. You should at least <link - linkend="makeworld">install a new kernel and rebuild the world</link> the first time through + carefully. You should at least <link linkend="makeworld">install a new kernel and rebuild the world</link> the first time through as part of the upgrading process. Reading the &a.stable; and <filename>/usr/src/UPDATING</filename> will keep you up-to-date on other bootstrapping procedures that sometimes become necessary as we move toward the next @@ -421,15 +397,14 @@ </sect2> </sect1> - <sect1 id="synching"> + <sect1 xml:id="synching"> <title>Synchronizing Your Source</title> <para>There are various ways of using an Internet (or email) connection to stay up-to-date with any given area of the &os; project sources, or all areas, depending on what interests you. The primary services we offer are <link linkend="anoncvs">Anonymous - CVS</link>, <link linkend="cvsup">CVSup</link>, and <link - linkend="ctm">CTM</link>.</para> + CVS</link>, <link linkend="cvsup">CVSup</link>, and <link linkend="ctm">CTM</link>.</para> <warning> <para>While it is possible to update only parts of your source tree, @@ -495,7 +470,7 @@ <application>Anonymous CVS</application>, simply delete the bad bits and resync.</para> </sect1> - <sect1 id="makeworld"> + <sect1 xml:id="makeworld"> <title>Rebuilding <quote>world</quote></title> <indexterm> @@ -575,13 +550,13 @@ <note> <para>There are a few rare cases when an extra run of <command>mergemaster -p</command> is needed before the - <maketarget>buildworld</maketarget> step. These are + <buildtarget>buildworld</buildtarget> step. These are described in <filename>UPDATING</filename>. In general, though, you can safely omit this step if you are not updating across one or more major &os; versions.</para> </note> - <para>After <maketarget>installkernel</maketarget> finishes + <para>After <buildtarget>installkernel</buildtarget> finishes successfully, you should boot in single user mode (i.e. using <command>boot -s</command> from the loader prompt). Then run:</para> @@ -638,14 +613,14 @@ idea to set them to something sensible for your system.</para> <para>A typical user will probably want to copy the - <makevar>CFLAGS</makevar> and - <makevar>NO_PROFILE</makevar> lines found in + <varname>CFLAGS</varname> and + <varname>NO_PROFILE</varname> lines found in <filename>/usr/share/examples/etc/make.conf</filename> to <filename>/etc/make.conf</filename> and uncomment them.</para> - <para>Examine the other definitions (<makevar>COPTFLAGS</makevar>, - <makevar>NOPORTDOCS</makevar> and so + <para>Examine the other definitions (<varname>COPTFLAGS</varname>, + <varname>NOPORTDOCS</varname> and so on) and decide if they are relevant to you.</para> </sect2> @@ -669,7 +644,7 @@ these users or groups exist.</para> <para>An example of this is when the - <username>smmsp</username> user was added. Users had the + <systemitem class="username">smmsp</systemitem> user was added. Users had the installation process fail for them when &man.mtree.8; was trying to create <filename>/var/spool/clientmqueue</filename>.</para> @@ -677,8 +652,8 @@ <para>The solution is to run &man.mergemaster.8; in pre-buildworld mode by providing the <option>-p</option> option. This will compare only those files that are essential for the success - of <maketarget>buildworld</maketarget> or - <maketarget>installworld</maketarget>. If your old version of + of <buildtarget>buildworld</buildtarget> or + <buildtarget>installworld</buildtarget>. If your old version of <command>mergemaster</command> does not support <option>-p</option>, use the new version in the source tree when running for the first time:</para> @@ -691,7 +666,7 @@ system to see which files are owned by the group you are renaming or deleting:</para> - <screen>&prompt.root; <userinput>find / -group <replaceable>GID</replaceable> -print</userinput></screen> + <screen>&prompt.root; <userinput>find / -group GID -print</userinput></screen> <para>will show all files owned by group <replaceable>GID</replaceable> (which can be either a group name @@ -699,7 +674,7 @@ </tip> </sect2> - <sect2 id="makeworld-singleuser"> + <sect2 xml:id="makeworld-singleuser"> <title>Drop to Single User Mode</title> <indexterm><primary>single-user mode</primary></indexterm> @@ -716,8 +691,8 @@ then drop into single user mode for the installation. If you would like to do it this way, simply hold off on the following steps until the build has completed. You can postpone dropping to single user - mode until you have to <maketarget>installkernel</maketarget> or - <maketarget>installworld</maketarget>.</para> + mode until you have to <buildtarget>installkernel</buildtarget> or + <buildtarget>installworld</buildtarget>.</para> <para>As the superuser, you can execute:</para> @@ -776,7 +751,7 @@ &prompt.root; <userinput>rm -rf *</userinput></screen> </sect2> - <sect2 id="cutting-edge-compilebase"> + <sect2 xml:id="cutting-edge-compilebase"> <title>Recompile the Base System</title> <sect3> @@ -805,10 +780,10 @@ Script done, …</screen> in <filename>/tmp</filename>. This directory may be cleared next time you reboot. A better place to store it is in <filename>/var/tmp</filename> (as in the previous example) or - in <username>root</username>'s home directory.</para> + in <systemitem class="username">root</systemitem>'s home directory.</para> </sect3> - <sect3 id="make-buildworld"> + <sect3 xml:id="make-buildworld"> <title>Compile the Base System</title> <para>You must be in the <filename>/usr/src</filename> @@ -828,7 +803,7 @@ Script done, …</screen> <para>The general format of the command line you will type is as follows:</para> - <screen>&prompt.root; <userinput>make -<replaceable>x</replaceable> -D<replaceable>VARIABLE</replaceable> <replaceable>target</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>make -x -DVARIABLE target</userinput></screen> <para>In this example, <option>-<replaceable>x</replaceable></option> is an option that you would pass to &man.make.1;. See the @@ -842,7 +817,7 @@ Script done, …</screen> <filename>/etc/make.conf</filename>, and this provides another way of setting them.</para> - <screen>&prompt.root; <userinput>make -DNO_PROFILE <replaceable>target</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>make -DNO_PROFILE target</userinput></screen> <para>is another way of specifying that profiled libraries should not be built, and corresponds with the</para> @@ -866,37 +841,37 @@ Script done, …</screen> &man.make.1;, and so your command like will look like this:</para> - <screen>&prompt.root; <userinput>make <replaceable>target</replaceable></userinput></screen> + <screen>&prompt.root; <userinput>make target</userinput></screen> <para>Where <replaceable>target</replaceable> will be one of many build options. The first target should always be - <makevar>buildworld</makevar>.</para> + <varname>buildworld</varname>.</para> - <para>As the names imply, <maketarget>buildworld</maketarget> + <para>As the names imply, <buildtarget>buildworld</buildtarget> builds a complete new tree under <filename>/usr/obj</filename>, - and <maketarget>installworld</maketarget>, another target, installs this tree on + and <buildtarget>installworld</buildtarget>, another target, installs this tree on the current machine.</para> <para>Having separate options is very useful for two reasons. First, it allows you to do the build safe in the knowledge that no components of your running system will be affected. The build is <quote>self hosted</quote>. Because of this, you can safely - run <maketarget>buildworld</maketarget> on a machine running + run <buildtarget>buildworld</buildtarget> on a machine running in multi-user mode with no fear of ill-effects. It is still recommended that you run the - <maketarget>installworld</maketarget> part in single user + <buildtarget>installworld</buildtarget> part in single user mode, though.</para> <para>Secondly, it allows you to use NFS mounts to upgrade multiple machines on your network. If you have three machines, - <hostid>A</hostid>, <hostid>B</hostid> and <hostid>C</hostid> that you want to upgrade, run <command>make + <systemitem>A</systemitem>, <systemitem>B</systemitem> and <systemitem>C</systemitem> that you want to upgrade, run <command>make buildworld</command> and <command>make installworld</command> on - <hostid>A</hostid>. <hostid>B</hostid> and <hostid>C</hostid> should then NFS mount <filename>/usr/src</filename> - and <filename>/usr/obj</filename> from <hostid>A</hostid>, and you can then run + <systemitem>A</systemitem>. <systemitem>B</systemitem> and <systemitem>C</systemitem> should then NFS mount <filename>/usr/src</filename> + and <filename>/usr/obj</filename> from <systemitem>A</systemitem>, and you can then run <command>make installworld</command> to install the results of - the build on <hostid>B</hostid> and <hostid>C</hostid>.</para> + the build on <systemitem>B</systemitem> and <systemitem>C</systemitem>.</para> - <para>Although the <maketarget>world</maketarget> target still exists, + <para>Although the <buildtarget>world</buildtarget> target still exists, you are strongly encouraged not to use it.</para> <para>Run</para> @@ -959,24 +934,23 @@ Script done, …</screen> can then build a new kernel based on your normal kernel configuration file.</para> - <para>On &os; it is important to <link - linkend="make-buildworld">build world</link> before building a + <para>On &os; it is important to <link linkend="make-buildworld">build world</link> before building a new kernel.</para> <note><para>If you want to build a custom kernel, and already have a configuration - file, just use <literal>KERNCONF=<replaceable>MYKERNEL</replaceable></literal> + file, just use <literal>KERNCONF=MYKERNEL</literal> like this:</para> <screen>&prompt.root; <userinput>cd /usr/src</userinput> -&prompt.root; <userinput>make buildkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput> -&prompt.root; <userinput>make installkernel KERNCONF=<replaceable>MYKERNEL</replaceable></userinput></screen> +&prompt.root; <userinput>make buildkernel KERNCONF=MYKERNEL</userinput> +&prompt.root; <userinput>make installkernel KERNCONF=MYKERNEL</userinput></screen> </note> <para>Note that if you have raised <literal>kern.securelevel</literal> above 1 <emphasis>and</emphasis> you have set either the <literal>noschg</literal> or similar flags to your kernel binary, you might find it necessary to drop into single user mode to use - <maketarget>installkernel</maketarget>. Otherwise you should be able + <buildtarget>installkernel</buildtarget>. Otherwise you should be able to run both these commands from multi user mode without problems. See &man.init.8; for details about <literal>kern.securelevel</literal> and &man.chflags.1; for details @@ -992,12 +966,12 @@ Script done, …</screen> <xref linkend="makeworld-singleuser"/>.</para> </sect2> - <sect2 id="make-installworld"> + <sect2 xml:id="make-installworld"> <title>Install the New System Binaries</title> <para>If you were building a version of &os; recent enough to have used <command>make buildworld</command> then you should now use - <maketarget>installworld</maketarget> to install the new system + <buildtarget>installworld</buildtarget> to install the new system binaries.</para> <para>Run</para> @@ -1011,7 +985,7 @@ Script done, …</screen> variables in the <command>make installworld</command> command line. This does not necessarily hold true for other options; for example, <option>-j</option> must never be used with - <maketarget>installworld</maketarget>.</para> + <buildtarget>installworld</buildtarget>.</para> <para>For example, if you ran:</para> @@ -1040,17 +1014,13 @@ Script done, …</screen> choose, be sure to make a backup of <filename>/etc</filename> in case anything goes wrong.</para> - <sect3 id="mergemaster"> - <sect3info> + <sect3 xml:id="mergemaster"> + <info><title><command>mergemaster</command></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> - </sect3info> - <title><command>mergemaster</command></title> + </info> + <indexterm><primary><command>mergemaster</command></primary></indexterm> <para>The &man.mergemaster.8; utility is a Bourne script that will @@ -1270,7 +1240,7 @@ Script done, …</screen> </sect3> </sect2> - <sect2 id="cutting-edge-rebooting"> + <sect2 xml:id="cutting-edge-rebooting"> <title>Rebooting</title> <para>You are now done. After you have verified that everything appears @@ -1466,7 +1436,7 @@ Building everything.. <listitem> <para>Also in <filename>/etc/make.conf</filename>, set - <makevar>CFLAGS</makevar> to something like <option>-O + <varname>CFLAGS</varname> to something like <option>-O -pipe</option>. The optimization <option>-O2</option> is much slower, and the optimization difference between <option>-O</option> and <option>-O2</option> is normally @@ -1565,17 +1535,13 @@ Building everything.. </sect2> </sect1> - <sect1 id="small-lan"> - <sect1info> + <sect1 xml:id="small-lan"> + <info><title>Tracking for Multiple Machines</title> <authorgroup> - <author> - <firstname>Mike</firstname> - <surname>Meyer</surname> - <contrib>Contributed by </contrib> - </author> + <author><personname><firstname>Mike</firstname><surname>Meyer</surname></personname><contrib>Contributed by </contrib></author> </authorgroup> - </sect1info> - <title>Tracking for Multiple Machines</title> + </info> + <indexterm> <primary>NFS</primary> <secondary>installing multiple machines</secondary> @@ -1589,7 +1555,7 @@ Building everything.. machines mount that work via NFS. This section outlines a method of doing so.</para> - <sect2 id="small-lan-preliminaries"> + <sect2 xml:id="small-lan-preliminaries"> <title>Preliminaries</title> <para>First, identify a set of machines that is going to run @@ -1623,12 +1589,12 @@ Building everything.. the build machine must build all the parts of the base system that any machine in the build set is going to install. Also, each build machine should have its kernel - name set with <makevar>KERNCONF</makevar> in + name set with <varname>KERNCONF</varname> in <filename>/etc/make.conf</filename>, and the build machine - should list them all in <makevar>KERNCONF</makevar>, listing + should list them all in <varname>KERNCONF</varname>, listing its own kernel first. The build machine must have the kernel configuration files for each machine in - <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf</filename> + <filename>/usr/src/sys/arch/conf</filename> if it is going to build their kernels.</para> </sect2> @@ -1636,8 +1602,7 @@ Building everything.. <title>The Base System</title> <para>Now that all that is done, you are ready to build - everything. Build the kernel and world as described in <xref - linkend="make-buildworld"/> on the build machine, + everything. Build the kernel and world as described in <xref linkend="make-buildworld"/> on the build machine, but do not install anything. After the build has finished, go to the test machine, and install the kernel you just built. If this machine mounts <filename>/usr/src</filename> @@ -1663,14 +1628,14 @@ Building everything.. critical step is mounting <filename>/usr/ports</filename> from the same machine to all the machines in the build set. You can then set up <filename>/etc/make.conf</filename> properly to share - distfiles. You should set <makevar>DISTDIR</makevar> to a + distfiles. You should set <varname>DISTDIR</varname> to a common shared directory that is writable by whichever user - <username>root</username> is mapped to by your NFS mounts. Each - machine should set <makevar>WRKDIRPREFIX</makevar> to a + <systemitem class="username">root</systemitem> is mapped to by your NFS mounts. Each + machine should set <varname>WRKDIRPREFIX</varname> to a local build directory. Finally, if you are going to be building and distributing packages, you should set - <makevar>PACKAGES</makevar> to a directory similar to - <makevar>DISTDIR</makevar>.</para> + <varname>PACKAGES</varname> to a directory similar to + <varname>DISTDIR</varname>.</para> </sect2> </sect1> </chapter> |