Attachment #17309 for bug #31447





    <para>CVS reference information, tutorials, and FAQs can also be found at:
      <ulink
	url="http://www.cvshome.org/docs/">http://www.cvshome.org/docs/</ulink>, 
      and the information in <ulink url="http://cvsbook.red-bean.com/cvsbook.html">Karl Fogel's
        chapters from <quote>Open Source Development with CVS</quote></ulink> are also very
      useful.</para>

          properly (tabs often look wrong in diffs because of the extra
          character in front of each line).</para>

        <para><ulink url="&url.people.server;/~eivind/cdiff">&url.people.server;/~eivind/cdiff</ulink></para>

        <para>Simply use it instead of &man.more.1; or &man.less.1;:</para>


    <itemizedlist>
      <listitem>
	<para>Add yourself to the <quote>Developers</quote> section of
	  the <ulink url="&url.top.articles;/contributors/index.html">Contributors List</ulink>
	  and remove yourself from the <quote>Additional
	  Contributors</quote> section.</para>



      <listitem>
	<para>If you have a PGP or GnuPG key, you may want to add it to
	  <filename>&url.doc.enUS;/books/handbook/pgpkeys</filename>.
	  </para>
      </listitem>


      </listitem>

      <listitem>
	<para><ulink url="&url.top.level;/support.html">&url.home.page;/support.html</ulink></para>
      </listitem>

      <listitem>
	<para><ulink url="&url.top.level;/send-pr.html">&url.home.page;/send-pr.html</ulink></para>
      </listitem>

      <listitem>

	
	<listitem>
	  <para>Nik oversees the
	    <ulink url="&url.top.level;/docproj/index.html">Doc. Project</ulink>.
	    As well as writing documentation he put together the
	    infrastructure under <filename>doc/share/mk</filename> and the
	    stylesheets and related code under

	    <email>doc@FreeBSD.org</email> mailing list.  Committers
	    interested in contributing to the documentation should familiarise
	    themself with the
	    <ulink url="&url.top.books;/fdp-primer/index.html">Documentation Project Primer</ulink>.</para>
	</listitem>
      </varlistentry>
      

	    <filename>Makefile</filename> for any package or subtree
	    which is being actively maintained by one or more people;
	    see <ulink
	    url="&url.top.books;/developers-handbook/policies.html">&url.home.page;/&url.doc.enUS;/books/developers-handbook/policies.html</ulink>
	    for documentation on this.  Where sections of code have
	    several maintainers, commits to affected areas by one
	    maintainer need to be reviewed by at least one other

	    someone who manages an overall category of FreeBSD
	    evolution, such as internationalization or networking.
	    See <ulink
	    url="&url.top.articles;/contributors/staff-who.html">&url.home.page;/&url.doc.enUS;/articles/contributors/staff-who.html</ulink> for more information on this.</para>
	</listitem>
	
	<listitem>

	    </screen>

	    <para>The 
	      <ulink url="&url.top.books;/porters-handbook/index.html">Porters
	      Handbook</ulink> contains more detailed
	      instructions.</para>


	    <para>If the port came from a submitter who has not
	      contributed to the project before, add that person's
	      name to the <ulink
	      url="&url.top.articles;/contributors/contrib-additional.html">Additional
	      Contributors</ulink> section of the FreeBSD Contributors
	      List.</para>





      pointed out that you <em>can</em> get KVM switches that also do
      serial consoles or Sun-compatible KVM switching as well as PCs,
      but they are expensive.  See <a
      href="http://www.avocent.com/">Avocent</a> for example.]</p>

    <p>You might be tempted to do without a console terminal, but when
      things go pear-shaped you <em>really</em> need to see what is on

      terminal server software may not support that.)  Also there is
      no logging or replay of console messages.  But with a bit of
      work, and the addition of some software such as <a
      href="http://www.conserver.com/">conserver</a> (described below),
      this can be made to work pretty well.</p>

    <p>A possibility suggested by Bron Gondwana is similar to the

      the "next" server, creating a ring of console connections (in
      some sort of order).  This can be made to work reasonably well
      with the aid of the <a
      href="http://www.conserver.com/">conserver</a> software, but can
      be a bit confusing otherwise (i.e. remembering which port is
      connected to which console).  And you are stuck if you need to
      use serial ports for other things (such as modems) or you have

      buy an off-the-shelf solution.  These vary in price and
      capability.  See, for example, <a
      href="http://www.lightwavecom.com/">Lightwave</a>, <a
      href="http://www.perle.com/">Perle</a>, <a
      href="http://www.avocent.com/">Avocent</a> or <a
      href="http://www.blackbox.com/faxbacks/23000/23362.PDF">Black
      Box</a>.  These solutions can be quite expensive - typically
      $USD100 - $USD400 per port.</p>

        enough.</p></li>

      <li><p>A PC Unix system.  We used <a
        href="../../../../index.html">FreeBSD 4.3</a> as that is used
        for other tasks within our office.</p></li>

      <li><p>A multi-port serial card.  We chose the <a
        href="http://www.stallion.com/html/products/easyio.html">EasyIO-PCI</a>
        8-port card from <a href="http://www.stallion.com/">Stallion
        Technologies</a>.  This cost us about $AUD740, or under
        $100/port, from <a href="http://www.ht.com.au/">Harris
        Technologies</a> (which has lots of stuff but is by no means

      config file with the appropriate entries.  See the
      <samp>stl(4)</samp> man page and the appropriate section of the
      <a
      href="../../../../doc/en_US.ISO8859-1/books/handbook/kernelconfig.html">FreeBSD
      Handbook</a>.</p>

    <h4>Building World</h4>

    <h2><a name="freebsd">Using a Serial Console on FreeBSD</a></h2>

    <p>The procedure for doing this is described in detail in the <a
      href="../../../../doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html">FreeBSD
      Handbook</a>.  This is a quick summary.</p>

    <h4>Check the kernel configuration</h4>

    <p>As shipped with FreeBSD, the 8.5 version does not authenticate
      against FreeBSD servers using MD5 passwords.  There is a patch
      in the FreeBSD GNATS system (<a
      href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28432">ports/28432</a>)
      that fixes this problem.  Kevin has indicated this patch will be
      included in future versions of conserver from him.  There are a
      couple of other problems with the 8.5 version as well.</p>

      href="ftp://ftp.conserver.com/conserver/conserver-7.0.2.tar.gz">FTP</a>
      the conserver 7.0.2 source tarball.</p>

    <p><a href="http://www.stallion.com/">Stallion Technologies</a> homepage.</p>

    <p>David Harris' <a
      href="http://www.conserver.com/consoles/msock.html">Minor Scroll

      similar console server</a> based on the <samp>screen</samp>
      program and an old SunOs host.</p>

    <p>The <a href="http://www.realweasel.com/">Real Weasel</a> company
      makes a ISA or PCI video card that looks like a PC video card
      but actually talks to a serial port.  This can be used to
      implement serial consoles on PC hardware for operating systems





      <indexterm><primary>problem reports database</primary></indexterm>
      <para>The <ulink
	  url="&url.cgi.server;/cgi/query-pr-summary.cgi">FreeBSD PR
	  list</ulink> shows all the current active problem reports and
	requests for enhancement that have been submitted by FreeBSD users.
	Look through the open PRs, and see if anything there takes your

	an interest in such things (and a tolerance for a
	<emphasis>high</emphasis> volume of mail!) may subscribe to the
	hackers mailing list by sending mail to &a.majordomo;.  See <ulink
	url="&url.top.books;/handbook/eresources.html#ERESOURCES-MAIL">The
	FreeBSD Handbook</ulink> for more information
	about this and other mailing lists.</para>
	  
      <para>If you find a bug or are submitting a specific change, please
	report it using the &man.send-pr.1; program or its <ulink
	  url="&url.top.level;/send-pr.html">WEB-based
	  equivalent</ulink>.  Try to fill-in each field of the bug report.
	Unless they exceed 65KB, include any patches directly in the report.
	If the patch is suitable to be applied to the source tree put

	because cut-and-paste turns tabs into spaces and makes them unusable.
	Consider compressing patches and using &man.uuencode.1; if they exceed
	20KB.  Upload very large submissions to <ulink
	  url="&url.ftp.server;/pub/FreeBSD/incoming/">ftp.FreeBSD.org:/pub/FreeBSD/incoming/</ulink>.</para>
	  
      <para>After filing a report, you should receive confirmation along with
	a tracking number.  Keep this tracking number so that you can update

	on-going release of FreeBSD known as <quote>FreeBSD-current</quote>
	which is made available in a variety of ways for the convenience of
	developers working actively on the system. See <ulink url="
	&url.top.books;/handbook/current-stable.html">The
	FreeBSD Handbook</ulink> for more
	information about getting and using FreeBSD-current.</para>
	  




	  <listitem>
	    <para><ulink url="http://www.osd.bsdi.com/">BSDi</ulink> (formerly Walnut Creek CDROM)
	      has donated almost more than we can say (see the History
	      section of the <ulink url="&url.top.books;/handbook/index.html">FreeBSD Handbook</ulink> for more details).
	      In particular, we would like to thank them for the original
	      hardware used for <hostid
		role="fqdn">freefall.FreeBSD.org</hostid>, our primary


    <title>The FreeBSD Documentation Project</title>
    
    <para>The <ulink url="&url.top.level;/docproj/index.html">FreeBSD
	Documentation Project</ulink> is responsible for a number of different
      services, each service being run by an individual and his
      <emphasis>deputies</emphasis> (if any):</para>

    <variablelist>
      <varlistentry>
	<term><ulink
	    url="&url.top.level;/docproj/index.html">Documentation
	    Project Manager</ulink></term>

	<listitem>

      </varlistentry>
      
      <varlistentry>
	<term><ulink url="&url.top.level;/security/index.html">Security
	    Officer</ulink></term>

	<listitem>

      </varlistentry>
      
      <varlistentry>
	<term><ulink url="&url.top.level;/support.html#cvs">Source
	    Repository Managers</ulink></term>

	<listitem>

      </varlistentry>
      
      <varlistentry>
	<term><ulink url="&url.top.level;/ports/index.html">Ports
	    Manager</ulink></term>

	<listitem>

      </varlistentry>
      
      <varlistentry>
	<term><ulink url="&url.top.level;/support.html#gnats">GNATS
	    Administrator</ulink></term>
	      
	<listitem>

Lines 51-57 Link Here

(-)en_US.ISO8859-1/articles/cvsup-advanced/article.sgml (-1 / +1 lines)
51	<title>Introduction</title>	51	<title>Introduction</title>
52		52
53	<para>If you have visited	53	<para>If you have visited
54	<ulink url="http://www.polstra.com">John Polstra's site</ulink>	54	<ulink url="http://www.polstra.com/">John Polstra's site</ulink>
55	and read	55	and read
56	<ulink url="http://www.polstra.com/projects/freeware/CVSup/faq.html">his	56	<ulink url="http://www.polstra.com/projects/freeware/CVSup/faq.html">his
57	FAQ</ulink>,	57	FAQ</ulink>,

Lines 50-56 Link Here

(-)en_US.ISO8859-1/articles/dialup-firewall/article.sgml (-1 / +1 lines)
50	<para>The first thing you will need to do is recompile your kernel	50	<para>The first thing you will need to do is recompile your kernel
51	If you need more information on how to recompile the kernel,	51	If you need more information on how to recompile the kernel,
52	then the best place to start is the <ulink	52	then the best place to start is the <ulink
53	URL="http://www.freebsd.org/handbook/kernelconfig.html">kernel	53	URL="&url.top.books;/handbook/kernelconfig.html">kernel
54	configuration section in the Handbook</ulink>. You need to add the	54	configuration section in the Handbook</ulink>. You need to add the
55	following options into your kernel configuration file:</para>	55	following options into your kernel configuration file:</para>
56		56




	  Operating System Counter</ulink>, as of April 1999 31.3% of the
	world's network connected machines run Linux.  14.6% run BSD UNIX.
	Some of the world's largest web operations, such as <ulink
          url="http://www.yahoo.com/">Yahoo!</ulink>, run BSD.  The world's
	busiest FTP server, <ulink
          url="ftp://ftp.cdrom.com/">ftp.cdrom.com</ulink>, uses BSD to
	transfer 1.4 TB of data a day.    Clearly this is not a niche
	market: BSD is a well-kept secret.</para>


      CSRG members, William F. Jolitz, wrote the remaining code and released
      it in early 1992 as <emphasis>386BSD</emphasis>.  At the same time,
      another group of ex-CSRG members formed a commercial company called
      <ulink url="http://www.bsdi.com/">Berkeley Software Design Inc.</ulink>
      and released a beta version of an operating system called
      <ulink url="http://www.bsdi.com/">BSD/386</ulink>, which was based on
      the same sources.  The name of the operating system has since changed
      to BSD/OS.</para>

    <para>386BSD never became a stable operating system.  Instead, two other
      projects split off from it in 1993:
      <ulink url="http://www.NetBSD.org/">NetBSD</ulink> and
      <ulink url="&url.top.level;/index.html">FreeBSD</ulink>.  The two projects
      originally diverged due to differences in patience waiting for
      improvements to 386BSD: the NetBSD people started early in the year,
      and the first version of FreeBSD was not ready until the end of the
      year.  In the meantime, the code base had diverged sufficiently to
      make it difficult to merge.  In addition, the projects had different
      aims, as we will see below.  In 1996, a further project,
      <ulink url="http://www.OpenBSD.org/">OpenBSD</ulink>, split off from
      NetBSD.</para>
  </sect1>
  


      <listitem>
	<para>In 1992, AT&amp;T sued
	  <ulink url="http://www.bsdi.com/">BSDI</ulink>,
	  the vendor of BSD/386, alleging that the product contained
	  AT&amp;T-copyrighted code.  The case was settled out of court in
	  1994, but the spectre of the litigation continues to haunt people.

      <para>The BSD kernels are developed and updated following the Open
	Source development model.  Each project maintains a publicly
	accessible <emphasis>source tree</emphasis> under the
	<ulink url="http://www.sourcegear.com/CVS/">Concurrent Versions
	  System</ulink> (CVS), which contains all source files for the
	project, including documentation and other incidental files.  CVS
	allows users to <quote>check out</quote> (in other words, to

	<listitem>
	  <para><ulink url="http://www.apple.com/macosx/server/">Mac OS
	      X</ulink> is the latest version of the operating system for
	    <ulink url="http://www.apple.com/">Apple Computer Inc.'s</ulink>
	      Macintosh line.  Unlike the rest of the operating system, the
	      kernel is open source.  As part of this development, key Apple
	      developers have commit access to the FreeBSD source tree.</para>


      <para>In addition, each of the projects has a list of consultants for
	hire:
	<ulink url="&url.top.level;/commercial/consulting_bycat.html">FreeBSD</ulink>,
	<ulink url="http://www.netbsd.org/gallery/consultants.html">NetBSD</ulink>,
	and <ulink url="http://www.openbsd.org/support.html">OpenBSD</ulink>.</para>
    </sect2>

Lines 102-108 Link Here

(-)en_US.ISO8859-1/articles/filtering-bridges/article.sgml (-1 / +1 lines)
102		102
103	<para>For instructions on how to build and install a new kernel, refer to	103	<para>For instructions on how to build and install a new kernel, refer to
104	the	104	the
105	<ulink url="http://www.FreeBSD.org/handbook/kernelconfig-building.html">Building and Installing a Custom Kernel</ulink> section of the handbook</para>	105	<ulink url="&url.top.books;/handbook/kernelconfig-building.html">Building and Installing a Custom Kernel</ulink> section of the handbook</para>
106	</sect1>	106	</sect1>
107		107
108	<sect1 id="filtering-bridges-finalprep">	108	<sect1 id="filtering-bridges-finalprep">





<!-- The section "Setting a virtual console to 80x60 line mode" was
     updated to reflect changes in FreeBSD system configuration
     files by Mark Ovens <mark@ukug.uk.FreeBSD.org> 27/5/00
 -->

<article>

	    metric (<filename>.afm</filename>) file.</para>

	  <para>Currently available at <ulink
	      url="http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/">http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/</ulink>.
	    Note: These files are postscript programs and must be
	    downloaded to disk by holding down the
	    <keycap>Shift</keycap> key when clicking on the link.

      <listitem>
        <para>The freetype module is included with XFree86 4.x.  For
        more information please see the <ulink
        url="&url.top.books;/handbook/x-fonts.html">FreeBSD
        Handbook</ulink> or the <ulink
        url="http://www.xfree86.org/4.0.2/fonts.html">XFree86 4.0.2
        Fonts</ulink> page.</para>

      <listitem>
	<para><command>xfstt</command> is another font server for X11,
	  available under <ulink url="
	    ftp://sunsite.unc.edu/pub/Linux/X11/fonts/">
	    ftp://sunsite.unc.edu/pub/Linux/X11/fonts/</ulink>.</para>
      </listitem>

      <listitem>
	<para>A program called <command>ttf2bdf</command> can produce
	  BDF files suitable for use in an X environment from TrueType
	  files.  Linux binaries are said to be available from <ulink
	    url="ftp://crl.nmsu.edu/CLR/multiling/General/">ftp://crl.nmsu.edu/CLR/multiling/General/</ulink>.</para>
      </listitem>

      <listitem>

    <itemizedlist>
      <listitem>
	<para><ulink
	    url="ftp://ftp.winsite.com/">ftp://ftp.winsite.com/</ulink>
	  (Formerly CICA)</para>
      </listitem>



      <listitem>
	<para><ulink
	    url="http://af-pc-plloyd.ecel.uwa.edu.au/fonts/">http://af-pc-plloyd.ecel.uwa.edu.au/fonts/</ulink></para>
      </listitem>

      <listitem>
	<para><ulink
	    url="http://www.esselte.com/letraset/">http://www.esselte.com/letraset/</ulink></para>
      </listitem>

      <listitem>

Lines 183-189 Link Here

(-)en_US.ISO8859-1/articles/ipsec-must/article.sgml (-1 / +1 lines)
183		183
184	<para>A comprehensive guide on running IPsec on FreeBSD is	184	<para>A comprehensive guide on running IPsec on FreeBSD is
185	provided in <ulink	185	provided in <ulink
186	url="../../books/handbook/ipsec.html">FreeBSD	186	url="&url.top.books;/handbook/ipsec.html">FreeBSD
187	Handbook</ulink>.</para>	187	Handbook</ulink>.</para>
188	</sect1>	188	</sect1>
189		189




      completely occupied by DOS, you might find the FIPS utility
      (included on the FreeBSD CDROM in the
      <filename>\TOOLS</filename> directory or via <ulink
	URL="&url.ftp.server;/pub/FreeBSD/tools/">ftp</ulink>)
      useful.  It lets you repartition your hard disk without
      destroying the data already on it.  There is also a commercial
      program available called Partition Magic, which lets you size

	    selecting the OS with your arrow keys.  It is included on
	    the FreeBSD CD in the <filename>\TOOLS</filename>
	    directory, and via <ulink
	      URL="&url.ftp.server;/pub/FreeBSD/tools/">ftp</ulink>.</para>
	</listitem>
      </varlistentry>


      previous boot manager.  Boot Easy can be reinstalled by using
      the BOOTINST.EXE utility included in the \TOOLS directory on the
      CDROM, and via <ulink
	URL="&url.ftp.server;/pub/FreeBSD/tools/">ftp</ulink>.
      You can also re-start the installation process and go to the
      partition editor.  From there, mark the FreeBSD partition as
      bootable, select Boot Manager, and then type W to (W)rite out

	mini-HOWTO</ulink> might be interesting as well.  The <ulink
	URL="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>
      is also helpful.</para>
<![ IGNORE [
<!-- dead link -->
    <para>The <ulink
	URL="http://www.dorsai.org/~dcl/publications/NTLDR_Hacking">NT
	Loader Hacking Guide</ulink> provides good information on
      multibooting Windows NT, '95, and DOS with other operating
      systems.</para>
]]>
    <para>And Hale Landis's "How It Works" document pack contains some
      good info on all sorts of disk geometry and booting related
      topics.  You can find it at




      <command>lp</command> or <command>lpr</command> should send a
      file to the printer.  Whether or not the file actually prints
      depends on configuring it, which is covered in the <ulink
      URL="&url.top.books;/handbook/index.html">FreeBSD
      handbook.</ulink></para>
  </sect1>


      edit files, so you can get everything up and running.  There is
      a great deal of information in the FreeBSD handbook (which is
      probably on your hard drive) and <ulink
      URL="&url.top.level;/index.html">FreeBSD's web site</ulink>.  A
      wide variety of packages and ports are on the CDROM as well as
      the web site.  The handbook tells you more about how to use them
      (get the package if it exists, with <command>pkg_add

      space after the slash.)</para>

    <para>You might want to get the most recent version of Netscape
      from their <ulink URL="ftp://ftp.netscape.com/">FTP site</ulink>.
      (Netscape requires the X Window System.) There is now a FreeBSD
      version, so look around carefully.  Just use <command>gunzip
      <replaceable>filename</replaceable></command> and <command>tar

Lines 11-17 Link Here

(-)en_US.ISO8859-1/articles/programming-tools/article.sgml (-1 / +1 lines)
11	<title>This document has moved!</title>	11	<title>This document has moved!</title>
12		12
13	<para>This document has been integrated into the <ulink	13	<para>This document has been integrated into the <ulink
14	url="../../books/developers-handbook/">Developer's	14	url="&url.top.books;/developers-handbook/index.html">Developer's
15	Handbook</ulink>. Please update your bookmarks.</para>	15	Handbook</ulink>. Please update your bookmarks.</para>
16	</sect1>	16	</sect1>
17	</article>	17	</article>




    <procedure>
      <step>
        <para>Install DHCP : Install isc-dhcp-2.0 you can use this config file 
          <ulink url="&url.people.server;/~alfred/pxe/dhcpd.conf">
          dhcpd.conf</ulink>, stick it in /usr/local/etc/</para>
      </step>
      

    <procedure>
      <step>
        <para>Download bootfiles : Download the 
          <ulink url="&url.ftp.server;/pub/FreeBSD/snapshots/i386/kern.flp">
          kern.flp</ulink> and 
          <ulink url="ftp://ftp.FreeBSD.opg/pub/FreeBSD/snapshots/i386/mfsroot.flp"> 
          mfsroot.flp</ulink> floppy images.</para>

        <para>Make a special <filename>loader.rc</filename> to and install it 
          in <filename>/usr/tftpboot/boot/loader.rc</filename> so that it 
          does not prompt for the second disk, here is 
          <ulink url="&url.people.server;/~alfred/pxe/loader.rc">
          mine</ulink>.</para>
      </step>
      

      <step>
        <para>Make your sysinstall script <filename>install.cfg</filename>, you
          can use 
          <ulink url="&url.people.server;/~alfred/pxe/install.cfg">
          mine</ulink> as a template, but you must edit it.</para>
      </step>
      

Lines 2035-2041 Link Here

(-)en_US.ISO8859-1/articles/serial-uart/article.sgml (-1 / +1 lines)
2035		2035
2036	<para>If you do not already have a custom kernel	2036	<para>If you do not already have a custom kernel
2037	configuration file set up, refer to <ulink	2037	configuration file set up, refer to <ulink
2038	url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html">Kernel	2038	url="&url.top.books;/handbook/kernelconfig.html">Kernel
2039	Configuration</ulink> chapter of the FreeBSD Handbook for	2039	Configuration</ulink> chapter of the FreeBSD Handbook for
2040	general procedures. The following are the specifics for the	2040	general procedures. The following are the specifics for the
2041	Boca 16 board and assume you are using the kernel name	2041	Boca 16 board and assume you are using the kernel name




	distributed without the publisher's express written
	<email>Chanda.Leary-Coutu@awl.com</email>.
	The other chapters of
	<ulink url="http://cseng.aw.com/book/0,,0201704811,00.html">the
	  book</ulink> covers topics such as system administration,
	fileserving, and e-mail delivery.  More information about this book is
	available from the publisher, with whom you can also sign up to

	    play.  I prefer using these devices because they are much cheaper
	    and more reliable than a standalone PC running printserver
	    software.  For example, Castelle
	    <ulink url="http://www.castelle.com/">http://www.castelle.com/</ulink>
	    sells the LANpress 1P/10BT printserver for about $170.00.  Using
	    these devices a FreeBSD UNIX server can have dozens of print spools
	    accepting print jobs and then route them back out over the network


	  <step>
	    <para>Obtain the <filename>TCP16.EXE</filename> file from
	      <ulink url="ftp://ftp3.novell.com/pub/updates/eol/nweol/tcp16.exe">ftp://ftp3.novell.com/pub/updates/eol/nweol/tcp16.exe</ulink>.</para>
	  </step>

	  <step>


	  <para>The better solution is to use a simple filter that converts
	    incoming text from UNIX style to DOS style.  The following filter
	    posted on questions@FreeBSD.org and the sample
	    <filename>/etc/printcap</filename> entry can be used to do
	    this:</para>





	helping with this project, send email to the &a.doc;.</para>

      <para>The latest version of this document is always available
        from the <ulink URL="&url.top.level;/index.html">FreeBSD World
        Wide Web server</ulink>.  It may also be downloaded in a
        variety of formats and compression options from the <ulink
        url="&url.ftp.server;/pub/FreeBSD/doc/">FreeBSD FTP
        server</ulink> or one of the numerous <ulink
        url="&url.top.books;/handbook/mirrors-ftp.html">mirror
        sites</ulink>.</para>
    </abstract>
  </bookinfo>

Lines 353-363 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/driverbasics/chapter.sgml (-2 / +2 lines)
353	<listitem><simpara><ulink	353	<listitem><simpara><ulink
354	url="http://www.daemonnews.org/200010/blueprints.html">Dynamic	354	url="http://www.daemonnews.org/200010/blueprints.html">Dynamic
355	Kernel Linker (KLD) Facility Programming Tutorial</ulink> -	355	Kernel Linker (KLD) Facility Programming Tutorial</ulink> -
356	<ulink url="http://www.daemonnews.org">Daemonnews</ulink> October 2000</simpara></listitem>	356	<ulink url="http://www.daemonnews.org/">Daemonnews</ulink> October 2000</simpara></listitem>
357	<listitem><simpara><ulink	357	<listitem><simpara><ulink
358	url="http://www.daemonnews.org/200007/newbus-intro.html">How	358	url="http://www.daemonnews.org/200007/newbus-intro.html">How
359	to Write Kernel Drivers with NEWBUS</ulink> - <ulink	359	to Write Kernel Drivers with NEWBUS</ulink> - <ulink
360	url="http://www.daemonnews.org">Daemonnews</ulink> July	360	url="http://www.daemonnews.org/">Daemonnews</ulink> July
361	2000</simpara></listitem>	361	2000</simpara></listitem>
362	</itemizedlist>	362	</itemizedlist>
363	</para>	363	</para>

Lines 15-21 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml (-1 / +1 lines)
15		15
16	<para>This section should explain IPv6 and IPsec related implementation	16	<para>This section should explain IPv6 and IPsec related implementation
17	internals. These functionalities are derived from <ulink	17	internals. These functionalities are derived from <ulink
18	url="http://www.kame.net">KAME project</ulink></para>	18	url="http://www.kame.net/">KAME project</ulink></para>
19		19
20	<sect2 id="ipv6details">	20	<sect2 id="ipv6details">
21	<title>IPv6</title>	21	<title>IPv6</title>

Lines 25-31 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml (-2 / +2 lines)
25	<filename>/etc/fstab</filename>. Dumps to non-swap devices,	25	<filename>/etc/fstab</filename>. Dumps to non-swap devices,
26	tapes for example, are currently not supported. Config your	26	tapes for example, are currently not supported. Config your
27	kernel using <command>config <option>-g</option></command>. See	27	kernel using <command>config <option>-g</option></command>. See
28	<ulink url="http://www.FreeBSD.org/handbook">The FreeBSD	28	<ulink url="&url.top.books;/handbook/index.html">The FreeBSD
29	Handbook</ulink> for details on configuring the FreeBSD	29	Handbook</ulink> for details on configuring the FreeBSD
30	kernel.</para>	30	kernel.</para>
31		31
Lines 315-321 Link Here
315	<programlisting>options DDB</programlisting>	315	<programlisting>options DDB</programlisting>
316		316
317	to your config file, and rebuild. (See <ulink	317	to your config file, and rebuild. (See <ulink
318	url="http://www.FreeBSD.org/handbook">The FreeBSD Handbook</ulink> for details on	318	url="&url.top.books;/handbook/index.html">The FreeBSD Handbook</ulink> for details on
319	configuring the FreeBSD kernel.</para>	319	configuring the FreeBSD kernel.</para>
320		320
321	<note>	321	<note>

Lines 47-56 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/l10n/chapter.sgml (-3 / +3 lines)
47		47
48	<para> Michael C. Wu will be maintaining an I18N works in progress	48	<para> Michael C. Wu will be maintaining an I18N works in progress
49	homepage at <ulink	49	homepage at <ulink
50	url="http://www.FreeBSD.org/~keichii/i18n/index.html">http://www.FreeBSD.org/~keichii/i18n/index.html</ulink>	50	url="&url.people.server;/~keichii/i18n/">&url.people.server;/~keichii/i18n/</ulink>
51	Please also read the BSDCon2000 I18N paper and presentations	51	Please also read the BSDCon2000 I18N paper and presentations
52	by Clive Lin, Chia-Liang Kao, and Michael C. Wu at <ulink	52	by Clive Lin, Chia-Liang Kao, and Michael C. Wu at <ulink
53	url="http://www.FreeBSD.org/~keichii/papers/">http://www.FreeBSD.org/~keichii/papers/</ulink></para>	53	url="&url.people.server;/~keichii/papers/">&url.people.server;/~keichii/papers/</ulink></para>
54	</sect2>	54	</sect2>
55		55
56	<sect2>	56	<sect2>
Lines 80-83 Link Here
80	<programlisting><envar>setenv LD_PRELOAD /usr/lib/libxpg4.so</envar></programlisting>	80	<programlisting><envar>setenv LD_PRELOAD /usr/lib/libxpg4.so</envar></programlisting>
81	</sect2>	81	</sect2>
82	</sect1>	82	</sect1>
83	</chapter>	83	</chapter>

Lines 205-211 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/pci/chapter.sgml (-1 / +1 lines)
205		205
206	<para>Additional Resources	206	<para>Additional Resources
207	<itemizedlist>	207	<itemizedlist>
208	<listitem><simpara><ulink url="http://www.pcisig.org">PCI	208	<listitem><simpara><ulink url="http://www.pcisig.org/">PCI
209	Special Interest Group</ulink></simpara></listitem>	209	Special Interest Group</ulink></simpara></listitem>
210		210
211	<listitem><simpara>PCI System Architecture, Fourth Edition by	211	<listitem><simpara>PCI System Architecture, Fourth Edition by





      <listitem>
        <para>Any encumbered file requires specific approval from the 
	  <ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> before it is added to the
	  CVS repository.</para>
      </listitem>



          <listitem>
            <para>Should always be in <filename>LINT</filename>, but the 
	      <ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> decides per case if it
	      should be commented out or not.  The 
	      <ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> can, of course, change
	      their minds later on.</para>
          </listitem>


        <orderedlist>
          <listitem>
            <indexterm><primary>core team</primary></indexterm>
            <para>The <ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> decides if
              the code should be part of <command>make world</command>.</para>
          </listitem>
         
          <listitem>
            <indexterm><primary>release engineer</primary></indexterm>
            <para>The <ulink url="&url.top.articles;/contributors/staff-who.html">Release Engineer</ulink>
              decides if it goes in to the release.</para>
          </listitem>
        </orderedlist>

Lines 440-446 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml (-1 / +1 lines)
440	auditing, access control lists, fine grained privileges,	440	auditing, access control lists, fine grained privileges,
441	information labeling, and mandatory access control.</para>	441	information labeling, and mandatory access control.</para>
442	<para>This is a work in progress and is the focus of the <ulink	442	<para>This is a work in progress and is the focus of the <ulink
443	url="http://www.trustedbsd.org">TrustedBSD</ulink> project. Some	443	url="http://www.trustedbsd.org/">TrustedBSD</ulink> project. Some
444	of the initial work has been committed to FreeBSD-current	444	of the initial work has been committed to FreeBSD-current
445	(cap_set_proc(3)).</para>	445	(cap_set_proc(3)).</para>
446		446





      <para>Here is a list of interpreters that are available as
	<ulink
	  URL="&url.ftp.server;/pub/FreeBSD/ports/packages/">FreeBSD
	  packages</ulink>, with a brief discussion of some of the
	more popular interpreted languages.</para>


	      for Visual Basic.</para>

	    <para>The <ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/bwbasic-2.10.tgz">Bywater
		Basic Interpreter</ulink> and the <ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/pbasic-2.0.tgz">Phil
		Cockroft's Basic Interpreter</ulink> (formerly Rabbit
	      Basic) are available as <ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/">FreeBSD
		packages</ulink>.</para>
	  </listitem>
	</varlistentry>

	      language, but can be rather large and unwieldy.</para>

	    <para>FreeBSD has <ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/gcl-2.0.tgz">GNU
		Common Lisp</ulink> available as a package.</para>
	  </listitem>
	</varlistentry>

	      abstraction to be used in research work.</para>

	    <para>FreeBSD has packages of the <ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/elk-3.0.tgz">Elk
		Scheme Interpreter</ulink>, the <ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/mit-scheme-7.3.tgz">MIT
		Scheme Interpreter</ulink> and the <ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/scm-4e1.tgz">SCM
		Scheme Interpreter</ulink>.</para>
	  </listitem>
	</varlistentry>


	  <listitem>
	    <para><ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/icon-9.0.tgz">The
		Icon Programming Language</ulink>.</para>
	  </listitem>
	</varlistentry>


	  <listitem>
	    <para><ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/ucblogo-3.3.tgz">Brian
		Harvey's LOGO Interpreter</ulink>.</para>
	  </listitem>
	</varlistentry>


	  <listitem>
	    <para><ulink
		URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/python-1.2.tgz">The
		Python Object-Oriented Programming
		Language</ulink></para>
	  </listitem>


      <para>Finally, if you find its text-based command-prompt style
	off-putting, there's a graphical front-end for it <ulink
	  URL="&url.top.level;/ports/devel.html">xxgdb</ulink> in the ports
	collection.</para>

      <para>This section is intended to be an introduction to using

      <para>And doubtless many more that I've overlooked.</para>

      <para>Emacs can be installed on FreeBSD using <ulink
	  URL="&url.top.level;/ports/editors.html">the Emacs
	  port</ulink>.</para>

      <para>Once it's installed, start it up and do <userinput>C-h

	quite big!).</para>

      <para>The best way to learn Emacs Lisp is to download the <ulink
	  URL="ftp://prep.ai.mit.edu/pub/gnu/elisp-manual-19-2.4.tar.gz">Emacs
	  Tutorial</ulink></para>

      <para>However, there's no need to actually know any Lisp to get




        construction. If you are interested in helping with this project,
        send email to the &a.doc;.  The latest version of this
        document is always available from the <ulink
        URL="&url.top.level;/index.html">FreeBSD World Wide Web
        server</ulink>. It may also be downloaded as one large <ulink
        URL="book.html">HTML</ulink> file with HTTP or as plain text,
        postscript, PDF, etc. from the <ulink
        URL="&url.ftp.server;/pub/FreeBSD/doc/">FreeBSD FTP
        server</ulink>. You may also want to <ulink
        URL="&url.top.level;/search/index.html">Search the
        FAQ</ulink>.</para>
    </abstract>
  </bookinfo>

           Berkeley's <quote>Net/2</quote> to the i386, known as <quote>386BSD</quote>, though very
           little of the 386BSD code remains.  A fuller description of
           what FreeBSD is and how it can work for you may be found on
           the <ulink URL="&url.top.level;/index.html">FreeBSD home
           page</ulink>.</para>

         <para>FreeBSD is used by companies, Internet Service Providers,
           researchers, computer professionals, students and home users
           all over the world in their work, education and recreation.
           See some of them in the <ulink
           URL="&url.top.level;/gallery/index.html">FreeBSD
           Gallery</ulink>.</para>

         <para>For more detailed information on FreeBSD, please see the
           <ulink URL="&url.top.books;/handbook/index.html">FreeBSD
           Handbook</ulink>.</para>
       </answer>
      </qandaentry>

            Software and one that we enthusiastically support.</para>

          <para>That code in our source tree which falls under the <ulink
            url="&url.top.level;/copyright/COPYING">GNU General Public
              License (GPL)</ulink> or <ulink
            url="&url.top.level;/copyright/COPYING.LIB">GNU Library
              General Public License (LGPL)</ulink> comes with slightly more
            strings attached, though at least on the side of enforced access
            rather than the usual opposite.  Due to the additional complexities
            that can evolve in the commercial use of GPL software, we do,
            however, endeavor to replace such software with submissions under
            the more relaxed <ulink
            url="&url.top.level;/copyright/freebsd-license.html">
              FreeBSD copyright</ulink> whenever possible.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>Version <ulink
            URL="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;</ulink>
            is the latest <emphasis>STABLE</emphasis> version; it was
            released in &rel.current.date;. This is also the latest
            <emphasis>RELEASE</emphasis> version.</para>


        <answer>
          <para><ulink
            URL="&url.top.books;/handbook/cutting-edge.html#CURRENT">FreeBSD-CURRENT</ulink>
            is the development version of the operating system, which will
            in due course become 5.0-RELEASE.  As such, it is really only
            of interest to developers working on the system and die-hard
            hobbyists.  See the <ulink
            URL="&url.top.books;/handbook/cutting-edge.html#CURRENT">relevant
            section</ulink> in the <ulink
            URL="&url.top.books;/handbook/index.html">handbook</ulink> for details on
            running -CURRENT.</para>

          <para>If you are not familiar with the operating system or are

            treated with contempt.</para>

          <para>Every day, <ulink
            URL="&url.top.level;/releases/snapshots.html">snapshot
            </ulink> releases are made based on the current state of the
            -CURRENT and -STABLE branches. Nowadays, distributions of the
            occasional snapshot are now being made available. The goals

        <answer>
          <para>Back when FreeBSD 2.0.5 was released, we decided to
            branch FreeBSD development into two parts.  One branch was
            named <ulink URL="&url.top.books;/handbook/current-stable.html#STABLE">-STABLE</ulink>,
            with the intention that only well-tested bug fixes and small
            incremental enhancements would be made to it (for Internet
            Service Providers and other commercial enterprises for whom
            sudden shifts or experimental features are quite
            undesirable).  The other branch was <ulink
            URL="&url.top.books;/handbook/cutting-edge.html#CURRENT">-CURRENT</ulink>,
            which essentially has been one unbroken line leading towards
            5.0-RELEASE (and beyond) since 2.0 was released. If a little
            ASCII art would help, this is how it looks:</para>

          <para>The key decisions concerning the FreeBSD project, such as
            the overall direction of the project and who is allowed to add
            code to the source tree, are made by a <ulink
            URL="&url.top.articles;/contributors/staff-core.html">core team</ulink> of
            9 people. There is a much larger team of more than 200 <ulink
            URL="&url.top.articles;/contributors/staff-committers.html">committers</ulink> who
            are authorized to make changes directly to the FreeBSD source
            tree.</para>


        <answer>
          <para>Every significant release of FreeBSD is available via
            anonymous FTP from the <ulink
            URL="&url.ftp.server;/pub/FreeBSD/">
            FreeBSD FTP site</ulink>:</para>

          <itemizedlist>
            <listitem>
              <para>For the current 3.X-STABLE release, 3.5.1-RELEASE, see
                the <ulink
                URL="&url.ftp.server;/pub/FreeBSD/releases/i386/3.5.1-RELEASE/">3.5.1-RELEASE directory</ulink>.</para>
            </listitem>

            <listitem>
              <para>The current 4-STABLE release, &rel.current;-RELEASE can be
                found in the <ulink
                URL="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">&rel.current;-RELEASE directory</ulink>.</para>
            </listitem>

            <listitem>

          </itemizedlist>

	  <para>Information about obtaining FreeBSD on CD, DVD, and other
	    media can be found in <ulink url="&url.top.books;/handbook/mirrors.html">the
	      Handbook</ulink>.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>You can find full information in the <ulink
            URL="&url.top.books;/handbook/eresources.html#ERESOURCES-MAIL">Handbook
            entry on mailing-lists</ulink>.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>You can find full information in the <ulink
            URL="&url.top.level;/y2kbug.html">FreeBSD Y2K
            page</ulink>.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>You can find full information in the <ulink
            URL="&url.top.books;/handbook/eresources-news.html">Handbook entry on
            newsgroups</ulink>.</para>
        </answer>
      </qandaentry>

          <para>The Problem Report database of all user change requests
            may be queried (or submitted to) by using our web-based PR
            <ulink
            URL="&url.top.level;/send-pr.html">submission</ulink>
            and <ulink
            URL="&url.cgi.server;/cgi/query-pr-summary.cgi?query">
            query</ulink>
            interfaces.  The &man.send-pr.1; command can
            also be used to submit problem reports and change requests via

          <para>Yes.  The documentation is available in a number of different
            formats and compression schemes on the FreeBSD FTP site, in the
            <ulink
            URL="&url.ftp.server;/pub/FreeBSD/doc/">/pub/FreeBSD/doc/</ulink> directory.</para>

          <para>The documentation is categorised in a number of different
            ways.  These include:</para>

          <para>Knowing this, you can use the following command to install the
            English PDF FAQ package.</para>

          <screen>&prompt.root; <userinput>pkg_add &url.ftp.server;/pub/FreeBSD/doc/packages/faq.en_US.ISO8859-1.pdf.tgz</userinput></screen>

          <para>Having done that, you can use &man.pkg.info.1; to determine
            where the file has been installed.</para>


          <para>For example, the split HTML version of the FAQ, compressed
            using &man.gzip.1;, can be found in the
            <filename>doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz</filename>
            file.  To download and uncompress that file you would have to do
            this.</para>

          <screen>&prompt.root; <userinput>fetch &url.ftp.server;/pub/FreeBSD/doc/en_US.ISO8859-1/books/faq/book.html-split.tar.gz</userinput>
&prompt.root; <userinput>gzip -d book.html-split.tar.gz</userinput>
&prompt.root; <userinput>tar xvf book.html-split.tar</userinput></screen>


                copy of the web site sources using your favorite ftp mirror
                tool.  Keep in mind that you have to build these sources before
                publishing them.  Simply start at
                <ulink URL="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/www">&url.ftp.server;/pub/FreeBSD/FreeBSD-current/www</ulink>.</para>
            </listitem>
          </itemizedlist>
        </answer>

          <itemizedlist>
            <listitem>
              <para>The <ulink
                URL="&url.top.level;/index.html">FreeBSD Home Page</ulink>.</para>
            </listitem>

            <listitem>
              <para><anchor id="pao">If you have a laptop, be sure and see
                <ulink URL="http://www.jp.FreeBSD.org/FAO/">Tatsumi
                Hosokawa's Mobile Computing page</ulink> in Japan.</para>
            </listitem>

            <listitem>
              <para><anchor id="smp">For information on SMP (Symmetric
                MultiProcessing), please see the <ulink
                URL="&url.people.server;/~fsmp/SMP/SMP.html">SMP support page</ulink>.</para>
            </listitem>

            <listitem>
              <para><anchor id="multimedia">For information on FreeBSD
                multimedia applications, please see the <ulink
                URL="&url.people.server;/~faulkner/multimedia/mm.html">multimedia</ulink>
                page.  If you are interested specifically in the <ulink
                URL="&url.people.server;/~ahasty/Bt848.html">Bt848</ulink>
                video capture chip, then follow that link.</para>
            </listitem>
          </itemizedlist>

          <para>The FreeBSD handbook also has a fairly complete <ulink
            URL="&url.top.books;/handbook/bibliography.html">bibliography</ulink>
            section which is worth reading if you are looking for actual
            books to buy.</para>
        </answer>

	<firstname>Nik</firstname>
	<surname>Clayton</surname>
	<affiliation>
	  <address><email>nik@FreeBSD.org</email></address>
	</affiliation>
      </author>
    </chapterinfo>


          <para>Full instructions on this procedure and a little bit more
            about installation issues in general can be found in the
            <ulink URL="&url.top.books;/handbook/install.html">Handbook entry on
            installing FreeBSD</ulink>.</para>

        </answer>

                <quote>raw</quote>, using the low-level tools (e.g.
                <command>fdimage</command> or <command>rawrite</command>)
                described in the <ulink
                URL="&url.top.books;/handbook/install.html">installation guide to
                FreeBSD</ulink>.</para>
            </listitem>
          </itemizedlist>


        <answer>
          <para>Installation instructions can be found in the
            <ulink URL="&url.top.books;/handbook/install.html">Handbook entry on installing FreeBSD</ulink>.</para>
        </answer>
      </qandaentry>



        <answer>
          <para>Have a look at
            <ulink URL="&url.top.articles;/multi-os/index.html">
            The multi-OS page</ulink>.</para>
        </answer>
      </qandaentry>


	  <para>It has been reported that later IBM BIOS revisions may have
	    reintroduced the bug.  <ulink
					  url="&url.cgi.server;/cgi/getmsg.cgi?fetch=200565+208320+/usr/local/www/db/text/2001/freebsd-mobile/20010429.freebsd-mobile">This message</ulink>
	    from Jacques Vidrine to the &a.mobile; describes a procedure
            which may work if your newer IBM laptop does not boot FreeBSD
            properly, and you can upgrade or downgrade the BIOS..</para>

            <step>
              <para>Download <filename>boot1</filename> and
                <filename>boot2</filename> from <ulink
                  url="&url.people.server;/~bmah/ThinkPad/">&url.people.server;/~bmah/ThinkPad/</ulink>.
                Put these files somewhere you will be able to retrieve them
                later.</para>
            </step>

              </listitem>

              <listitem>
                <para><ulink URL="&url.top.books;/handbook/kernelconfig.html">Rebuild
                  your kernel,</ulink> modify the wd configuration lines to
                  read:</para>


          <para>We <emphasis>strongly</emphasis> recommend that you use
            binary snapshots to do this. 4-STABLE snapshots are available at
            <ulink
            URL="ftp://releng4.FreeBSD.org/">ftp://releng4.FreeBSD.org/</ulink>.</para>

          <para>If you wish to upgrade using source, please see the <ulink
            URL="&url.top.books;/handbook/cutting-edge.html">FreeBSD
            Handbook</ulink> for more information.</para>

          <caution>

               <para>The security profile is not a silver bullet!  Even if you use the
                 extreme setting, you need to keep up with security
                 issues by reading an appropriate <ulink
                 url="&url.top.books;/handbook/eresources.html#ERESOURCES-MAIL">mailing
                 list</ulink>, using good passwords and passphrases, and
                 generally adhering to good security practices.  It simply
                 sets up the desired security to convenience ratio out of


        <answer>
          <para>See the complete list in the <ulink
            URL="&url.top.books;/handbook/install.html#INSTALL-HW">Handbook</ulink>.</para>
        </answer>
      </qandaentry>



        <answer>
          <para>There is a list of these in the <ulink
            URL="&url.top.books;/handbook/install.html#INSTALL-MISC">Miscellaneous
            devices</ulink> section of the handbook.</para>

          <para>Some unnamed clone cards have also been known to work,

          <programlisting>device psm0 at atkbdc? irq 12</programlisting>

          <para>See the <ulink
            URL="&url.top.books;/handbook/kernelconfig.html">Handbook entry on
            configuring the kernel</ulink> if you have no experience with
            building kernels.</para>



        <answer>
          <para>See the <ulink
            URL="&url.top.books;/handbook/install.html#INSTALL-NICS">
            Ethernet cards</ulink> section of the handbook for a more
            complete list.</para>
        </answer>


        <answer>
          <para>See the <ulink
            URL="&url.top.books;/handbook/install.html#INSTALL-MISC">Handbook</ulink>
            for the list of other devices supported.</para>

        </answer>

          <para>The newer AIC789x series Adaptec chips are supported under
            the CAM SCSI framework which made it's debut in 3.0. Patches
            against 2.2-STABLE are in <ulink
            URL="&url.ftp.server;/pub/FreeBSD/development/cam/">
            &url.ftp.server;/pub/FreeBSD/development/cam/</ulink>.
            A CAM-enhanced boot floppy is available at <ulink
            URL="&url.people.server;/~abial/cam-boot/">
            &url.people.server;/~abial/cam-boot/</ulink>.
            In both cases read the README before beginning.</para>
        </answer>
      </qandaentry>

            address range clash :), by bumping the kernel option
            <literal>EISA_SLOTS</literal> to a value of 12. Configure and
            compile a kernel, as described in the <ulink
            URL="&url.top.books;/handbook/kernelconfig.html">Handbook entry on
            configuring the kernel</ulink>.</para>

          <para>Of course, this does present you with a chicken-and-egg

          interest in FreeBSD can have very positive effects on FreeBSD's
          long-term viability). We encourage commercial software vendors to
          send their entries here for inclusion. See <ulink
          URL="&url.top.level;/commercial/index.html">the
          Vendors page</ulink> for a longer list.</para>
      </note>


        <answer>
	  <itemizedlist>
  	    <listitem>
	      <para><ulink url="http://www.freebsdmall.com/">The FreeBSD Mall</ulink>
                offers a FreeBSD native version of <ulink
                url="http://www.vistasource.com/">VistaSource</ulink>
                ApplixWare 5.</para>
	
	      <para>ApplixWare is a rich full-featured, commercial

  	    </listitem>
	    <listitem>
	      <para>The Linux version of <ulink
	        url="http://www.sun.com/staroffice/">StarOffice</ulink>
	        works flawlessly on FreeBSD.  The easiest way to
	        install the Linux version of StarOffice is through the
	        <ulink
	        url="&url.top.books;/handbook/ports.html">FreeBSD
	        Ports collection</ulink>.  Future versions of the
	        open-source <ulink
	        url="http://www.openoffice.org/">OpenOffice</ulink>
	        suite should work as well.</para>
	    </listitem>
	  </itemizedlist>

	  <para>The Open Group has released the source code to Motif 2.1.30.
	    You can install the <literal>open-motif</literal> package, or
	    compile it from ports.  Refer to
	    <ulink url="&url.top.books;/handbook/ports.html">the ports section of the
	      Handbook</ulink> for more information on how to do this.

	    <note>
	      <para>The Open Motif distribution only allows redistribution
		if it is running on an <ulink url="http://www.opensource.org/">
		  open source</ulink> operating system.</para>
	    </note>
	  </para>

            source X11 desktop which is similar to CDE in many respects.
            You might also like the look and feel of <ulink
            URL="http://www.xfce.org/">xfce</ulink>. KDE and xfce are both
            in the <ulink URL="&url.top.level;/ports/index.html">ports
            system</ulink>.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>Yes! See the <ulink
            URL="&url.top.level;/commercial/software_bycat.html#CATEGORY_DATABASE">
            Commercial Vendors</ulink> section of FreeBSD's Web site.</para>

          <para>Also see the <ulink
            URL="&url.top.level;/ports/databases.html">
            Databases</ulink> section of the Ports collection.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>Please take a look at
            <ulink URL="&url.top.level;/ports/index.html">the ports
            page</ulink> for info on software packages ported to FreeBSD.
            The list currently tops 3400 and is growing daily, so come back
            to check often or subscribe to the

                <term>for 2.2.8-RELEASE/2.2.8-STABLE</term>
                <listitem>
                  <para><ulink
                    URL="&url.ftp.server;/pub/FreeBSD/ports/i386/packages-2.2.8/">
                    &url.ftp.server;/pub/FreeBSD/ports/i386/packages-2.2.8/</ulink></para>
                </listitem>
              </varlistentry>


                <term>for 3.X-RELEASE/3.X-STABLE</term>
                <listitem>
                  <para><ulink
                    URL="&url.ftp.server;/pub/FreeBSD/ports/i386/packages-3-stable/">
                    &url.ftp.server;/pub/FreeBSD/ports/i386/packages-3-stable/</ulink></para>
                </listitem>
              </varlistentry>


                <term>for 4.X-RELEASE/4-STABLE</term>
                <listitem>
                  <para><ulink
                    URL="&url.ftp.server;/pub/FreeBSD/ports/i386/packages-4-stable/">
                    &url.ftp.server;/pub/FreeBSD/ports/i386/packages-4-stable/</ulink></para>

                </listitem>
              </varlistentry>

                <term>for 5.X-CURRENT</term>
                <listitem>
                  <para><ulink
                    URL="&url.ftp.server;/pub/FreeBSD/ports/i386/packages-5-current/">
                    &url.ftp.server;/pub/FreeBSD/ports/i386/packages-5-current</ulink></para>
                </listitem>
              </varlistentry>
            </variablelist>

            new ones are constantly being added. It is always a good idea
            to check back periodically to see which packages are available
            at the <ulink
            URL="&url.ftp.server;/pub/FreeBSD/">ftp.FreeBSD.org</ulink>
            master site.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>Yes. Please see <ulink
            URL="&url.top.level;/java/index.html">
            &url.home.page;/java/</ulink>.</para>
        </answer>
      </qandaentry>


        <answer>
          <para>If you are running a FreeBSD version that lags
            significantly behind -CURRENT or -STABLE, you may need a ports
            upgrade kit from <ulink URL="&url.top.level;/ports/index.html">
            &url.home.page;/ports/</ulink>. If you are up to date,
            then someone might have committed a change to the port which
            works for -CURRENT but which broke the port for -STABLE. Please
            submit a bug report on this with the


        <answer>
          <para>Not at all! Check out the <ulink
            URL="&url.top.books;/handbook/kernelconfig.html">
            kernel config section of the Handbook</ulink>.</para>

            <note>


        <answer>
          <para>See the Disk Formatting Tutorial at <ulink
            URL="&url.top.articles;/formatting-media/index.html">
            www.FreeBSD.org</ulink>.</para>
        </answer>
      </qandaentry>

              <listitem>
                <para>A read-only NTFS driver exists for FreeBSD. For more
                  information, see this tutorial by Mark Ovens at <ulink
                  URL="http://ukug.uk.FreeBSD.org/~mark/ntfs_install.html">
                  http://ukug.uk.FreeBSD.org/~mark/ntfs_install.html</ulink>.
                  </para>
              </listitem>
            </varlistentry>

        <answer>
          <para>Please have a look at the Handbook entry on printing. It
            should cover most of your problem. See the <ulink
            URL="&url.top.books;/handbook/printing.html">
            Handbook entry on printing</ulink>.</para>

	  <para>Some printers require a host-based driver to do any kind of

	    only hope of getting one of these to work is to check if the
	    <filename>ports/print/pnm2ppa</filename> port supports it.
	    From <ulink
	    url="&url.cgi.server;/cgi/url.cgi?ports/print/pnm2ppa/pkg-descr">its
	    package description</ulink>:</para>

	  <blockquote>

              <para>This point and others are often discussed on the
                mailing lists, particularly freebsd-security.  Please search
                the archives <ulink
                url="&url.top.level;/search/index.html">here</ulink> for an
                extensive discussion.  Some people are hopeful that
                securelevel will soon go away in favor of a more
                fine-grained mechanism, but things are still hazy in this

          <para>Enabling <varname>vfs.usermount</varname>, however, has
            negative security implications.  A better way to access MSDOS
            formatted media is to use the <ulink
            URL="&url.cgi.server;/cgi/ports.cgi?query=%5Emtools-&amp;stype=name">mtools</ulink> package in the ports collection.</para>
        </answer>
      </qandaentry>


            on both disks with &man.boot0cfg.8;, so that you can
            dual boot to the old or new system after the copying
            is done.  See the <ulink
            url="&url.top.articles;/formatting-media/index.html">
            formatting-media article</ulink> for details on this
            process.</para>

          <para>Now you have the new disk set up, and are ready

        </question><answer>

          <para>There are two schools of thought on how to start <ulink
            URL="&url.cgi.server;/cgi/man.cgi?manpath=xfree86&amp;query=xdm">
            xdm</ulink>. One school starts xdm from
            <filename>/etc/ttys</filename> (see &man.ttys.5;)
            using the supplied example, while the other simply runs xdm

            <para><quote>Diskless booting</quote> means that the FreeBSD
              box is booted over a network, and reads the necessary files
              from a server instead of its hard disk. For full details,
              please read <ulink URL="&url.top.books;/handbook/diskless.html">the
              Handbook entry on diskless booting</ulink></para>
        </answer>
      </qandaentry>


          <para>More detailed information about setting this up can be
            found in the <ulink
            URL="&url.top.books;/ppp-primer/index.html">
            Pedantic PPP Primer</ulink> by Steve Sims.</para>

          <para>If you are using kernel-mode ppp, or have an Ethernet

            with outgoing connections.</para>

          <para>For more information on how to use these, please see the
            <ulink url="&url.top.books;/handbook/ppp-and-slip.html">Handbook chapter on
            PPP and SLIP</ulink>.</para>

          <para>If you only have access to the Internet through a

            it mildly) and can sometimes cause problems with network
            intensive applications like NFS.</para>

          <para>See <ulink URL="&url.top.books;/handbook/nfs.html">
            the Handbook entry on NFS</ulink> for more information on
            this topic.</para>
        </answer>

            in <filename>/etc/rc.conf</filename>.</para>

          <para>For further information on configuring a FreeBSD firewall,
            see the <ulink URL="&url.top.books;/handbook/firewalls.html">
            Handbook section</ulink>.</para>
        </answer>
      </qandaentry>

          <para>See the <link linkend="service-redirect">FAQ about
            redirecting services</link>, the &man.natd.8; manual, or one of
            the several port redirecting utilities in the <ulink
            url="&url.top.level;/ports/index.html">ports collection</ulink> for a correct way to do
            this.</para>
        </answer>
      </qandaentry>

          <screen>&prompt.root; <userinput>sh MAKEDEV bpf0</userinput></screen>

          <para>Please see the <ulink
            URL="&url.top.books;/handbook/kernelconfig-nodes.html">
            handbook's entry on device nodes</ulink> for more information
            on creating devices.</para>
        </answer>

          <para>You should first read the
            &man.ppp.8;
            man page and the <ulink
            URL="&url.top.books;/handbook/ppp-and-slip.html#USERPPP">
            ppp section of the handbook</ulink>.  Enable logging with
            the command</para>



          <para>If your version of ppp does not understand the
            <command>set log</command> command, you should download the
            <ulink URL="&url.people.server;/~brian/">
            latest version</ulink>. It will build on FreeBSD version
            2.1.5 and higher.</para>
        </answer>


          <para>from <filename>ppp.conf</filename>.  If this is the case,
            go back to the <ulink
            URL="&url.top.books;/handbook/ppp-and-slip.html#USERPPP-FINAL">
            Final system configuration</ulink> section of the
            handbook.</para>
        </answer>

