<para>¦Ó packages ¥H¤Î ports ¥¦­Ì³£¬O¤@¼Ë¡A³£·|»{ <emphasis>dependencies(³nÅé¬Û¨ÌÃö«Y)</emphasis>¡C

    <para>¦Ó packages ¥H¤Î ports ¥¦­Ì³£¬O¤@¼Ë·|»{ <emphasis>dependencies(³nÅé¬Û¨ÌÃö«Y)</emphasis>¡C

	<para>If you know the exact name of the port, but just need to

	<para>­Yª¾¹D¸Ó port ªº¥¿½T¦WºÙ¡A¦ý¤£ª¾¹D©ñ¦b­þ­Ó¤ÀÃþ¥Ø¿ý¡A

        find out which category it is in, you can use the

        ¥i¥H¥Î &man.whereis.1; «ü¥O¨Ó§ä¥X¨Ó¡C

        &man.whereis.1; command.

	¥u­n¥´ <command>whereis

	Simply type <command>whereis

        <replaceable>file</replaceable></command> §Y¥i¡A¦Ó 

        <replaceable>file</replaceable></command>, where

        <replaceable>file</replaceable> ªº¦a¤è½Ð§ï¬°·Q¸Ëªº³nÅé¦WºÙ¡C

        <replaceable>file</replaceable> is the program you want to

        ­Y§ä¨ì¸Ó³nÅé¡A´N·|§i¶D§A¡A´N¹³¤U­±³o¼Ë¡G</para>

        install.  If it is found on your system, you will be told

        where it is, as follows:</para>

      <para>This tells us that <command>lsof</command> (a system

      <para>¦p¦¹¤@¨Ó¡A´N·|ª¾¹D <command>lsof</command> (¨t²Î¤u¨ãµ{¦¡) ¬O©ñ¦b 

	utility) can be found in the

	<filename>/usr/ports/sysutils/lsof</filename> ¥Ø¿ý¡C</para></listitem>

	<filename>/usr/ports/sysutils/lsof</filename>

	directory.</para></listitem>

	<para>Yet another way to find a particular port is by using the

	<para>ÁÙ¦³¥t¤@©Û¡A´N¬O¥Î Ports Collection ¥»¨­¤º«Øªº·j´M¾÷¨î¡C

        Ports Collection's built-in search mechanism.  To use the

        ­n¥Îªº®É­Ô¡A½Ð¥ý¤Á´«¨ì <filename>/usr/ports</filename> ¥Ø¿ý¡C

        search feature, you will need to be in the

        µM«á¡A¥´ <command>make search 

        <filename>/usr/ports</filename> directory.  Once in that

	name=<replaceable>program-name</replaceable></command>¡A¨ä¤¤

        directory, run <command>make search

        <replaceable>program-name</replaceable> ½Ð§ï¬°·Q§äªº³nÅé¦WºÙ¡C

        name=<replaceable>program-name</replaceable></command> where

        Á|¨Ò¨Ó»¡¡A­Y­n§äªº¬O <command>lsof</command> ªº¸Ü¡A¨º»ò´N¬O¡G</para>

        <replaceable>program-name</replaceable> is the name of the

        program you want to find.  For example, if you were looking

        for <command>lsof</command>:</para>

      <para>The part of the output you want to pay particular

      <para>³o¨Ç·j´Mµ²ªG¤¤¡A­nª`·Nªº¬O <quote>Path:</quote> ³o¦æ¡A

        attention to is the <quote>Path:</quote> line, since that

        ¦]¬°³o¦æ·|§i¶D§A¥i¥H¦b­þÃä§ä¨ì¸Ó port¡C

        tells you where to find the port.  The other information

	¦Ó·j´Mµ²ªGªº¨ä¥L³¡¤À¡A¦]¬°»P port ¦w¸Ë¸ûµLÃö«Y¡A©Ò¥H³o¸Ì´N¤£Á¿¤F¡C</para>

        provided is not needed in order to install the port, so it

        will not be covered here.</para>

      <para>­Y­n§ó¹ý©³ªº·j´M¡A¨º»ò¥i¥H§ï¥Î <command>make

        search key=<replaceable>string</replaceable></command>¡A¨ä¤¤ 

      <para>For more in-depth searching you can also use <command>make

        <replaceable>string</replaceable> ½Ð§ï¬°·Q·j´MªºÃöÁä¦r¡C

       search key=<replaceable>string</replaceable></command> where

        ¦p¦¹¤@¨Ó·|§ä port ¦WºÙ¡B³nÅ鲤¶(comments)¡B³nÅé±Ô­zÀÉ(descriptions)

       <replaceable>string</replaceable> is some text to search for.

        ¥H¤Î³nÅé¬Û¨ÌÃö«Y(dependencies)¸Ì­±¬O§_¦³²Å¦XÃöÁä¦r¡A

       This searches port names, comments, descriptions and

        ¦¹¥~¡A¤£²M·¡³nÅé¦WºÙªº¸Ü¡A¤]¥i¥H®³¨Ó§ä¦³²Å¦XÃöÁä¦r¥DÃDªº port¡C</para>

       dependencies and can be used to find ports which relate to a

       particular subject if you do not know the name of the program

      <para>­èÁ¿ªº³o¨âºØ¤è¦¡¡A·j´M¦r²´³£¬O case-insensitive(¤£¥²°Ï¤À¤j¤p¼g)¡C

       you are looking for.</para>

        ¤ñ¦p¡A·j´M <quote>LSOF</quote> »P <quote>lsof</quote> ¨âªÌµ²ªG³£·|¬O¤@¼Ëªº¡C</para>

      <para>In both of these cases, the search string is case-insensitive.

       Searching for <quote>LSOF</quote> will yield the same results as 

       searching for <quote>lsof</quote>.</para>

      <para>If you do not have a source of local packages (such as a

      <para>­Y¤âÃä¨S¦³ package ¨Ó·½(¹³¬O FreeBSD ¥úºÐ)ªº¸Ü¡A

        FreeBSD CD-ROM set) then it will probably be easier to use the

        ¨º»ò«Øij¨Ï¥Î &man.pkg.add.1; ®É¡A¥[¤W <option>-r</option> 

        <option>-r</option> option to &man.pkg.add.1;.  This will

	¿ï¶µ¨Ó§ó»´ÃP¦w¸Ë package¡C¦p¦¹¤@¨Ó¡A´N·|¦Û°Ê§PÂ_¥¿½Tªº package ®æ¦¡¡B

        cause the utility to automatically determine the correct

	¥H¤Î©Ò·f°tªº§@·~¨t²Î release ª©¥»¡A

        object format and release and then fetch and install the

	µM«á·|¦Û¤v±q FTP ¯¸§ì¦^¡B¦w¸Ë¬Û¹ïÀ³ªº package¡C

        package from an FTP site.

      <para>The example above would download the correct package and

      <para>¤W­±³o¨Ò¤l·|¦Û°Ê¤U¸ü¥¿½Tªº package ¨Ã¦w¸Ë¡C

	add it without any further user intervention.

	­Y·Q§ï´«¥Î¨ä¥L &os; Packages Mirror ¯¸¡A¨º»ò´N­n³]©w <envar>PACKAGESITE</envar> Àô¹ÒÅܼơA

	If you want to specify an alternative &os; Packages Mirror,

	¦p¦¹¤@¨Ó¤~·|¨ú¥N¹w³]³]©w¡C  &man.pkg.add.1;

	instead of the main distribution site, you have to set

	·|¥Î &man.fetch.3; «ü¥O¨Ó¤U¸üÀɮסA¦Ó &man.fetch.3; ¥»¨­«h·|¨Ï¥Î¬ÛÃöÀô¹ÒÅܼƪº³]©w¡A

	<envar>PACKAGESITE</envar> accordingly, to

	¹³¬O¡G

	override the default settings.  &man.pkg.add.1;

	<envar>FTP_PASSIVE_MODE</envar>¡B<envar>FTP_PROXY</envar> ¥H¤Î 

	uses &man.fetch.3; to download the files, which honors various

	<envar>FTP_PASSWORD</envar>¡C  ¦pªG§Aºô¸ôÀô¹Ò³B©ó firewall «á­±¡A©ÎªÌ»Ý­n¥Î

	environment variables, including

	FTP/HTTP proxy ªº¸Ü¡A¨º»ò´N»Ý­n³]©w¡C ³]©w²Ó¸`½Ð°Ñ¾\ &man.fetch.3;¡C

	<envar>FTP_PASSIVE_MODE</envar>, <envar>FTP_PROXY</envar>, and

	½Ðª`·N¡G¤W­±©Ò»¡ªº¨Ò¤l¬O¼g <literal>lsof</literal> ¦Ó«D 

	<envar>FTP_PASSWORD</envar>.  You may need to set one or more

	<literal>lsof-4.56.4</literal>¡C  ·í¨Ï¥Î»·ºÝ§ì¨ú¥\¯à®É¡A¸Ó package ª©¸¹´N¤£¥²¥[¤W¥h¤F¡C

	of these if you are behind a firewall, or need to use an

	&man.pkg.add.1; ·|¦Û°Ê¤U¸ü¸Ó³nÅ骺³Ì·sª©¦^¨Ó¦w¸Ë¡C</para>

	FTP/HTTP proxy.  See &man.fetch.3; for the complete list.

	Note that in the example above

	<literal>lsof</literal> is used instead of

	<literal>lsof-4.56.4</literal>.  When the remote fetching

	feature is used, the version number of the package must be

	removed.  &man.pkg.add.1; will automatically fetch the latest

	version of the application.</para>

	<para>&man.pkg.add.1; will download the latest version of

	<para>­Y¥Îªº¬O &os.current; ©Î &os.stable; ªº¸Ü¡A&man.pkg.add.1; 

	  your application if you are using &os.current; or

	  ·|¦Û°Ê¤U¸ü¸Ó³nÅé³Ì·sª©¦^¨Ó¡C

	  &os.stable;.  If you run a -RELEASE version, it will grab

	  ­Y¥Îªº¬OÄÝ©ó -RELEASE ª©¥»¡A¨º»ò¥L·|§ì¦^ÄÝ©ó¸Ó release ¤W©Ò½sĶªº package¡C

	  the version of the package that was built with your

	  ¤]¥i¥H§ó§ï <envar>PACKAGESITE</envar> Àô¹ÒÅܼơA¥H§ïÅܤU¸ü¤è¦¡¡C

	  release.  It is possible to change this behavior by

	  Á|¨Ò¨Ó»¡¡A¦pªG¬O &os; 5.4-RELEASE ªº¸Ü¡A¨º»ò &man.pkg.add.1; ¹w³]·|±q

	  overriding the <envar>PACKAGESITE</envar> environment

	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/</literal>

	  variable.  For example, if you run a &os; 5.4-RELEASE

	  ¨Ó§ì package¡C­Y­n±j¨î &man.pkg.add.1; ¤U¸ü &os; 5-STABLE ©Ò¥Îªº package

	  system, by default &man.pkg.add.1; will try to fetch

	  ¡A¨º»ò´N§â <envar>PACKAGESITE</envar> §ï³]¬° 

	  packages from

	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/</literal>§Y¥i¡C

	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/</literal>.

	  If you want to force &man.pkg.add.1; to download

	  &os;&nbsp;5-STABLE packages, set <envar>PACKAGESITE</envar>

	  to

	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/</literal>.

      <para>Package files are distributed in <filename>.tgz</filename>

      <para>Package Àɦ³ <filename>.tgz</filename> ¥H¤Î <filename>.tbz</filename> ¨âºØ®æ¦¡¡C

          and <filename>.tbz</filename> formats.  You can find them at <ulink

          ³o¨Ç³£¥i³z¹L <ulink

          url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/"></ulink>,

          url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/"></ulink>¡A©ÎªÌ FreeBSd ¥úºÐ¤º¨ú±o¡C

          or on the FreeBSD CD-ROM distribution.  Every CD on the

          Every CD on the

          FreeBSD 4-CD set (and the PowerPak, etc.) contains packages

          FreeBSD 4 ¥úºÐ®M¥ó¤º¥H¤Î PowerPak(«Â¤O¥]) µ¥µ¥..¨C¤@¤ù¥úºÐ³£·|¦b <filename>/packages</filename>

          in the <filename>/packages</filename> directory.  The layout

	  ¥Ø¿ý¤º©ñ package¡C¸Ì­±ªº¥Ø¿ý¬[ºcÃþ¦ü <filename>/usr/ports</filename> ªº¥Ø¿ý¬[ºc¡C

          of the packages is similar to that of the

          ¨C­Ó¤ÀÃþ³£¦U¦Û¦³±MÄݥؿý¡A¥B¨C¥÷ package ³£·|©ñ¦b <filename>All</filename> ¥Ø¿ý¤º¡C

          <filename>/usr/ports</filename> tree.  Each category has its

          own directory, and every package can be found within the

          <filename>All</filename> directory.

      <para>The directory structure of the package system matches the

      <para>package ¥Ø¿ý¬[ºc»P port ªº³£¤@­P¡F¥¦­Ì¦@¦Pºc¦¨¾ã­Ó package/port ¨t²Î¾÷¨î¡C</para>

        ports layout; they work with each other to form the entire

        package/port system.

      </para>

      <para>&man.pkg.info.1; is a utility that lists and describes 

      <para>&man.pkg.info.1; ¥i¥Î¨Ó¦C¥X©Ò¦³¤w¦w¸Ëªº³nÅé¡B³nÅ鲤¶¡C</para>

        the various packages installed.

      </para>

      <para>&man.pkg.version.1; is a utility that summarizes the

      <para>&man.pkg.version.1; «h¬O¦C¥X©Ò¦³¤w¦w¸Ëªº³nÅ骩¥»¡C

        versions of all installed packages.  It compares the package 

        ¥¦·|Åã¥Ü¤w¸Ëª©¥»¥H¤Î¥Ø«e¾÷¾¹¤W port tree ªºª©¥»®t²§¡C

        version to the current version found in the ports tree.

      <para>The symbols in the second column indicate the relative age

      <para>²Ä¤GÄ檺²Å¸¹ªí¥Ü¡G¤w¦w¸Ëªº³nÅ骩¥»»P¥Ø«e¾÷¾¹¤W port tree ªºª©¥»®t²§¡C</para>

        of the installed version and the version available in the

        local ports tree.</para>

	    <entry>=</entry> <entry>The version of the

	    <entry>=</entry> <entry>¤w¸Ëªºª©¥»»P¥Ø«e¾÷¾¹¤W port tree ªºª©¥»¬O¦P¤@ª©ªº¡C

	    installed package matches the one found in the

	    </entry>

	    local ports tree.</entry>

	<entry>The installed version is older than the one available

	<entry>»P¥Ø«e¾÷¾¹¤W port tree ª©¥»¬Û¤ñ°_¨Ó¡A¤w¸Ëªºª©¥»¸û¡C</entry>

	in the ports tree.</entry>

        <row><entry>&gt;</entry><entry>The installed version is newer

        <row><entry>&gt;</entry><entry>»P¥Ø«e¾÷¾¹¤W port tree ª©¥»¬Û¤ñ°_¨Ó¡A

          than the one found in the local ports tree. (The local ports

	  ¤w¸Ëªºª©¥»¸û·s¡C(¥i¯à¬O¥Ø«e¾÷¾¹¤W port tree ©|¥¼§ó·s¡C)</entry></row>

          tree is probably out of date.)</entry></row>

        <row><entry>?</entry><entry>¤w¸Ëªº³nÅé¦b ports ¯Á¤Þ¤º§äµL¬ÛÃö¸ê®Æ¡C

        <row><entry>?</entry><entry>The installed package cannot be

	  (³q±`¥i¯à¬O¡AÁ|¨Ò¨Ó»¡¡G¤w¦w¸Ëªº¸Ó port ¤w±q Ports Collection ¤¤²¾°£©Î§ï¦W¤F¡C)

	  found in the ports index.  (This can happen, for instance, if an

	  </entry></row>

	  installed port is removed from the Ports Collection or

	  renamed.)</entry></row>

        <row><entry>*</entry><entry>There are multiple versions of the

        <row><entry>*</entry><entry>¸Ó³nÅé¦P®É¦³³\¦hª©¥»¡C</entry></row>

        package.</entry></row>

	    <application>CVSup</application> Server¡C

	    <application>CVSup</application> ¥D¾÷¡C

	    <para>One may want to use his own

	    <para>­Y·Q§ï¥Î¦Û¤v³]ªº 

	      <filename>ports-supfile</filename>, for example to avoid

	      <filename>ports-supfile</filename>¡A¤ñ¦p»¡¡A¤£·Q¨C¦¸³£±o¥´«ü¥O¨Ó«ü©w©Ò¨Ï¥Îªº 

	      the need of passing the <application>CVSup</application>

	      <application>CVSup</application> ¥D¾÷¡C</para>

	      server on the command line.</para>

		<para>In this case, as <username>root</username>, copy

		<para>³oºØ±¡ªp¤U¡A½Ð¥H <username>root</username> Åv­­§â 

		  to a new location, such as

		  ½Æ»s¨ì¨ä¥L¦ì¸m¡A¤ñ¦p  

		  <filename>/root</filename> or your home

		  <filename>/root</filename> ©ÎªÌ¦Û¤v±b¸¹ªº®a¥Ø¿ý¡C</para>

		  directory.</para>

		<para>Edit <filename>ports-supfile</filename>.</para>

		<para>­×§ï·sªº <filename>ports-supfile</filename> ÀÉ¡C</para>

		<para>Change

		<para>§â 

		  to a <application>CVSup</application> server near

		  §ï¬°Â÷§A¤ñ¸ûªñ(§Ö)ªº <application>CVSup</application> ¥D¾÷¡C

		  you.  See <link linkend="cvsup-mirrors">CVSup

		  ³o³¡¤À¥i¥H°Ñ¾\§¹¾ãªº <link linkend="cvsup-mirrors">CVSup

		  Mirrors</link> (<xref linkend="cvsup-mirrors">) for

		  Mirrors</link> (<xref linkend="cvsup-mirrors">) ¯¸¦Cªí</para>

		  a complete listing of mirror sites.</para>

		<para>And now to run <command>cvsup</command>, use the

		<para>µM«á´N¶}©l¥HÃþ¦ü¤U¦C«ü¥O¶] <command>cvsup</command>¡G</para>

		  following:</para>

	  <para>Running the &man.cvsup.1; command later will download and apply all

	  <para>°õ¦æ &man.cvsup.1; ¤§«á¡A´N·|¶}©l§ó·s Ports Collection¡C

	    the recent changes to your Ports Collection, except

	    ¤£¹L³o°Ê§@¥u¬O¡y§ó·s¡z¨Ã¤£¬O¡y¤É¯Å¡z¡A¤£·|§â¤w¸Ëªº³nÅé­«·s½sĶ¡B¤É¯Å¡C</para>

	    actually rebuilding the ports for your own system.</para>

	<para>&man.portsnap.8; is an alternative system for distributing the

	<para>&man.portsnap.8; ¤]¬O§ó·s Ports Collection ªº¤è¦¡¤§¤@¡C

	  Ports Collection.  It was first included in &os; 6.0.  On older

	  &os;&nbsp;6.0 °_¶}©l¤º«Ø Portsnap ¾÷¨î¡A¦Ó¸ûªº¨t²Î¡A«h¥i³z¹L <filename

	  systems, you can install it from <filename

	  role="package">sysutils/portsnap</filename> port ¨Ó¦w¸Ë¡G</para>

	  role="package">sysutils/portsnap</filename> port:</para>

	<para>Please refer to <link linkend="portsnap">Using Portsnap</link>

	<para><application>Portsnap</application> ²Ó¸`¥\¯à¡A½Ð°Ñ¾\ 

	  for a detailed description of all <application>Portsnap</application>

	  <link linkend="portsnap">Portsnap ¨Ï¥Î½g</link>¡C</para>

	  features.</para>

	  <para>Create an empty directory <filename

	  <para>­Y <filename

	    role="directory">/usr/ports</filename> if it does not exists.</para>

	    role="directory">/usr/ports</filename> ¥Ø¿ý¤£¦s¦bªº¸Ü¡A´N«Ø¥ß¤@¤U§a¡G</para>

	  <para>Download a compressed snapshot of the Ports Collection into

	  <para>±µ¤U¨Ó¡A¤U¸üÀ£ÁYªº Ports Collection ©w´Á§ó·sÀɨì 

	    <filename role="directory">/var/db/portsnap</filename>.  You can

	    <filename role="directory">/var/db/portsnap</filename> ¥Ø¿ý¡C

	    disconnect from the Internet after this step, if you wish.</para>

	    §¹¦¨¤U¸ü«á¡A­nÂ_½u»P§_³£¥i¥H¡C</para>

	  <para>If you are running <application>Portsnap</application> for the

	  <para>­Y¬O²Ä¤@¦¸¶] <application>Portsnap</application> ªº¸Ü¡A«h»Ý­n¥ý¸ÑÀ£¨ì <filename

	    first time, extract the snapshot into <filename

	    role="directory">/usr/ports</filename>¡G

	    role="directory">/usr/ports</filename>:

	  <para>If you already have a populated <filename

	  <para>­Y¤w¦³ <filename

	    role="directory">/usr/ports</filename> and you are just updating,

	    role="directory">/usr/ports</filename> ¦Ó¥B¥u¬O·Q§ó·s¦Ó¤w¡A¨º»ò´N·Ó¤U­±§@¡G</para>

	    run the following command instead:</para>

	<para>This method involves using <application>sysinstall</application>

	<para>³o¤è¦¡­n¥Î <application>sysinstall</application> ³z¹L¦w¸Ë¨Ó·½¨Ó¸Ë Ports Collection¡C

	  to install the Ports Collection from the installation media.  Note

	  ½Ðª`·N¡G©Ò¦w¸Ëªº Ports Collection ª©¥»¥u¬O¸Ó release µo§G®Éªºª©¥»¦Ó¤w¡A¦Ó«D³Ì·s¡C

	  that the old copy of Ports Collection from the date of the release

	  ­Y¯à¤Wºô(Internet)ªº¸Ü¡A½Ð¨Ï¥Î¤W­z¤è¦¡¤§¤@·|¤ñ¸û¦n¡C</para>

	  will be installed.  If you have Internet access, you should always

	  use one of the methods mentioned above.</para>

	  <para>As <username>root</username>, run

	  <para>¥H <username>root</username> Åv­­°õ¦æ

	    <command>sysinstall</command>

	    <command>sysinstall</command> 

	    (<command>/stand/sysinstall</command> in &os;

	    (¦b &os; 5.2 ¤§«eª©¥»«h¬O <command>/stand/sysinstall</command>)¡A¤è¦¡¦p¤U¡G</para>

	    versions older than 5.2) as shown below:</para>

	  <para>Scroll down and select <guimenuitem>Configure</guimenuitem>,

	  <para>½Ð¥H¤è¦VÁä²¾°Ê¿ï¾Ü¶µ¥Ø¡A¿ï¾Ü <guimenuitem>Configure</guimenuitem>¡AµM«á«ö 

	    press <keycap>Enter</keycap>.</para>

	    <keycap>Enter</keycap> Áä¡C</para>

	  <para>Scroll down and select

	  <para>¿ï¾Ü

	    <guimenuitem>Distributions</guimenuitem>, press

	    <guimenuitem>Distributions</guimenuitem>¡AµM«á«ö 

	    <keycap>Enter</keycap>.</para>

	    <keycap>Enter</keycap> Áä¡C</para>

	  <para>Scroll down to <guimenuitem>ports</guimenuitem>, press

	  <para>¿ï¾Ü <guimenuitem>ports</guimenuitem>¡AµM«á«ö 

	    <keycap>Space</keycap>.</para>

	    <keycap>Space</keycap> Áä¡C</para>

	  <para>Scroll up to <guimenuitem>Exit</guimenuitem>, press

	  <para>¿ï <guimenuitem>Exit</guimenuitem>¡AµM«á«ö 

	    <keycap>Enter</keycap>.</para>

	    <keycap>Enter</keycap> Áä¡C</para>

	  <para>Select your desired installation media, such as CDROM,

	  <para>¿ï¾Ü­n¥Îªº¦w¸Ë¨Ó·½¡A¤ñ¦p¡GCDROM(¥úºÐ)¡BFTP µ¥¤è¦¡¡C</para>

	    FTP, and so on.</para>

	  <para>Scroll up to <guimenuitem>Exit</guimenuitem> and press

	  <para>¿ï <guimenuitem>Exit</guimenuitem>¡AµM«á«ö

	    <keycap>Enter</keycap>.</para>

	    <keycap>Enter</keycap> Áä¡C</para>

	  <para>Press <keycap>X</keycap> to exit

	  <para>«ö¤U <keycap>X</keycap> Áä´N¥iÂ÷¶}

	    <application>sysinstall</application>.</para>

	    <application>sysinstall</application> µ{¦¡¡C</para>

      <para>The first thing that should be explained when it comes to

      <para>´£¨ì Ports Collection¡A­º¥ý­n¥ý»¡©úªº¬O¡G¦ó¿× <quote>skeleton</quote>¡C

        the Ports Collection is what is actually meant by a

        ²³æ¨ÓÁ¿¡Aport skeleton ´N¬OÅý³nÅé¦p¦ó¦b FreeBSD ¶¶§Q½sĶ¡B¦w¸Ëªº³Ì°ò¥»ÀɮײզX¡C

        <quote>skeleton</quote>.  In a nutshell, a port skeleton is a

        ¨C¥÷ port skeleton °ò¥»¤W·|¦³¡G</para>

        minimal set of files that tell your FreeBSD system how to

        cleanly compile and install a program.  Each port skeleton

        includes:</para>

	  <para>A <filename>Makefile</filename>.  The

	  <para><filename>Makefile</filename> ÀÉ¡C

	    <filename>Makefile</filename> contains various statements

	    ³o­Ó <filename>Makefile</filename> ¤º®e¦³¤À³\¦h³¡¤À¡A

	    that specify how the application should be compiled and

	    ¬O¥Î¨Ó«ü©w­n¦p¦ó½sĶ¡A¥H¤Î¸Ó¸Ë¦b¨t²Îªº¦ó³B¡C</para>

	    where it should be installed on your system.</para>

	  <para>A <filename>distinfo</filename> file.  This file

	  <para><filename>distinfo</filename> ÀÉ¡C  

	    contains information about the files that must be

	    ½sĶ¸Ó³nÅé©Ò»Ý¤U¸üªºÀɮסBchecksum(ÀËÅçÀÉ®×¥Î)³£·|°O¿ý¦b³oÀÉ¡A

	    downloaded to build the port and their checksums, to

	    ¨Ã·|¥Î &man.md5.1; ¬ÛÃö¤u¨ã¨Ó½T«O©Ò¤U¸üªºÀɮ׬O¥¿½TµL»~ªº¡C</para>

	    verify that files have not been corrupted during the

	    download using &man.md5.1;.</para>

	  <para>A <filename>files</filename> directory.  This

	  <para><filename>files</filename> ¥Ø¿ý¡C ³o¥Ø¿ý©ñªº¬OÅý³nÅ饿±`½sĶ¡B¦w¸Ëªº patch ÀÉ¡C

	    directory contains patches to make the program compile and

	    Patches ÀÉ°ò¥»¤W¬O¤@¨Ç¤pÀɮסA¨Ã°w¹ï¯S©wÀɮרӰµ­×§ï¡A¥B¬O¯Â¤å¦rÀɮ榡¡A

	    install on your FreeBSD system.  Patches are basically

	    °ò¥»¤W¤º®e³q±`·|¹³¬O <quote>Remove line 10(§R°£²Ä 10 ¦æ)</quote> ©Î

	    small files that specify changes to particular files.

	    <quote>Change line 26 to this ...(§â²Ä 26 ¦æ§ï¬°...)</quote> ¤§Ãþªº¡C

	    They are in plain text format, and basically say

	    ³o¨Ç Patches ³q±`¤]ºÙ¬° <quote>diffs</quote>

	    <quote>Remove line 10</quote> or <quote>Change line 26 to

	    ¡A¦]¬°³£¬O¥Ñ &man.diff.1; µ{¦¡©Ò²£¥Íªº¡C</para>

	    this ...</quote>.  Patches are also known as

	    <quote>diffs</quote> because they are generated by the

	    &man.diff.1; program.</para>

	  <para>This directory may also contain other files used to build

	  <para>¦¹¥~¡A¥»¥Ø¿ý¤]¥i¯à·|©ñ¤@¨Ç¨ó§U½sĶ¸Ó port ªºÀɮסC</para>

	    the port.</para>

	  <para>A <filename>pkg-descr</filename> file.  This is a more

	  <para><filename>pkg-descr</filename> ÀÉ¡A¤º®e¬O¤ñ¸û¸Ô²Óªº³nÅ餶²Ð¡A³q±`·|¼g±o¤ñ¸û¦h¦æ¡C</para>

	    detailed, often multiple-line, description of the program.</para>

	  <para>A <filename>pkg-plist</filename> file.  This is a list

	  <para><filename>pkg-plist</filename> ÀÉ¡A¸Ó port ·|¦w¸Ëªº©Ò¦³ÀɮײM³æ¡C

	    of all the files that will be installed by the port.  It

	    ¤]¬O§i¶D¨t²Î¦b²¾°£¸Ó port ®É¡A»Ý­n§R°£­þ¨ÇÀɮסC</para>

	    also tells the ports system what files to remove upon

	    deinstallation.</para>

      <para>Some ports have other files, such as

      <para>¦³¨Ç port ÁÙ·|¦³¨ä¥LÀɮסA¹³¬O <filename>pkg-message</filename> ÀÉ¡C

        <filename>pkg-message</filename>.  The ports system uses these

        port ¨t²Î¦b¤@¨Ç±¡ªp®É¡A·|¥Î³o¨ÇÀɮסC

        files to handle special situations.  If you want more details

        ¦pªG·Qª¾¹D³o¨ÇÀɮתº§ó¦h²Ó¸`¥Î³~¡A¥H¤Î port ¤@¯ë¥Îªk¡A½Ð°Ñ¾\ <ulink

        on these files, and on ports in general, check out the <ulink

        Handbook</ulink>.</para>

        Handbook</ulink>¡C</para>

      <para>The port includes instructions on how to build source

      <para>port ¤º¼gªº¬O§i¶D¨t²Î¦p¦ó½sĶ source code ªº¬ÛÃö«ü¥O¡A¦ý¨Ã¤£¬O¯u¥¿ªº source code¡C

        code, but does not include the actual source code.  You can

        ¦Ó source code ¥i¥H±q¥úºÐ©Îºô¸ô(Internet)¨Ó¨ú±o¡A

        get the source code from a CD-ROM or from the Internet.

        ¸Ó³nÅé¶}µoªÌ¥i¯à·|§â source code ¥H¦UºØ®æ¦¡¨Óµo§G¡C

        Source code is distributed in whatever manner the software

        ³q±`¬O¥H tar ¥H¤Î gzip ³o¨âªÌ¤u¨ã¤@°_À£ÁYªºÀɮסA¤]¦³¥i¯à¬O¥H¨ä¥L¤u¨ãÀ£ÁY¡A©Î®Ú¥»¨SÀ£ÁY¡C

        author desires.  Frequently this is a tarred and gzipped file,

	¦Ó³nÅ骺 source code µL½×¬O¥H­þ¤@ºØÀ£ÁYÀÉ«¬ºA¡A§Ú­Ì³£ºÙ¤§¬° <quote>distfile</quote>¡C

        but it might be compressed with some other tool or even

        ¤U­±±N¤¶²Ð¨âºØ¦w¸Ë &os; port ªº¤è¦¡¡C</para>

        uncompressed.  The program source code, whatever form it comes

        in, is called a <quote>distfile</quote>.  The two methods for

        installing a &os; port are described below.</para>

        <para>You must be logged in as <username>root</username> to

        <para>­n¦w¸Ë port ªº¸Ü¡A½Ð°È¥²¤Á¬° <username>root</username> ¨­¥÷¡C</para>

          install ports.</para>

	<para>Before installing any port, you should be sure to have

	<para>¦b¦w¸Ë¥ô¦ó port ¤§«e¡A½Ð°È¥²½T»{¦³§ó·s Ports Collection ¨ì³Ì·sª©¡A

	  an up-to-date Ports Collection and you should check <ulink

	  ¦¹¥~½ÐÀ˾\ <ulink

	  url="http://vuxml.freebsd.org/"></ulink> for security issues

	  url="http://vuxml.freebsd.org/"></ulink> ¨ÓÀˬd©Ò­n¸Ëªº port 

	  related to your port.</para>

	  ¬O§_¦³¬ÛÃö¦w¥þº|¬}ijÃD»Ý­nª`·Nªº¡C</para>

	<para>A security vulnerabilities check can be automatically

	<para><application>portaudit</application> ·|¦b¦w¸Ë¥ô¦ó port ¤§«e¡A

	  done by <application>portaudit</application> before any new

	  ¥ý¦Û°ÊÀˬd¬O§_¦³¬ÛÃö¤wª¾ªº¦w¥þº|¬}¡C³o­Ó¤u¨ã¦b Ports Collection ¤º¦³

	  application installation.  This tool can be found in the

	  (<filename role="package">security/portaudit</filename>)¡C

	  Ports Collection (<filename

	  ¦b¦w¸Ë port ¤§«e¡A¥i¥H¥ý¶] <command>portaudit -F</command> «ü¥O¡A

	  role="package">security/portaudit</filename>).  Consider

	  ¦p¦¹¤@¨Ó´N·|§ì³Ì·sªº¸ê¦wº|¬}¸ê®Æ®w¦^¨Ó®Ö¹ï¡C

	  running <command>portaudit -F</command> before installing a

	  ¨C¤Ñªº¨t²Î©w´Á¦wÀË·|¦Û°Ê§ó·s¸ê®Æ®w¡A¨Ã§@¦w¥þ½]®Ö¡C

	  new port, to fetch the current vulnerabilities database.  A

	  ¸Ô±¡½Ð°Ñ¾\ &man.portaudit.1; ¥H¤Î &man.periodic.8; ªº½u¤W»¡©ú¡C</para>

	  security audit and an update of the database will be

	  performed during the daily security system check.  For more

	  information read the &man.portaudit.1; and &man.periodic.8;

	  manual pages.</para>

      <para>The Ports Collection makes an assumption that you have a working

      <para>Ports Collection ·|°²³]§Aªººô¸ô¬O¥i¥¿±`³s½uªº¡C

	Internet connection.  If you do not, you will need to put a copy of the

        ¦pªG¨S¦³ªº¸Ü¡A¨º»ò»Ý¤â°Ê§â©Ò»Ýªº distfile Àɽƻs¨ì 

	distfile into <filename>/usr/ports/distfiles</filename>

	<filename>/usr/ports/distfiles</filename> ¤~¦æ¡C</para>

	manually.</para>

	<para>To begin, change to the directory for the port you want to

	<para>¶}©l¾Þ§@¤§«e¡A­n¥ý¶i¤J¥´ºâ¦w¸Ëªº port ¥Ø¿ý¤º¡G</para>

	  install:</para>

        <para>Once inside the <filename>lsof</filename> directory, you

        <para>¤@¥¹¶i¤J <filename>lsof</filename> ¥Ø¿ý«á¡A´N¥i¥H¬Ý¨ì³o­Ó port ªº skeleton µ²ºc¡C

	  will see the port skeleton.  The next step is to compile, or

	  ±µ¤U¨Ó¡A´N¬O½sĶ¡A¤]´N¬O <quote>build</quote> ³o­Ó port¡C

	  <quote>build</quote>, the port.  This is done by simply

	  ¥u»Ý²³æ¿é¤J <command>make</command> «ü¥O¡A´N¥i»´ÃP§¹¦¨½sĶ¡C

	  typing <command>make</command> at the prompt.  Once you have

	  §¹¦¨«á¡AÀ³¸Ó¥i¥H¬Ý¨ìÃþ¦ü¤U­±°T®§¡G</para>

	  done so, you should see something like this:</para>

        <para>Notice that once the compile is complete you are

        <para>½Ðª`·N¡G½sĶ§¹¦¨«á¡A´N·|¦^¨ì´£¥Ü¦C(prompt)¡C±µ¤U¨Ó´N¬O¦w¸Ë¸Ó port ¤F¡A

	  returned to your prompt.  The next step is to install the

	  ­n¸Ëªº¸Ü¡A¥u»Ý¦b­ì¥»ªº <command>make</command> «ü¥O«á­±¦A¥[¤W¤@­Ó¦r§Y¥i¡A

	  port.  In order to install it, you simply need to tack one word

	  ¨º­Ó¦r´N¬O <command>install</command>¡G</para>

	  onto the <command>make</command> command, and that word is

	  <command>install</command>:</para>

        <para>Once you are returned to your prompt, you should be able to

        <para>¤@¥¹¦^¨ì´£¥Ü¦C(prompt)¡A´N¥i¥H°õ¦æ­è¸Ëªºµ{¦¡¤F¡C

          run the application you just installed.  Since 

	  ¥t¥~¡A¦]¬° <command>lsof</command> ³oµ{¦¡°õ¦æ®É·|¦³ÃB¥~Åv­­¡A

	  <command>lsof</command> is a

	  ©Ò¥H·|¥X²{¦w¥þĵ§i¡C¦b½sĶ¡B¦w¸Ë port ªº®É­Ô¡A

	  program that runs with increased privileges, a security

	  ½Ð¯d·N¥ô¦ó¥X²{ªºÄµ§i¡C</para>

	  warning is shown.  During the building and installation of

	  ports, you should take heed of any other warnings that

	<para>¦¹¥~¡A«Øij§R°£½sĶ¥Îªº¤u§@¥Ø¿ý(¹w³]¬O <filename>work</filename>)¡A

	  may appear.</para>

	  ³o¥Ø¿ý¤º¬°¦b½sĶ¹Lµ{¤¤©Ò¥Î¨ìªº¤@¨ÇÁ{®ÉÀɮסA

	  ³o¨ÇÀɮפ£¥u¦ûµwºÐªÅ¶¡¡A¦Ó¥B¤]¥i¯à·|¦b¸Ó port ¤É¯Å·sª©®É¡A

	<para>It is a good idea to delete the working subdirectory,

	  ³y¦¨¤£¥²­nªº§xÂZ¡C</para>

	  which contains all the temporary files used during compilation.

	  Not only it consumes a valuable disk space, it would also cause

	  problems later when upgrading to the newer version of the port.</para>

          <para>You can save an extra step by just running <command>make

          <para>¥Î <command>make install clean</command> ´N¥i¥H¤@¤f®ð§¹¦¨­è©Ò»¡ 

	    install clean</command> instead of <command>make</command>,

	    <command>make</command>¡B<command>make install</command>¡B

	    <command>make install</command> and <command>make clean</command>

	    <command>make clean</command> ³o¤T­Ó¨BÆJ¤F¡C</para>

	    as three separate steps.</para>

	  <para>Some shells keep a cache of the commands that are

	  <para>¦³¨Ç shell ·|¨Ì¾Ú <envar>PATH</envar> Àô¹ÒÅܼƪº¸ô®|¡A

	    available in the directories listed in the

	    §â¨º¨Ç¸ô®|ªº°õ¦æÀÉ cache °_¨Ó¡A¨Ó¥[³t·j´M°õ¦æÀÉ¡C

	    <envar>PATH</envar> environment variable, to speed up

	    ¦pªG§A¥Îªº¬O³oÃþªº shell¡A¨º»ò¦b¸Ë§¹ port «á»Ý­n¥´ 

	    lookup operations for the executable file of these

	    <command>rehash</command> «ü¥O¡A¤~¯à°õ¦æ·s¸Ëªº°õ¦æÀÉ¡A¦Ó 

	    commands.  If you are using one of these shells, you might

	    <command>rehash</command> «ü¥O¥i¥H¦b <command>tcsh</command> 

	    have to use the <command>rehash</command> command after

	    ¤§Ãþªº shell ¤W¨Ï¥Î¡A­Y¬O <command>sh</command> ªº¸Ü¡A«h¬O 

	    installing a port, before the newly installed commands can

	    <command>hash -r</command>¡C

	    be used.  This command will work for shells like

	    ¸Ô±¡½Ð°Ñ¾\§A©Ò¨Ï¥Îªº shell ¬ÛÃö¤å¥ó¡C</para>

	    <command>tcsh</command>.  Use the <command>hash -r</command>

	    command for shells like <command>sh</command>.  Look at the

	    documentation for your shell for more information.</para>