Date: Wed, 24 Jul 2013 04:38:49 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r42409 - in head/en_US.ISO8859-1/books/handbook: boot cutting-edge install introduction l10n network-servers Message-ID: <201307240438.r6O4cnjT004319@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: wblock Date: Wed Jul 24 04:38:49 2013 New Revision: 42409 URL: http://svnweb.freebsd.org/changeset/doc/42409 Log: Whitespace-only fixes. Translators, please ignore. Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml head/en_US.ISO8859-1/books/handbook/install/chapter.xml head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Wed Jul 24 03:00:29 2013 (r42408) +++ head/en_US.ISO8859-1/books/handbook/boot/chapter.xml Wed Jul 24 04:38:49 2013 (r42409) @@ -65,20 +65,18 @@ operating system, and the operating system programs are on the disk, how is the operating system started?</para> - <para>This problem parallels one in the book <citetitle>The - Adventures of Baron Munchausen</citetitle>. A character had - fallen part way down a manhole, and pulled himself out by - grabbing his bootstraps, and lifting. In the early days of - computing the term <firstterm>bootstrap</firstterm> was applied - to the mechanism used to load the operating system, which has - become shortened to <quote>booting</quote>.</para> + <para>This problem parallels one in the book + <citetitle>The Adventures of Baron Munchausen</citetitle>. A + character had fallen part way down a manhole, and pulled himself + out by grabbing his bootstraps, and lifting. In the early days + of computing the term <firstterm>bootstrap</firstterm> was + applied to the mechanism used to load the operating system, + which has become shortened to <quote>booting</quote>.</para> <indexterm><primary><acronym>BIOS</acronym></primary></indexterm> - <indexterm> - <primary>Basic Input/Output System</primary> - <see><acronym>BIOS</acronym></see> - </indexterm> + <indexterm><primary>Basic Input/Output + System</primary><see><acronym>BIOS</acronym></see></indexterm> <para>On x86 hardware the Basic Input/Output System (<acronym>BIOS</acronym>) is responsible for loading the @@ -340,7 +338,7 @@ boot:</screen> <para>Finally, by default, the loader issues a 10 second wait for key presses, and boots the kernel if it is not - interrupted. If interrupted, the user is presented with a + interrupted. If interrupted, the user is presented with a prompt which understands the command set, where the user may adjust variables, unload all modules, load modules, and then finally boot or reboot.</para> @@ -505,7 +503,9 @@ boot:</screen> <itemizedlist> <listitem> - <para>To boot the usual kernel in single-user mode<indexterm><primary>single-user mode</primary></indexterm>:</para> + <para>To boot the usual kernel in single-user + mode<indexterm><primary>single-user + mode</primary></indexterm>:</para> <screen><userinput>boot -s</userinput></screen> </listitem> @@ -521,8 +521,9 @@ boot:</screen> the default kernel that comes with an installation, or <filename>kernel.old</filename><indexterm> <primary><filename>kernel.old</filename></primary></indexterm> - to refer to the previously installed kernel before a system - upgrade or before configuring a custom kernel.</para> + to refer to the previously installed kernel before a + system upgrade or before configuring a custom + kernel.</para> <note> <para>Use the following to load the usual modules with @@ -788,6 +789,7 @@ bitmap_name="<replaceable>/boot/splash.b <para> </para> </sect2> --> + </sect1> <sect1 id="device-hints"> Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Wed Jul 24 03:00:29 2013 (r42408) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Wed Jul 24 04:38:49 2013 (r42409) @@ -1288,9 +1288,9 @@ Fetching 133 new ports or files... done. </listitem> <listitem> - <para>A quick way of getting bug fixes. Any given commit is - just as likely to introduce new bugs as to fix existing - ones.</para> + <para>A quick way of getting bug fixes. Any given commit + is just as likely to introduce new bugs as to fix + existing ones.</para> </listitem> <listitem> @@ -1334,15 +1334,21 @@ Fetching 133 new ports or files... done. <orderedlist> <listitem> - <para>Use <link linkend="svn">svn</link><indexterm><primary>Subversion</primary> - </indexterm><indexterm><primary>-CURRENT</primary> - <secondary>Syncing with <application>Subversion</application></secondary> - </indexterm> to check out - the desired development or release branch. This is - the recommended method, providing access to &os; - development as it occurs. Checkout the -CURRENT - code from the <literal>head</literal> branch of one - of the <link linkend="svn-mirrors">Subversion mirror + <para>Use <link + linkend="svn">svn</link><indexterm> + <primary>Subversion</primary> + </indexterm> + <indexterm> + <primary>-CURRENT</primary> + <secondary>Syncing with + <application>Subversion</application></secondary> + </indexterm> + to check out the desired development or release + branch. This is the recommended method, providing + access to &os; development as it occurs. Checkout + the -CURRENT code from the <literal>head</literal> + branch of one of the <link + linkend="svn-mirrors">Subversion mirror sites</link>. Due to the size of the repository, it is recommended that only desired subtrees be checked out.</para> @@ -1351,13 +1357,13 @@ Fetching 133 new ports or files... done. <listitem> <para>Use the <application><link linkend="ctm">CTM</link></application><indexterm> - <primary>-CURRENT</primary><secondary>Syncing with CTM</secondary> - </indexterm> facility. - If you have bad connectivity such as high price - connections or only email access, + <primary>-CURRENT</primary> + <secondary>Syncing with CTM</secondary> + </indexterm> facility. If you have bad connectivity + such as high price connections or only email access, <application>CTM</application> is an option, but it - is not as reliable as <application><link - linkend="svn">Subversion</link></application>. + is not as reliable as <application> + <link linkend="svn">Subversion</link></application>. For this reason, <application><link linkend="svn">Subversion</link></application> is the recommended method for any system with @@ -1374,8 +1380,11 @@ Fetching 133 new ports or files... done. compile just a subset is almost guaranteed to cause problems.</para> - <para>Before compiling &os.current;<indexterm><primary>-CURRENT</primary> - <secondary>compiling</secondary></indexterm>, read + <para>Before compiling + &os.current;<indexterm> + <primary>-CURRENT</primary> + <secondary>compiling</secondary> + </indexterm>, read <filename>/usr/src/Makefile</filename> very carefully. <link linkend="makeworld">Install a new kernel and rebuild the world</link> the first time through as part @@ -1504,16 +1513,20 @@ Fetching 133 new ports or files... done. <orderedlist> <listitem> <para>Use <link linkend="svn">svn</link><indexterm> - <primary>Subversion</primary></indexterm> to check out - the desired development or release branch. This is - the recommended method, providing access to &os; - development as it occurs. Branch names include - <literal>head</literal> for the current development - head, and branches identified in <ulink - url="&url.base;/releng/">the release engineering - page</ulink>, such as <literal>stable/9</literal><indexterm> - <primary>-STABLE</primary> - <secondary>syncing with <application>Subversion</application></secondary></indexterm> + <primary>Subversion</primary> + + </indexterm> to check out the desired development or + release branch. This is the recommended method, + providing access to &os; development as it occurs. + Branch names include <literal>head</literal> for the + current development head, and branches identified in + <ulink url="&url.base;/releng/">the release + engineering page</ulink>, such as + <literal>stable/9</literal><indexterm> + <primary>-STABLE</primary> + <secondary>syncing with + <application>Subversion</application></secondary> + </indexterm> or <literal>releng/9.0</literal>. URL prefixes for <application>Subversion</application> checkout of the base system are shown in <link @@ -1527,20 +1540,23 @@ Fetching 133 new ports or files... done. <listitem> <para>Consider using <application><link linkend="ctm">CTM</link></application><indexterm> - <primary>-STABLE</primary><secondary>syncing with CTM</secondary> - </indexterm> if you do - not have a fast connection to the Internet.</para> + <primary>-STABLE</primary> + <secondary>syncing with CTM</secondary> + </indexterm> if you do not have a fast connection to + the Internet.</para> </listitem> </orderedlist> </listitem> <listitem> - <para>Before compiling &os.stable;<indexterm><primary>-STABLE</primary> - <secondary>compiling</secondary></indexterm>, read - <filename>/usr/src/Makefile</filename> carefully. <link - linkend="makeworld">Install a new kernel and rebuild - the world</link> the first time through as part of the - upgrading process. Read &a.stable; and + <para>Before compiling &os.stable;<indexterm> + <primary>-STABLE</primary> + <secondary>compiling</secondary> + </indexterm>, read + <filename>/usr/src/Makefile</filename> carefully. + <link linkend="makeworld">Install a new kernel and + rebuild the world</link> the first time through as part + of the upgrading process. Read &a.stable; and <filename>/usr/src/UPDATING</filename> to keep up-to-date on other bootstrapping procedures that sometimes become necessary on the road to the next @@ -1694,12 +1710,12 @@ Fetching 133 new ports or files... done. help about synchronizing to a newer version.</para> <para>Updating the system from source is a more subtle process - than it might initially seem to be, and the &os; developers have - found it necessary over the years to change the recommended - approach fairly dramatically as new kinds of unavoidable - dependencies come to light. The rest of this section - describes the rationale behind the currently recommended - upgrade sequence.</para> + than it might initially seem to be, and the &os; developers + have found it necessary over the years to change the + recommended approach fairly dramatically as new kinds of + unavoidable dependencies come to light. The rest of this + section describes the rationale behind the currently + recommended upgrade sequence.</para> <para>Any successful update sequence must deal with the following issues:</para> @@ -1833,11 +1849,12 @@ Fetching 133 new ports or files... done. <para><command>make <maketarget>delete-old</maketarget></command></para> - <para>This target deletes old (obsolete) files. This is important - because sometimes they cause problems if left on the disk, for - example the presence of the old <filename>utmp.h</filename> - causes problems in some ports when the new - <filename>utmpx.h</filename> is installed.</para> + <para>This target deletes old (obsolete) files. This is + important because sometimes they cause problems if left on + the disk, for example the presence of the old + <filename>utmp.h</filename> causes problems in some ports + when the new <filename>utmpx.h</filename> is + installed.</para> </listitem> <listitem> @@ -1848,10 +1865,11 @@ Fetching 133 new ports or files... done. </listitem> <listitem> - <para><command>make <maketarget>delete-old-libs</maketarget></command></para> + <para><command>make + <maketarget>delete-old-libs</maketarget></command></para> - <para>Remove any obsolete libraries to avoid conflicts with newer - ones. Make sure that all ports have been rebuilt + <para>Remove any obsolete libraries to avoid conflicts with + newer ones. Make sure that all ports have been rebuilt before old libraries are removed.</para> </listitem> </orderedlist> @@ -2622,27 +2640,28 @@ Script done, …</screen> <primary>Deleting obsolete files and directories</primary> </indexterm> - <para>As a part of the &os; development lifecycle, files and their - contents occasionally become obsolete. This may be because - functionality is implemented elsewhere, the version number of - the library has changed, or it was removed from the system - entirely. This includes old files, libraries, and directories, - which should be removed when updating the system. The benefit - is that the system is not cluttered with old files which take up - unnecessary space on the storage and backup media. - Additionally, if the old library has a security or stability - issue, the system should be updated to the newer library to keep - it safe and to prevent crashes caused by the old library. - Files, directories, and libraries which are considered obsolete - are listed in <filename>/usr/src/ObsoleteFiles.inc</filename>. - The following instructions should be used to remove obsolete - files during the system upgrade process.</para> - - <para>After the <command>make - <maketarget>installworld</maketarget></command> - and the subsequent <command>mergemaster</command> have finished - successfully, check for obsolete files and libraries as - follows:</para> + <para>As a part of the &os; development lifecycle, files and + their contents occasionally become obsolete. This may be + because functionality is implemented elsewhere, the version + number of the library has changed, or it was removed from the + system entirely. This includes old files, libraries, and + directories, which should be removed when updating the system. + The benefit is that the system is not cluttered with old files + which take up unnecessary space on the storage and backup + media. Additionally, if the old library has a security or + stability issue, the system should be updated to the newer + library to keep it safe and to prevent crashes caused by the + old library. Files, directories, and libraries which are + considered obsolete are listed in + <filename>/usr/src/ObsoleteFiles.inc</filename>. The + following instructions should be used to remove obsolete files + during the system upgrade process.</para> + + <para>After the + <command>make <maketarget>installworld</maketarget></command> + and the subsequent <command>mergemaster</command> have + finished successfully, check for obsolete files and libraries + as follows:</para> <screen>&prompt.root; <userinput>cd /usr/src</userinput> &prompt.root; <userinput>make check-old</userinput></screen> @@ -2686,9 +2705,9 @@ Script done, …</screen> <title>Warning</title> <para>Deleting obsolete files will break applications that - still depend on those obsolete files. This is especially true - for old libraries. In most cases, the programs, ports, or - libraries that used the old library need to be recompiled + still depend on those obsolete files. This is especially + true for old libraries. In most cases, the programs, ports, + or libraries that used the old library need to be recompiled before <command>make <maketarget>delete-old-libs</maketarget></command> is executed.</para> @@ -2696,28 +2715,29 @@ Script done, …</screen> <para>Utilities for checking shared library dependencies are available from the Ports Collection in - <filename role="package">sysutils/libchk</filename> or <filename + <filename role="package">sysutils/libchk</filename> or + <filename role="package">sysutils/bsdadminscripts</filename>.</para> - <para>Obsolete shared libraries can conflict with newer libraries, - causing messages like these:</para> + <para>Obsolete shared libraries can conflict with newer + libraries, causing messages like these:</para> <screen>/usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libtiff.so, may conflict with libz.so.5 /usr/bin/ld: warning: librpcsvc.so.4, needed by /usr/local/lib/libXext.so, may conflict with librpcsvc.so.5</screen> - <para>To solve these problems, determine which port installed the - library:</para> + <para>To solve these problems, determine which port installed + the library:</para> <screen>&prompt.root; <userinput>pkg_info -W /usr/local/lib/libtiff.so</userinput> /usr/local/lib/libtiff.so was installed by package tiff-3.9.4 &prompt.root; <userinput>pkg_info -W /usr/local/lib/libXext.so</userinput> /usr/local/lib/libXext.so was installed by package libXext-1.1.1,1</screen> - <para>Then deinstall, rebuild and reinstall the port. <filename - role="package">ports-mgmt/portmaster</filename> can be used to - automate this process. After all ports are rebuilt and no - longer use the old libraries, delete the old libraries using the - following command:</para> + <para>Then deinstall, rebuild and reinstall the port. + <filename role="package">ports-mgmt/portmaster</filename> can + be used to automate this process. After all ports are rebuilt + and no longer use the old libraries, delete the old libraries + using the following command:</para> <screen>&prompt.root; <userinput>make delete-old-libs</userinput></screen> @@ -2780,7 +2800,9 @@ Script done, …</screen> <qandaentry> <question> <para>My compile failed with lots of - signal 11<indexterm><primary>signal 11</primary></indexterm> + signal 11<indexterm> + <primary>signal 11</primary> + </indexterm> (or other signal number) errors. What happened?</para> </question> Modified: head/en_US.ISO8859-1/books/handbook/install/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/install/chapter.xml Wed Jul 24 03:00:29 2013 (r42408) +++ head/en_US.ISO8859-1/books/handbook/install/chapter.xml Wed Jul 24 04:38:49 2013 (r42409) @@ -2292,47 +2292,47 @@ Mounting root from ufs:/dev/md0c firewall</guimenuitem></term> <listitem> - <para>This option instructs &man.sysinstall.8; - to use passive mode<indexterm> - <primary>FTP</primary><secondary>passive mode</secondary> - </indexterm> for all FTP operations. - This allows the user to pass through firewalls - that do not allow incoming connections on random TCP ports. + <para>This option instructs &man.sysinstall.8; to use + passive mode<indexterm> + <primary>FTP</primary> + <secondary>passive mode</secondary> + </indexterm> for all FTP operations. This allows the + user to pass through firewalls that do not allow + incoming connections on random TCP ports. </para> </listitem> </varlistentry> <varlistentry> - <term>FTP via a HTTP proxy: <guimenuitem>Install from an FTP server - through a http proxy</guimenuitem></term> + <term>FTP via a HTTP proxy: <guimenuitem>Install from an FTP + server through a http proxy</guimenuitem></term> <listitem> - <para>This option instructs &man.sysinstall.8; - to use the HTTP - protocol to connect to a proxy - for all FTP operations. The proxy will translate - the requests and send them to the FTP server. - This allows the user to pass through firewalls - that do not allow FTP, but offer a HTTP - proxy<indexterm><primary>FTP</primary> - <secondary>via a HTTP proxy</secondary></indexterm>. - In this case, specify the proxy in + <para>This option instructs &man.sysinstall.8; to use the + HTTP protocol to connect to a proxy for all FTP + operations. The proxy will translate the requests and + send them to the FTP server. This allows the user to + pass through firewalls that do not allow FTP, but offer + a HTTP proxy<indexterm> + <primary>FTP</primary> + <secondary>via a HTTP proxy</secondary> + </indexterm>. In this case, specify the proxy in addition to the FTP server.</para> </listitem> </varlistentry> </variablelist> - <para>For a proxy FTP server, give the name of the - server as part of the username, after an - <quote>@</quote> sign. The proxy server then <quote>fakes</quote> - the real server. For example, to install from - <hostid role="fqdn">ftp.FreeBSD.org</hostid>, using the proxy FTP - server <hostid role="fqdn">foo.example.com</hostid>, listening on port - 1234, go to the options menu, set the FTP username - to <literal>ftp@ftp.FreeBSD.org</literal> and the password to - an - email address. As the installation media, specify FTP (or - passive FTP, if the proxy supports it), and the URL + <para>For a proxy FTP server, give the name of the server as + part of the username, after an <quote>@</quote> sign. The + proxy server then <quote>fakes</quote> the real server. For + example, to install from + <hostid role="fqdn">ftp.FreeBSD.org</hostid>, using the proxy + FTP server <hostid role="fqdn">foo.example.com</hostid>, + listening on port 1234, go to the options menu, set the FTP + username to <literal>ftp@ftp.FreeBSD.org</literal> and the + password to an email address. As the installation media, + specify FTP (or passive FTP, if the proxy supports it), and + the URL <literal>ftp://foo.example.com:1234/pub/FreeBSD</literal>.</para>; <para>Since <filename class="directory">/pub/FreeBSD</filename> Modified: head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Wed Jul 24 03:00:29 2013 (r42408) +++ head/en_US.ISO8859-1/books/handbook/introduction/chapter.xml Wed Jul 24 04:38:49 2013 (r42409) @@ -78,76 +78,81 @@ <itemizedlist> <listitem> - <para><emphasis>Preemptive multitasking</emphasis><indexterm> - <primary>preemptive multitasking</primary></indexterm> with - dynamic priority adjustment to ensure smooth and fair - sharing of the computer between applications and users, - even under the heaviest of loads.</para> + <para><emphasis>Preemptive + multitasking</emphasis><indexterm> + <primary>preemptive multitasking</primary> + </indexterm> with dynamic priority adjustment to ensure + smooth and fair sharing of the computer between + applications and users, even under the heaviest of + loads.</para> </listitem> <listitem> <para><emphasis>Multi-user facilities</emphasis><indexterm> - <primary>multi-user facilities</primary></indexterm> which allow - many people to use a &os; system simultaneously for a - variety of things. This means, for example, that system - peripherals such as printers and tape drives are properly - shared between all users on the system or the network and - that individual resource limits can be placed on users or - groups of users, protecting critical system resources from - over-use.</para> - </listitem> - <listitem> - <para>Strong <emphasis>TCP/IP networking</emphasis><indexterm> - <primary>TCP/IP networking</primary></indexterm> with - support for industry standards such as SCTP, DHCP, NFS, - NIS, PPP, SLIP, IPsec, and IPv6. This means that your - &os; machine can interoperate easily with other systems as - well as act as an enterprise server, providing vital - functions such as NFS (remote file access) and email - services or putting your organization on the Internet with - WWW, FTP, routing and firewall (security) services.</para> + <primary>multi-user facilities</primary> + </indexterm> which allow many people to use a &os; system + simultaneously for a variety of things. This means, for + example, that system peripherals such as printers and tape + drives are properly shared between all users on the system + or the network and that individual resource limits can be + placed on users or groups of users, protecting critical + system resources from over-use.</para> + </listitem> + + <listitem> + <para>Strong <emphasis>TCP/IP + networking</emphasis><indexterm> + <primary>TCP/IP networking</primary> + </indexterm> with support for industry standards such as + SCTP, DHCP, NFS, NIS, PPP, SLIP, IPsec, and IPv6. This + means that your &os; machine can interoperate easily with + other systems as well as act as an enterprise server, + providing vital functions such as NFS (remote file access) + and email services or putting your organization on the + Internet with WWW, FTP, routing and firewall (security) + services.</para> </listitem> <listitem> <para><emphasis>Memory protection</emphasis><indexterm> - <primary>memory protection</primary></indexterm> ensures that - applications (or users) cannot interfere with each other. - One application crashing will not affect others in any - way.</para> + <primary>memory protection</primary> + </indexterm> ensures that applications (or users) cannot + interfere with each other. One application crashing will + not affect others in any way.</para> </listitem> <listitem> <para>The industry standard <emphasis>X Window System</emphasis><indexterm> - <primary>X Window System</primary></indexterm> - (X11R7) provides a graphical user - interface (GUI) for the cost of a common VGA card and - monitor and comes with full sources.</para> + <primary>X Window System</primary> + </indexterm> (X11R7) provides a graphical user interface + (GUI) for the cost of a common VGA card and monitor and + comes with full sources.</para> </listitem> <listitem> <para> - <indexterm> - <primary>binary compatibility</primary> - <secondary>Linux</secondary> - </indexterm> - <indexterm> - <primary>binary compatibility</primary> - <secondary>SCO</secondary> - </indexterm> - <indexterm> - <primary>binary compatibility</primary> - <secondary>SVR4</secondary> - </indexterm> - <indexterm> - <primary>binary compatibility</primary> - <secondary>BSD/OS</secondary> - </indexterm> - <indexterm> - <primary>binary compatibility</primary> - <secondary>NetBSD</secondary> - </indexterm> - <emphasis>Binary compatibility</emphasis> with many + <indexterm> + <primary>binary compatibility</primary> + <secondary>Linux</secondary> + </indexterm> + <indexterm> + <primary>binary compatibility</primary> + <secondary>SCO</secondary> + </indexterm> + <indexterm> + <primary>binary compatibility</primary> + <secondary>SVR4</secondary> + </indexterm> + <indexterm> + <primary>binary compatibility</primary> + <secondary>BSD/OS</secondary> + </indexterm> + <indexterm> + <primary>binary compatibility</primary> + <secondary>NetBSD</secondary> + </indexterm> + <emphasis>Binary compatibility</emphasis> with many programs built for Linux, SCO, SVR4, BSDI and NetBSD.</para> </listitem> @@ -169,30 +174,33 @@ compile.</para> </listitem> <listitem> - <para>Demand paged <emphasis>virtual memory</emphasis><indexterm> - <primary>virtual memory</primary></indexterm> and - <quote>merged VM/buffer cache</quote> design efficiently - satisfies applications with large appetites for memory - while still maintaining interactive response to other - users.</para> + <para>Demand paged <emphasis>virtual + memory</emphasis><indexterm> + <primary>virtual memory</primary> + </indexterm> and <quote>merged VM/buffer cache</quote> + design efficiently satisfies applications with large + appetites for memory while still maintaining interactive + response to other users.</para> </listitem> <listitem> <para><emphasis>SMP</emphasis><indexterm> - <primary>Symmetric Multi-Processing (SMP)</primary></indexterm> - support for machines with multiple CPUs.</para> + <primary>Symmetric Multi-Processing + (SMP)</primary> + </indexterm> support for machines with multiple + CPUs.</para> </listitem> <listitem> <para> - <indexterm> - <primary>compilers</primary> - <secondary>C</secondary> - </indexterm> - <indexterm> - <primary>compilers</primary> - <secondary>C++</secondary> - </indexterm> + <indexterm> + <primary>compilers</primary> + <secondary>C</secondary> + </indexterm> + <indexterm> + <primary>compilers</primary> + <secondary>C++</secondary> + </indexterm> A full complement of <emphasis>C</emphasis> and <emphasis>C++</emphasis> development tools. @@ -203,11 +211,11 @@ <listitem> <para><emphasis>Source code</emphasis><indexterm> - <primary>source code</primary></indexterm> for the entire system - means you have the greatest degree of control over your - environment. Why be locked into a proprietary solution - at the mercy of your vendor when you can have a truly open - system?</para> + <primary>source code</primary> + </indexterm> for the entire system means you have the + greatest degree of control over your environment. Why be + locked into a proprietary solution at the mercy of your + vendor when you can have a truly open system?</para> </listitem> <listitem> @@ -221,18 +229,19 @@ </itemizedlist> <para>&os; is based on the 4.4BSD-Lite<indexterm> - <primary>4.4BSD-Lite</primary></indexterm> release from Computer + <primary>4.4BSD-Lite</primary> + </indexterm> release from Computer Systems Research Group (CSRG)<indexterm> - <primary>Computer Systems Research Group (CSRG)</primary></indexterm> - at the University of California - at Berkeley, and carries on the distinguished tradition of BSD - systems development. In addition to the fine work provided by - CSRG, the &os; Project has put in many thousands of hours - in fine tuning the system for maximum performance and - reliability in real-life load situations. As many of the - commercial giants struggle to field PC operating systems with - such features, performance and reliability, &os; can offer - them <emphasis>now</emphasis>!</para> + <primary>Computer Systems Research Group (CSRG)</primary> + </indexterm> at the University of California at Berkeley, and + carries on the distinguished tradition of BSD systems + development. In addition to the fine work provided by CSRG, + the &os; Project has put in many thousands of hours in + fine tuning the system for maximum performance and reliability + in real-life load situations. As many of the commercial + giants struggle to field PC operating systems with such + features, performance and reliability, &os; can offer them + <emphasis>now</emphasis>!</para> <para>The applications to which &os; can be put are truly limited only by your own imagination. From software @@ -264,13 +273,15 @@ <itemizedlist> <listitem> <para>FTP servers<indexterm> - <primary>FTP servers</primary></indexterm></para> + <primary>FTP servers</primary> + </indexterm></para> </listitem> <listitem> <para>World Wide Web servers<indexterm> - <primary>web servers</primary></indexterm> (standard or secure - [SSL])</para> + <primary>web servers</primary> + </indexterm> + (standard or secure [SSL])</para> </listitem> <listitem> @@ -278,25 +289,31 @@ </listitem> <listitem> - <para>Firewalls<indexterm><primary>firewall</primary></indexterm> - and NAT<indexterm><primary>NAT</primary></indexterm> + <para>Firewalls<indexterm> + <primary>firewall</primary> + </indexterm> + and NAT<indexterm> + <primary>NAT</primary> + </indexterm> (<quote>IP masquerading</quote>) gateways</para> </listitem> <listitem> <para> - <indexterm> - <primary>electronic mail</primary> - <see>email</see> - </indexterm> - <indexterm> - <primary>email</primary> - </indexterm> - Electronic Mail servers</para> + <indexterm> + <primary>electronic mail</primary> + <see>email</see> + </indexterm> + <indexterm> + <primary>email</primary> + </indexterm> + Electronic Mail servers</para> </listitem> <listitem> - <para>USENET<indexterm><primary>USENET</primary></indexterm> + <para>USENET<indexterm> + <primary>USENET</primary> + </indexterm> News or Bulletin Board Systems</para> </listitem> @@ -335,11 +352,12 @@ </listitem> <listitem> - <para><emphasis>Networking:</emphasis> Need a new router?<indexterm> - <primary>router</primary></indexterm> - A name server (DNS)?<indexterm> - <primary>DNS Server</primary></indexterm> A firewall to - keep people out of your + <para><emphasis>Networking:</emphasis> Need a new + router?<indexterm> + <primary>router</primary> + </indexterm> A name server (DNS)?<indexterm> + <primary>DNS Server</primary> + </indexterm> A firewall to keep people out of your internal network? &os; can easily turn that unused 386 or 486 PC sitting in the corner into an advanced router with sophisticated packet-filtering capabilities.</para> @@ -347,14 +365,14 @@ <listitem> <para> - <indexterm> - <primary>X Window System</primary> - </indexterm> - <indexterm> - <primary>X Window System</primary> - <secondary>Accelerated-X</secondary> - </indexterm> - <emphasis>X Window workstation:</emphasis> &os; is a + <indexterm> + <primary>X Window System</primary> + </indexterm> + <indexterm> + <primary>X Window System</primary> + <secondary>Accelerated-X</secondary> + </indexterm> + <emphasis>X Window workstation:</emphasis> &os; is a fine choice for an inexpensive X terminal solution, using the freely available X11 server. Unlike an X terminal, &os; allows many applications to @@ -368,7 +386,9 @@ <para><emphasis>Software Development:</emphasis> The basic &os; system comes with a full complement of development tools including the renowned GNU - C/C++<indexterm><primary>GNU Compiler Collection</primary></indexterm> + C/C++<indexterm> + <primary>GNU Compiler Collection</primary> + </indexterm> compiler and debugger.</para> </listitem> </itemizedlist> @@ -444,19 +464,21 @@ </listitem> <listitem> - <para><ulink url="http://www.sina.com/">Sina</ulink><indexterm>; - <primary>Sina</primary></indexterm></para> + <para><ulink + url="http://www.sina.com/">Sina</ulink><indexterm>; + <primary>Sina</primary> + </indexterm></para> </listitem> <listitem> - <para><ulink - url="http://www.pair.com/">Pair Networks</ulink><indexterm> + <para><ulink url="http://www.pair.com/">Pair + Networks</ulink><indexterm> <primary>Pair Networks</primary></indexterm></para> </listitem> <listitem> - <para><ulink - url="http://www.sony.co.jp/">Sony Japan</ulink><indexterm> + <para><ulink url="http://www.sony.co.jp/">Sony + Japan</ulink><indexterm> <primary>Sony Japan</primary></indexterm></para> </listitem> @@ -480,14 +502,16 @@ <listitem> <para><ulink url="http://www.telehouse.com/">TELEHOUSE - America</ulink><indexterm><primary>TELEHOUSE America</primary> - </indexterm></para> + America</ulink><indexterm> + <primary>TELEHOUSE America</primary> + </indexterm></para> </listitem> <listitem> <para><ulink url="http://www.experts-exchange.com/">Experts - Exchange</ulink><indexterm><primary>Experts Exchange</primary> - </indexterm></para> + Exchange</ulink><indexterm> + <primary>Experts Exchange</primary> + </indexterm></para> </listitem> </itemizedlist> @@ -541,11 +565,11 @@ <indexterm><primary>Greenman, David</primary></indexterm> <indexterm><primary>Walnut Creek CDROM</primary></indexterm> <para>The trio thought that the goal remained - worthwhile, even without Bill's support, and so they adopted the - name "&os;" coined by David Greenman. The - initial objectives were set after consulting with the system's - current users and, once it became clear that the project was - on the road to perhaps even becoming a reality, Jordan contacted + worthwhile, even without Bill's support, and so they adopted + the name "&os;" coined by David Greenman. The initial + objectives were set after consulting with the system's current + users and, once it became clear that the project was on the + road to perhaps even becoming a reality, Jordan contacted Walnut Creek CDROM with an eye toward improving &os;'s distribution channels for those many unfortunates without easy access to the Internet. Walnut Creek CDROM not only supported @@ -704,32 +728,32 @@ id="development-cvs-repository"/></term> <listitem> <para> - <indexterm> - <primary>CVS</primary> - </indexterm> + <indexterm> + <primary>CVS</primary> + </indexterm> - <indexterm> - <primary>CVS Repository</primary> - </indexterm> + <indexterm> + <primary>CVS Repository</primary> + </indexterm> - <indexterm> - <primary>Concurrent Versions System</primary> - <see>CVS</see> - </indexterm> + <indexterm> + <primary>Concurrent Versions System</primary> + <see>CVS</see> + </indexterm> - <indexterm> - <primary>Subversion</primary> - </indexterm> + <indexterm> + <primary>Subversion</primary> + </indexterm> - <indexterm> - <primary>Subversion Repository</primary> - </indexterm> + <indexterm> + <primary>Subversion Repository</primary> + </indexterm> - <indexterm> - <primary>SVN</primary> - <see>Subversion</see> - </indexterm> - For several years, the central source tree for &os; + <indexterm> + <primary>SVN</primary> + <see>Subversion</see> + </indexterm> + For several years, the central source tree for &os; was maintained by <ulink url="http://www.nongnu.org/cvs/">CVS</ulink>; (Concurrent Versions System), a freely available source @@ -749,7 +773,7 @@ your source tree</link> section for more information on obtaining the &os; <literal>src/</literal> repository and <link linkend="ports-using">Using the Ports - Collection</link> for details on obtaining the &os; + Collection</link> for details on obtaining the &os; Ports Collection.</para> </listitem> </varlistentry> @@ -760,7 +784,7 @@ <listitem> <para>The <firstterm>committers</firstterm><indexterm> - <primary>committers</primary></indexterm> + <primary>committers</primary></indexterm> are the people who have <emphasis>write</emphasis> access to the Subversion tree, and are authorized to make modifications to the &os; source (the term @@ -780,17 +804,18 @@ <listitem> <para>The <firstterm>&os; core team</firstterm><indexterm> - <primary>core team</primary></indexterm> - would be equivalent to the board of directors if the - &os; Project were a company. The primary task of - the core team is to make sure the project, as a whole, - is in good shape and is heading in the right directions. - Inviting dedicated and responsible developers to join - our group of committers is one of the functions of the - core team, as is the recruitment of new core team - members as others move on. The current core team was - elected from a pool of committer candidates in July - 2012. Elections are held every 2 years.</para> + <primary>core team</primary> + </indexterm> would be equivalent to the board of + directors if the &os; Project were a company. The + primary task of the core team is to make sure the + project, as a whole, is in good shape and is heading in + the right directions. Inviting dedicated and + responsible developers to join our group of committers + is one of the functions of the core team, as is the + recruitment of new core team members as others move on. + The current core team was elected from a pool of + committer candidates in July 2012. Elections are held + every 2 years.</para> <para>Some core team members also have specific areas of responsibility, meaning that they are committed to @@ -867,18 +892,18 @@ were over &os.numports; ports! The list of ports ranges from http servers, to games, languages, editors, and almost everything in between. The entire Ports Collection requires - approximately &ports.size;. To compile a port, you simply change - to the directory of the program you wish to install, type - <command>make install</command>, and let the system do the - rest. The full original distribution for each port you build - is retrieved dynamically - so you need only enough disk space to build the ports you - want. Almost every port is also provided as a pre-compiled - <quote>package</quote>, which can be installed with a simple - command (<command>pkg_add</command>) by those who do not wish - to compile their own ports from source. More information on - packages and ports can be found in <xref - linkend="ports"/>.</para> + approximately &ports.size;. To compile a port, you simply + change to the directory of the program you wish to install, + type <command>make install</command>, and let the system do + the rest. The full original distribution for each port you + build is retrieved dynamically so you need only enough disk + space to build the ports you want. Almost every port is also *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201307240438.r6O4cnjT004319>