add 0 0 HISADDR</programlisting>

          <para>Refer to the <ulink
            URL="&url.top.books;/handbook/ppp-and-slip.html#USERPPP-DYNAMICIP">
            PPP and Dynamic IP addresses</ulink> section of the handbook
            for further details.</para>
        </answer>

        </question>

        <answer>
          <para>See the <ulink url="&url.top.books;/fdp-primer/translations.html">
            Translation FAQ</ulink> in the FreeBSD Documentation Project
            Primer.</para>
        </answer>

        </question>

        <answer>
          <para><ulink URL="&url.cgi.server;/cgi/ports.cgi?^sup">
            SUP</ulink> stands for Software Update Protocol, and was
            developed by CMU for keeping their development trees in sync.
            We used it to keep remote sites in sync with our central


          <para>SUP is not bandwidth friendly, and has been retired.
            The current recommended method to keep your sources up to
            date is <ulink URL="&url.top.books;/handbook/synching.html#CVSUP">
            Handbook entry on CVSup</ulink></para>
        </answer>
      </qandaentry>

            long argument about whether &man.sleep.1; should take
            fractional second arguments, &a.phk; posted a long
            message entitled <quote><ulink
            url="&url.cgi.server;/cgi/getmsg.cgi?fetch=506636+517178+/usr/local/www/db/text/1999/freebsd-hackers/19991003.freebsd-hackers">A bike
            shed (any colour will do) on greener grass...</ulink></quote>.
            The appropriate portions of that message are quoted
            below.</para>

        <answer>
          <para>There are currently three active/semi-active branches
            in the FreeBSD <ulink
            URL="&url.cgi.server;/cgi/cvsweb.cgi">
            CVS Repository</ulink> (the RELENG_2 branch is probably
            only changed twice a year, which is why there are only three
            active branches of development):</para>


          <para>Second, you have to have the whole CVS repository at
            hand.  To get this you can use <ulink
            URL="&url.top.books;/handbook/synching.html#CVSUP">CVSUP</ulink> but in
            your supfile set the release name to cvs and remove any tag or
            date fields:</para>


        <answer>
          <para>Yes, you can do this <literal>without</literal>
            downloading the whole source tree by using the <ulink
            URL="&url.top.books;/handbook/synching.html#CTM">CTM facility</ulink>.</para>
        </answer>
      </qandaentry>



        <answer>
          <para>Please take a look at <ulink
            URL="&url.top.articles;/contributing/index.html">The contributing to FreeBSD article on how to
            submit code</ulink>.</para>

          <para>And thanks for the thought!</para>

Lines 44-50 Link Here

(-)en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml (-1 / +1 lines)
44	source for this and other documents, available in the	44	source for this and other documents, available in the
45	<application>CVSup</application> <literal>doc</literal> collection, or	45	<application>CVSup</application> <literal>doc</literal> collection, or
46	available online starting at <ulink	46	available online starting at <ulink
47	url="http://www.FreeBSD.org/cgi/cvsweb.cgi/doc/">http://www.FreeBSD.org/cgi/cvsweb.cgi/doc/</ulink>.</para>	47	url="&url.cgi.server;/cgi/cvsweb.cgi/doc/">&url.cgi.server;/cgi/cvsweb.cgi/doc/</ulink>.</para>
48		48
49	<para>To avoid confusion, these examples use the standard DocBook 3.1 DTD	49	<para>To avoid confusion, these examples use the standard DocBook 3.1 DTD
50	rather than the FreeBSD extension. They also use the stock stylesheets	50	rather than the FreeBSD extension. They also use the stock stylesheets




         <listitem>
           <para>This is the main FreeBSD presence on the World Wide Web,
	    visible at <ulink
	      url="&url.top.level;/index.html">&url.home.page;/</ulink>
	    and many mirrors around the world.  The web site is many people's
	    first exposure to FreeBSD.</para>
	</listitem>


	<para>If you have the CVS repository locally then as a minimum you
	  will need to checkout the <filename>doc/share</filename>, and
	  <filename>&url.doc.enUS;/share</filename>
	  directories.</para>

	<screen>&prompt.user; <userinput>cvs checkout doc/share</userinput>
&prompt.user; <userinput>cvs checkout &url.doc.enUS;/share</userinput></screen>

	<para>If you have plenty of disk space then you could check out
	  everything.</para>

	    <para>Check out the <filename>articles</filename>
	      directory.</para>

	    <screen>&prompt.user; <userinput>cvs checkout &url.doc.enUS;/articles</userinput></screen>
	  </step>

	  <step>

	      case, you have decided that your new article belongs in a
	      directory called <filename>vpn-w2k</filename>.</para>

	    <screen>&prompt.user; <userinput>cd &url.doc.enUS;/articles</userinput>
&prompt.user; <userinput>cp -r committers-guide vpn-w2k</userinput></screen>
	  </step>
	</procedure>

	<para>If you wanted to edit an existing document, such as the the FAQ,
	  which is in <filename>&url.doc.enUS;/books/faq</filename> you
	  would check it out of the repository like this.</para>

	<screen>&prompt.user; <userinput>cvs checkout &url.doc.enUS;/books/faq</userinput></screen>
      </step>

      <step>





    <itemizedlist>
      <listitem>
	<para><ulink url="&url.top.level;/docproj/index.html">The FreeBSD
	    Documentation Project web pages</ulink></para>
      </listitem>

      <listitem>
	<para><ulink url="&url.top.books;/handbook/index.html">The FreeBSD Handbook</ulink></para>
      </listitem>
    </itemizedlist>
  </sect1>

      </listitem>

      <listitem>
	<para><ulink url="http://docbook.sourceforge.net/">The DocBook Open
	    Repository</ulink> contains DSSSL stylesheets and other resources
	  for people using DocBook.</para>
      </listitem>




  There's a new copy of my primer for contributers to the FreeBSD
  Documentation Project available at

    <URL:&url.people.server;/~nik/primer/index.html>

  Comments appreciated.


	  <para>Use:</para>

	  <programlisting><![ CDATA [<p>More information is available at the
  <a href="&url.home.page;/">FreeBSD web site</a>.</p>]]></programlisting>
	</example>

	<para>These links will take the user to the top of the chosen


      <para>The FreeBSD extensions are not (currently) in the ports
	collection.  They are stored in the FreeBSD CVS tree, as <ulink
	url="&url.cgi.server;/cgi/cvsweb.cgi/doc/share/sgml/freebsd.dtd">doc/share/sgml/freebsd.dtd</ulink>.</para>
    </sect2>

    <sect2>

	best suited to information that can be broken up into several
	chapters, possibly with appendices and similar content as well.</para>

      <para>The <ulink url="&url.top.level;/docs.html">FreeBSD
	  tutorials</ulink> are all marked up as articles, while this
	document, the <ulink url="&url.top.books;/faq/index.html">FreeBSD
	  FAQ</ulink>, and the <ulink
	  url="&url.top.books;/handbook/index.html">FreeBSD Handbook</ulink> are
	all marked up as books.</para>

      <sect3>

	  by hand.</para>

	<para>The best example of what follows in practice is the
	  <filename>&url.doc.enUS;/articles/vm-design/</filename> document.
	  If you're unsure of the description that follows, take a look at the
	  files in that directory to see how everything hangs togther.
	  Experiment with creating different formatted versions of the

	  <para>Use:</para>

	  <programlisting><![ CDATA [<para>Of course, you could stop reading this document and
  go to the <ulink url="&url.top.level;/index.html">FreeBSD
  home page</ulink> instead.</para>]]></programlisting>

	  <para>Appearance:</para>

	  <para>Of course, you could stop reading this document and go to the
	    <ulink url="&url.top.level;/index.html">FreeBSD home page</ulink>
	    instead.</para>
	</example>
      </sect3>

Lines 53-60 Link Here

(-)en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml (-2 / +2 lines)
53	<para>Setup a CVS repository. You need the directories www, doc and	53	<para>Setup a CVS repository. You need the directories www, doc and
54	ports in the CVS tree (plus the CVSROOT of course). Please read the	54	ports in the CVS tree (plus the CVSROOT of course). Please read the
55	CVSup introduction <ulink	55	CVSup introduction <ulink
56	url="http://www.freebsd.org/handbook/synching.html#CVSUP">	56	url="&url.top.books;/handbook/synching.html#CVSUP">
57	http://www.freebsd.org/handbook/synching.html#CVSUP</ulink> how to	57	http://www.FreeBSD.org/handbook/synching.html#CVSUP</ulink> how to
58	mirror a CVS tree or parts of a CVS tree.</para>	58	mirror a CVS tree or parts of a CVS tree.</para>
59		59
60	<para>The essential cvsup collections are: <literal>www</literal>,	60	<para>The essential cvsup collections are: <literal>www</literal>,

Lines 171-177 Link Here

(-)en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml (-1 / +1 lines)
171		171
172	<answer>	172	<answer>
173	<para>The <ulink	173	<para>The <ulink
174	url="http://www.FreeBSD.org/docproj/translations.html">Documentation	174	url="&url.top.level;/docproj/translations.html">Documentation
175	Project translations page</ulink> lists the translation efforts	175	Project translations page</ulink> lists the translation efforts
176	that are currently known about. If others are already working	176	that are currently known about. If others are already working
177	on translating documentation to your language, please don't	177	on translating documentation to your language, please don't

Lines 142-148 Link Here

(-)en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml (-1 / +1 lines)
142	</variablelist>	142	</variablelist>
143		143
144	<para>For more information about writing style, see <ulink	144	<para>For more information about writing style, see <ulink
145	url="http://www.bartleby.com/141/index.html">Elements of	145	url="http://www.bartleby.com/141/">Elements of
146	Style</ulink>, by William Strunk.</para>	146	Style</ulink>, by William Strunk.</para>
147		147
148	<sect1>	148	<sect1>

Lines 96-101 Link Here

(-)en_US.ISO8859-1/books/handbook/Makefile (-2 / +11 lines)
96	IMAGES+= install/disk-layout.eps	96	IMAGES+= install/disk-layout.eps
97	IMAGES+= install/edit-inetd-conf.scr	97	IMAGES+= install/edit-inetd-conf.scr
98		98
		99	# Images from the cross-document image library
		100	IMAGES_LIB= callouts/1.png
		101	IMAGES_LIB+= callouts/2.png
		102	IMAGES_LIB+= callouts/3.png
		103	IMAGES_LIB+= callouts/4.png
		104	IMAGES_LIB+= callouts/5.png
		105
99	#	106	#
100	# SRCS lists the individual SGML files that make up the document. Changes	107	# SRCS lists the individual SGML files that make up the document. Changes
101	# to any of these files will force a rebuild	108	# to any of these files will force a rebuild
Lines 143-153 Link Here
143	# limits in pdftex. Until we split the Handbook up, build the PDF	150	# limits in pdftex. Until we split the Handbook up, build the PDF
144	# version using ps2pdf instead of pdftex.	151	# version using ps2pdf instead of pdftex.
145		152
		153	PS2PDF?= ${PREFIX}/bin/ps2pdf
		154
146	book.tex-pdf:	155	book.tex-pdf:
147	touch book.tex-pdf	156	${TOUCH} book.tex-pdf
148		157
149	book.pdf: book.ps	158	book.pdf: book.ps
150	ps2pdf book.ps book.pdf	159	${PS2PDF} book.ps book.pdf
151		160
152	pgpkeyring: pgpkeys/chapter.sgml	161	pgpkeyring: pgpkeys/chapter.sgml
153	@${JADE} -V nochunks ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC}	162	@${JADE} -V nochunks ${JADEOPTS} -d ${DSLPGP} -t sgml ${MASTERDOC}




	that do exist need to be updated.  If you are interested in helping
	with this project, send email to the &a.doc;.  The latest version of
	this document is always available from the <ulink
	  url="&url.top.level;/index.html">FreeBSD web site</ulink>.
	It may also be downloaded in a variety of formats and compression
	options from the <ulink 
          url="&url.ftp.server;/pub/FreeBSD/doc/">FreeBSD FTP 
          server</ulink> or one of the numerous <link
	  linkend="mirrors-ftp">mirror sites</link>.  If you would prefer
	  to have a hard copy of the handbook, you can purchase one at the
	  <ulink
	  url="http://www.freebsdmall.com/">FreeBSD Mall</ulink>.  You
	  may also want to <ulink
	  url="&url.top.level;/search/index.html">search the
	  handbook</ulink>.</para>
    </abstract>
  </bookinfo>




	  url="http://www.freebsd-support.de/i4b/">homepage of
	  isdn4bsd</ulink> which also has pointers to hints, erratas and
	much more documentation such as the <ulink
	  url="&url.people.server;/~hm/">isdn4bsd
	  handbook</ulink>.</para>

      <para>In case you are interested in adding support for a
	different ISDN protocol, a currently unsupported ISDN PC card or
	otherwise enhancing <application>isdn4bsd</application>, please
	get in touch with <email>hm@FreeBSD.org</email>.</para>

      <para>For questions regarding the installation, configuration
	and troubleshooting <application>isdn4bsd</application>, a

	serial card in your computer.</para>
	  
      <para>You should read the <ulink
	url="&url.top.articles;/serial-uart/index.html">FreeBSD Serial
	Hardware</ulink> tutorial for a detailed understanding of
	serial devices, and the differences between asynchronous and
	synchronous serial ports.</para>

      <para>The choice of sync/TA v.s. stand-alone router is largely a
	religious issue.  There has been some discussion of this in
	the mailing lists.  I suggest you search the <ulink
	url="&url.top.level;/search/index.html">archives</ulink> for
	the complete discussion.</para>
    </sect2>
    


      <para>
        Currently, BIND is maintained by the <ulink 
        url="http://www.isc.org/">
        Internet Software Consortium (www.isc.org)</ulink>
      </para>
    </sect2>


      <para>
        It is a good idea to subscribe to <ulink 
        url="http://www.cert.org/">CERT</ulink> and
        <ulink url="&url.top.books;/handbook/eresources.html#ERESOURCES-MAIL">freebsd-announce</ulink>
        to stay up to date with the current Internet and FreeBSD security 
        issues.
      </para>




    <itemizedlist>
      <listitem>
	<para><ulink
	    url="http://jdli.tw.FreeBSD.org/publication/book/freebsd2/index.htm">Using FreeBSD</ulink> (in Chinese).</para>
      </listitem>
      
      <listitem>

      </listitem>

      <listitem>
	<para><ulink url="http://www.freebsd-corp-net-guide.com/">The
	  FreeBSD Corporate Networker's Guide</ulink>, published by
	  <ulink url="http://www.awl.com/aw/">Addison-Wesley</ulink>.</para>
      </listitem>

      
      <listitem>
	<para><emphasis>The BSD family tree</emphasis>.  1997.  <ulink
	    url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree">&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree</ulink> or <ulink url="file:/usr/share/misc/bsd-family-tree">local</ulink> on a FreeBSD-current machine.</para>
      </listitem>
      
      <listitem>





      <indexterm><primary>problem reports database</primary></indexterm>
      <para>The <ulink
	  url="&url.cgi.server;/cgi/query-pr-summary.cgi">FreeBSD PR
	  list</ulink> shows all the current active problem reports and
	requests for enhancement that have been submitted by FreeBSD users.
	Look through the open PRs, and see if anything there takes your

	  
      <para>If you find a bug or are submitting a specific change, please
	report it using the &man.send-pr.1; program or its <ulink
	  url="&url.top.level;/send-pr.html">WEB-based
	  equivalent</ulink>.  Try to fill-in each field of the bug report.
	Unless they exceed 65KB, include any patches directly in the report.
	If the patch is suitable to be applied to the source tree put

	because cut-and-paste turns tabs into spaces and makes them unusable.
	Consider compressing patches and using &man.uuencode.1; if they exceed
	20KB.  Upload very large submissions to <ulink
	  url="&url.ftp.server;/pub/FreeBSD/incoming/">&url.ftp.server;/pub/FreeBSD/incoming/</ulink>.</para>
	  
      <para>After filing a report, you should receive confirmation along with
	a tracking number.  Keep this tracking number so that you can update


	<para>More information about the FreeBSD Foundation can be
	  found in <ulink
	  url="&url.people.server;/~jdp/foundation/announcement.html">The
	  FreeBSD Foundation -- an Introduction</ulink>.  To contact
	  the Foundation by email, write to
	  <email>bod@FreeBSDFoundation.org</email>.</para>




	      <listitem>
		<para>Use the <link linkend="cvsup">cvsup</link> program
		  with <ulink
		  url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this
		  supfile</ulink>.  This is the second most recommended
		  method, since it allows  you to grab the entire
		  collection once and then only what has changed from then

		  sources up-to-date automatically.  For a fairly easy
		  interface to this, simply type:</para>

		<blockquote><screen>&prompt.root; <userinput>pkg_add -f &url.ftp.server;/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></screen></blockquote>
	      </listitem>
              <indexterm>
	        <primary>-CURRENT</primary>

		<para>Use <command>ftp</command>.  The source tree for
		  &os.current; is always <quote>exported</quote> on:
		  <ulink
		  url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/">&url.ftp.server;/pub/FreeBSD/FreeBSD-current/</ulink>.
		  Our FTP server also allows
		  compressed/tarred grabbing of whole trees.  e.g. you
		  see:</para>

  	    support them for many years.  For a complete description
  	    of the current security policy for old releases of
  	    FreeBSD, please see <ulink
  	    url="&url.top.level;/security/index.html">&url.home.page;/security/</ulink></para>
	  </footnote>
	  , and tracking an entire development branch just
	  for security reasons is likely to bring in a lot of unwanted

	      <listitem>
		<para>Use the <link linkend="cvsup">cvsup</link> program
		  with <ulink
		  url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/stable-supfile">this
		  supfile</ulink>.  This is the second most recommended
		  method, since it allows  you to grab the entire
		  collection once and then only what has changed from then

		  sources up-to-date automatically.  For a fairly easy
		  interface to this, simply type:</para>
	      
		<blockquote><screen>&prompt.root; <userinput>pkg_add -f &url.ftp.server;/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></screen></blockquote>
	      </listitem>

	      <indexterm>

		<para>Use <command>ftp</command>.  The source tree for
		  &os.stable; is always <quote>exported</quote> on:
		  <ulink
		  url="&url.ftp.server;/pub/FreeBSD/FreeBSD-stable/">&url.ftp.server;/pub/FreeBSD/FreeBSD-stable/</ulink></para>

		<para>Our FTP server also allows
		  compressed/tarred grabbing of whole trees.  e.g. you

Lines 998-1004 Link Here

(-)en_US.ISO8859-1/books/handbook/disks/chapter.sgml (-1 / +1 lines)
998		998
999	<para>The next consideration was how to attach them as part of	999	<para>The next consideration was how to attach them as part of
1000	the filesystem. I did a little research on <ulink	1000	the filesystem. I did a little research on <ulink
1001	url="http://www.vinumvm.org">&man.vinum.8;</ulink> and FreeBSD's	1001	url="http://www.vinumvm.org/">&man.vinum.8;</ulink> and FreeBSD's
1002	&man.ccd.4;. In this particular configuration, &man.ccd.4;	1002	&man.ccd.4;. In this particular configuration, &man.ccd.4;
1003	appeared to be a better choice mainly because it has fewer	1003	appeared to be a better choice mainly because it has fewer
1004	parts. Less parts tends to indicate less chance of breakage.	1004	parts. Less parts tends to indicate less chance of breakage.




      the project.</para>

    <para>Archives are kept for all of the mailing lists and can be searched
      using the <ulink url="&url.top.level;/search/index.html">FreeBSD World
	Wide Web server</ulink>.  The keyword searchable archive offers an
      excellent way of finding answers to frequently asked questions and
      should be consulted before posting a question.</para>


	    <row>
	      <entry>freebsd-www</entry>
	      <entry>Maintainers of <ulink url="&url.top.level;/index.html">www.FreeBSD.org</ulink></entry>
	    </row>
	  </tbody>
	</tgroup>

	      touch a part of the system where a bug may adversely affect
	      the integrity of the system.</para>

<!-- I can't actually find a charter for this, but there's this email: &url.cgi.server;/cgi/getmsg.cgi?fetch=223347+225804+/usr/local/www/db/text/2000/cvs-all/20001210.cvs-all -->
	  </listitem>
	</varlistentry>


	      Whenever possible, bugs should be submitted using the
		&man.send-pr.1;
	      command or the <ulink
		url="&url.top.level;/send-pr.html">WEB
		interface</ulink> to it.</para>
	  </listitem>
	</varlistentry>

    <itemizedlist>
      <listitem>
	<para><ulink
	    url="&url.top.level;/index.html">&url.home.page;/</ulink>
	  &mdash; Central Server.</para>
      </listitem>
      




      <para>Information about all the releases, including the errata for each
	release, can be found on the 
	<ulink
	url="&url.top.level;/releases/index.html">release
	information</ulink> section of the 
	<ulink
	  url="&url.top.level;/index.html">FreeBSD web site</ulink>.</para>
    </sect2>

    <sect2 id="install-floppies">

	  <para>The boot discs are available on your installation media
	    in the floppies directory, and
	    can also be downloaded from the <ulink
	    url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">
	      floppies directory</ulink>.</para>

	  <para>The floppy images have a <filename>.flp</filename> extension.

	    Adjust the command line as necessary, depending on where you have
	    placed the <filename>.flp</filename> files.  If you do not have
	    the CDROM, then <command>fdimage</command> can be downloaded from
	    the <ulink url="&url.ftp.server;/pub/FreeBSD/tools/"><filename>tools</filename> directory</ulink> on the FreeBSD FTP site.</para>
	  
	  <para>If you are writing the floppies on a Unix system (such as
	    another FreeBSD system) you can use the &man.dd.1; command to

BIOS drive C: is disk3
BIOS 639kB/64512kB available memory
FreeBSD/i386 bootstrap loader, Revision 0.8
(jkh@bento.FreeBSD.org, Mon Nov 20 11:41:23 GMT 2000)
|
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel] in 9 seconds... _</screen>


 For more information on the ports collection & the latest ports,
 visit: 
     http://www.FreeBSD.org/ports  

                              [ Yes ]     No</screen>



      <para>For detailed information on Local Area Networks and
	configuring FreeBSD as a gateway/router refer to the tutorial
	<ulink url="&url.top.books;/ppp-primer/index.html">
	PPP- Pendantic PPP Primer</ulink>.</para>

      <screen>                      User Confirmation Requested 


      <para>More information about security profiles can be found in the
	<ulink
	url="&url.top.books;/faq/install.html#SECURITY-PROFILES">
	  FreeBSD FAQ</ulink>.</para>

      <screen>                       User Confirmation Requested

            read input from a local keyboard.  Enough of that now,
            let's get back to getting these disk images.</para>

	  <para>You will need to get <ulink url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/kern.flp">kern.flp</ulink> and
            <ulink url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/mfsroot.flp">
            mfsroot.flp</ulink> from the
            <ulink url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">
            floppies directory</ulink>.</para>

        </step>

	    placed the <filename>.flp</filename> files.  If you do not
	    have the CDROM then <command>fdimage</command> can be
	    downloaded from the <ulink
	    url="&url.ftp.server;/pub/FreeBSD/tools/"><filename>tools</filename>
	    directory</ulink> on the FreeBSD FTP site.</para>

	  <para>If you are writing the floppies on a Unix system (such

	
	<para>If you do not have a CDROM drive, you can download the
	distribution from <ulink
	url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">
	ftp.FreeBSD.org</ulink>. Each distribution is in its own directory; 
	for example, the <emphasis>bin</emphasis> distribution can be 
	found in the <ulink
	url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/bin/">&rel.current;/bin/</ulink> directory.</para>
    
	<para>For as many distributions you wish to install from an MS-DOS
	  partition (and you have the free space for), install each one

	  specific to your modem, as the PPP dialer provides only a very
	  simple terminal emulator. Please refer
	  to the user-ppp <link linkend="userppp">handbook</link> and <ulink
	  url="&url.top.books;/faq/ppp.html">FAQ</ulink> entries for further
	  information.  If you have problems, logging can be directed to
	  the screen using the command <command>set log local
	  ...</command>.</para>




      read about <link linkend="history">the history of FreeBSD</link>,
      or the <link linkend="relnotes">current release</link>.  If you
      are interested in contributing something to the Project (code,
      hardware, unmarked bills), see the <ulink
	url="&url.top.articles;/contributing/index.html">Contributing to FreeBSD</ulink> article.</para>

    <sect2>
      <title>What Can FreeBSD Do?</title>

      <para>Long-term development projects continue to take place in the
	5.0-CURRENT (trunk) branch, and SNAPshot releases of 5.0 on
	CDROM (and, of course, on the net) are continually made available
	from <ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">
	the snapshot server</ulink> as work progresses.</para>
    </sect2>
      

	process, FreeBSD being literally built from the contributions
	of hundreds of people around the world, as can be seen from
	our our <ulink
	url="&url.top.articles;/contributors/article.html">list of
	contributors</ulink>.  We are constantly on the lookout for
	new developers and ideas, and those interested in becoming
	more closely involved with the project need simply contact us

	  </indexterm>
	  <listitem>
	    <para>The central source tree for FreeBSD is maintained by
	      <ulink url="http://www.cvshome.org/">CVS</ulink>
	      (Concurrent Versions System), a freely available source code
	      control tool that comes bundled with FreeBSD.  The primary
	      <ulink url="&url.cgi.server;/cgi/cvsweb.cgi">CVS
	      repository</ulink> resides on a machine in Santa Clara CA, USA
	      from where it is replicated to numerous mirror machines
	      throughout the world.  The CVS tree, as well as the <link

	      ensuring that some large portion of the system works as
	      advertised.  For a complete list of FreeBSD developers
	      and their areas of responsibility, please see the <ulink
	      url="&url.top.articles;/contributors/article.html">Contributors
	      List</ulink></para>

	    <note>

	      such things are discussed.</para>
	  
	    <para><citetitle><ulink
	      url="&url.top.articles;/contributors/article.html">The
	      FreeBSD Contributors List</ulink></citetitle> is a long
	      and growing one, so why not join it by contributing
	      something back to FreeBSD today?</para>

	    <para>Providing code is not the only way of contributing to
	      the project; for a more complete list of things that need
	      doing, please refer to the <ulink
	      url="&url.top.level;/index.html">FreeBSD Project web
	      site</ulink>.</para>
	  </listitem>
	</varlistentry>

    
      <para>You can also view the master (and most frequently updated)
        copies at <ulink
	url="&url.top.level;/index.html">&url.home.page;/</ulink>.</para>
    </sect2>
  </sect1>
</chapter>

Lines 421-427 Link Here

(-)en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml (-1 / +1 lines)
421	# For more information on this file, please read the handbook section on	421	# For more information on this file, please read the handbook section on
422	# Kernel Configuration Files:	422	# Kernel Configuration Files:
423	#	423	#
424	# http://www.freebsd.org/handbook/kernelconfig-config.html	424	# http://www.FreeBSD.org/handbook/kernelconfig-config.html
425	#	425	#
426	# The handbook is also available locally in /usr/share/doc/handbook	426	# The handbook is also available locally in /usr/share/doc/handbook
427	# if you've installed the doc distribution, otherwise always see the	427	# if you've installed the doc distribution, otherwise always see the




	implementation, users may be required to compile an application
	with wide or multibyte characters support, or configure it correctly.
	To be able to input and process wide or multibyte characters, the <ulink 
	url="&url.top.level;/ports/index.html">FreeBSD Ports collection</ulink> has provided
	each language with different programs.  Refer to the I18N
	documentation in the respective FreeBSD Port.</para>


      <title>Traditional Chinese Localization for Taiwan</title>
      <indexterm><primary>Traditional Chinese localization</primary></indexterm>
      <para>The FreeBSD-Taiwan Project has an I18N/L10N tutorial for
	FreeBSD at <ulink url="http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/">http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/</ulink>
	using many <port>chinese/*</port> applications.
	The editor for the <literal>zh-L10N-tut</literal> is Clive Lin
	<email>Clive@CirX.org</email>.  You can also cvsup the following


      <para>Some FreeBSD contributors have translated parts of FreeBSD to
	other languages.  They are available through links on the <ulink
	url="&url.top.level;/index.html">main site</ulink> or in
	<filename>/usr/share/doc</filename>.</para>
    </sect2>
  </sect1>





	<para>This is by far the easiest method to use when installing the
	  runtime libraries.  It is just like installing any other port
	  from the <ulink url="file://localhost/usr/ports/">ports collection</ulink>.
	  Simply do the following:</para>

	<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base</userinput>

      <sect3 id="install-via-ftp">
        <title>Installation via FTP</title> <para>Get the diskimages
        kern.flp and mfsroot.flp and put them on floppy disks (I got
        mine from ftp7.de.FreeBSD.org. Please choose the appropriate
        mirror).</para>

        <screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput> 

        are not out of date):</para>

      <itemizedlist>
        <listitem><para>ftp7.de.FreeBSD.org/pub/FreeBSD/distfiles/rpm</para></listitem>
        <listitem><para>ftp.redhat.com/pub/redhat/linux/6.1/en/os/i386/RedHat/RPMS</para></listitem>
      </itemizedlist>


Lines 174-180 Link Here

(-)en_US.ISO8859-1/books/handbook/mail/chapter.sgml (-1 / +1 lines)
174	<procedure>	174	<procedure>
175	<step>	175	<step>
176	<para>Get a POP or IMAP daemon from the <ulink	176	<para>Get a POP or IMAP daemon from the <ulink
177	url="/ports/mail.html">ports collection</ulink> and install	177	url="&url.top.level;/ports/mail.html">ports collection</ulink> and install
178	it on your system.</para>	178	it on your system.</para>
179	</step>	179	</step>
180		180





      <blockquote>
	<para><ulink
	    url="&url.ftp.server;/pub/FreeBSD/">&url.ftp.server;/pub/FreeBSD/</ulink>.</para>
      </blockquote></para>

    <para>The <ulink


	  <listitem>
	    <para><ulink
		url="&url.cgi.server;/cgi/cvsweb.cgi">CVSWeb</ulink> is
	      the FreeBSD Project web interface for CVS.</para>
	  </listitem>
	</itemizedlist>

	  directly from:</para>
	    
	<para><ulink
	  url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm/">&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm/</ulink></para>

	<para>The <quote>deltas</quote> you feed
	  <application>CTM</application> can be had two ways, FTP or

	  <application>CTM</application>:</para>

	<para><ulink
	  url="&url.ftp.server;/pub/FreeBSD/CTM/">&url.ftp.server;/pub/FreeBSD/CTM/</ulink></para>

	<para>or see section <link
	  linkend="mirrors-ctm">mirrors</link>.</para>

	  <itemizedlist>
	    <listitem>
	      <para><ulink
		  url="&url.ftp.server;/pub/FreeBSD/development/CTM/">&url.ftp.server;/pub/FreeBSD/development/CTM/</ulink></para>
	    </listitem>
	  </itemizedlist>
	</listitem>

    <para>If you did not find a mirror near to you or the mirror is
      incomplete, try  <ulink url="http://ftpsearch.ntnu.no/">FTP
	search</ulink> at <ulink
	url="http://ftpsearch.ntnu.no/ftpsearch/">http://ftpsearch.ntnu.no/ftpsearch/</ulink>.
      FTP search is a great free archie server in Trondheim, Norway.</para>
  </sect2></sect1>


	single package which will install it, set up the configuration
	file and start the transfer via a pointy-clicky type of
	interface, then get the <ulink
	  url="&url.ftp.server;/pub/FreeBSD/development/CVSup/cvsupit.tgz">cvsupit</ulink>
	package.  Just hand it to &man.pkg.add.1; and it will lead you
	through the configuration process in a menu-oriented
	fashion.</para>


	    <listitem>
	      <para>cvsup2.ca.FreeBSD.org (maintainer
		<email>hostmaster@ca.FreeBSD.org</email>)</para>
	    </listitem>
	  </itemizedlist>
	</listitem>


	    <listitem>
	      <para>cvsup5.de.FreeBSD.org (maintainer
		<email>rse@FreeBSD.org</email>)</para>
	    </listitem>
	  </itemizedlist>
	</listitem>

	  <itemizedlist>
	    <listitem>
	      <para>cvsup.tw.FreeBSD.org (maintainer
		<email>jdli@FreeBSD.csie.nctu.edu.tw</email>)</para>
	    </listitem>

	    <listitem>

Lines 11-17 Link Here

(-)en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml (-1 / +1 lines)
11	<para>In case you need to verify a signature or send encrypted email	11	<para>In case you need to verify a signature or send encrypted email
12	to one of the officers or developers a number of keys are provided	12	to one of the officers or developers a number of keys are provided
13	here for your convenience. A complete keyring of FreeBSD.org	13	here for your convenience. A complete keyring of FreeBSD.org
14	users is available for download from <ulink url="http://www.FreeBSD.org/doc/pgpkeyring.txt">http://www.FreeBSD.org/doc/pgpkeyring.txt</ulink>.</para>	14	users is available for download from <ulink url="&url.top.level;/doc/pgpkeyring.txt">&url.home.page;/doc/pgpkeyring.txt</ulink>.</para>
15		15
16	<sect1 id="pgpkeys-officers">	16	<sect1 id="pgpkeys-officers">
17	<title>Officers</title>	17	<title>Officers</title>




    </itemizedlist>

    <para>To keep track of updated ports, subscribe to the
      <email>freebsd-ports@FreeBSD.org</email> mailing list.</para>

    <para>The remainder of this chapter will explain how to use packages and
      ports to install and manage third party software on FreeBSD.</para>

      <listitem>
	<para>The FreeBSD web site maintains an up-to-date searchable list of
	  all the available applications, at
	  <ulink url="&url.top.level;/ports/index.html">&url.home.page;/ports/</ulink>.
	  The name space is divided in to categories, and you may either
	  search for an application by name (if you know it), or you can list
	  all the applications available in a category.</para>

      <example>
        <title>Downloading a Package and then Installing It Locally</title>

        <screen>&prompt.root; <userinput>ftp -a <replaceable>ftp2.FreeBSD.org</replaceable></userinput>
Connected to ftp2.FreeBSD.org.
220 ftp2.FreeBSD.org FTP server (Version 6.00LS) ready.
331 Guest login ok, send your email address as password.
230-
230-     This machine is in Vienna, VA, USA, hosted by Verio.


      <para>Package files are distributed in .tgz format.  You can
          find them at <ulink
          url="&url.ftp.server;/pub/FreeBSD/ports/packages/">
          &url.ftp.server;/pub/FreeBSD/ports/packages/</ulink>,
          or on the FreeBSD CDROM distribution.  Every CD on the
          FreeBSD 4-CD set (and PowerPak, etc) contains packages in
          the <filename>/packages</filename> directory.  The layout of

      <para>Before we get into that however, you will need to choose a
        port to install.  There are a few ways to do this, with the
	easiest method being the <ulink
	url="&url.top.level;/ports/index.html">ports listing on the FreeBSD
	web site</ulink>.  You can browse through the ports listed there
	or use the search function on the site.  Each port also includes
	a description so you can read a bit about each port before


        <screen>&prompt.root; <userinput>make install</userinput>
&gt;&gt; lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
&gt;&gt; Attempting to fetch from &url.ftp.server;/pub/FreeBSD/ports/distfiles/.
Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
439860 bytes transferred in 18.0 seconds (23.90 kBps)
===&gt;  Extracting for lsof-4.57


	  <screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
&prompt.root; <userinput>make MASTER_SITE_OVERRIDE= \
&url.ftp.server;/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
	  </answer>
	</qandaentry>


      <orderedlist>
        <listitem>
	  <para>Fix it!  The <ulink
	    url="&url.top.books;/porters-handbook/index.html">Porter's
	    Handbook</ulink> includes detailed information on the
	    "Ports" infrastructure so that you can fix the occasional
	    broken port or even submit your own!</para>

	  <para>Grab the package from an ftp site near you.  The
	    <quote>master</quote> package collection is on <hostid
	    role="fqdn">ftp.FreeBSD.org</hostid> in the <ulink
	    URL="&url.ftp.server;/pub/FreeBSD/ports/packages/">packages
	    directory</ulink>, but be sure to check your local mirror
	    <emphasis>first!</emphasis>  These are more likely to work
	    than trying to compile from source and are a lot faster as

Lines 2346-2352 Link Here

(-)en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml (-1 / +1 lines)
2346	system for this yet, please see the tutorial for configuring	2346	system for this yet, please see the tutorial for configuring
2347	dialup services; if you have a World-Wide Web browser available,	2347	dialup services; if you have a World-Wide Web browser available,
2348	browse the list of tutorials at <ulink	2348	browse the list of tutorials at <ulink
2349	url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>.	2349	url="&url.top.level;/index.html">&url.home.page;/</ulink>.
2350	You may also want to check the manual pages for &man.sio.4; for	2350	You may also want to check the manual pages for &man.sio.4; for
2351	information on the serial port device driver and &man.ttys.5;,	2351	information on the serial port device driver and &man.ttys.5;,
2352	&man.gettytab.5;, &man.getty.8;, & &man.init.8; for	2352	&man.gettytab.5;, &man.getty.8;, & &man.init.8; for

Lines 2717-2723 Link Here

(-)en_US.ISO8859-1/books/handbook/security/chapter.sgml (-2 / +2 lines)
2717	layer and socket layer communication. This section should	2717	layer and socket layer communication. This section should
2718	explain how to use them. For implementation details, please	2718	explain how to use them. For implementation details, please
2719	refer to <ulink	2719	refer to <ulink
2720	url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/ipv6.html">The	2720	url="&url.top.books;/developers-handbook/ipv6.html">The
2721	Developers' Handbook</ulink>.</para>	2721	Developers' Handbook</ulink>.</para>
2722		2722
2723	<para>The current IPsec implementation supports both transport mode	2723	<para>The current IPsec implementation supports both transport mode
Lines 3382-3388 Link Here
3382		3382
3383	<sect2>	3383	<sect2>
3384	<title>Further Reading</title>	3384	<title>Further Reading</title>
3385	<para><ulink url="http://www.openssh.com">OpenSSH</ulink></para>	3385	<para><ulink url="http://www.openssh.com/">OpenSSH</ulink></para>
3386	<para>&man.ssh.1; &man.scp.1; &man.ssh-keygen.1;	3386	<para>&man.ssh.1; &man.scp.1; &man.ssh-keygen.1;
3387	&man.ssh-agent.1; &man.ssh-add.1;</para>	3387	&man.ssh-agent.1; &man.ssh-add.1;</para>
3388	<para>&man.sshd.8; &man.sftp-server.8;</para>	3388	<para>&man.sshd.8; &man.sftp-server.8;</para>

Lines 2035-2041 Link Here

(-)en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml (-1 / +1 lines)
2035	use as the serial console. The only use of this	2035	use as the serial console. The only use of this
2036	flag is to designate the unit for kernel remote	2036	flag is to designate the unit for kernel remote
2037	debugging. See <ulink	2037	debugging. See <ulink
2038	url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/developers-handbook/">The	2038	url="&url.top.books;/developers-handbook/index.html">The
2039	Developer's Handbook</ulink> for more information on	2039	Developer's Handbook</ulink> for more information on
2040	remote debugging.</para>	2040	remote debugging.</para>
2041		2041




          directory or the <filename>pkgname.tgz</filename> package, so delete
          them now.  Next, simply include the output of <command>shar `find
            port_dir`</command> in a bug report and send it with the
            &man.send-pr.1; program (see <ulink url="&url.top.articles;/contributing/contrib-how.html#CONTRIB-GENERAL">Bug
            Reports and General Commentary</ulink> for more information about
            &man.send-pr.1;.  If the uncompressed port is larger than 20KB,
          you should compress it into a tarfile and use &man.uuencode.1;

              cannot find the required files in <makevar>DISTDIR</makevar> it
              will look up the URL <makevar>MASTER_SITES</makevar>, which is
              set in the Makefile, as well as our main FTP site at <ulink
                url="&url.ftp.server;/pub/FreeBSD/ports/distfiles/">&url.ftp.server;/pub/FreeBSD/ports/distfiles/</ulink>,
              where we put sanctioned distfiles as backup.  It will then
              attempt to fetch the named distribution file with
              <makevar>FETCH</makevar>, assuming that the requesting site has

          --><emphasis>:-)</emphasis></para>

        <para>For a detailed description of the responsibilities of maintainers,
          refer to the <ulink url="&url.top.books;/developers-handbook/policies.html#POLICIES-MAINTAINER">MAINTAINER on
            Makefiles</ulink> section.</para>
      </sect1>


    <chapter>
      <title>Shared library versions</title>

      <para>Please read our <ulink url="&url.top.books;/developers-handbook/policies-shlib.html">policy on
        shared library versioning</ulink> to understand what to do with
        shared library versions in general.  Do not blindly assume software
        authors know what they are doing; many of them do not.  It is very

        port.  You can find them in the
        <filename>ports/ports-current</filename> directory of the FTP mirror
        sites.  You may also use CVSup to keep your whole ports collection
        up-to-date, as described in <ulink url="&url.top.books;/handbook/synching.html#CVSUP-CONFIG">the Handbook</ulink>.</para>

      <para>The next step is to send a mail to the maintainer, if one is
        listed in the port's <filename>Makefile</filename>.  That person may

        the porting process.You should check your own port against this list,
        but you can also check ports in the PR database that others have
        submitted.  Submit any comments on ports you check as described in
        <ulink url="&url.top.articles;/contributing/contrib-how.html#CONTRIB-GENERAL">Bug Reports and General
          Commentary</ulink>.  Checking ports in the PR database will both make
        it faster for us to commit them, and prove that you know what you are
        doing.</para>

        <para>Do not write anything to files outside
          <makevar>WRKDIR</makevar>.  <makevar>WRKDIR</makevar> is the only
          place that is guaranteed to be writable during the port build (see
          <ulink url="&url.top.books;/handbook/ports-using.html#PORTS-CD">compiling ports from CDROM</ulink> for an
          example of building ports from a read-only tree).  If you need to
          modify one of the <filename>pkg-<replaceable>*</replaceable></filename>
          files, do so by <link

        &a.ports;.  Important changes to the way ports work will be announced
        there.  You can always find more detailed information on the latest
        changes by looking at <ulink
          url="&url.cgi.server;/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk"> the
          bsd.port.mk CVS log</ulink>.</para>
    </chapter>





</listitem>

<listitem>
<para>The IBM Network (<ulink URL="http://www.ibm.net/">http://www.ibm.net/</ulink>)</para>
</listitem>

<listitem>
<para>AT&amp;T WorldNet (<ulink URL="http://att.com/worldnet/">http://att.com/worldnet/</ulink>)</para>
</listitem>

<listitem>
<para>Erol's (<ulink URL="http://www.erols.com/">http://www.erols.com/</ulink>)</para>
</listitem>

</itemizedlist>

they need to be properly configured.  Note that this section does not
explain how to configure the Windows workstations for Dial-Up
networking.  If you need a good explanation of that procedure, I
recommend <ulink URL="http://www.aladdin.co.uk/techweb/">http://www.aladdin.co.uk/techweb/</ulink>.</para>
  

<sect1>

Configuration" and "Bindings" tabs are not necessary.</para>
  
<para>If you wish to use the Windows Internet Naming Service ("WINS")
your attention is invited to <ulink URL="http://www.localnet.org/">http://www.localnet.org/</ulink> for
more information about WINS settings, specifically regarding sharing
files transparently across the Internet.</para>
  

"Routing" tabs are not used.</para>
  
<para>If you wish to use the Windows Internet Naming Service ("WINS")
your attention is invited to <ulink URL="http://www.localnet.org/">http://www.localnet.org/</ulink> for
more information about WINS settings, specifically regarding sharing
files transparently across the Internet.</para>
  

requires that the Microsoft TCP/IP-32 driver diskette has been
installed on the workstation.  The TCP/IP drivers are not included
with the WfW CD or diskettes; if you need a copy they're available at
<ulink URL="ftp://ftp.microsoft.com/peropsys/windows/public/tcpip/">ftp://ftp.microsoft.com/peropsys/windows/public/tcpip/</ulink>.</para>
  
<para>Once the TCP/IP drivers have been loaded, perform the following
steps:</para>





CSS_SHEET?=	${DOC_PREFIX}/share/misc/docbook.css

TOPLEVEL?=	-1

PRINTOPTS?=    -ioutput.print

.if defined(BOOK_OUTPUT)

all: ${_docs}

index.html HTML.manifest: ${SRCS} ${LOCAL_IMAGES_LIB} ${IMAGES_PNG} ${INDEX_SGML} ${HTML_SPLIT_INDEX} docbook.css
	${JADE} -V html-manifest -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC}
.if !defined(NO_TIDY)
	-tidy -i -m -f /dev/null ${TIDYFLAGS} `xargs < HTML.manifest`
.endif

${DOC}.html: ${SRCS} ${LOCAL_IMAGES_LIB} ${IMAGES_PNG} ${INDEX_SGML} ${HTML_INDEX} docbook.css
	${JADE} -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > ${.TARGET} || (rm -f ${.TARGET} && false)
.if !defined(NO_TIDY)
	-tidy -i -m -f /dev/null ${TIDYFLAGS} ${.TARGET}
.endif

# Special target to produce HTML with no images in it.
${DOC}.html-text: ${SRCS} ${INDEX_SGML} ${HTML_INDEX}
	${JADE} -ioutput.html -iurl.top.level.${TOPLEVEL} -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > ${.TARGET} || (rm -f ${.TARGET} && false)

${DOC}.html-split.tar: HTML.manifest
	tar cf ${.TARGET} `xargs < HTML.manifest`

.endif

${HTML_INDEX}:
	${JADE} -V html-index -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > /dev/null
	perl ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -g -o ${INDEX_SGML} ${.TARGET}

${HTML_SPLIT_INDEX}:
	${JADE} -V html-index -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > /dev/null
	perl ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -g -o ${INDEX_SGML} ${.TARGET}

${PRINT_INDEX}: ${HTML_INDEX}




<!ENTITY prompt.root		"<prompt>#</prompt>">
<!ENTITY prompt.user		"<prompt>%</prompt>">

<!-- maybe the following entities should go in freebsd.ent ?
     in which case, it should be included w/in every book -->

<!ENTITY url.www.server         "http://www.FreeBSD.org">
<!ENTITY url.cgi.server         "&url.www.server;">
<!ENTITY url.stat.server        "&url.www.server;">
<!ENTITY url.docs.server        "http://docs.FreeBSD.org">
<!ENTITY url.people.server      "http://people.FreeBSD.org">
<!ENTITY url.ftp.server         "ftp://ftp.FreeBSD.org">

<![ %output.html.images; [
<!ENTITY % url.top.level.-1	"IGNORE">
<!ENTITY % url.top.level.0	"IGNORE">
<!ENTITY % url.top.level.1	"IGNORE">
<!ENTITY % url.top.level.2	"IGNORE">
<!ENTITY % url.top.level.3	"IGNORE">
<!ENTITY % url.top.level.4	"IGNORE">
<![ %url.top.level.0; [
<!ENTITY url.top.level		".">
]]>
<![ %url.top.level.1; [
<!ENTITY url.top.level		"..">
]]>
<![ %url.top.level.2; [
<!ENTITY url.top.level		"../..">
]]>
<![ %url.top.level.3; [
<!ENTITY url.top.level		"../../..">
]]>
<![ %url.top.level.4; [
<!ENTITY url.top.level		"../../../..">
]]>
]]>

<!ENTITY url.home.page		"&url.www.server;">

<!-- not % output.html -->
<!ENTITY url.top.level		"&url.home.page;">

<!-- where to find articles and books -->
<!ENTITY url.doc.enUS		"doc/en_US.ISO8859-1">
<!ENTITY url.www.articles	"&url.home.page;/&url.doc.enUS;/articles">
<!ENTITY url.www.books		"&url.home.page;/&url.doc.enUS;/books">
<!ENTITY url.top.articles	"&url.top.level;/&url.doc.enUS;/articles">
<!ENTITY url.top.books		"&url.top.level;/&url.doc.enUS;/books">




<!ENTITY prompt.root		"<prompt>#</prompt>">
<!ENTITY prompt.user		"<prompt>%</prompt>">

<!-- maybe the following entities should go in freebsd.ent ?
     in which case, it should be included w/in every book -->

<!ENTITY url.www.server         "http://www.FreeBSD.org">
<!ENTITY url.cgi.server         "&url.www.server;">
<!ENTITY url.stat.server        "&url.www.server;">
<!ENTITY url.docs.server        "http://docs.FreeBSD.org">
<!ENTITY url.people.server      "http://people.FreeBSD.org">
<!ENTITY url.ftp.server         "ftp://ftp.FreeBSD.org">

<![ %output.html.images; [
<!ENTITY % url.top.level.-1	"IGNORE">
<!ENTITY % url.top.level.0	"IGNORE">
<!ENTITY % url.top.level.1	"IGNORE">
<!ENTITY % url.top.level.2	"IGNORE">
<!ENTITY % url.top.level.3	"IGNORE">
<!ENTITY % url.top.level.4	"IGNORE">
<![ %url.top.level.0; [
<!ENTITY url.top.level		".">
]]>
<![ %url.top.level.1; [
<!ENTITY url.top.level		"..">
]]>
<![ %url.top.level.2; [
<!ENTITY url.top.level		"../..">
]]>
<![ %url.top.level.3; [
<!ENTITY url.top.level		"../../..">
]]>
<![ %url.top.level.4; [
<!ENTITY url.top.level		"../../../..">
]]>
]]>

<!ENTITY url.home.page		"&url.www.server;">

<!-- not % output.html -->
<!ENTITY url.top.level		"&url.home.page;">

<!-- where to find articles and books -->
<!ENTITY url.doc.enUS		"doc/en_US.ISO8859-1">
<!ENTITY url.www.articles	"&url.home.page;/&url.doc.enUS;/articles">
<!ENTITY url.www.books		"&url.home.page;/&url.doc.enUS;/books">
<!ENTITY url.top.articles	"&url.top.level;/&url.doc.enUS;/articles">
<!ENTITY url.top.books		"&url.top.level;/&url.doc.enUS;/books">




# requirements here.
#

TOPLEVEL?=	4

all:
	(unset DESTDIR || true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html TOPLEVEL=${TOPLEVEL} INSTALL_COMPRESSED= all)
	(unset DESTDIR || true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html TOPLEVEL=${TOPLEVEL} INSTALL_COMPRESSED= DOCDIR=${.CURDIR} install)
	(unset DESTDIR || true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1/books/handbook && ${MAKE} TOPLEVEL=${TOPLEVEL} pgpkeyring > ${.CURDIR}/pgpkeyring.txt)

install clean:
	(unset DESTDIR || true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html TOPLEVEL=${TOPLEVEL} INSTALL_COMPRESSED= DOCDIR=${DESTDIR}/data/doc ${.TARGET})
.if make(install)
	(unset DESTDIR || true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1/books/handbook && ${MAKE} TOPLEVEL=${TOPLEVEL} pgpkeyring > ${DESTDIR}/data/doc/pgpkeyring.txt)	
.endif
.if make(clean)
	rm -rf en* handbook faq pgpkeyring.txt

Return to bug 31447

Lines 158-164 Link Here

(-)en_US.ISO8859-1/articles/committers-guide/article.sgml (-12 / +12 lines)
158		158
159	<para>CVS reference information, tutorials, and FAQs can also be found at:	159	<para>CVS reference information, tutorials, and FAQs can also be found at:
160	<ulink	160	<ulink
161	url="http://www.cvshome.org/docs/index.html">http://www.cvshome.org/docs/index.html</ulink>,	161	url="http://www.cvshome.org/docs/">http://www.cvshome.org/docs/</ulink>,
162	and the information in <ulink url="http://cvsbook.red-bean.com/cvsbook.html">Karl Fogel's	162	and the information in <ulink url="http://cvsbook.red-bean.com/cvsbook.html">Karl Fogel's
163	chapters from <quote>Open Source Development with CVS</quote></ulink> are also very	163	chapters from <quote>Open Source Development with CVS</quote></ulink> are also very
164	useful.</para>	164	useful.</para>
Lines 766-772 Link Here
766	properly (tabs often look wrong in diffs because of the extra	766	properly (tabs often look wrong in diffs because of the extra
767	character in front of each line).</para>	767	character in front of each line).</para>
768		768
769	<para><ulink url="http://people.FreeBSD.org/~eivind/cdiff">http://people.FreeBSD.org/~eivind/cdiff</ulink></para>	769	<para><ulink url="&url.people.server;/~eivind/cdiff">&url.people.server;/~eivind/cdiff</ulink></para>
770		770
771	<para>Simply use it instead of &man.more.1; or &man.less.1;:</para>	771	<para>Simply use it instead of &man.more.1; or &man.less.1;:</para>
772		772
Lines 815-821 Link Here
815	<itemizedlist>	815	<itemizedlist>
816	<listitem>	816	<listitem>
817	<para>Add yourself to the <quote>Developers</quote> section of	817	<para>Add yourself to the <quote>Developers</quote> section of
818	the <ulink url="../contributors">Contributors List</ulink>	818	the <ulink url="&url.top.articles;/contributors/index.html">Contributors List</ulink>
819	and remove yourself from the <quote>Additional	819	and remove yourself from the <quote>Additional
820	Contributors</quote> section.</para>	820	Contributors</quote> section.</para>
821		821
Lines 832-838 Link Here
832		832
833	<listitem>	833	<listitem>
834	<para>If you have a PGP or GnuPG key, you may want to add it to	834	<para>If you have a PGP or GnuPG key, you may want to add it to
835	<filename>doc/en_US.ISO8859-1/books/handbook/pgpkeys</filename>.	835	<filename>&url.doc.enUS;/books/handbook/pgpkeys</filename>.
836	</para>	836	</para>
837	</listitem>	837	</listitem>
838		838
Lines 949-959 Link Here
949	</listitem>	949	</listitem>
950		950
951	<listitem>	951	<listitem>
952	<para><ulink url="http://www.FreeBSD.org/support.html">http://www.FreeBSD.org/support.html</ulink></para>	952	<para><ulink url="&url.top.level;/support.html">&url.home.page;/support.html</ulink></para>
953	</listitem>	953	</listitem>
954		954
955	<listitem>	955	<listitem>
956	<para><ulink url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink></para>	956	<para><ulink url="&url.top.level;/send-pr.html">&url.home.page;/send-pr.html</ulink></para>
957	</listitem>	957	</listitem>
958		958
959	<listitem>	959	<listitem>
Lines 1089-1095 Link Here
1089		1089
1090	<listitem>	1090	<listitem>
1091	<para>Nik oversees the	1091	<para>Nik oversees the
1092	<ulink url="http://www.FreeBSD.org/docproj/index.html">Doc. Project</ulink>.	1092	<ulink url="&url.top.level;/docproj/index.html">Doc. Project</ulink>.
1093	As well as writing documentation he put together the	1093	As well as writing documentation he put together the
1094	infrastructure under <filename>doc/share/mk</filename> and the	1094	infrastructure under <filename>doc/share/mk</filename> and the
1095	stylesheets and related code under	1095	stylesheets and related code under
Lines 1098-1104 Link Here
1098	<email>doc@FreeBSD.org</email> mailing list. Committers	1098	<email>doc@FreeBSD.org</email> mailing list. Committers
1099	interested in contributing to the documentation should familiarise	1099	interested in contributing to the documentation should familiarise
1100	themself with the	1100	themself with the
1101	<ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/fdp-primer/index.html">Documentation Project Primer</ulink>.</para>	1101	<ulink url="&url.top.books;/fdp-primer/index.html">Documentation Project Primer</ulink>.</para>
1102	</listitem>	1102	</listitem>
1103	</varlistentry>	1103	</varlistentry>
1104		1104
Lines 1526-1532 Link Here
1526	<filename>Makefile</filename> for any package or subtree	1526	<filename>Makefile</filename> for any package or subtree
1527	which is being actively maintained by one or more people;	1527	which is being actively maintained by one or more people;
1528	see <ulink	1528	see <ulink
1529	url="http://www.FreeBSD.org/handbook/policies.html">http://www.FreeBSD.org/handbook/policies.html</ulink>	1529	url="&url.top.books;/developers-handbook/policies.html">&url.home.page;/&url.doc.enUS;/books/developers-handbook/policies.html</ulink>
1530	for documentation on this. Where sections of code have	1530	for documentation on this. Where sections of code have
1531	several maintainers, commits to affected areas by one	1531	several maintainers, commits to affected areas by one
1532	maintainer need to be reviewed by at least one other	1532	maintainer need to be reviewed by at least one other
Lines 1540-1546 Link Here
1540	someone who manages an overall category of FreeBSD	1540	someone who manages an overall category of FreeBSD
1541	evolution, such as internationalization or networking.	1541	evolution, such as internationalization or networking.
1542	See <ulink	1542	See <ulink
1543	url="../contributors/staff-who.html">http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/staff-who.html</ulink> for more information on this.</para>	1543	url="&url.top.articles;/contributors/staff-who.html">&url.home.page;/&url.doc.enUS;/articles/contributors/staff-who.html</ulink> for more information on this.</para>
1544	</listitem>	1544	</listitem>
1545		1545
1546	<listitem>	1546	<listitem>
Lines 1814-1820 Link Here
1814	</screen>	1814	</screen>
1815		1815
1816	<para>The	1816	<para>The
1817	<ulink url="http://www.FreeBSD.org/porters-handbook/index.html">Porters	1817	<ulink url="&url.top.books;/porters-handbook/index.html">Porters
1818	Handbook</ulink> contains more detailed	1818	Handbook</ulink> contains more detailed
1819	instructions.</para>	1819	instructions.</para>
1820		1820
Lines 1825-1831 Link Here
1825	<para>If the port came from a submitter who has not	1825	<para>If the port came from a submitter who has not
1826	contributed to the project before, add that person's	1826	contributed to the project before, add that person's
1827	name to the <ulink	1827	name to the <ulink
1828	url="../contributors/contrib-additional.html">Additional	1828	url="&url.top.articles;/contributors/contrib-additional.html">Additional
1829	Contributors</ulink> section of the FreeBSD Contributors	1829	Contributors</ulink> section of the FreeBSD Contributors
1830	List.</para>	1830	List.</para>
1831		1831

Lines 259-265 Link Here

(-)en_US.ISO8859-1/articles/contributors/article.sgml (-7 / +7 lines)
259	<listitem>	259	<listitem>
260	<para><ulink url="http://www.osd.bsdi.com/">BSDi</ulink> (formerly Walnut Creek CDROM)	260	<para><ulink url="http://www.osd.bsdi.com/">BSDi</ulink> (formerly Walnut Creek CDROM)
261	has donated almost more than we can say (see the History	261	has donated almost more than we can say (see the History
262	section of the <ulink url="/handbook">FreeBSD Handbook</ulink> for more details).	262	section of the <ulink url="&url.top.books;/handbook/index.html">FreeBSD Handbook</ulink> for more details).
263	In particular, we would like to thank them for the original	263	In particular, we would like to thank them for the original
264	hardware used for <hostid	264	hardware used for <hostid
265	role="fqdn">freefall.FreeBSD.org</hostid>, our primary	265	role="fqdn">freefall.FreeBSD.org</hostid>, our primary
Lines 1478-1484 Link Here
1478		1478
1479	<title>The FreeBSD Documentation Project</title>	1479	<title>The FreeBSD Documentation Project</title>
1480		1480
1481	<para>The <ulink url="http://www.FreeBSD.org/docproj/docproj.html">FreeBSD	1481	<para>The <ulink url="&url.top.level;/docproj/index.html">FreeBSD
1482	Documentation Project</ulink> is responsible for a number of different	1482	Documentation Project</ulink> is responsible for a number of different
1483	services, each service being run by an individual and his	1483	services, each service being run by an individual and his
1484	<emphasis>deputies</emphasis> (if any):</para>	1484	<emphasis>deputies</emphasis> (if any):</para>
Lines 1605-1611 Link Here
1605	<variablelist>	1605	<variablelist>
1606	<varlistentry>	1606	<varlistentry>
1607	<term><ulink	1607	<term><ulink
1608	url="http://www.FreeBSD.org/docproj/docproj.html">Documentation	1608	url="&url.top.level;/docproj/index.html">Documentation
1609	Project Manager</ulink></term>	1609	Project Manager</ulink></term>
1610		1610
1611	<listitem>	1611	<listitem>
Lines 1663-1669 Link Here
1663	</varlistentry>	1663	</varlistentry>
1664		1664
1665	<varlistentry>	1665	<varlistentry>
1666	<term><ulink url="http://www.FreeBSD.org/security/">Security	1666	<term><ulink url="&url.top.level;/security/index.html">Security
1667	Officer</ulink></term>	1667	Officer</ulink></term>
1668		1668
1669	<listitem>	1669	<listitem>
Lines 1672-1678 Link Here
1672	</varlistentry>	1672	</varlistentry>
1673		1673
1674	<varlistentry>	1674	<varlistentry>
1675	<term><ulink url="http://www.FreeBSD.org/support.html#cvs">Source	1675	<term><ulink url="&url.top.level;/support.html#cvs">Source
1676	Repository Managers</ulink></term>	1676	Repository Managers</ulink></term>
1677		1677
1678	<listitem>	1678	<listitem>
Lines 1683-1689 Link Here
1683	</varlistentry>	1683	</varlistentry>
1684		1684
1685	<varlistentry>	1685	<varlistentry>
1686	<term><ulink url="http://www.FreeBSD.org/ports/">Ports	1686	<term><ulink url="&url.top.level;/ports/index.html">Ports
1687	Manager</ulink></term>	1687	Manager</ulink></term>
1688		1688
1689	<listitem>	1689	<listitem>
Lines 1708-1714 Link Here
1708	</varlistentry>	1708	</varlistentry>
1709		1709
1710	<varlistentry>	1710	<varlistentry>
1711	<term><ulink url="http://www.FreeBSD.org/support.html#gnats">GNATS	1711	<term><ulink url="&url.top.level;/support.html#gnats">GNATS
1712	Administrator</ulink></term>	1712	Administrator</ulink></term>
1713		1713
1714	<listitem>	1714	<listitem>

Lines 24-30 Link Here

(-)en_US.ISO8859-1/articles/fonts/article.sgml (-9 / +9 lines)
24		24
25	<!-- The section "Setting a virtual console to 80x60 line mode" was	25	<!-- The section "Setting a virtual console to 80x60 line mode" was
26	updated to reflect changes in FreeBSD system configuration	26	updated to reflect changes in FreeBSD system configuration
27	files by Mark Ovens <mark@ukug.uk.freebsd.org> 27/5/00	27	files by Mark Ovens <mark@ukug.uk.FreeBSD.org> 27/5/00
28	-->	28	-->
29		29
30	<article>	30	<article>
Lines 662-668 Link Here
662	metric (<filename>.afm</filename>) file.</para>	662	metric (<filename>.afm</filename>) file.</para>
663		663
664	<para>Currently available at <ulink	664	<para>Currently available at <ulink
665	url="http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/">http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf</ulink>.	665	url="http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/">http://sunsite.icm.edu.pl/pub/GUST/contrib/BachoTeX98/ttf2pf/</ulink>.
666	Note: These files are postscript programs and must be	666	Note: These files are postscript programs and must be
667	downloaded to disk by holding down the	667	downloaded to disk by holding down the
668	<keycap>Shift</keycap> key when clicking on the link.	668	<keycap>Shift</keycap> key when clicking on the link.
Lines 850-856 Link Here
850	<listitem>	850	<listitem>
851	<para>The freetype module is included with XFree86 4.x. For	851	<para>The freetype module is included with XFree86 4.x. For
852	more information please see the <ulink	852	more information please see the <ulink
853	url="http://www.freebsd.org/handbook/x-fonts.html">FreeBSD	853	url="&url.top.books;/handbook/x-fonts.html">FreeBSD
854	Handbook</ulink> or the <ulink	854	Handbook</ulink> or the <ulink
855	url="http://www.xfree86.org/4.0.2/fonts.html">XFree86 4.0.2	855	url="http://www.xfree86.org/4.0.2/fonts.html">XFree86 4.0.2
856	Fonts</ulink> page.</para>	856	Fonts</ulink> page.</para>
Lines 871-885 Link Here
871	<listitem>	871	<listitem>
872	<para><command>xfstt</command> is another font server for X11,	872	<para><command>xfstt</command> is another font server for X11,
873	available under <ulink url="	873	available under <ulink url="
874	ftp://sunsite.unc.edu/pub/Linux/X11/fonts">	874	ftp://sunsite.unc.edu/pub/Linux/X11/fonts/">
875	ftp://sunsite.unc.edu/pub/Linux/X11/fonts</ulink>.</para>	875	ftp://sunsite.unc.edu/pub/Linux/X11/fonts/</ulink>.</para>
876	</listitem>	876	</listitem>
877		877
878	<listitem>	878	<listitem>
879	<para>A program called <command>ttf2bdf</command> can produce	879	<para>A program called <command>ttf2bdf</command> can produce
880	BDF files suitable for use in an X environment from TrueType	880	BDF files suitable for use in an X environment from TrueType
881	files. Linux binaries are said to be available from <ulink	881	files. Linux binaries are said to be available from <ulink
882	url="ftp://crl.nmsu.edu/CLR/multiling/General">ftp://crl.nmsu.edu/CLR/multiling/General/</ulink>.</para>	882	url="ftp://crl.nmsu.edu/CLR/multiling/General/">ftp://crl.nmsu.edu/CLR/multiling/General/</ulink>.</para>
883	</listitem>	883	</listitem>
884		884
885	<listitem>	885	<listitem>
Lines 912-918 Link Here
912	<itemizedlist>	912	<itemizedlist>
913	<listitem>	913	<listitem>
914	<para><ulink	914	<para><ulink
915	url="ftp://ftp.winsite.com">ftp://ftp.winsite.com</ulink>	915	url="ftp://ftp.winsite.com/">ftp://ftp.winsite.com/</ulink>
916	(Formerly CICA)</para>	916	(Formerly CICA)</para>
917	</listitem>	917	</listitem>
918		918
Lines 928-939 Link Here
928		928
929	<listitem>	929	<listitem>
930	<para><ulink	930	<para><ulink
931	url="http://af-pc-plloyd.ecel.uwa.edu.au/fonts/index.html">http://af-pc-plloyd.ecel.uwa.edu.au/fonts/index.html</ulink></para>	931	url="http://af-pc-plloyd.ecel.uwa.edu.au/fonts/">http://af-pc-plloyd.ecel.uwa.edu.au/fonts/</ulink></para>
932	</listitem>	932	</listitem>
933		933
934	<listitem>	934	<listitem>
935	<para><ulink	935	<para><ulink
936	url="http://www.esselte.com/letraset/index.html">http://www.esselte.com/letraset/index.html</ulink></para>	936	url="http://www.esselte.com/letraset/">http://www.esselte.com/letraset/</ulink></para>
937	</listitem>	937	</listitem>
938		938
939	<listitem>	939	<listitem>

Lines 249-255 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml (-5 / +5 lines)
249		249
250	<listitem>	250	<listitem>
251	<para>Any encumbered file requires specific approval from the	251	<para>Any encumbered file requires specific approval from the
252	<ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-core.html">Core team</ulink> before it is added to the	252	<ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> before it is added to the
253	CVS repository.</para>	253	CVS repository.</para>
254	</listitem>	254	</listitem>
255		255
Lines 280-288 Link Here
280		280
281	<listitem>	281	<listitem>
282	<para>Should always be in <filename>LINT</filename>, but the	282	<para>Should always be in <filename>LINT</filename>, but the
283	<ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-core.html">Core team</ulink> decides per case if it	283	<ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> decides per case if it
284	should be commented out or not. The	284	should be commented out or not. The
285	<ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-core.html">Core team</ulink> can, of course, change	285	<ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> can, of course, change
286	their minds later on.</para>	286	their minds later on.</para>
287	</listitem>	287	</listitem>
288		288
Lines 299-311 Link Here
299	<orderedlist>	299	<orderedlist>
300	<listitem>	300	<listitem>
301	<indexterm><primary>core team</primary></indexterm>	301	<indexterm><primary>core team</primary></indexterm>
302	<para>The <ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-core.html">Core team</ulink> decides if	302	<para>The <ulink url="&url.top.articles;/contributors/staff-core.html">Core team</ulink> decides if
303	the code should be part of <command>make world</command>.</para>	303	the code should be part of <command>make world</command>.</para>
304	</listitem>	304	</listitem>
305		305
306	<listitem>	306	<listitem>
307	<indexterm><primary>release engineer</primary></indexterm>	307	<indexterm><primary>release engineer</primary></indexterm>
308	<para>The <ulink url="http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributors/staff-who.html">Release Engineer</ulink>	308	<para>The <ulink url="&url.top.articles;/contributors/staff-who.html">Release Engineer</ulink>
309	decides if it goes in to the release.</para>	309	decides if it goes in to the release.</para>
310	</listitem>	310	</listitem>
311	</orderedlist>	311	</orderedlist>

Lines 82-88 Link Here

(-)en_US.ISO8859-1/articles/console-server/article.sgml (-12 / +12 lines)
82	pointed out that you <em>can</em> get KVM switches that also do	82	pointed out that you <em>can</em> get KVM switches that also do
83	serial consoles or Sun-compatible KVM switching as well as PCs,	83	serial consoles or Sun-compatible KVM switching as well as PCs,
84	but they are expensive. See <a	84	but they are expensive. See <a
85	href="http://www.avocent.com">Avocent</a> for example.]</p>	85	href="http://www.avocent.com/">Avocent</a> for example.]</p>
86		86
87	<p>You might be tempted to do without a console terminal, but when	87	<p>You might be tempted to do without a console terminal, but when
88	things go pear-shaped you <em>really</em> need to see what is on	88	things go pear-shaped you <em>really</em> need to see what is on
Lines 122-128 Link Here
122	terminal server software may not support that.) Also there is	122	terminal server software may not support that.) Also there is
123	no logging or replay of console messages. But with a bit of	123	no logging or replay of console messages. But with a bit of
124	work, and the addition of some software such as <a	124	work, and the addition of some software such as <a
125	href="http://www.conserver.com">conserver</a> (described below),	125	href="http://www.conserver.com/">conserver</a> (described below),
126	this can be made to work pretty well.</p>	126	this can be made to work pretty well.</p>
127		127
128	<p>A possibility suggested by Bron Gondwana is similar to the	128	<p>A possibility suggested by Bron Gondwana is similar to the
Lines 131-137 Link Here
131	the "next" server, creating a ring of console connections (in	131	the "next" server, creating a ring of console connections (in
132	some sort of order). This can be made to work reasonably well	132	some sort of order). This can be made to work reasonably well
133	with the aid of the <a	133	with the aid of the <a
134	href="http://www.conserver.com">conserver</a> software, but can	134	href="http://www.conserver.com/">conserver</a> software, but can
135	be a bit confusing otherwise (i.e. remembering which port is	135	be a bit confusing otherwise (i.e. remembering which port is
136	connected to which console). And you are stuck if you need to	136	connected to which console). And you are stuck if you need to
137	use serial ports for other things (such as modems) or you have	137	use serial ports for other things (such as modems) or you have
Lines 141-148 Link Here
141	buy an off-the-shelf solution. These vary in price and	141	buy an off-the-shelf solution. These vary in price and
142	capability. See, for example, <a	142	capability. See, for example, <a
143	href="http://www.lightwavecom.com/">Lightwave</a>, <a	143	href="http://www.lightwavecom.com/">Lightwave</a>, <a
144	href="http://www.perle.com">Perle</a>, <a	144	href="http://www.perle.com/">Perle</a>, <a
145	href="http://www.avocent.com">Avocent</a> or <a	145	href="http://www.avocent.com/">Avocent</a> or <a
146	href="http://www.blackbox.com/faxbacks/23000/23362.PDF">Black	146	href="http://www.blackbox.com/faxbacks/23000/23362.PDF">Black
147	Box</a>. These solutions can be quite expensive - typically	147	Box</a>. These solutions can be quite expensive - typically
148	$USD100 - $USD400 per port.</p>	148	$USD100 - $USD400 per port.</p>
Lines 162-173 Link Here
162	enough.</p></li>	162	enough.</p></li>
163		163
164	<li><p>A PC Unix system. We used <a	164	<li><p>A PC Unix system. We used <a
165	href="http://www.freebsd.org">FreeBSD 4.3</a> as that is used	165	href="../../../../index.html">FreeBSD 4.3</a> as that is used
166	for other tasks within our office.</p></li>	166	for other tasks within our office.</p></li>
167		167
168	<li><p>A multi-port serial card. We chose the <a	168	<li><p>A multi-port serial card. We chose the <a
169	href="http://www.stallion.com/html/products/easyio.html">EasyIO-PCI</a>	169	href="http://www.stallion.com/html/products/easyio.html">EasyIO-PCI</a>
170	8-port card from <a href="http://www.stallion.com">Stallion	170	8-port card from <a href="http://www.stallion.com/">Stallion
171	Technologies</a>. This cost us about $AUD740, or under	171	Technologies</a>. This cost us about $AUD740, or under
172	$100/port, from <a href="http://www.ht.com.au/">Harris	172	$100/port, from <a href="http://www.ht.com.au/">Harris
173	Technologies</a> (which has lots of stuff but is by no means	173	Technologies</a> (which has lots of stuff but is by no means
Lines 275-281 Link Here
275	config file with the appropriate entries. See the	275	config file with the appropriate entries. See the
276	<samp>stl(4)</samp> man page and the appropriate section of the	276	<samp>stl(4)</samp> man page and the appropriate section of the
277	<a	277	<a
278	href="http://www.au.freebsd.org/handbook/kernelconfig.html">FreeBSD	278	href="../../../../doc/en_US.ISO8859-1/books/handbook/kernelconfig.html">FreeBSD
279	Handbook</a>.</p>	279	Handbook</a>.</p>
280		280
281	<h4>Building World</h4>	281	<h4>Building World</h4>
Lines 993-999 Link Here
993	<h2><a name="freebsd">Using a Serial Console on FreeBSD</a></h2>	993	<h2><a name="freebsd">Using a Serial Console on FreeBSD</a></h2>
994		994
995	<p>The procedure for doing this is described in detail in the <a	995	<p>The procedure for doing this is described in detail in the <a
996	href="http://www.freebsd.org/handbook/serialconsole-setup.html">FreeBSD	996	href="../../../../doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html">FreeBSD
997	Handbook</a>. This is a quick summary.</p>	997	Handbook</a>. This is a quick summary.</p>
998		998
999	<h4>Check the kernel configuration</h4>	999	<h4>Check the kernel configuration</h4>
Lines 1089-1095 Link Here
1089	<p>As shipped with FreeBSD, the 8.5 version does not authenticate	1089	<p>As shipped with FreeBSD, the 8.5 version does not authenticate
1090	against FreeBSD servers using MD5 passwords. There is a patch	1090	against FreeBSD servers using MD5 passwords. There is a patch
1091	in the FreeBSD GNATS system (<a	1091	in the FreeBSD GNATS system (<a
1092	href="http://www.freebsd.org/cgi/query-pr.cgi?pr=28432">ports/28432</a>)	1092	href="http://www.FreeBSD.org/cgi/query-pr.cgi?pr=28432">ports/28432</a>)
1093	that fixes this problem. Kevin has indicated this patch will be	1093	that fixes this problem. Kevin has indicated this patch will be
1094	included in future versions of conserver from him. There are a	1094	included in future versions of conserver from him. There are a
1095	couple of other problems with the 8.5 version as well.</p>	1095	couple of other problems with the 8.5 version as well.</p>
Lines 1138-1144 Link Here
1138	href="ftp://ftp.conserver.com/conserver/conserver-7.0.2.tar.gz">FTP</a>	1138	href="ftp://ftp.conserver.com/conserver/conserver-7.0.2.tar.gz">FTP</a>
1139	the conserver 7.0.2 source tarball.</p>	1139	the conserver 7.0.2 source tarball.</p>
1140		1140
1141	<p><a href="http://www.stallion.com">Stallion Technologies</a> homepage.</p>	1141	<p><a href="http://www.stallion.com/">Stallion Technologies</a> homepage.</p>
1142		1142
1143	<p>David Harris' <a	1143	<p>David Harris' <a
1144	href="http://www.conserver.com/consoles/msock.html">Minor Scroll	1144	href="http://www.conserver.com/consoles/msock.html">Minor Scroll
Lines 1155-1161 Link Here
1155	similar console server</a> based on the <samp>screen</samp>	1155	similar console server</a> based on the <samp>screen</samp>
1156	program and an old SunOs host.</p>	1156	program and an old SunOs host.</p>
1157		1157
1158	<p>The <a href="http://www.realweasel.com">Real Weasel</a> company	1158	<p>The <a href="http://www.realweasel.com/">Real Weasel</a> company
1159	makes a ISA or PCI video card that looks like a PC video card	1159	makes a ISA or PCI video card that looks like a PC video card
1160	but actually talks to a serial port. This can be used to	1160	but actually talks to a serial port. This can be used to
1161	implement serial consoles on PC hardware for operating systems	1161	implement serial consoles on PC hardware for operating systems

Lines 169-175 Link Here

(-)en_US.ISO8859-1/articles/contributing/article.sgml (-5 / +5 lines)
169		169
170	<indexterm><primary>problem reports database</primary></indexterm>	170	<indexterm><primary>problem reports database</primary></indexterm>
171	<para>The <ulink	171	<para>The <ulink
172	url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD PR	172	url="&url.cgi.server;/cgi/query-pr-summary.cgi">FreeBSD PR
173	list</ulink> shows all the current active problem reports and	173	list</ulink> shows all the current active problem reports and
174	requests for enhancement that have been submitted by FreeBSD users.	174	requests for enhancement that have been submitted by FreeBSD users.
175	Look through the open PRs, and see if anything there takes your	175	Look through the open PRs, and see if anything there takes your
Lines 199-211 Link Here
199	an interest in such things (and a tolerance for a	199	an interest in such things (and a tolerance for a
200	<emphasis>high</emphasis> volume of mail!) may subscribe to the	200	<emphasis>high</emphasis> volume of mail!) may subscribe to the
201	hackers mailing list by sending mail to &a.majordomo;. See <ulink	201	hackers mailing list by sending mail to &a.majordomo;. See <ulink
202	url="http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL">The	202	url="&url.top.books;/handbook/eresources.html#ERESOURCES-MAIL">The
203	FreeBSD Handbook</ulink> for more information	203	FreeBSD Handbook</ulink> for more information
204	about this and other mailing lists.</para>	204	about this and other mailing lists.</para>
205		205
206	<para>If you find a bug or are submitting a specific change, please	206	<para>If you find a bug or are submitting a specific change, please
207	report it using the &man.send-pr.1; program or its <ulink	207	report it using the &man.send-pr.1; program or its <ulink
208	url="http://www.FreeBSD.org/send-pr.html">WEB-based	208	url="&url.top.level;/send-pr.html">WEB-based
209	equivalent</ulink>. Try to fill-in each field of the bug report.	209	equivalent</ulink>. Try to fill-in each field of the bug report.
210	Unless they exceed 65KB, include any patches directly in the report.	210	Unless they exceed 65KB, include any patches directly in the report.
211	If the patch is suitable to be applied to the source tree put	211	If the patch is suitable to be applied to the source tree put
Lines 214-220 Link Here
214	because cut-and-paste turns tabs into spaces and makes them unusable.	214	because cut-and-paste turns tabs into spaces and makes them unusable.
215	Consider compressing patches and using &man.uuencode.1; if they exceed	215	Consider compressing patches and using &man.uuencode.1; if they exceed
216	20KB. Upload very large submissions to <ulink	216	20KB. Upload very large submissions to <ulink
217	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/">ftp.FreeBSD.org:/pub/FreeBSD/incoming/</ulink>.</para>	217	url="&url.ftp.server;/pub/FreeBSD/incoming/">ftp.FreeBSD.org:/pub/FreeBSD/incoming/</ulink>.</para>
218		218
219	<para>After filing a report, you should receive confirmation along with	219	<para>After filing a report, you should receive confirmation along with
220	a tracking number. Keep this tracking number so that you can update	220	a tracking number. Keep this tracking number so that you can update
Lines 250-256 Link Here
250	on-going release of FreeBSD known as <quote>FreeBSD-current</quote>	250	on-going release of FreeBSD known as <quote>FreeBSD-current</quote>
251	which is made available in a variety of ways for the convenience of	251	which is made available in a variety of ways for the convenience of
252	developers working actively on the system. See <ulink url="	252	developers working actively on the system. See <ulink url="
253	http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html">The	253	&url.top.books;/handbook/current-stable.html">The
254	FreeBSD Handbook</ulink> for more	254	FreeBSD Handbook</ulink> for more
255	information about getting and using FreeBSD-current.</para>	255	information about getting and using FreeBSD-current.</para>
256		256

Lines 28-36 Link Here

(-)en_US.ISO8859-1/articles/explaining-bsd/article.sgml (-11 / +11 lines)
28	Operating System Counter</ulink>, as of April 1999 31.3% of the	28	Operating System Counter</ulink>, as of April 1999 31.3% of the
29	world's network connected machines run Linux. 14.6% run BSD UNIX.	29	world's network connected machines run Linux. 14.6% run BSD UNIX.
30	Some of the world's largest web operations, such as <ulink	30	Some of the world's largest web operations, such as <ulink
31	url="http://www.yahoo.com">Yahoo!</ulink>, run BSD. The world's	31	url="http://www.yahoo.com/">Yahoo!</ulink>, run BSD. The world's
32	busiest FTP server, <ulink	32	busiest FTP server, <ulink
33	url="ftp://ftp.cdrom.com">ftp.cdrom.com</ulink>, uses BSD to	33	url="ftp://ftp.cdrom.com/">ftp.cdrom.com</ulink>, uses BSD to
34	transfer 1.4 TB of data a day. Clearly this is not a niche	34	transfer 1.4 TB of data a day. Clearly this is not a niche
35	market: BSD is a well-kept secret.</para>	35	market: BSD is a well-kept secret.</para>
36		36
Lines 145-167 Link Here
145	CSRG members, William F. Jolitz, wrote the remaining code and released	145	CSRG members, William F. Jolitz, wrote the remaining code and released
146	it in early 1992 as <emphasis>386BSD</emphasis>. At the same time,	146	it in early 1992 as <emphasis>386BSD</emphasis>. At the same time,
147	another group of ex-CSRG members formed a commercial company called	147	another group of ex-CSRG members formed a commercial company called
148	<ulink url="http://www.bsdi.com">Berkeley Software Design Inc.</ulink>	148	<ulink url="http://www.bsdi.com/">Berkeley Software Design Inc.</ulink>
149	and released a beta version of an operating system called	149	and released a beta version of an operating system called
150	<ulink url="http://www.bsdi.com">BSD/386</ulink>, which was based on	150	<ulink url="http://www.bsdi.com/">BSD/386</ulink>, which was based on
151	the same sources. The name of the operating system has since changed	151	the same sources. The name of the operating system has since changed
152	to BSD/OS.</para>	152	to BSD/OS.</para>
153		153
154	<para>386BSD never became a stable operating system. Instead, two other	154	<para>386BSD never became a stable operating system. Instead, two other
155	projects split off from it in 1993:	155	projects split off from it in 1993:
156	<ulink url="http://www.NetBSD.org">NetBSD</ulink> and	156	<ulink url="http://www.NetBSD.org/">NetBSD</ulink> and
157	<ulink url="http://www.FreeBSD.org">FreeBSD</ulink>. The two projects	157	<ulink url="&url.top.level;/index.html">FreeBSD</ulink>. The two projects
158	originally diverged due to differences in patience waiting for	158	originally diverged due to differences in patience waiting for
159	improvements to 386BSD: the NetBSD people started early in the year,	159	improvements to 386BSD: the NetBSD people started early in the year,
160	and the first version of FreeBSD was not ready until the end of the	160	and the first version of FreeBSD was not ready until the end of the
161	year. In the meantime, the code base had diverged sufficiently to	161	year. In the meantime, the code base had diverged sufficiently to
162	make it difficult to merge. In addition, the projects had different	162	make it difficult to merge. In addition, the projects had different
163	aims, as we will see below. In 1996, a further project,	163	aims, as we will see below. In 1996, a further project,
164	<ulink url="http://www.OpenBSD.org">OpenBSD</ulink>, split off from	164	<ulink url="http://www.OpenBSD.org/">OpenBSD</ulink>, split off from
165	NetBSD.</para>	165	NetBSD.</para>
166	</sect1>	166	</sect1>
167		167
Lines 191-197 Link Here
191		191
192	<listitem>	192	<listitem>
193	<para>In 1992, AT&T sued	193	<para>In 1992, AT&T sued
194	<ulink url="http://www.bsdi.com">BSDI</ulink>,	194	<ulink url="http://www.bsdi.com/">BSDI</ulink>,
195	the vendor of BSD/386, alleging that the product contained	195	the vendor of BSD/386, alleging that the product contained
196	AT&T-copyrighted code. The case was settled out of court in	196	AT&T-copyrighted code. The case was settled out of court in
197	1994, but the spectre of the litigation continues to haunt people.	197	1994, but the spectre of the litigation continues to haunt people.
Lines 245-251 Link Here
245	<para>The BSD kernels are developed and updated following the Open	245	<para>The BSD kernels are developed and updated following the Open
246	Source development model. Each project maintains a publicly	246	Source development model. Each project maintains a publicly
247	accessible <emphasis>source tree</emphasis> under the	247	accessible <emphasis>source tree</emphasis> under the
248	<ulink url="http://www.sourcegear.com/CVS">Concurrent Versions	248	<ulink url="http://www.sourcegear.com/CVS/">Concurrent Versions
249	System</ulink> (CVS), which contains all source files for the	249	System</ulink> (CVS), which contains all source files for the
250	project, including documentation and other incidental files. CVS	250	project, including documentation and other incidental files. CVS
251	allows users to <quote>check out</quote> (in other words, to	251	allows users to <quote>check out</quote> (in other words, to
Lines 436-442 Link Here
436	<listitem>	436	<listitem>
437	<para><ulink url="http://www.apple.com/macosx/server/">Mac OS	437	<para><ulink url="http://www.apple.com/macosx/server/">Mac OS
438	X</ulink> is the latest version of the operating system for	438	X</ulink> is the latest version of the operating system for
439	<ulink url="http://www.apple.com">Apple Computer Inc.'s</ulink>	439	<ulink url="http://www.apple.com/">Apple Computer Inc.'s</ulink>
440	Macintosh line. Unlike the rest of the operating system, the	440	Macintosh line. Unlike the rest of the operating system, the
441	kernel is open source. As part of this development, key Apple	441	kernel is open source. As part of this development, key Apple
442	developers have commit access to the FreeBSD source tree.</para>	442	developers have commit access to the FreeBSD source tree.</para>
Lines 528-534 Link Here
528		528
529	<para>In addition, each of the projects has a list of consultants for	529	<para>In addition, each of the projects has a list of consultants for
530	hire:	530	hire:
531	<ulink url="http://www.freebsd.org/commercial/consulting_bycat.html">FreeBSD</ulink>,	531	<ulink url="&url.top.level;/commercial/consulting_bycat.html">FreeBSD</ulink>,
532	<ulink url="http://www.netbsd.org/gallery/consultants.html">NetBSD</ulink>,	532	<ulink url="http://www.netbsd.org/gallery/consultants.html">NetBSD</ulink>,
533	and <ulink url="http://www.openbsd.org/support.html">OpenBSD</ulink>.</para>	533	and <ulink url="http://www.openbsd.org/support.html">OpenBSD</ulink>.</para>
534	</sect2>	534	</sect2>

Lines 48-54 Link Here

(-)en_US.ISO8859-1/articles/multi-os/article.sgml (-5 / +6 lines)
48	completely occupied by DOS, you might find the FIPS utility	48	completely occupied by DOS, you might find the FIPS utility
49	(included on the FreeBSD CDROM in the	49	(included on the FreeBSD CDROM in the
50	<filename>\TOOLS</filename> directory or via <ulink	50	<filename>\TOOLS</filename> directory or via <ulink
51	URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools">ftp</ulink>)	51	URL="&url.ftp.server;/pub/FreeBSD/tools/">ftp</ulink>)
52	useful. It lets you repartition your hard disk without	52	useful. It lets you repartition your hard disk without
53	destroying the data already on it. There is also a commercial	53	destroying the data already on it. There is also a commercial
54	program available called Partition Magic, which lets you size	54	program available called Partition Magic, which lets you size
Lines 105-111 Link Here
105	selecting the OS with your arrow keys. It is included on	105	selecting the OS with your arrow keys. It is included on
106	the FreeBSD CD in the <filename>\TOOLS</filename>	106	the FreeBSD CD in the <filename>\TOOLS</filename>
107	directory, and via <ulink	107	directory, and via <ulink
108	URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools">ftp</ulink>.</para>	108	URL="&url.ftp.server;/pub/FreeBSD/tools/">ftp</ulink>.</para>
109	</listitem>	109	</listitem>
110	</varlistentry>	110	</varlistentry>
111		111
Lines 277-283 Link Here
277	previous boot manager. Boot Easy can be reinstalled by using	277	previous boot manager. Boot Easy can be reinstalled by using
278	the BOOTINST.EXE utility included in the \TOOLS directory on the	278	the BOOTINST.EXE utility included in the \TOOLS directory on the
279	CDROM, and via <ulink	279	CDROM, and via <ulink
280	URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools">ftp</ulink>.	280	URL="&url.ftp.server;/pub/FreeBSD/tools/">ftp</ulink>.
281	You can also re-start the installation process and go to the	281	You can also re-start the installation process and go to the
282	partition editor. From there, mark the FreeBSD partition as	282	partition editor. From there, mark the FreeBSD partition as
283	bootable, select Boot Manager, and then type W to (W)rite out	283	bootable, select Boot Manager, and then type W to (W)rite out
Lines 344-356 Link Here
344	mini-HOWTO</ulink> might be interesting as well. The <ulink	344	mini-HOWTO</ulink> might be interesting as well. The <ulink
345	URL="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>	345	URL="http://www.in.net/~jkatz/win95/Linux-HOWTO.html">Linux-HOWTO</ulink>
346	is also helpful.</para>	346	is also helpful.</para>
347		347	<![ IGNORE [
		348	<!-- dead link -->
348	<para>The <ulink	349	<para>The <ulink
349	URL="http://www.dorsai.org/~dcl/publications/NTLDR_Hacking">NT	350	URL="http://www.dorsai.org/~dcl/publications/NTLDR_Hacking">NT
350	Loader Hacking Guide</ulink> provides good information on	351	Loader Hacking Guide</ulink> provides good information on
351	multibooting Windows NT, '95, and DOS with other operating	352	multibooting Windows NT, '95, and DOS with other operating
352	systems.</para>	353	systems.</para>
353		354	]]>
354	<para>And Hale Landis's "How It Works" document pack contains some	355	<para>And Hale Landis's "How It Works" document pack contains some
355	good info on all sorts of disk geometry and booting related	356	good info on all sorts of disk geometry and booting related
356	topics. You can find it at	357	topics. You can find it at

Lines 689-695 Link Here

(-)en_US.ISO8859-1/articles/new-users/article.sgml (-3 / +3 lines)
689	<command>lp</command> or <command>lpr</command> should send a	689	<command>lp</command> or <command>lpr</command> should send a
690	file to the printer. Whether or not the file actually prints	690	file to the printer. Whether or not the file actually prints
691	depends on configuring it, which is covered in the <ulink	691	depends on configuring it, which is covered in the <ulink
692	URL="../../books/handbook/handbook.html">FreeBSD	692	URL="&url.top.books;/handbook/index.html">FreeBSD
693	handbook.</ulink></para>	693	handbook.</ulink></para>
694	</sect1>	694	</sect1>
695		695
Lines 792-798 Link Here
792	edit files, so you can get everything up and running. There is	792	edit files, so you can get everything up and running. There is
793	a great deal of information in the FreeBSD handbook (which is	793	a great deal of information in the FreeBSD handbook (which is
794	probably on your hard drive) and <ulink	794	probably on your hard drive) and <ulink
795	URL="http://www.FreeBSD.org/">FreeBSD's web site</ulink>. A	795	URL="&url.top.level;/index.html">FreeBSD's web site</ulink>. A
796	wide variety of packages and ports are on the CDROM as well as	796	wide variety of packages and ports are on the CDROM as well as
797	the web site. The handbook tells you more about how to use them	797	the web site. The handbook tells you more about how to use them
798	(get the package if it exists, with <command>pkg_add	798	(get the package if it exists, with <command>pkg_add
Lines 882-888 Link Here
882	space after the slash.)</para>	882	space after the slash.)</para>
883		883
884	<para>You might want to get the most recent version of Netscape	884	<para>You might want to get the most recent version of Netscape
885	from their <ulink URL="ftp://ftp.netscape.com">FTP site</ulink>.	885	from their <ulink URL="ftp://ftp.netscape.com/">FTP site</ulink>.
886	(Netscape requires the X Window System.) There is now a FreeBSD	886	(Netscape requires the X Window System.) There is now a FreeBSD
887	version, so look around carefully. Just use <command>gunzip	887	version, so look around carefully. Just use <command>gunzip
888	<replaceable>filename</replaceable></command> and <command>tar	888	<replaceable>filename</replaceable></command> and <command>tar

Lines 80-86 Link Here

(-)en_US.ISO8859-1/articles/pxe/article.sgml (-4 / +4 lines)
80	<procedure>	80	<procedure>
81	<step>	81	<step>
82	<para>Install DHCP : Install isc-dhcp-2.0 you can use this config file	82	<para>Install DHCP : Install isc-dhcp-2.0 you can use this config file
83	<ulink url="http://people.freebsd.org/~alfred/pxe/dhcpd.conf">	83	<ulink url="&url.people.server;/~alfred/pxe/dhcpd.conf">
84	dhcpd.conf</ulink>, stick it in /usr/local/etc/</para>	84	dhcpd.conf</ulink>, stick it in /usr/local/etc/</para>
85	</step>	85	</step>
86		86
Lines 133-139 Link Here
133	<procedure>	133	<procedure>
134	<step>	134	<step>
135	<para>Download bootfiles : Download the	135	<para>Download bootfiles : Download the
136	<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386/kern.flp">	136	<ulink url="&url.ftp.server;/pub/FreeBSD/snapshots/i386/kern.flp">
137	kern.flp</ulink> and	137	kern.flp</ulink> and
138	<ulink url="ftp://ftp.FreeBSD.opg/pub/FreeBSD/snapshots/i386/mfsroot.flp">	138	<ulink url="ftp://ftp.FreeBSD.opg/pub/FreeBSD/snapshots/i386/mfsroot.flp">
139	mfsroot.flp</ulink> floppy images.</para>	139	mfsroot.flp</ulink> floppy images.</para>
Lines 176-182 Link Here
176	<para>Make a special <filename>loader.rc</filename> to and install it	176	<para>Make a special <filename>loader.rc</filename> to and install it
177	in <filename>/usr/tftpboot/boot/loader.rc</filename> so that it	177	in <filename>/usr/tftpboot/boot/loader.rc</filename> so that it
178	does not prompt for the second disk, here is	178	does not prompt for the second disk, here is
179	<ulink url="http://people.FreeBSD.org/~alfred/pxe/loader.rc">	179	<ulink url="&url.people.server;/~alfred/pxe/loader.rc">
180	mine</ulink>.</para>	180	mine</ulink>.</para>
181	</step>	181	</step>
182		182
Lines 197-203 Link Here
197	<step>	197	<step>
198	<para>Make your sysinstall script <filename>install.cfg</filename>, you	198	<para>Make your sysinstall script <filename>install.cfg</filename>, you
199	can use	199	can use
200	<ulink url="http://people.FreeBSD.org/~alfred/pxe/install.cfg">	200	<ulink url="&url.people.server;/~alfred/pxe/install.cfg">
201	mine</ulink> as a template, but you must edit it.</para>	201	mine</ulink> as a template, but you must edit it.</para>
202	</step>	202	</step>
203		203

Lines 26-32 Link Here

(-)en_US.ISO8859-1/books/corp-net-guide/book.sgml (-4 / +4 lines)
26	distributed without the publisher's express written	26	distributed without the publisher's express written
27	<email>Chanda.Leary-Coutu@awl.com</email>.	27	<email>Chanda.Leary-Coutu@awl.com</email>.
28	The other chapters of	28	The other chapters of
29	<ulink url="http://www.awl.com/cseng/titles/0-201-70481-1">the	29	<ulink url="http://cseng.aw.com/book/0,,0201704811,00.html">the
30	book</ulink> covers topics such as system administration,	30	book</ulink> covers topics such as system administration,
31	fileserving, and e-mail delivery. More information about this book is	31	fileserving, and e-mail delivery. More information about this book is
32	available from the publisher, with whom you can also sign up to	32	available from the publisher, with whom you can also sign up to
Lines 571-577 Link Here
571	play. I prefer using these devices because they are much cheaper	571	play. I prefer using these devices because they are much cheaper
572	and more reliable than a standalone PC running printserver	572	and more reliable than a standalone PC running printserver
573	software. For example, Castelle	573	software. For example, Castelle
574	<ulink url="http://www.castelle.com">http://www.castelle.com</ulink>	574	<ulink url="http://www.castelle.com/">http://www.castelle.com/</ulink>
575	sells the LANpress 1P/10BT printserver for about $170.00. Using	575	sells the LANpress 1P/10BT printserver for about $170.00. Using
576	these devices a FreeBSD UNIX server can have dozens of print spools	576	these devices a FreeBSD UNIX server can have dozens of print spools
577	accepting print jobs and then route them back out over the network	577	accepting print jobs and then route them back out over the network
Lines 684-690 Link Here
684		684
685	<step>	685	<step>
686	<para>Obtain the <filename>TCP16.EXE</filename> file from	686	<para>Obtain the <filename>TCP16.EXE</filename> file from
687	<ulink url="ftp3.novell.com/pub/updates/eol/nweol/tcp16.exe">ftp3.novell.com/pub/updates/eol/nweol/tcp16.exe</ulink>.</para>	687	<ulink url="ftp://ftp3.novell.com/pub/updates/eol/nweol/tcp16.exe">ftp://ftp3.novell.com/pub/updates/eol/nweol/tcp16.exe</ulink>.</para>
688	</step>	688	</step>
689		689
690	<step>	690	<step>
Lines 2131-2137 Link Here
2131		2131
2132	<para>The better solution is to use a simple filter that converts	2132	<para>The better solution is to use a simple filter that converts
2133	incoming text from UNIX style to DOS style. The following filter	2133	incoming text from UNIX style to DOS style. The following filter
2134	posted on questions@freebsd.org and the sample	2134	posted on questions@FreeBSD.org and the sample
2135	<filename>/etc/printcap</filename> entry can be used to do	2135	<filename>/etc/printcap</filename> entry can be used to do
2136	this:</para>	2136	this:</para>
2137		2137

Lines 38-49 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/book.sgml (-3 / +3 lines)
38	helping with this project, send email to the &a.doc;.</para>	38	helping with this project, send email to the &a.doc;.</para>
39		39
40	<para>The latest version of this document is always available	40	<para>The latest version of this document is always available
41	from the <ulink URL="http://www.FreeBSD.org/">FreeBSD World	41	from the <ulink URL="&url.top.level;/index.html">FreeBSD World
42	Wide Web server</ulink>. It may also be downloaded in a	42	Wide Web server</ulink>. It may also be downloaded in a
43	variety of formats and compression options from the <ulink	43	variety of formats and compression options from the <ulink
44	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc">FreeBSD FTP	44	url="&url.ftp.server;/pub/FreeBSD/doc/">FreeBSD FTP
45	server</ulink> or one of the numerous <ulink	45	server</ulink> or one of the numerous <ulink
46	url="http://www.freebsd.org/handbook/mirrors-ftp.html">mirror	46	url="&url.top.books;/handbook/mirrors-ftp.html">mirror
47	sites</ulink>.</para>	47	sites</ulink>.</para>
48	</abstract>	48	</abstract>
49	</bookinfo>	49	</bookinfo>

Lines 106-112 Link Here

(-)en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml (-14 / +14 lines)
106		106
107	<para>Here is a list of interpreters that are available as	107	<para>Here is a list of interpreters that are available as
108	<ulink	108	<ulink
109	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/">FreeBSD	109	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/">FreeBSD
110	packages</ulink>, with a brief discussion of some of the	110	packages</ulink>, with a brief discussion of some of the
111	more popular interpreted languages.</para>	111	more popular interpreted languages.</para>
112		112
Lines 133-144 Link Here
133	for Visual Basic.</para>	133	for Visual Basic.</para>
134		134
135	<para>The <ulink	135	<para>The <ulink
136	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/bwbasic-2.10.tgz">Bywater	136	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/bwbasic-2.10.tgz">Bywater
137	Basic Interpreter</ulink> and the <ulink	137	Basic Interpreter</ulink> and the <ulink
138	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/pbasic-2.0.tgz">Phil	138	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/pbasic-2.0.tgz">Phil
139	Cockroft's Basic Interpreter</ulink> (formerly Rabbit	139	Cockroft's Basic Interpreter</ulink> (formerly Rabbit
140	Basic) are available as <ulink	140	Basic) are available as <ulink
141	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/">FreeBSD	141	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/">FreeBSD
142	packages</ulink>.</para>	142	packages</ulink>.</para>
143	</listitem>	143	</listitem>
144	</varlistentry>	144	</varlistentry>
Lines 159-165 Link Here
159	language, but can be rather large and unwieldy.</para>	159	language, but can be rather large and unwieldy.</para>
160		160
161	<para>FreeBSD has <ulink	161	<para>FreeBSD has <ulink
162	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/gcl-2.0.tgz">GNU	162	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/gcl-2.0.tgz">GNU
163	Common Lisp</ulink> available as a package.</para>	163	Common Lisp</ulink> available as a package.</para>
164	</listitem>	164	</listitem>
165	</varlistentry>	165	</varlistentry>
Lines 187-197 Link Here
187	abstraction to be used in research work.</para>	187	abstraction to be used in research work.</para>
188		188
189	<para>FreeBSD has packages of the <ulink	189	<para>FreeBSD has packages of the <ulink
190	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/elk-3.0.tgz">Elk	190	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/elk-3.0.tgz">Elk
191	Scheme Interpreter</ulink>, the <ulink	191	Scheme Interpreter</ulink>, the <ulink
192	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/mit-scheme-7.3.tgz">MIT	192	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/mit-scheme-7.3.tgz">MIT
193	Scheme Interpreter</ulink> and the <ulink	193	Scheme Interpreter</ulink> and the <ulink
194	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/scm-4e1.tgz">SCM	194	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/scm-4e1.tgz">SCM
195	Scheme Interpreter</ulink>.</para>	195	Scheme Interpreter</ulink>.</para>
196	</listitem>	196	</listitem>
197	</varlistentry>	197	</varlistentry>
Lines 201-207 Link Here
201		201
202	<listitem>	202	<listitem>
203	<para><ulink	203	<para><ulink
204	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/icon-9.0.tgz">The	204	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/icon-9.0.tgz">The
205	Icon Programming Language</ulink>.</para>	205	Icon Programming Language</ulink>.</para>
206	</listitem>	206	</listitem>
207	</varlistentry>	207	</varlistentry>
Lines 211-217 Link Here
211		211
212	<listitem>	212	<listitem>
213	<para><ulink	213	<para><ulink
214	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/ucblogo-3.3.tgz">Brian	214	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/ucblogo-3.3.tgz">Brian
215	Harvey's LOGO Interpreter</ulink>.</para>	215	Harvey's LOGO Interpreter</ulink>.</para>
216	</listitem>	216	</listitem>
217	</varlistentry>	217	</varlistentry>
Lines 221-227 Link Here
221		221
222	<listitem>	222	<listitem>
223	<para><ulink	223	<para><ulink
224	URL="ftp://ftp.FreeBSD.org:pub/FreeBSD/packages/lang/python-1.2">The	224	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/lang/python-1.2.tgz">The
225	Python Object-Oriented Programming	225	Python Object-Oriented Programming
226	Language</ulink></para>	226	Language</ulink></para>
227	</listitem>	227	</listitem>
Lines 1367-1373 Link Here
1367		1367
1368	<para>Finally, if you find its text-based command-prompt style	1368	<para>Finally, if you find its text-based command-prompt style
1369	off-putting, there's a graphical front-end for it <ulink	1369	off-putting, there's a graphical front-end for it <ulink
1370	URL="../../../../ports/devel.html">xxgdb</ulink> in the ports	1370	URL="&url.top.level;/ports/devel.html">xxgdb</ulink> in the ports
1371	collection.</para>	1371	collection.</para>
1372		1372
1373	<para>This section is intended to be an introduction to using	1373	<para>This section is intended to be an introduction to using
Lines 1694-1700 Link Here
1694	<para>And doubtless many more that I've overlooked.</para>	1694	<para>And doubtless many more that I've overlooked.</para>
1695		1695
1696	<para>Emacs can be installed on FreeBSD using <ulink	1696	<para>Emacs can be installed on FreeBSD using <ulink
1697	URL="../../ports/editors.html">the Emacs	1697	URL="&url.top.level;/ports/editors.html">the Emacs
1698	port</ulink>.</para>	1698	port</ulink>.</para>
1699		1699
1700	<para>Once it's installed, start it up and do <userinput>C-h	1700	<para>Once it's installed, start it up and do <userinput>C-h
Lines 1777-1783 Link Here
1777	quite big!).</para>	1777	quite big!).</para>
1778		1778
1779	<para>The best way to learn Emacs Lisp is to download the <ulink	1779	<para>The best way to learn Emacs Lisp is to download the <ulink
1780	URL="ftp://prep.ai.mit.edu:pub/gnu/elisp-manual-19-2.4.tar.gz">Emacs	1780	URL="ftp://prep.ai.mit.edu/pub/gnu/elisp-manual-19-2.4.tar.gz">Emacs
1781	Tutorial</ulink></para>	1781	Tutorial</ulink></para>
1782		1782
1783	<para>However, there's no need to actually know any Lisp to get	1783	<para>However, there's no need to actually know any Lisp to get

Lines 122-128 Link Here

(-)en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml (-7 / +7 lines)
122	<listitem>	122	<listitem>
123	<para>This is the main FreeBSD presence on the World Wide Web,	123	<para>This is the main FreeBSD presence on the World Wide Web,
124	visible at <ulink	124	visible at <ulink
125	url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>	125	url="&url.top.level;/index.html">&url.home.page;/</ulink>
126	and many mirrors around the world. The web site is many people's	126	and many mirrors around the world. The web site is many people's
127	first exposure to FreeBSD.</para>	127	first exposure to FreeBSD.</para>
128	</listitem>	128	</listitem>
Lines 190-200 Link Here
190		190
191	<para>If you have the CVS repository locally then as a minimum you	191	<para>If you have the CVS repository locally then as a minimum you
192	will need to checkout the <filename>doc/share</filename>, and	192	will need to checkout the <filename>doc/share</filename>, and
193	<filename>doc/en_US.ISO8859-1/share</filename>	193	<filename>&url.doc.enUS;/share</filename>
194	directories.</para>	194	directories.</para>
195		195
196	<screen>&prompt.user; <userinput>cvs checkout doc/share</userinput>	196	<screen>&prompt.user; <userinput>cvs checkout doc/share</userinput>
197	&prompt.user; <userinput>cvs checkout doc/en_US.ISO8859-1/share</userinput></screen>	197	&prompt.user; <userinput>cvs checkout &url.doc.enUS;/share</userinput></screen>
198		198
199	<para>If you have plenty of disk space then you could check out	199	<para>If you have plenty of disk space then you could check out
200	everything.</para>	200	everything.</para>
Lines 217-223 Link Here
217	<para>Check out the <filename>articles</filename>	217	<para>Check out the <filename>articles</filename>
218	directory.</para>	218	directory.</para>
219		219
220	<screen>&prompt.user; <userinput>cvs checkout doc/en_US.ISO8859-1/articles</userinput></screen>	220	<screen>&prompt.user; <userinput>cvs checkout &url.doc.enUS;/articles</userinput></screen>
221	</step>	221	</step>
222		222
223	<step>	223	<step>
Lines 225-240 Link Here
225	case, you have decided that your new article belongs in a	225	case, you have decided that your new article belongs in a
226	directory called <filename>vpn-w2k</filename>.</para>	226	directory called <filename>vpn-w2k</filename>.</para>
227		227
228	<screen>&prompt.user; <userinput>cd doc/en_US.ISO8859-1/articles</userinput>	228	<screen>&prompt.user; <userinput>cd &url.doc.enUS;/articles</userinput>
229	&prompt.user; <userinput>cp -r committers-guide vpn-w2k</userinput></screen>	229	&prompt.user; <userinput>cp -r committers-guide vpn-w2k</userinput></screen>
230	</step>	230	</step>
231	</procedure>	231	</procedure>
232		232
233	<para>If you wanted to edit an existing document, such as the the FAQ,	233	<para>If you wanted to edit an existing document, such as the the FAQ,
234	which is in <filename>doc/en_US.ISO8859-1/books/faq</filename> you	234	which is in <filename>&url.doc.enUS;/books/faq</filename> you
235	would check it out of the repository like this.</para>	235	would check it out of the repository like this.</para>
236		236
237	<screen>&prompt.user; <userinput>cvs checkout doc/en_US.ISO8859-1/books/faq</userinput></screen>	237	<screen>&prompt.user; <userinput>cvs checkout &url.doc.enUS;/books/faq</userinput></screen>
238	</step>	238	</step>
239		239
240	<step>	240	<step>

Lines 43-54 Link Here

(-)en_US.ISO8859-1/books/fdp-primer/see-also/chapter.sgml (-3 / +3 lines)
43		43
44	<itemizedlist>	44	<itemizedlist>
45	<listitem>	45	<listitem>
46	<para><ulink url="http://www.FreeBSD.org/docproj/">The FreeBSD	46	<para><ulink url="&url.top.level;/docproj/index.html">The FreeBSD
47	Documentation Project web pages</ulink></para>	47	Documentation Project web pages</ulink></para>
48	</listitem>	48	</listitem>
49		49
50	<listitem>	50	<listitem>
51	<para><ulink url="http://www.FreeBSD.org/handbook/">The FreeBSD Handbook</ulink></para>	51	<para><ulink url="&url.top.books;/handbook/index.html">The FreeBSD Handbook</ulink></para>
52	</listitem>	52	</listitem>
53	</itemizedlist>	53	</itemizedlist>
54	</sect1>	54	</sect1>
Lines 102-108 Link Here
102	</listitem>	102	</listitem>
103		103
104	<listitem>	104	<listitem>
105	<para><ulink url="http://docbook.sourceforge.net">The DocBook Open	105	<para><ulink url="http://docbook.sourceforge.net/">The DocBook Open
106	Repository</ulink> contains DSSSL stylesheets and other resources	106	Repository</ulink> contains DSSSL stylesheets and other resources
107	for people using DocBook.</para>	107	for people using DocBook.</para>
108	</listitem>	108	</listitem>

Lines 333-339 Link Here

(-)en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml (-9 / +9 lines)
333	There's a new copy of my primer for contributers to the FreeBSD	333	There's a new copy of my primer for contributers to the FreeBSD
334	Documentation Project available at	334	Documentation Project available at
335		335
336	<URL:http://people.FreeBSD.org/~nik/primer/index.html>	336	<URL:&url.people.server;/~nik/primer/index.html>
337		337
338	Comments appreciated.	338	Comments appreciated.
339		339
Lines 595-601 Link Here
595	<para>Use:</para>	595	<para>Use:</para>
596		596
597	<programlisting><![ CDATA [<p>More information is available at the	597	<programlisting><![ CDATA [<p>More information is available at the
598	<a href="http://www.FreeBSD.org/">FreeBSD web site</a>.</p>]]></programlisting>	598	<a href="&url.home.page;/">FreeBSD web site</a>.</p>]]></programlisting>
599	</example>	599	</example>
600		600
601	<para>These links will take the user to the top of the chosen	601	<para>These links will take the user to the top of the chosen
Lines 705-711 Link Here
705		705
706	<para>The FreeBSD extensions are not (currently) in the ports	706	<para>The FreeBSD extensions are not (currently) in the ports
707	collection. They are stored in the FreeBSD CVS tree, as <ulink	707	collection. They are stored in the FreeBSD CVS tree, as <ulink
708	url="http://www.freebsd.org/cgi/cvsweb.cgi/doc/share/sgml/freebsd.dtd">doc/share/sgml/freebsd.dtd</ulink>.</para>	708	url="&url.cgi.server;/cgi/cvsweb.cgi/doc/share/sgml/freebsd.dtd">doc/share/sgml/freebsd.dtd</ulink>.</para>
709	</sect2>	709	</sect2>
710		710
711	<sect2>	711	<sect2>
Lines 751-761 Link Here
751	best suited to information that can be broken up into several	751	best suited to information that can be broken up into several
752	chapters, possibly with appendices and similar content as well.</para>	752	chapters, possibly with appendices and similar content as well.</para>
753		753
754	<para>The <ulink url="http://www.FreeBSD.org/tutorials/">FreeBSD	754	<para>The <ulink url="&url.top.level;/docs.html">FreeBSD
755	tutorials</ulink> are all marked up as articles, while this	755	tutorials</ulink> are all marked up as articles, while this
756	document, the <ulink url="http://www.FreeBSD.org/FAQ/">FreeBSD	756	document, the <ulink url="&url.top.books;/faq/index.html">FreeBSD
757	FAQ</ulink>, and the <ulink	757	FAQ</ulink>, and the <ulink
758	url="http://www.FreeBSD.org/handbook/">FreeBSD Handbook</ulink> are	758	url="&url.top.books;/handbook/index.html">FreeBSD Handbook</ulink> are
759	all marked up as books.</para>	759	all marked up as books.</para>
760		760
761	<sect3>	761	<sect3>
Lines 2184-2190 Link Here
2184	by hand.</para>	2184	by hand.</para>
2185		2185
2186	<para>The best example of what follows in practice is the	2186	<para>The best example of what follows in practice is the
2187	<filename>en_US.ISO8859-1/articles/vm-design/</filename> document.	2187	<filename>&url.doc.enUS;/articles/vm-design/</filename> document.
2188	If you're unsure of the description that follows, take a look at the	2188	If you're unsure of the description that follows, take a look at the
2189	files in that directory to see how everything hangs togther.	2189	files in that directory to see how everything hangs togther.
2190	Experiment with creating different formatted versions of the	2190	Experiment with creating different formatted versions of the
Lines 2572-2584 Link Here
2572	<para>Use:</para>	2572	<para>Use:</para>
2573		2573
2574	<programlisting><![ CDATA [<para>Of course, you could stop reading this document and	2574	<programlisting><![ CDATA [<para>Of course, you could stop reading this document and
2575	go to the <ulink url="http://www.FreeBSD.org/">FreeBSD	2575	go to the <ulink url="&url.top.level;/index.html">FreeBSD
2576	home page</ulink> instead.</para>]]></programlisting>	2576	home page</ulink> instead.</para>]]></programlisting>
2577		2577
2578	<para>Appearance:</para>	2578	<para>Appearance:</para>
2579		2579
2580	<para>Of course, you could stop reading this document and go to the	2580	<para>Of course, you could stop reading this document and go to the
2581	<ulink url="http://www.FreeBSD.org/">FreeBSD home page</ulink>	2581	<ulink url="&url.top.level;/index.html">FreeBSD home page</ulink>
2582	instead.</para>	2582	instead.</para>
2583	</example>	2583	</example>
2584	</sect3>	2584	</sect3>

Lines 81-97 Link Here

(-)en_US.ISO8859-1/books/handbook/book.sgml (-3 / +3 lines)
81	that do exist need to be updated. If you are interested in helping	81	that do exist need to be updated. If you are interested in helping
82	with this project, send email to the &a.doc;. The latest version of	82	with this project, send email to the &a.doc;. The latest version of
83	this document is always available from the <ulink	83	this document is always available from the <ulink
84	URL="http://www.FreeBSD.org/">FreeBSD web site</ulink>.	84	url="&url.top.level;/index.html">FreeBSD web site</ulink>.
85	It may also be downloaded in a variety of formats and compression	85	It may also be downloaded in a variety of formats and compression
86	options from the <ulink	86	options from the <ulink
87	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc">FreeBSD FTP	87	url="&url.ftp.server;/pub/FreeBSD/doc/">FreeBSD FTP
88	server</ulink> or one of the numerous <link	88	server</ulink> or one of the numerous <link
89	linkend="mirrors-ftp">mirror sites</link>. If you would prefer	89	linkend="mirrors-ftp">mirror sites</link>. If you would prefer
90	to have a hard copy of the handbook, you can purchase one at the	90	to have a hard copy of the handbook, you can purchase one at the
91	<ulink	91	<ulink
92	url="http://www.freebsdmall.com/">FreeBSD Mall</ulink>. You	92	url="http://www.freebsdmall.com/">FreeBSD Mall</ulink>. You
93	may also want to <ulink	93	may also want to <ulink
94	URL="http://www.FreeBSD.org/search.html">search the	94	url="&url.top.level;/search/index.html">search the
95	handbook</ulink>.</para>	95	handbook</ulink>.</para>
96	</abstract>	96	</abstract>
97	</bookinfo>	97	</bookinfo>

Lines 1680-1692 Link Here

(-)en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml (-7 / +7 lines)
1680	url="http://www.freebsd-support.de/i4b/">homepage of	1680	url="http://www.freebsd-support.de/i4b/">homepage of
1681	isdn4bsd</ulink> which also has pointers to hints, erratas and	1681	isdn4bsd</ulink> which also has pointers to hints, erratas and
1682	much more documentation such as the <ulink	1682	much more documentation such as the <ulink
1683	url="http://people.freebsd.org/~hm/">isdn4bsd	1683	url="&url.people.server;/~hm/">isdn4bsd
1684	handbook</ulink>.</para>	1684	handbook</ulink>.</para>
1685		1685
1686	<para>In case you are interested in adding support for a	1686	<para>In case you are interested in adding support for a
1687	different ISDN protocol, a currently unsupported ISDN PC card or	1687	different ISDN protocol, a currently unsupported ISDN PC card or
1688	otherwise enhancing <application>isdn4bsd</application>, please	1688	otherwise enhancing <application>isdn4bsd</application>, please
1689	get in touch with <email>hm@freebsd.org</email>.</para>	1689	get in touch with <email>hm@FreeBSD.org</email>.</para>
1690		1690
1691	<para>For questions regarding the installation, configuration	1691	<para>For questions regarding the installation, configuration
1692	and troubleshooting <application>isdn4bsd</application>, a	1692	and troubleshooting <application>isdn4bsd</application>, a
Lines 1749-1755 Link Here
1749	serial card in your computer.</para>	1749	serial card in your computer.</para>
1750		1750
1751	<para>You should read the <ulink	1751	<para>You should read the <ulink
1752	url="http://www.FreeBSD.org/tutorials">FreeBSD Serial	1752	url="&url.top.articles;/serial-uart/index.html">FreeBSD Serial
1753	Hardware</ulink> tutorial for a detailed understanding of	1753	Hardware</ulink> tutorial for a detailed understanding of
1754	serial devices, and the differences between asynchronous and	1754	serial devices, and the differences between asynchronous and
1755	synchronous serial ports.</para>	1755	synchronous serial ports.</para>
Lines 1772-1778 Link Here
1772	<para>The choice of sync/TA v.s. stand-alone router is largely a	1772	<para>The choice of sync/TA v.s. stand-alone router is largely a
1773	religious issue. There has been some discussion of this in	1773	religious issue. There has been some discussion of this in
1774	the mailing lists. I suggest you search the <ulink	1774	the mailing lists. I suggest you search the <ulink
1775	url="http://www.FreeBSD.org/search.html">archives</ulink> for	1775	url="&url.top.level;/search/index.html">archives</ulink> for
1776	the complete discussion.</para>	1776	the complete discussion.</para>
1777	</sect2>	1777	</sect2>
1778		1778
Lines 3481-3487 Link Here
3481		3481
3482	<para>	3482	<para>
3483	Currently, BIND is maintained by the <ulink	3483	Currently, BIND is maintained by the <ulink
3484	url="http://www.isc.org">	3484	url="http://www.isc.org/">
3485	Internet Software Consortium (www.isc.org)</ulink>	3485	Internet Software Consortium (www.isc.org)</ulink>
3486	</para>	3486	</para>
3487	</sect2>	3487	</sect2>
Lines 4275-4282 Link Here
4275		4275
4276	<para>	4276	<para>
4277	It is a good idea to subscribe to <ulink	4277	It is a good idea to subscribe to <ulink
4278	url="http://www.cert.org">CERT</ulink> and	4278	url="http://www.cert.org/">CERT</ulink> and
4279	<ulink url="http://www.FreeBSD.org/handbook/eresources.html#ERESOURCES-MAIL">freebsd-announce</ulink>	4279	<ulink url="&url.top.books;/handbook/eresources.html#ERESOURCES-MAIL">freebsd-announce</ulink>
4280	to stay up to date with the current Internet and FreeBSD security	4280	to stay up to date with the current Internet and FreeBSD security
4281	issues.	4281	issues.
4282	</para>	4282	</para>

Lines 22-28 Link Here

(-)en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml (-3 / +3 lines)
22	<itemizedlist>	22	<itemizedlist>
23	<listitem>	23	<listitem>
24	<para><ulink	24	<para><ulink
25	url="http://jdli.tw.freebsd.org/publication/book/freebsd2/index.htm">Using FreeBSD</ulink> (in Chinese).</para>	25	url="http://jdli.tw.FreeBSD.org/publication/book/freebsd2/index.htm">Using FreeBSD</ulink> (in Chinese).</para>
26	</listitem>	26	</listitem>
27		27
28	<listitem>	28	<listitem>
Lines 82-88 Link Here
82	</listitem>	82	</listitem>
83		83
84	<listitem>	84	<listitem>
85	<para><ulink url="http://www.freebsd-corp-net-guide.com">The	85	<para><ulink url="http://www.freebsd-corp-net-guide.com/">The
86	FreeBSD Corporate Networker's Guide</ulink>, published by	86	FreeBSD Corporate Networker's Guide</ulink>, published by
87	<ulink url="http://www.awl.com/aw/">Addison-Wesley</ulink>.</para>	87	<ulink url="http://www.awl.com/aw/">Addison-Wesley</ulink>.</para>
88	</listitem>	88	</listitem>
Lines 444-450 Link Here
444		444
445	<listitem>	445	<listitem>
446	<para><emphasis>The BSD family tree</emphasis>. 1997. <ulink	446	<para><emphasis>The BSD family tree</emphasis>. 1997. <ulink
447	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree</ulink> or <ulink url="file:/usr/share/misc/bsd-family-tree">local</ulink> on a FreeBSD-current machine.</para>	447	url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree">&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree</ulink> or <ulink url="file:/usr/share/misc/bsd-family-tree">local</ulink> on a FreeBSD-current machine.</para>
448	</listitem>	448	</listitem>
449		449
450	<listitem>	450	<listitem>

Lines 154-160 Link Here

(-)en_US.ISO8859-1/books/handbook/contrib/chapter.sgml (-4 / +4 lines)
154		154
155	<indexterm><primary>problem reports database</primary></indexterm>	155	<indexterm><primary>problem reports database</primary></indexterm>
156	<para>The <ulink	156	<para>The <ulink
157	url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD PR	157	url="&url.cgi.server;/cgi/query-pr-summary.cgi">FreeBSD PR
158	list</ulink> shows all the current active problem reports and	158	list</ulink> shows all the current active problem reports and
159	requests for enhancement that have been submitted by FreeBSD users.	159	requests for enhancement that have been submitted by FreeBSD users.
160	Look through the open PRs, and see if anything there takes your	160	Look through the open PRs, and see if anything there takes your
Lines 189-195 Link Here
189		189
190	<para>If you find a bug or are submitting a specific change, please	190	<para>If you find a bug or are submitting a specific change, please
191	report it using the &man.send-pr.1; program or its <ulink	191	report it using the &man.send-pr.1; program or its <ulink
192	url="http://www.FreeBSD.org/send-pr.html">WEB-based	192	url="&url.top.level;/send-pr.html">WEB-based
193	equivalent</ulink>. Try to fill-in each field of the bug report.	193	equivalent</ulink>. Try to fill-in each field of the bug report.
194	Unless they exceed 65KB, include any patches directly in the report.	194	Unless they exceed 65KB, include any patches directly in the report.
195	If the patch is suitable to be applied to the source tree put	195	If the patch is suitable to be applied to the source tree put
Lines 198-204 Link Here
198	because cut-and-paste turns tabs into spaces and makes them unusable.	198	because cut-and-paste turns tabs into spaces and makes them unusable.
199	Consider compressing patches and using &man.uuencode.1; if they exceed	199	Consider compressing patches and using &man.uuencode.1; if they exceed
200	20KB. Upload very large submissions to <ulink	200	20KB. Upload very large submissions to <ulink
201	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/">ftp.FreeBSD.org:/pub/FreeBSD/incoming/</ulink>.</para>	201	url="&url.ftp.server;/pub/FreeBSD/incoming/">&url.ftp.server;/pub/FreeBSD/incoming/</ulink>.</para>
202		202
203	<para>After filing a report, you should receive confirmation along with	203	<para>After filing a report, you should receive confirmation along with
204	a tracking number. Keep this tracking number so that you can update	204	a tracking number. Keep this tracking number so that you can update
Lines 414-420 Link Here
414		414
415	<para>More information about the FreeBSD Foundation can be	415	<para>More information about the FreeBSD Foundation can be
416	found in <ulink	416	found in <ulink
417	url="http://people.freebsd.org/~jdp/foundation/announcement.html">The	417	url="&url.people.server;/~jdp/foundation/announcement.html">The
418	FreeBSD Foundation -- an Introduction</ulink>. To contact	418	FreeBSD Foundation -- an Introduction</ulink>. To contact
419	the Foundation by email, write to	419	the Foundation by email, write to
420	<email>bod@FreeBSDFoundation.org</email>.</para>	420	<email>bod@FreeBSDFoundation.org</email>.</para>

Lines 227-233 Link Here

(-)en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml (-7 / +7 lines)
227	<listitem>	227	<listitem>
228	<para>Use the <link linkend="cvsup">cvsup</link> program	228	<para>Use the <link linkend="cvsup">cvsup</link> program
229	with <ulink	229	with <ulink
230	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this	230	url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/standard-supfile">this
231	supfile</ulink>. This is the second most recommended	231	supfile</ulink>. This is the second most recommended
232	method, since it allows you to grab the entire	232	method, since it allows you to grab the entire
233	collection once and then only what has changed from then	233	collection once and then only what has changed from then
Lines 236-242 Link Here
236	sources up-to-date automatically. For a fairly easy	236	sources up-to-date automatically. For a fairly easy
237	interface to this, simply type:</para>	237	interface to this, simply type:</para>
238		238
239	<blockquote><screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></screen></blockquote>	239	<blockquote><screen>&prompt.root; <userinput>pkg_add -f &url.ftp.server;/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></screen></blockquote>
240	</listitem>	240	</listitem>
241	<indexterm>	241	<indexterm>
242	<primary>-CURRENT</primary>	242	<primary>-CURRENT</primary>
Lines 247-253 Link Here
247	<para>Use <command>ftp</command>. The source tree for	247	<para>Use <command>ftp</command>. The source tree for
248	&os.current; is always <quote>exported</quote> on:	248	&os.current; is always <quote>exported</quote> on:
249	<ulink	249	<ulink
250	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/</ulink>.	250	url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/">&url.ftp.server;/pub/FreeBSD/FreeBSD-current/</ulink>.
251	Our FTP server also allows	251	Our FTP server also allows
252	compressed/tarred grabbing of whole trees. e.g. you	252	compressed/tarred grabbing of whole trees. e.g. you
253	see:</para>	253	see:</para>
Lines 345-351 Link Here
345	support them for many years. For a complete description	345	support them for many years. For a complete description
346	of the current security policy for old releases of	346	of the current security policy for old releases of
347	FreeBSD, please see <ulink	347	FreeBSD, please see <ulink
348	url="http://www.FreeBSD.org">http://www.FreeBSD.org/security</ulink></para>	348	url="&url.top.level;/security/index.html">&url.home.page;/security/</ulink></para>
349	</footnote>	349	</footnote>
350	, and tracking an entire development branch just	350	, and tracking an entire development branch just
351	for security reasons is likely to bring in a lot of unwanted	351	for security reasons is likely to bring in a lot of unwanted
Lines 440-446 Link Here
440	<listitem>	440	<listitem>
441	<para>Use the <link linkend="cvsup">cvsup</link> program	441	<para>Use the <link linkend="cvsup">cvsup</link> program
442	with <ulink	442	with <ulink
443	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/stable-supfile">this	443	url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/share/examples/cvsup/stable-supfile">this
444	supfile</ulink>. This is the second most recommended	444	supfile</ulink>. This is the second most recommended
445	method, since it allows you to grab the entire	445	method, since it allows you to grab the entire
446	collection once and then only what has changed from then	446	collection once and then only what has changed from then
Lines 449-455 Link Here
449	sources up-to-date automatically. For a fairly easy	449	sources up-to-date automatically. For a fairly easy
450	interface to this, simply type:</para>	450	interface to this, simply type:</para>
451		451
452	<blockquote><screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></screen></blockquote>	452	<blockquote><screen>&prompt.root; <userinput>pkg_add -f &url.ftp.server;/pub/FreeBSD/development/CVSup/cvsupit.tgz</userinput></screen></blockquote>
453	</listitem>	453	</listitem>
454		454
455	<indexterm>	455	<indexterm>
Lines 460-466 Link Here
460	<para>Use <command>ftp</command>. The source tree for	460	<para>Use <command>ftp</command>. The source tree for
461	&os.stable; is always <quote>exported</quote> on:	461	&os.stable; is always <quote>exported</quote> on:
462	<ulink	462	<ulink
463	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/</ulink></para>	463	url="&url.ftp.server;/pub/FreeBSD/FreeBSD-stable/">&url.ftp.server;/pub/FreeBSD/FreeBSD-stable/</ulink></para>
464		464
465	<para>Our FTP server also allows	465	<para>Our FTP server also allows
466	compressed/tarred grabbing of whole trees. e.g. you	466	compressed/tarred grabbing of whole trees. e.g. you

Lines 41-47 Link Here

(-)en_US.ISO8859-1/books/handbook/eresources/chapter.sgml (-5 / +5 lines)
41	the project.</para>	41	the project.</para>
42		42
43	<para>Archives are kept for all of the mailing lists and can be searched	43	<para>Archives are kept for all of the mailing lists and can be searched
44	using the <ulink url="http://www.FreeBSD.org/search.html">FreeBSD World	44	using the <ulink url="&url.top.level;/search/index.html">FreeBSD World
45	Wide Web server</ulink>. The keyword searchable archive offers an	45	Wide Web server</ulink>. The keyword searchable archive offers an
46	excellent way of finding answers to frequently asked questions and	46	excellent way of finding answers to frequently asked questions and
47	should be consulted before posting a question.</para>	47	should be consulted before posting a question.</para>
Lines 392-398 Link Here
392		392
393	<row>	393	<row>
394	<entry>freebsd-www</entry>	394	<entry>freebsd-www</entry>
395	<entry>Maintainers of <ulink url="http://www.FreeBSD.org">www.freebsd.org</ulink></entry>	395	<entry>Maintainers of <ulink url="&url.top.level;/index.html">www.FreeBSD.org</ulink></entry>
396	</row>	396	</row>
397	</tbody>	397	</tbody>
398	</tgroup>	398	</tgroup>
Lines 692-698 Link Here
692	touch a part of the system where a bug may adversely affect	692	touch a part of the system where a bug may adversely affect
693	the integrity of the system.</para>	693	the integrity of the system.</para>
694		694
695	<!-- I can't actually find a charter for this, but there's this email: http://www.freebsd.org/cgi/getmsg.cgi?fetch=223347+225804+/usr/local/www/db/text/2000/cvs-all/20001210.cvs-all -->	695	<!-- I can't actually find a charter for this, but there's this email: &url.cgi.server;/cgi/getmsg.cgi?fetch=223347+225804+/usr/local/www/db/text/2000/cvs-all/20001210.cvs-all -->
696	</listitem>	696	</listitem>
697	</varlistentry>	697	</varlistentry>
698		698
Lines 721-727 Link Here
721	Whenever possible, bugs should be submitted using the	721	Whenever possible, bugs should be submitted using the
722	&man.send-pr.1;	722	&man.send-pr.1;
723	command or the <ulink	723	command or the <ulink
724	url="http://www.FreeBSD.org/send-pr.html">WEB	724	url="&url.top.level;/send-pr.html">WEB
725	interface</ulink> to it.</para>	725	interface</ulink> to it.</para>
726	</listitem>	726	</listitem>
727	</varlistentry>	727	</varlistentry>
Lines 1259-1265 Link Here
1259	<itemizedlist>	1259	<itemizedlist>
1260	<listitem>	1260	<listitem>
1261	<para><ulink	1261	<para><ulink
1262	url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>	1262	url="&url.top.level;/index.html">&url.home.page;/</ulink>
1263	— Central Server.</para>	1263	— Central Server.</para>
1264	</listitem>	1264	</listitem>
1265		1265

Lines 451-460 Link Here

(-)en_US.ISO8859-1/books/handbook/install/chapter.sgml (-15 / +15 lines)
451	<para>Information about all the releases, including the errata for each	451	<para>Information about all the releases, including the errata for each
452	release, can be found on the	452	release, can be found on the
453	<ulink	453	<ulink
454	url="http://www.FreeBSD.org/releases/index.html">release	454	url="&url.top.level;/releases/index.html">release
455	information</ulink> section of the	455	information</ulink> section of the
456	<ulink	456	<ulink
457	url="http://www.FreeBSD.org/">FreeBSD web site</ulink>.</para>	457	url="&url.top.level;/index.html">FreeBSD web site</ulink>.</para>
458	</sect2>	458	</sect2>
459		459
460	<sect2 id="install-floppies">	460	<sect2 id="install-floppies">
Lines 497-503 Link Here
497	<para>The boot discs are available on your installation media	497	<para>The boot discs are available on your installation media
498	in the floppies directory, and	498	in the floppies directory, and
499	can also be downloaded from the <ulink	499	can also be downloaded from the <ulink
500	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">	500	url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">
501	floppies directory</ulink>.</para>	501	floppies directory</ulink>.</para>
502		502
503	<para>The floppy images have a <filename>.flp</filename> extension.	503	<para>The floppy images have a <filename>.flp</filename> extension.
Lines 564-570 Link Here
564	Adjust the command line as necessary, depending on where you have	564	Adjust the command line as necessary, depending on where you have
565	placed the <filename>.flp</filename> files. If you do not have	565	placed the <filename>.flp</filename> files. If you do not have
566	the CDROM, then <command>fdimage</command> can be downloaded from	566	the CDROM, then <command>fdimage</command> can be downloaded from
567	the <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename>tools</filename> directory</ulink> on the FreeBSD FTP site.</para>	567	the <ulink url="&url.ftp.server;/pub/FreeBSD/tools/"><filename>tools</filename> directory</ulink> on the FreeBSD FTP site.</para>
568		568
569	<para>If you are writing the floppies on a Unix system (such as	569	<para>If you are writing the floppies on a Unix system (such as
570	another FreeBSD system) you can use the &man.dd.1; command to	570	another FreeBSD system) you can use the &man.dd.1; command to
Lines 694-700 Link Here
694	BIOS drive C: is disk3	694	BIOS drive C: is disk3
695	BIOS 639kB/64512kB available memory	695	BIOS 639kB/64512kB available memory
696	FreeBSD/i386 bootstrap loader, Revision 0.8	696	FreeBSD/i386 bootstrap loader, Revision 0.8
697	(jkh@bento.freebsd.org, Mon Nov 20 11:41:23 GMT 2000)	697	(jkh@bento.FreeBSD.org, Mon Nov 20 11:41:23 GMT 2000)
698	\|	698	\|
699	Hit [Enter] to boot immediately, or any other key for command prompt.	699	Hit [Enter] to boot immediately, or any other key for command prompt.
700	Booting [kernel] in 9 seconds... _</screen>	700	Booting [kernel] in 9 seconds... _</screen>
Lines 2559-2565 Link Here
2559		2559
2560	For more information on the ports collection & the latest ports,	2560	For more information on the ports collection & the latest ports,
2561	visit:	2561	visit:
2562	http://www.freebsd.org/ports	2562	http://www.FreeBSD.org/ports
2563		2563
2564	[ Yes ] No</screen>	2564	[ Yes ] No</screen>
2565		2565
Lines 2784-2790 Link Here
2784		2784
2785	<para>For detailed information on Local Area Networks and	2785	<para>For detailed information on Local Area Networks and
2786	configuring FreeBSD as a gateway/router refer to the tutorial	2786	configuring FreeBSD as a gateway/router refer to the tutorial
2787	<ulink url="http://www.FreeBSD.org/tutorials/ppp/index.html">	2787	<ulink url="&url.top.books;/ppp-primer/index.html">
2788	PPP- Pendantic PPP Primer</ulink>.</para>	2788	PPP- Pendantic PPP Primer</ulink>.</para>
2789		2789
2790	<screen> User Confirmation Requested	2790	<screen> User Confirmation Requested
Lines 3199-3205 Link Here
3199		3199
3200	<para>More information about security profiles can be found in the	3200	<para>More information about security profiles can be found in the
3201	<ulink	3201	<ulink
3202	url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/install.html#SECURITY-PROFILES">	3202	url="&url.top.books;/faq/install.html#SECURITY-PROFILES">
3203	FreeBSD FAQ</ulink>.</para>	3203	FreeBSD FAQ</ulink>.</para>
3204		3204
3205	<screen> User Confirmation Requested	3205	<screen> User Confirmation Requested
Lines 4698-4707 Link Here
4698	read input from a local keyboard. Enough of that now,	4698	read input from a local keyboard. Enough of that now,
4699	let's get back to getting these disk images.</para>	4699	let's get back to getting these disk images.</para>
4700		4700
4701	<para>You will need to get <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/kern.flp">kern.flp</ulink> and	4701	<para>You will need to get <ulink url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/kern.flp">kern.flp</ulink> and
4702	<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/mfsroot.flp">	4702	<ulink url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/mfsroot.flp">
4703	mfsroot.flp</ulink> from the	4703	mfsroot.flp</ulink> from the
4704	<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">	4704	<ulink url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">
4705	floppies directory</ulink>.</para>	4705	floppies directory</ulink>.</para>
4706		4706
4707	</step>	4707	</step>
Lines 4738-4744 Link Here
4738	placed the <filename>.flp</filename> files. If you do not	4738	placed the <filename>.flp</filename> files. If you do not
4739	have the CDROM then <command>fdimage</command> can be	4739	have the CDROM then <command>fdimage</command> can be
4740	downloaded from the <ulink	4740	downloaded from the <ulink
4741	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/"><filename>tools</filename>	4741	url="&url.ftp.server;/pub/FreeBSD/tools/"><filename>tools</filename>
4742	directory</ulink> on the FreeBSD FTP site.</para>	4742	directory</ulink> on the FreeBSD FTP site.</para>
4743		4743
4744	<para>If you are writing the floppies on a Unix system (such	4744	<para>If you are writing the floppies on a Unix system (such
Lines 5031-5041 Link Here
5031		5031
5032	<para>If you do not have a CDROM drive, you can download the	5032	<para>If you do not have a CDROM drive, you can download the
5033	distribution from <ulink	5033	distribution from <ulink
5034	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">	5034	url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/">
5035	ftp.FreeBSD.org</ulink>. Each distribution is in its own directory;	5035	ftp.FreeBSD.org</ulink>. Each distribution is in its own directory;
5036	for example, the <emphasis>bin</emphasis> distribution can be	5036	for example, the <emphasis>bin</emphasis> distribution can be
5037	found in the <ulink	5037	found in the <ulink
5038	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/bin">&rel.current;/bin</ulink> directory.</para>	5038	url="&url.ftp.server;/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/bin/">&rel.current;/bin/</ulink> directory.</para>
5039		5039
5040	<para>For as many distributions you wish to install from an MS-DOS	5040	<para>For as many distributions you wish to install from an MS-DOS
5041	partition (and you have the free space for), install each one	5041	partition (and you have the free space for), install each one
Lines 5122-5128 Link Here
5122	specific to your modem, as the PPP dialer provides only a very	5122	specific to your modem, as the PPP dialer provides only a very
5123	simple terminal emulator. Please refer	5123	simple terminal emulator. Please refer
5124	to the user-ppp <link linkend="userppp">handbook</link> and <ulink	5124	to the user-ppp <link linkend="userppp">handbook</link> and <ulink
5125	url="../FAQ/ppp.html">FAQ</ulink> entries for further	5125	url="&url.top.books;/faq/ppp.html">FAQ</ulink> entries for further
5126	information. If you have problems, logging can be directed to	5126	information. If you have problems, logging can be directed to
5127	the screen using the command <command>set log local	5127	the screen using the command <command>set log local
5128	...</command>.</para>	5128	...</command>.</para>

Lines 58-65 Link Here

(-)en_US.ISO8859-1/books/handbook/introduction/chapter.sgml (-10 / +10 lines)
58	read about <link linkend="history">the history of FreeBSD</link>,	58	read about <link linkend="history">the history of FreeBSD</link>,
59	or the <link linkend="relnotes">current release</link>. If you	59	or the <link linkend="relnotes">current release</link>. If you
60	are interested in contributing something to the Project (code,	60	are interested in contributing something to the Project (code,
61	hardware, unmarked bills), see the <ulink url="	61	hardware, unmarked bills), see the <ulink
62	http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributing/article.html">Contributing to FreeBSD</ulink> article.</para>	62	url="&url.top.articles;/contributing/index.html">Contributing to FreeBSD</ulink> article.</para>
63		63
64	<sect2>	64	<sect2>
65	<title>What Can FreeBSD Do?</title>	65	<title>What Can FreeBSD Do?</title>
Lines 587-593 Link Here
587	<para>Long-term development projects continue to take place in the	587	<para>Long-term development projects continue to take place in the
588	5.0-CURRENT (trunk) branch, and SNAPshot releases of 5.0 on	588	5.0-CURRENT (trunk) branch, and SNAPshot releases of 5.0 on
589	CDROM (and, of course, on the net) are continually made available	589	CDROM (and, of course, on the net) are continually made available
590	from <ulink url="ftp://current.freebsd.org/pub/FreeBSD/snapshots">	590	from <ulink url="ftp://current.FreeBSD.org/pub/FreeBSD/snapshots/">
591	the snapshot server</ulink> as work progresses.</para>	591	the snapshot server</ulink> as work progresses.</para>
592	</sect2>	592	</sect2>
593		593
Lines 658-664 Link Here
658	process, FreeBSD being literally built from the contributions	658	process, FreeBSD being literally built from the contributions
659	of hundreds of people around the world, as can be seen from	659	of hundreds of people around the world, as can be seen from
660	our our <ulink	660	our our <ulink
661	url="../../articles/contributors/article.html">list of	661	url="&url.top.articles;/contributors/article.html">list of
662	contributors</ulink>. We are constantly on the lookout for	662	contributors</ulink>. We are constantly on the lookout for
663	new developers and ideas, and those interested in becoming	663	new developers and ideas, and those interested in becoming
664	more closely involved with the project need simply contact us	664	more closely involved with the project need simply contact us
Lines 685-694 Link Here
685	</indexterm>	685	</indexterm>
686	<listitem>	686	<listitem>
687	<para>The central source tree for FreeBSD is maintained by	687	<para>The central source tree for FreeBSD is maintained by
688	<ulink url="http://www.cyclic.com/CVS/index_html">CVS</ulink>	688	<ulink url="http://www.cvshome.org/">CVS</ulink>
689	(Concurrent Versions System), a freely available source code	689	(Concurrent Versions System), a freely available source code
690	control tool that comes bundled with FreeBSD. The primary	690	control tool that comes bundled with FreeBSD. The primary
691	<ulink url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVS	691	<ulink url="&url.cgi.server;/cgi/cvsweb.cgi">CVS
692	repository</ulink> resides on a machine in Santa Clara CA, USA	692	repository</ulink> resides on a machine in Santa Clara CA, USA
693	from where it is replicated to numerous mirror machines	693	from where it is replicated to numerous mirror machines
694	throughout the world. The CVS tree, as well as the <link	694	throughout the world. The CVS tree, as well as the <link
Lines 743-749 Link Here
743	ensuring that some large portion of the system works as	743	ensuring that some large portion of the system works as
744	advertised. For a complete list of FreeBSD developers	744	advertised. For a complete list of FreeBSD developers
745	and their areas of responsibility, please see the <ulink	745	and their areas of responsibility, please see the <ulink
746	url="../../articles/contributors/article.html">Contributors	746	url="&url.top.articles;/contributors/article.html">Contributors
747	List</ulink></para>	747	List</ulink></para>
748		748
749	<note>	749	<note>
Lines 774-780 Link Here
774	such things are discussed.</para>	774	such things are discussed.</para>
775		775
776	<para><citetitle><ulink	776	<para><citetitle><ulink
777	url="../../article/contributors/article.html">The	777	url="&url.top.articles;/contributors/article.html">The
778	FreeBSD Contributors List</ulink></citetitle> is a long	778	FreeBSD Contributors List</ulink></citetitle> is a long
779	and growing one, so why not join it by contributing	779	and growing one, so why not join it by contributing
780	something back to FreeBSD today?</para>	780	something back to FreeBSD today?</para>
Lines 782-788 Link Here
782	<para>Providing code is not the only way of contributing to	782	<para>Providing code is not the only way of contributing to
783	the project; for a more complete list of things that need	783	the project; for a more complete list of things that need
784	doing, please refer to the <ulink	784	doing, please refer to the <ulink
785	url="http://www.FreeBSD.org">FreeBSD Project web	785	url="&url.top.level;/index.html">FreeBSD Project web
786	site</ulink>.</para>	786	site</ulink>.</para>
787	</listitem>	787	</listitem>
788	</varlistentry>	788	</varlistentry>
Lines 888-894 Link Here
888		888
889	<para>You can also view the master (and most frequently updated)	889	<para>You can also view the master (and most frequently updated)
890	copies at <ulink	890	copies at <ulink
891	url="http://www.FreeBSD.org/">http://www.FreeBSD.org/</ulink>.</para>	891	url="&url.top.level;/index.html">&url.home.page;/</ulink>.</para>
892	</sect2>	892	</sect2>
893	</sect1>	893	</sect1>
894	</chapter>	894	</chapter>

Lines 166-172 Link Here

(-)en_US.ISO8859-1/books/handbook/l10n/chapter.sgml (-3 / +3 lines)
166	implementation, users may be required to compile an application	166	implementation, users may be required to compile an application
167	with wide or multibyte characters support, or configure it correctly.	167	with wide or multibyte characters support, or configure it correctly.
168	To be able to input and process wide or multibyte characters, the <ulink	168	To be able to input and process wide or multibyte characters, the <ulink
169	url="/ports/">FreeBSD Ports collection</ulink> has provided	169	url="&url.top.level;/ports/index.html">FreeBSD Ports collection</ulink> has provided
170	each language with different programs. Refer to the I18N	170	each language with different programs. Refer to the I18N
171	documentation in the respective FreeBSD Port.</para>	171	documentation in the respective FreeBSD Port.</para>
172		172
Lines 889-895 Link Here
889	<title>Traditional Chinese Localization for Taiwan</title>	889	<title>Traditional Chinese Localization for Taiwan</title>
890	<indexterm><primary>Traditional Chinese localization</primary></indexterm>	890	<indexterm><primary>Traditional Chinese localization</primary></indexterm>
891	<para>The FreeBSD-Taiwan Project has an I18N/L10N tutorial for	891	<para>The FreeBSD-Taiwan Project has an I18N/L10N tutorial for
892	FreeBSD at <ulink url="http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/index.html">http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/index.html</ulink>	892	FreeBSD at <ulink url="http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/">http://freebsd.sinica.edu.tw/~ncvs/zh-l10n-tut/</ulink>
893	using many <port>chinese/*</port> applications.	893	using many <port>chinese/*</port> applications.
894	The editor for the <literal>zh-L10N-tut</literal> is Clive Lin	894	The editor for the <literal>zh-L10N-tut</literal> is Clive Lin
895	<email>Clive@CirX.org</email>. You can also cvsup the following	895	<email>Clive@CirX.org</email>. You can also cvsup the following
Lines 959-965 Link Here
959		959
960	<para>Some FreeBSD contributors have translated parts of FreeBSD to	960	<para>Some FreeBSD contributors have translated parts of FreeBSD to
961	other languages. They are available through links on the <ulink	961	other languages. They are available through links on the <ulink
962	url="../">main site</ulink> or in	962	url="&url.top.level;/index.html">main site</ulink> or in
963	<filename>/usr/share/doc</filename>.</para>	963	<filename>/usr/share/doc</filename>.</para>
964	</sect2>	964	</sect2>
965	</sect1>	965	</sect1>

Lines 161-167 Link Here

(-)en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml (-3 / +3 lines)
161		161
162	<para>This is by far the easiest method to use when installing the	162	<para>This is by far the easiest method to use when installing the
163	runtime libraries. It is just like installing any other port	163	runtime libraries. It is just like installing any other port
164	from the <ulink url="/usr/ports/">ports collection</ulink>.	164	from the <ulink url="file://localhost/usr/ports/">ports collection</ulink>.
165	Simply do the following:</para>	165	Simply do the following:</para>
166		166
167	<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base</userinput>	167	<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base</userinput>
Lines 1139-1145 Link Here
1139	<sect3 id="install-via-ftp">	1139	<sect3 id="install-via-ftp">
1140	<title>Installation via FTP</title> <para>Get the diskimages	1140	<title>Installation via FTP</title> <para>Get the diskimages
1141	kern.flp and mfsroot.flp and put them on floppy disks (I got	1141	kern.flp and mfsroot.flp and put them on floppy disks (I got
1142	mine from ftp7.de.freebsd.org. Please choose the appropriate	1142	mine from ftp7.de.FreeBSD.org. Please choose the appropriate
1143	mirror).</para>	1143	mirror).</para>
1144		1144
1145	<screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput>	1145	<screen>&prompt.root; <userinput>dd if=kern.flp of=/dev/fd0</userinput>
Lines 1309-1315 Link Here
1309	are not out of date):</para>	1309	are not out of date):</para>
1310		1310
1311	<itemizedlist>	1311	<itemizedlist>
1312	<listitem><para>ftp7.de.freebsd.org/pub/FreeBSD/distfiles/rpm</para></listitem>	1312	<listitem><para>ftp7.de.FreeBSD.org/pub/FreeBSD/distfiles/rpm</para></listitem>
1313	<listitem><para>ftp.redhat.com/pub/redhat/linux/6.1/en/os/i386/RedHat/RPMS</para></listitem>	1313	<listitem><para>ftp.redhat.com/pub/redhat/linux/6.1/en/os/i386/RedHat/RPMS</para></listitem>
1314	</itemizedlist>	1314	</itemizedlist>
1315		1315

Lines 136-142 Link Here

(-)en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml (-10 / +10 lines)
136		136
137	<blockquote>	137	<blockquote>
138	<para><ulink	138	<para><ulink
139	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/">ftp://ftp.FreeBSD.org/pub/FreeBSD/</ulink>.</para>	139	url="&url.ftp.server;/pub/FreeBSD/">&url.ftp.server;/pub/FreeBSD/</ulink>.</para>
140	</blockquote></para>	140	</blockquote></para>
141		141
142	<para>The <ulink	142	<para>The <ulink
Lines 1196-1202 Link Here
1196		1196
1197	<listitem>	1197	<listitem>
1198	<para><ulink	1198	<para><ulink
1199	url="http://www.FreeBSD.org/cgi/cvsweb.cgi">CVSWeb</ulink> is	1199	url="&url.cgi.server;/cgi/cvsweb.cgi">CVSWeb</ulink> is
1200	the FreeBSD Project web interface for CVS.</para>	1200	the FreeBSD Project web interface for CVS.</para>
1201	</listitem>	1201	</listitem>
1202	</itemizedlist>	1202	</itemizedlist>
Lines 1261-1267 Link Here
1261	directly from:</para>	1261	directly from:</para>
1262		1262
1263	<para><ulink	1263	<para><ulink
1264	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm/">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm/</ulink></para>	1264	url="&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm/">&url.ftp.server;/pub/FreeBSD/FreeBSD-current/src/usr.sbin/ctm/</ulink></para>
1265		1265
1266	<para>The <quote>deltas</quote> you feed	1266	<para>The <quote>deltas</quote> you feed
1267	<application>CTM</application> can be had two ways, FTP or	1267	<application>CTM</application> can be had two ways, FTP or
Lines 1270-1276 Link Here
1270	<application>CTM</application>:</para>	1270	<application>CTM</application>:</para>
1271		1271
1272	<para><ulink	1272	<para><ulink
1273	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/</ulink></para>	1273	url="&url.ftp.server;/pub/FreeBSD/CTM/">&url.ftp.server;/pub/FreeBSD/CTM/</ulink></para>
1274		1274
1275	<para>or see section <link	1275	<para>or see section <link
1276	linkend="mirrors-ctm">mirrors</link>.</para>	1276	linkend="mirrors-ctm">mirrors</link>.</para>
Lines 1503-1509 Link Here
1503	<itemizedlist>	1503	<itemizedlist>
1504	<listitem>	1504	<listitem>
1505	<para><ulink	1505	<para><ulink
1506	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/">ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/</ulink></para>	1506	url="&url.ftp.server;/pub/FreeBSD/development/CTM/">&url.ftp.server;/pub/FreeBSD/development/CTM/</ulink></para>
1507	</listitem>	1507	</listitem>
1508	</itemizedlist>	1508	</itemizedlist>
1509	</listitem>	1509	</listitem>
Lines 1562-1568 Link Here
1562	<para>If you did not find a mirror near to you or the mirror is	1562	<para>If you did not find a mirror near to you or the mirror is
1563	incomplete, try <ulink url="http://ftpsearch.ntnu.no/">FTP	1563	incomplete, try <ulink url="http://ftpsearch.ntnu.no/">FTP
1564	search</ulink> at <ulink	1564	search</ulink> at <ulink
1565	url="http://ftpsearch.ntnu.no/ftpsearch/">http://ftpsearch.ntnu.no/ftpsearch</ulink>.	1565	url="http://ftpsearch.ntnu.no/ftpsearch/">http://ftpsearch.ntnu.no/ftpsearch/</ulink>.
1566	FTP search is a great free archie server in Trondheim, Norway.</para>	1566	FTP search is a great free archie server in Trondheim, Norway.</para>
1567	</sect2></sect1>	1567	</sect2></sect1>
1568		1568
Lines 1625-1631 Link Here
1625	single package which will install it, set up the configuration	1625	single package which will install it, set up the configuration
1626	file and start the transfer via a pointy-clicky type of	1626	file and start the transfer via a pointy-clicky type of
1627	interface, then get the <ulink	1627	interface, then get the <ulink
1628	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz">cvsupit</ulink>	1628	url="&url.ftp.server;/pub/FreeBSD/development/CVSup/cvsupit.tgz">cvsupit</ulink>
1629	package. Just hand it to &man.pkg.add.1; and it will lead you	1629	package. Just hand it to &man.pkg.add.1; and it will lead you
1630	through the configuration process in a menu-oriented	1630	through the configuration process in a menu-oriented
1631	fashion.</para>	1631	fashion.</para>
Lines 2936-2942 Link Here
2936		2936
2937	<listitem>	2937	<listitem>
2938	<para>cvsup2.ca.FreeBSD.org (maintainer	2938	<para>cvsup2.ca.FreeBSD.org (maintainer
2939	<email>hostmaster@ca.freebsd.org</email>)</para>	2939	<email>hostmaster@ca.FreeBSD.org</email>)</para>
2940	</listitem>	2940	</listitem>
2941	</itemizedlist>	2941	</itemizedlist>
2942	</listitem>	2942	</listitem>
Lines 3062-3068 Link Here
3062		3062
3063	<listitem>	3063	<listitem>
3064	<para>cvsup5.de.FreeBSD.org (maintainer	3064	<para>cvsup5.de.FreeBSD.org (maintainer
3065	<email>rse@freebsd.org</email>)</para>	3065	<email>rse@FreeBSD.org</email>)</para>
3066	</listitem>	3066	</listitem>
3067	</itemizedlist>	3067	</itemizedlist>
3068	</listitem>	3068	</listitem>
Lines 3388-3394 Link Here
3388	<itemizedlist>	3388	<itemizedlist>
3389	<listitem>	3389	<listitem>
3390	<para>cvsup.tw.FreeBSD.org (maintainer	3390	<para>cvsup.tw.FreeBSD.org (maintainer
3391	<email>jdli@freebsd.csie.nctu.edu.tw</email>)</para>	3391	<email>jdli@FreeBSD.csie.nctu.edu.tw</email>)</para>
3392	</listitem>	3392	</listitem>
3393		3393
3394	<listitem>	3394	<listitem>

Lines 200-206 Link Here

(-)en_US.ISO8859-1/books/handbook/ports/chapter.sgml (-12 / +12 lines)
200	</itemizedlist>	200	</itemizedlist>
201		201
202	<para>To keep track of updated ports, subscribe to the	202	<para>To keep track of updated ports, subscribe to the
203	<email>freebsd-ports@freebsd.org</email> mailing list.</para>	203	<email>freebsd-ports@FreeBSD.org</email> mailing list.</para>
204		204
205	<para>The remainder of this chapter will explain how to use packages and	205	<para>The remainder of this chapter will explain how to use packages and
206	ports to install and manage third party software on FreeBSD.</para>	206	ports to install and manage third party software on FreeBSD.</para>
Lines 220-226 Link Here
220	<listitem>	220	<listitem>
221	<para>The FreeBSD web site maintains an up-to-date searchable list of	221	<para>The FreeBSD web site maintains an up-to-date searchable list of
222	all the available applications, at	222	all the available applications, at
223	<ulink url="http://www.FreeBSD.org/ports/">http://www.FreeBSD.org/ports/</ulink>.	223	<ulink url="&url.top.level;/ports/index.html">&url.home.page;/ports/</ulink>.
224	The name space is divided in to categories, and you may either	224	The name space is divided in to categories, and you may either
225	search for an application by name (if you know it), or you can list	225	search for an application by name (if you know it), or you can list
226	all the applications available in a category.</para>	226	all the applications available in a category.</para>
Lines 281-289 Link Here
281	<example>	281	<example>
282	<title>Downloading a Package and then Installing It Locally</title>	282	<title>Downloading a Package and then Installing It Locally</title>
283		283
284	<screen>&prompt.root; <userinput>ftp -a <replaceable>ftp2.freebsd.org</replaceable></userinput>	284	<screen>&prompt.root; <userinput>ftp -a <replaceable>ftp2.FreeBSD.org</replaceable></userinput>
285	Connected to ftp2.freebsd.org.	285	Connected to ftp2.FreeBSD.org.
286	220 ftp2.freebsd.org FTP server (Version 6.00LS) ready.	286	220 ftp2.FreeBSD.org FTP server (Version 6.00LS) ready.
287	331 Guest login ok, send your email address as password.	287	331 Guest login ok, send your email address as password.
288	230-	288	230-
289	230- This machine is in Vienna, VA, USA, hosted by Verio.	289	230- This machine is in Vienna, VA, USA, hosted by Verio.
Lines 322-329 Link Here
322		322
323	<para>Package files are distributed in .tgz format. You can	323	<para>Package files are distributed in .tgz format. You can
324	find them at <ulink	324	find them at <ulink
325	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">	325	url="&url.ftp.server;/pub/FreeBSD/ports/packages/">
326	ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/</ulink>,	326	&url.ftp.server;/pub/FreeBSD/ports/packages/</ulink>,
327	or on the FreeBSD CDROM distribution. Every CD on the	327	or on the FreeBSD CDROM distribution. Every CD on the
328	FreeBSD 4-CD set (and PowerPak, etc) contains packages in	328	FreeBSD 4-CD set (and PowerPak, etc) contains packages in
329	the <filename>/packages</filename> directory. The layout of	329	the <filename>/packages</filename> directory. The layout of
Lines 507-513 Link Here
507	<para>Before we get into that however, you will need to choose a	507	<para>Before we get into that however, you will need to choose a
508	port to install. There are a few ways to do this, with the	508	port to install. There are a few ways to do this, with the
509	easiest method being the <ulink	509	easiest method being the <ulink
510	url="http://www.FreeBSD.org/ports/">ports listing on the FreeBSD	510	url="&url.top.level;/ports/index.html">ports listing on the FreeBSD
511	web site</ulink>. You can browse through the ports listed there	511	web site</ulink>. You can browse through the ports listed there
512	or use the search function on the site. Each port also includes	512	or use the search function on the site. Each port also includes
513	a description so you can read a bit about each port before	513	a description so you can read a bit about each port before
Lines 669-675 Link Here
669		669
670	<screen>&prompt.root; <userinput>make install</userinput>	670	<screen>&prompt.root; <userinput>make install</userinput>
671	>> lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/.	671	>> lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
672	>> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.	672	>> Attempting to fetch from &url.ftp.server;/pub/FreeBSD/ports/distfiles/.
673	Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%	673	Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
674	439860 bytes transferred in 18.0 seconds (23.90 kBps)	674	439860 bytes transferred in 18.0 seconds (23.90 kBps)
675	===> Extracting for lsof-4.57	675	===> Extracting for lsof-4.57
Lines 973-979 Link Here
973		973
974	<screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>	974	<screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
975	&prompt.root; <userinput>make MASTER_SITE_OVERRIDE= \	975	&prompt.root; <userinput>make MASTER_SITE_OVERRIDE= \
976	ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>	976	&url.ftp.server;/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
977	</answer>	977	</answer>
978	</qandaentry>	978	</qandaentry>
979		979
Lines 1288-1294 Link Here
1288	<orderedlist>	1288	<orderedlist>
1289	<listitem>	1289	<listitem>
1290	<para>Fix it! The <ulink	1290	<para>Fix it! The <ulink
1291	url="http://www.FreeBSD.org/porters-handbook/index.html">Porter's	1291	url="&url.top.books;/porters-handbook/index.html">Porter's
1292	Handbook</ulink> includes detailed information on the	1292	Handbook</ulink> includes detailed information on the
1293	"Ports" infrastructure so that you can fix the occasional	1293	"Ports" infrastructure so that you can fix the occasional
1294	broken port or even submit your own!</para>	1294	broken port or even submit your own!</para>
Lines 1311-1317 Link Here
1311	<para>Grab the package from an ftp site near you. The	1311	<para>Grab the package from an ftp site near you. The
1312	<quote>master</quote> package collection is on <hostid	1312	<quote>master</quote> package collection is on <hostid
1313	role="fqdn">ftp.FreeBSD.org</hostid> in the <ulink	1313	role="fqdn">ftp.FreeBSD.org</hostid> in the <ulink
1314	URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/">packages	1314	URL="&url.ftp.server;/pub/FreeBSD/ports/packages/">packages
1315	directory</ulink>, but be sure to check your local mirror	1315	directory</ulink>, but be sure to check your local mirror
1316	<emphasis>first!</emphasis> These are more likely to work	1316	<emphasis>first!</emphasis> These are more likely to work
1317	than trying to compile from source and are a lot faster as	1317	than trying to compile from source and are a lot faster as

Lines 321-327 Link Here

(-)en_US.ISO8859-1/books/porters-handbook/book.sgml (-8 / +8 lines)
321	directory or the <filename>pkgname.tgz</filename> package, so delete	321	directory or the <filename>pkgname.tgz</filename> package, so delete
322	them now. Next, simply include the output of <command>shar `find	322	them now. Next, simply include the output of <command>shar `find
323	port_dir`</command> in a bug report and send it with the	323	port_dir`</command> in a bug report and send it with the
324	&man.send-pr.1; program (see <ulink url="../handbook/contrib-how.html#CONTRIB-GENERAL">Bug	324	&man.send-pr.1; program (see <ulink url="&url.top.articles;/contributing/contrib-how.html#CONTRIB-GENERAL">Bug
325	Reports and General Commentary</ulink> for more information about	325	Reports and General Commentary</ulink> for more information about
326	&man.send-pr.1;. If the uncompressed port is larger than 20KB,	326	&man.send-pr.1;. If the uncompressed port is larger than 20KB,
327	you should compress it into a tarfile and use &man.uuencode.1;	327	you should compress it into a tarfile and use &man.uuencode.1;
Lines 399-405 Link Here
399	cannot find the required files in <makevar>DISTDIR</makevar> it	399	cannot find the required files in <makevar>DISTDIR</makevar> it
400	will look up the URL <makevar>MASTER_SITES</makevar>, which is	400	will look up the URL <makevar>MASTER_SITES</makevar>, which is
401	set in the Makefile, as well as our main FTP site at <ulink	401	set in the Makefile, as well as our main FTP site at <ulink
402	url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/">ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/</ulink>,	402	url="&url.ftp.server;/pub/FreeBSD/ports/distfiles/">&url.ftp.server;/pub/FreeBSD/ports/distfiles/</ulink>,
403	where we put sanctioned distfiles as backup. It will then	403	where we put sanctioned distfiles as backup. It will then
404	attempt to fetch the named distribution file with	404	attempt to fetch the named distribution file with
405	<makevar>FETCH</makevar>, assuming that the requesting site has	405	<makevar>FETCH</makevar>, assuming that the requesting site has
Lines 1062-1068 Link Here
1062	--><emphasis>:-)</emphasis></para>	1062	--><emphasis>:-)</emphasis></para>
1063		1063
1064	<para>For a detailed description of the responsibilities of maintainers,	1064	<para>For a detailed description of the responsibilities of maintainers,
1065	refer to the <ulink url="../handbook/policies.html#POLICIES-MAINTAINER">MAINTAINER on	1065	refer to the <ulink url="&url.top.books;/developers-handbook/policies.html#POLICIES-MAINTAINER">MAINTAINER on
1066	Makefiles</ulink> section.</para>	1066	Makefiles</ulink> section.</para>
1067	</sect1>	1067	</sect1>
1068		1068
Lines 1621-1627 Link Here
1621	<chapter>	1621	<chapter>
1622	<title>Shared library versions</title>	1622	<title>Shared library versions</title>
1623		1623
1624	<para>Please read our <ulink url="../developers-handbook/policies-shlib.html">policy on	1624	<para>Please read our <ulink url="&url.top.books;/developers-handbook/policies-shlib.html">policy on
1625	shared library versioning</ulink> to understand what to do with	1625	shared library versioning</ulink> to understand what to do with
1626	shared library versions in general. Do not blindly assume software	1626	shared library versions in general. Do not blindly assume software
1627	authors know what they are doing; many of them do not. It is very	1627	authors know what they are doing; many of them do not. It is very
Lines 2320-2326 Link Here
2320	port. You can find them in the	2320	port. You can find them in the
2321	<filename>ports/ports-current</filename> directory of the FTP mirror	2321	<filename>ports/ports-current</filename> directory of the FTP mirror
2322	sites. You may also use CVSup to keep your whole ports collection	2322	sites. You may also use CVSup to keep your whole ports collection
2323	up-to-date, as described in <ulink url="../handbook/synching.html#CVSUP-CONFIG">the Handbook</ulink>.</para>	2323	up-to-date, as described in <ulink url="&url.top.books;/handbook/synching.html#CVSUP-CONFIG">the Handbook</ulink>.</para>
2324		2324
2325	<para>The next step is to send a mail to the maintainer, if one is	2325	<para>The next step is to send a mail to the maintainer, if one is
2326	listed in the port's <filename>Makefile</filename>. That person may	2326	listed in the port's <filename>Makefile</filename>. That person may
Lines 2356-2362 Link Here
2356	the porting process.You should check your own port against this list,	2356	the porting process.You should check your own port against this list,
2357	but you can also check ports in the PR database that others have	2357	but you can also check ports in the PR database that others have
2358	submitted. Submit any comments on ports you check as described in	2358	submitted. Submit any comments on ports you check as described in
2359	<ulink url="../handbook/contrib-how.html#CONTRIB-GENERAL">Bug Reports and General	2359	<ulink url="&url.top.articles;/contributing/contrib-how.html#CONTRIB-GENERAL">Bug Reports and General
2360	Commentary</ulink>. Checking ports in the PR database will both make	2360	Commentary</ulink>. Checking ports in the PR database will both make
2361	it faster for us to commit them, and prove that you know what you are	2361	it faster for us to commit them, and prove that you know what you are
2362	doing.</para>	2362	doing.</para>
Lines 2418-2424 Link Here
2418	<para>Do not write anything to files outside	2418	<para>Do not write anything to files outside
2419	<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only	2419	<makevar>WRKDIR</makevar>. <makevar>WRKDIR</makevar> is the only
2420	place that is guaranteed to be writable during the port build (see	2420	place that is guaranteed to be writable during the port build (see
2421	<ulink url="../handbook/ports-using.html#PORTS-CD">compiling ports from CDROM</ulink> for an	2421	<ulink url="&url.top.books;/handbook/ports-using.html#PORTS-CD">compiling ports from CDROM</ulink> for an
2422	example of building ports from a read-only tree). If you need to	2422	example of building ports from a read-only tree). If you need to
2423	modify one of the <filename>pkg-<replaceable>*</replaceable></filename>	2423	modify one of the <filename>pkg-<replaceable>*</replaceable></filename>
2424	files, do so by <link	2424	files, do so by <link
Lines 4540-4546 Link Here
4540	&a.ports;. Important changes to the way ports work will be announced	4540	&a.ports;. Important changes to the way ports work will be announced
4541	there. You can always find more detailed information on the latest	4541	there. You can always find more detailed information on the latest
4542	changes by looking at <ulink	4542	changes by looking at <ulink
4543	url="http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk"> the	4543	url="&url.cgi.server;/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk"> the
4544	bsd.port.mk CVS log</ulink>.</para>	4544	bsd.port.mk CVS log</ulink>.</para>
4545	</chapter>	4545	</chapter>
4546		4546

Lines 1040-1054 Link Here

(-)en_US.ISO8859-1/books/ppp-primer/book.sgml (-7 / +7 lines)
1040	</listitem>	1040	</listitem>
1041		1041
1042	<listitem>	1042	<listitem>
1043	<para>The IBM Network (<ulink URL="http://www.ibm.net">http://www.ibm.net</ulink>)</para>	1043	<para>The IBM Network (<ulink URL="http://www.ibm.net/">http://www.ibm.net/</ulink>)</para>
1044	</listitem>	1044	</listitem>
1045		1045
1046	<listitem>	1046	<listitem>
1047	<para>AT&T WorldNet (<ulink URL="http://att.com/worldnet">http://att.com/worldnet</ulink>)</para>	1047	<para>AT&T WorldNet (<ulink URL="http://att.com/worldnet/">http://att.com/worldnet/</ulink>)</para>
1048	</listitem>	1048	</listitem>
1049		1049
1050	<listitem>	1050	<listitem>
1051	<para>Erol's (<ulink URL="http://www.erols.com">http://www.erols.com</ulink>)</para>	1051	<para>Erol's (<ulink URL="http://www.erols.com/">http://www.erols.com/</ulink>)</para>
1052	</listitem>	1052	</listitem>
1053		1053
1054	</itemizedlist>	1054	</itemizedlist>
Lines 1415-1421 Link Here
1415	they need to be properly configured. Note that this section does not	1415	they need to be properly configured. Note that this section does not
1416	explain how to configure the Windows workstations for Dial-Up	1416	explain how to configure the Windows workstations for Dial-Up
1417	networking. If you need a good explanation of that procedure, I	1417	networking. If you need a good explanation of that procedure, I
1418	recommend <ulink URL="http://www.aladdin.co.uk/techweb">http://www.aladdin.co.uk/techweb</ulink>.</para>	1418	recommend <ulink URL="http://www.aladdin.co.uk/techweb/">http://www.aladdin.co.uk/techweb/</ulink>.</para>
1419		1419
1420		1420
1421	<sect1>	1421	<sect1>
Lines 1580-1586 Link Here
1580	Configuration" and "Bindings" tabs are not necessary.</para>	1580	Configuration" and "Bindings" tabs are not necessary.</para>
1581		1581
1582	<para>If you wish to use the Windows Internet Naming Service ("WINS")	1582	<para>If you wish to use the Windows Internet Naming Service ("WINS")
1583	your attention is invited to <ulink URL="http://www.localnet.org">http://www.localnet.org</ulink> for	1583	your attention is invited to <ulink URL="http://www.localnet.org/">http://www.localnet.org/</ulink> for
1584	more information about WINS settings, specifically regarding sharing	1584	more information about WINS settings, specifically regarding sharing
1585	files transparently across the Internet.</para>	1585	files transparently across the Internet.</para>
1586		1586
Lines 1778-1784 Link Here
1778	"Routing" tabs are not used.</para>	1778	"Routing" tabs are not used.</para>
1779		1779
1780	<para>If you wish to use the Windows Internet Naming Service ("WINS")	1780	<para>If you wish to use the Windows Internet Naming Service ("WINS")
1781	your attention is invited to <ulink URL="http://www.localnet.org">http://www.localnet.org</ulink> for	1781	your attention is invited to <ulink URL="http://www.localnet.org/">http://www.localnet.org/</ulink> for
1782	more information about WINS settings, specifically regarding sharing	1782	more information about WINS settings, specifically regarding sharing
1783	files transparently across the Internet.</para>	1783	files transparently across the Internet.</para>
1784		1784
Lines 1813-1819 Link Here
1813	requires that the Microsoft TCP/IP-32 driver diskette has been	1813	requires that the Microsoft TCP/IP-32 driver diskette has been
1814	installed on the workstation. The TCP/IP drivers are not included	1814	installed on the workstation. The TCP/IP drivers are not included
1815	with the WfW CD or diskettes; if you need a copy they're available at	1815	with the WfW CD or diskettes; if you need a copy they're available at
1816	<ulink URL="ftp://ftp.microsoft.com:/peropsys/windows/public/tcpip">ftp://ftp.microsoft.com:/peropsys/windows/public/tcpip</ulink>.</para>	1816	<ulink URL="ftp://ftp.microsoft.com/peropsys/windows/public/tcpip/">ftp://ftp.microsoft.com/peropsys/windows/public/tcpip/</ulink>.</para>
1817		1817
1818	<para>Once the TCP/IP drivers have been loaded, perform the following	1818	<para>Once the TCP/IP drivers have been loaded, perform the following
1819	steps:</para>	1819	steps:</para>

Lines 127-132 Link Here

(-)share/mk/doc.docbook.mk (-5 / +7 lines)
127		127
128	CSS_SHEET?= ${DOC_PREFIX}/share/misc/docbook.css	128	CSS_SHEET?= ${DOC_PREFIX}/share/misc/docbook.css
129		129
		130	TOPLEVEL?= -1
		131
130	PRINTOPTS?= -ioutput.print	132	PRINTOPTS?= -ioutput.print
131		133
132	.if defined(BOOK_OUTPUT)	134	.if defined(BOOK_OUTPUT)
Lines 298-317 Link Here
298	all: ${_docs}	300	all: ${_docs}
299		301
300	index.html HTML.manifest: ${SRCS} ${LOCAL_IMAGES_LIB} ${IMAGES_PNG} ${INDEX_SGML} ${HTML_SPLIT_INDEX} docbook.css	302	index.html HTML.manifest: ${SRCS} ${LOCAL_IMAGES_LIB} ${IMAGES_PNG} ${INDEX_SGML} ${HTML_SPLIT_INDEX} docbook.css
301	${JADE} -V html-manifest -ioutput.html -ioutput.html.images ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC}	303	${JADE} -V html-manifest -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC}
302	.if !defined(NO_TIDY)	304	.if !defined(NO_TIDY)
303	-tidy -i -m -f /dev/null ${TIDYFLAGS} `xargs < HTML.manifest`	305	-tidy -i -m -f /dev/null ${TIDYFLAGS} `xargs < HTML.manifest`
304	.endif	306	.endif
305		307
306	${DOC}.html: ${SRCS} ${LOCAL_IMAGES_LIB} ${IMAGES_PNG} ${INDEX_SGML} ${HTML_INDEX} docbook.css	308	${DOC}.html: ${SRCS} ${LOCAL_IMAGES_LIB} ${IMAGES_PNG} ${INDEX_SGML} ${HTML_INDEX} docbook.css
307	${JADE} -ioutput.html -ioutput.html.images -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > ${.TARGET} \|\| (rm -f ${.TARGET} && false)	309	${JADE} -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > ${.TARGET} \|\| (rm -f ${.TARGET} && false)
308	.if !defined(NO_TIDY)	310	.if !defined(NO_TIDY)
309	-tidy -i -m -f /dev/null ${TIDYFLAGS} ${.TARGET}	311	-tidy -i -m -f /dev/null ${TIDYFLAGS} ${.TARGET}
310	.endif	312	.endif
311		313
312	# Special target to produce HTML with no images in it.	314	# Special target to produce HTML with no images in it.
313	${DOC}.html-text: ${SRCS} ${INDEX_SGML} ${HTML_INDEX}	315	${DOC}.html-text: ${SRCS} ${INDEX_SGML} ${HTML_INDEX}
314	${JADE} -ioutput.html -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > ${.TARGET} \|\| (rm -f ${.TARGET} && false)	316	${JADE} -ioutput.html -iurl.top.level.${TOPLEVEL} -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > ${.TARGET} \|\| (rm -f ${.TARGET} && false)
315		317
316	${DOC}.html-split.tar: HTML.manifest	318	${DOC}.html-split.tar: HTML.manifest
317	tar cf ${.TARGET} `xargs < HTML.manifest`	319	tar cf ${.TARGET} `xargs < HTML.manifest`
Lines 407-417 Link Here
407	.endif	409	.endif
408		410
409	${HTML_INDEX}:	411	${HTML_INDEX}:
410	${JADE} -V html-index -ioutput.html -ioutput.html.images -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > /dev/null	412	${JADE} -V html-index -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images -V nochunks ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > /dev/null
411	perl ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -g -o ${INDEX_SGML} ${.TARGET}	413	perl ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -g -o ${INDEX_SGML} ${.TARGET}
412		414
413	${HTML_SPLIT_INDEX}:	415	${HTML_SPLIT_INDEX}:
414	${JADE} -V html-index -ioutput.html -ioutput.html.images ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > /dev/null	416	${JADE} -V html-index -ioutput.html -iurl.top.level.${TOPLEVEL} -ioutput.html.images ${JADEOPTS} -d ${DSLHTML} -t sgml ${MASTERDOC} > /dev/null
415	perl ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -g -o ${INDEX_SGML} ${.TARGET}	417	perl ${PREFIX}/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -g -o ${INDEX_SGML} ${.TARGET}
416		418
417	${PRINT_INDEX}: ${HTML_INDEX}	419	${PRINT_INDEX}: ${HTML_INDEX}

Lines 118-120 Link Here

(-)share/sgml/freebsd.dtd (+45 lines)
118	<!ENTITY prompt.root "<prompt>#</prompt>">	118	<!ENTITY prompt.root "<prompt>#</prompt>">
119	<!ENTITY prompt.user "<prompt>%</prompt>">	119	<!ENTITY prompt.user "<prompt>%</prompt>">
120		120
		121	<!-- maybe the following entities should go in freebsd.ent ?
		122	in which case, it should be included w/in every book -->
		123
		124	<!ENTITY url.www.server "http://www.FreeBSD.org">
		125	<!ENTITY url.cgi.server "&url.www.server;">
		126	<!ENTITY url.stat.server "&url.www.server;">
		127	<!ENTITY url.docs.server "http://docs.FreeBSD.org">
		128	<!ENTITY url.people.server "http://people.FreeBSD.org">
		129	<!ENTITY url.ftp.server "ftp://ftp.FreeBSD.org">
		130
		131	<![ %output.html.images; [
		132	<!ENTITY % url.top.level.-1 "IGNORE">
		133	<!ENTITY % url.top.level.0 "IGNORE">
		134	<!ENTITY % url.top.level.1 "IGNORE">
		135	<!ENTITY % url.top.level.2 "IGNORE">
		136	<!ENTITY % url.top.level.3 "IGNORE">
		137	<!ENTITY % url.top.level.4 "IGNORE">
		138	<![ %url.top.level.0; [
		139	<!ENTITY url.top.level ".">
		140	]]>
		141	<![ %url.top.level.1; [
		142	<!ENTITY url.top.level "..">
		143	]]>
		144	<![ %url.top.level.2; [
		145	<!ENTITY url.top.level "../..">
		146	]]>
		147	<![ %url.top.level.3; [
		148	<!ENTITY url.top.level "../../..">
		149	]]>
		150	<![ %url.top.level.4; [
		151	<!ENTITY url.top.level "../../../..">
		152	]]>
		153	]]>
		154
		155	<!ENTITY url.home.page "&url.www.server;">
		156
		157	<!-- not % output.html -->
		158	<!ENTITY url.top.level "&url.home.page;">
		159
		160	<!-- where to find articles and books -->
		161	<!ENTITY url.doc.enUS "doc/en_US.ISO8859-1">
		162	<!ENTITY url.www.articles "&url.home.page;/&url.doc.enUS;/articles">
		163	<!ENTITY url.www.books "&url.home.page;/&url.doc.enUS;/books">
		164	<!ENTITY url.top.articles "&url.top.level;/&url.doc.enUS;/articles">
		165	<!ENTITY url.top.books "&url.top.level;/&url.doc.enUS;/books">

Lines 135-137 Link Here

(-)share/sgml/freebsd41.dtd (+45 lines)
135	<!ENTITY prompt.root "<prompt>#</prompt>">	135	<!ENTITY prompt.root "<prompt>#</prompt>">
136	<!ENTITY prompt.user "<prompt>%</prompt>">	136	<!ENTITY prompt.user "<prompt>%</prompt>">
137		137
		138	<!-- maybe the following entities should go in freebsd.ent ?
		139	in which case, it should be included w/in every book -->
		140
		141	<!ENTITY url.www.server "http://www.FreeBSD.org">
		142	<!ENTITY url.cgi.server "&url.www.server;">
		143	<!ENTITY url.stat.server "&url.www.server;">
		144	<!ENTITY url.docs.server "http://docs.FreeBSD.org">
		145	<!ENTITY url.people.server "http://people.FreeBSD.org">
		146	<!ENTITY url.ftp.server "ftp://ftp.FreeBSD.org">
		147
		148	<![ %output.html.images; [
		149	<!ENTITY % url.top.level.-1 "IGNORE">
		150	<!ENTITY % url.top.level.0 "IGNORE">
		151	<!ENTITY % url.top.level.1 "IGNORE">
		152	<!ENTITY % url.top.level.2 "IGNORE">
		153	<!ENTITY % url.top.level.3 "IGNORE">
		154	<!ENTITY % url.top.level.4 "IGNORE">
		155	<![ %url.top.level.0; [
		156	<!ENTITY url.top.level ".">
		157	]]>
		158	<![ %url.top.level.1; [
		159	<!ENTITY url.top.level "..">
		160	]]>
		161	<![ %url.top.level.2; [
		162	<!ENTITY url.top.level "../..">
		163	]]>
		164	<![ %url.top.level.3; [
		165	<!ENTITY url.top.level "../../..">
		166	]]>
		167	<![ %url.top.level.4; [
		168	<!ENTITY url.top.level "../../../..">
		169	]]>
		170	]]>
		171
		172	<!ENTITY url.home.page "&url.www.server;">
		173
		174	<!-- not % output.html -->
		175	<!ENTITY url.top.level "&url.home.page;">
		176
		177	<!-- where to find articles and books -->
		178	<!ENTITY url.doc.enUS "doc/en_US.ISO8859-1">
		179	<!ENTITY url.www.articles "&url.home.page;/&url.doc.enUS;/articles">
		180	<!ENTITY url.www.books "&url.home.page;/&url.doc.enUS;/books">
		181	<!ENTITY url.top.articles "&url.top.level;/&url.doc.enUS;/articles">
		182	<!ENTITY url.top.books "&url.top.level;/&url.doc.enUS;/books">

Lines 9-23 Link Here

(-)www/en/doc/Makefile (-5 / +7 lines)
9	# requirements here.	9	# requirements here.
10	#	10	#
11		11
		12	TOPLEVEL?= 4
		13
12	all:	14	all:
13	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html all)	15	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html TOPLEVEL=${TOPLEVEL} INSTALL_COMPRESSED= all)
14	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html DOCDIR=${.CURDIR} install)	16	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html TOPLEVEL=${TOPLEVEL} INSTALL_COMPRESSED= DOCDIR=${.CURDIR} install)
15	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1/books/handbook && ${MAKE} pgpkeyring > ${.CURDIR}/pgpkeyring.txt)	17	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1/books/handbook && ${MAKE} TOPLEVEL=${TOPLEVEL} pgpkeyring > ${.CURDIR}/pgpkeyring.txt)
16		18
17	install clean:	19	install clean:
18	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html DOCDIR=${DESTDIR}/data/doc ${.TARGET})	20	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1 && ${MAKE} FORMATS=html-split\ html TOPLEVEL=${TOPLEVEL} INSTALL_COMPRESSED= DOCDIR=${DESTDIR}/data/doc ${.TARGET})
19	.if make(install)	21	.if make(install)
20	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1/books/handbook && ${MAKE} pgpkeyring > ${DESTDIR}/data/doc/pgpkeyring.txt)	22	(unset DESTDIR \|\| true; cd ${.CURDIR}/../../../doc/en_US.ISO8859-1/books/handbook && ${MAKE} TOPLEVEL=${TOPLEVEL} pgpkeyring > ${DESTDIR}/data/doc/pgpkeyring.txt)
21	.endif	23	.endif
22	.if make(clean)	24	.if make(clean)
23	rm -rf en* handbook faq pgpkeyring.txt	25	rm -rf en* handbook faq pgpkeyring.txt