From chinsan.tw@gmail.com  Sat Aug  5 04:42:14 2006
Return-Path: <chinsan.tw@gmail.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CE2EB16A4E2;
	Sat,  5 Aug 2006 04:42:14 +0000 (UTC)
	(envelope-from chinsan.tw@gmail.com)
Received: from smtp2.bc.hgc.com.tw (smtp2.bc.hgc.com.tw [203.133.1.156])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4359643D70;
	Sat,  5 Aug 2006 04:42:04 +0000 (GMT)
	(envelope-from chinsan.tw@gmail.com)
Received: from smtp2.bc.hgc.com.tw (u14-109.u203-187.giga.net.tw [203.187.14.109])
	by smtp2.bc.hgc.com.tw (Postfix) with SMTP id E15A32F068;
	Sat,  5 Aug 2006 12:42:01 +0800 (CST)
Received: by smtp2.bc.hgc.com.tw (sSMTP sendmail emulation); Sat,  5 Aug 2006 12:48:13 +0800
Message-Id: <20060805044201.E15A32F068@smtp2.bc.hgc.com.tw>
Date: Sat,  5 Aug 2006 12:48:13 +0800
From: chinsan <chinsan.tw@gmail.com>
Reply-To: chinsan <chinsan.tw@gmail.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc: vanilla@FreeBSD.org
Subject: [UPDATE] zh_TW: Update handbook/ports to SVN#963
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         101392
>Category:       docs
>Synopsis:       [UPDATE] zh_TW: Update handbook/ports to SVN#963
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          update
>Submitter-Id:   current-users
>Arrival-Date:   Sat Aug 05 04:50:12 GMT 2006
>Closed-Date:    Sat Aug 05 05:10:50 GMT 2006
>Last-Modified:  Sat Aug 05 05:10:50 GMT 2006
>Originator:     chinsan
>Release:        FreeBSD 6.1-STABLE i386
>Organization:
FreeBSD Taiwan
>Environment:
System: FreeBSD chinsan2.twbbs.org 6.1-STABLE FreeBSD 6.1-STABLE #1: Fri Jun 2 16:44:35 CST 2006 root@chinsan2.twbbs.org:/usr/obj/usr/src/sys/GENERIC i386


	
>Description:
 - Update handbook/ports to SVN#963
  (patch URL http://chinsan2.twbbs.org/chinsan/zh_TW.Big5.20060805_5.diff)

 - ChangeLog (Trac Timeline)
   https://opensvn.csie.org/traccgi/freebsddoc/timeline

>How-To-Repeat:
	
>Fix:

	

--- zh_TW.Big5.20060805_5.diff begins here ---
diff -ruN zh_TW.Big5.orig/books/handbook/ports/chapter.sgml zh_TW.Big5/books/handbook/ports/chapter.sgml
--- zh_TW.Big5.orig/books/handbook/ports/chapter.sgml	Thu Jul 20 14:27:17 2006
+++ zh_TW.Big5/books/handbook/ports/chapter.sgml	Sat Aug  5 12:26:55 2006
@@ -94,7 +94,7 @@
     <para>ƹWAports ٥iHΨӲ packagesAHKLHiH 
       <command>pkg_add</command> ӦwˡAάOy|Ш쪺LM޲zOC</para>
 
-    <para> packages H ports ̳O@ˡA|{ <emphasis>dependencies(nۨY)</emphasis>C
+    <para> packages H ports ̳O@˷|{ <emphasis>dependencies(nۨY)</emphasis>C
       ]GzQwˬY{Ḁۨt@Ӥw˪禡w(library)A
       Ӧb FreeBSD  port H package o{HθӨ禡wFC
       ҥHL׬O <command>pkg_add</command> OΪ port 覡Ӹ˸ӵ{A
@@ -237,33 +237,26 @@
       </listitem>
 
       <listitem>
-	<para>If you know the exact name of the port, but just need to
-        find out which category it is in, you can use the
-        &man.whereis.1; command.
-	Simply type <command>whereis
-        <replaceable>file</replaceable></command>, where
-        <replaceable>file</replaceable> is the program you want to
-        install.  If it is found on your system, you will be told
-        where it is, as follows:</para>
+	<para>YD port TW١ADbӤؿA
+        iH &man.whereis.1; OӧXӡC
+	un <command>whereis
+        <replaceable>file</replaceable></command> YiA 
+        <replaceable>file</replaceable> aЧאּQ˪nW١C
+        YӳnAN|iDAANUoˡG</para>
 
       <screen>&prompt.root; <userinput>whereis lsof</userinput>
 lsof: /usr/ports/sysutils/lsof</screen>
 
-      <para>This tells us that <command>lsof</command> (a system
-	utility) can be found in the
-	<filename>/usr/ports/sysutils/lsof</filename>
-	directory.</para></listitem>
+      <para>p@ӡAN|D <command>lsof</command> (tΤu{) Ob 
+	<filename>/usr/ports/sysutils/lsof</filename> ؿC</para></listitem>
 
       <listitem>
-	<para>Yet another way to find a particular port is by using the
-        Ports Collection's built-in search mechanism.  To use the
-        search feature, you will need to be in the
-        <filename>/usr/ports</filename> directory.  Once in that
-        directory, run <command>make search
-        name=<replaceable>program-name</replaceable></command> where
-        <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>٦t@ۡANO Ports Collection تjMC
+        nΪɭԡAХ <filename>/usr/ports</filename> ؿC
+        MA <command>make search 
+	name=<replaceable>program-name</replaceable></command>A䤤
+        <replaceable>program-name</replaceable> ЧאּQ䪺nW١C
+        |ҨӻAYn䪺O <command>lsof</command> ܡANOG</para>
 
       <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
 &prompt.root; <userinput>make search name=lsof</userinput>
@@ -275,23 +268,19 @@
 B-deps: 
 R-deps: </screen>
 
-      <para>The part of the output you want to pay particular
-        attention to is the <quote>Path:</quote> line, since that
-        tells you where to find the port.  The other information
-        provided is not needed in order to install the port, so it
-        will not be covered here.</para>
-
-      <para>For more in-depth searching you can also use <command>make
-       search key=<replaceable>string</replaceable></command> where
-       <replaceable>string</replaceable> is some text to search for.
-       This searches port names, comments, descriptions and
-       dependencies and can be used to find ports which relate to a
-       particular subject if you do not know the name of the program
-       you are looking for.</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>oǷjMGAn`NO <quote>Path:</quote> oA
+        ]o|iDAiHb portC
+	ӷjMGLA]P port w˸LYAҥHo̴NFC</para>
+
+      <para>YnjMAiH <command>make
+        search key=<replaceable>string</replaceable></command>A䤤 
+        <replaceable>string</replaceable> ЧאּQjMrC
+        p@ӷ| port W١Bn²(comments)Bnԭz(descriptions)
+        HγnۨY(dependencies)̭O_ŦXrA
+        ~AMnW٪ܡA]iHӧ䦳ŦXrDD portC</para>
+
+      <para>oؤ覡AjMrO case-insensitive(Ϥjpg)C
+        pAjM <quote>LSOF</quote> P <quote>lsof</quote> ̵G|O@˪C</para>
       </listitem>
 
     </itemizedlist>
@@ -351,71 +340,52 @@
 &prompt.root; <userinput>pkg_add <replaceable>lsof-4.56.4.tgz</replaceable></userinput></screen>
       </example>
 
-      <para>If you do not have a source of local packages (such as a
-        FreeBSD CD-ROM set) then it will probably be easier to use the
-        <option>-r</option> option to &man.pkg.add.1;.  This will
-        cause the utility to automatically determine the correct
-        object format and release and then fetch and install the
-        package from an FTP site.
+      <para>YS package ӷ(O FreeBSD )ܡA
+        ĳϥ &man.pkg.add.1; ɡA[W <option>-r</option> 
+	ﶵӧPw packageCp@ӡAN|۰ʧP_T package 榡B
+	HΩҷft@~t release A
+	M|ۤvq FTP ^Bwˬ۹ packageC
       </para>
 
       <indexterm>
         <primary><command>pkg_add</command></primary></indexterm>
       <screen>&prompt.root; <userinput>pkg_add -r <replaceable>lsof</replaceable></userinput></screen>
 
-      <para>The example above would download the correct package and
-	add it without any further user intervention.
-	If you want to specify an alternative &os; Packages Mirror,
-	instead of the main distribution site, you have to set
-	<envar>PACKAGESITE</envar> accordingly, to
-	override the default settings.  &man.pkg.add.1;
-	uses &man.fetch.3; to download the files, which honors various
-	environment variables, including
-	<envar>FTP_PASSIVE_MODE</envar>, <envar>FTP_PROXY</envar>, and
-	<envar>FTP_PASSWORD</envar>.  You may need to set one or more
-	of these if you are behind a firewall, or need to use an
-	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>WoҤl|۰ʤUT package æwˡC
+	YQﴫΨL &os; Packages Mirror ANn]w <envar>PACKAGESITE</envar> ܼơA
+	p@Ӥ~|Nw]]wC  &man.pkg.add.1;
+	| &man.fetch.3; OӤUɮסA &man.fetch.3; h|ϥάܼƪ]wA
+	OG
+	<envar>FTP_PASSIVE_MODE</envar>B<envar>FTP_PROXY</envar> H 
+	<envar>FTP_PASSWORD</envar>C  pGAҳB firewall ᭱AΪ̻ݭn
+	FTP/HTTP proxy ܡANݭn]wC ]wӸ`аѾ\ &man.fetch.3;C
+	Ъ`NGWһҤlOg <literal>lsof</literal> ӫD 
+	<literal>lsof-4.56.4</literal>C  ϥλݧ\ɡA package N[WhFC
+	&man.pkg.add.1; |۰ʤUӳn骺̷s^ӦwˡC</para>
 
       <note>
-	<para>&man.pkg.add.1; will download the latest version of
-	  your application if you are using &os.current; or
-	  &os.stable;.  If you run a -RELEASE version, it will grab
-	  the version of the package that was built with your
-	  release.  It is possible to change this behavior by
-	  overriding the <envar>PACKAGESITE</envar> environment
-	  variable.  For example, if you run a &os;&nbsp;5.4-RELEASE
-	  system, by default &man.pkg.add.1; will try to fetch
-	  packages from
-	  <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>YΪO &os.current;  &os.stable; ܡA&man.pkg.add.1; 
+	  |۰ʤUӳn̷s^ӡC
+	  YΪOݩ -RELEASE AL|^ݩ release WҽsĶ packageC
+	  ]iH <envar>PACKAGESITE</envar> ܼơAHܤU覡C
+	  |ҨӻApGO &os;&nbsp;5.4-RELEASE ܡA &man.pkg.add.1; w]|q
+	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/</literal>
+	  ӧ packageCYnj &man.pkg.add.1; U &os;&nbsp;5-STABLE ҥΪ package
+	  AN <envar>PACKAGESITE</envar> ] 
+	  <literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/</literal>YiC
 	</para>
       </note>
 
-      <para>Package files are distributed in <filename>.tgz</filename>
-          and <filename>.tbz</filename> formats.  You can find them at <ulink
-          url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/"></ulink>,
-          or on the FreeBSD CD-ROM distribution.  Every CD on the
-          FreeBSD 4-CD set (and the PowerPak, etc.) contains packages
-          in the <filename>/packages</filename> directory.  The layout
-          of the packages is similar to that of the
-          <filename>/usr/ports</filename> tree.  Each category has its
-          own directory, and every package can be found within the
-          <filename>All</filename> directory.
+      <para>Package ɦ <filename>.tgz</filename> H <filename>.tbz</filename> خ榡C
+          oǳizL <ulink
+          url="ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/"></ulink>AΪ FreeBSd ФoC
+          Every CD on the
+          FreeBSD 4 ЮM󤺥H PowerPak(¤O]) ..C@г|b <filename>/packages</filename>
+	  ؿ packageC̭ؿ[c <filename>/usr/ports</filename> ؿ[cC
+          CӤUۦMݥؿABC package |b <filename>All</filename> ؿC
       </para>
 
-      <para>The directory structure of the package system matches the
-        ports layout; they work with each other to form the entire
-        package/port system.
-      </para>
+      <para>package ؿ[cP port @PF̦@Pc package/port tξC</para>
 
     </sect2>
 
@@ -426,9 +396,7 @@
         <primary>packages</primary>
         <secondary>managing</secondary>
       </indexterm>
-      <para>&man.pkg.info.1; is a utility that lists and describes 
-        the various packages installed.
-      </para>
+      <para>&man.pkg.info.1; iΨӦCXҦww˪nBn²C</para>
 
       <indexterm>
         <primary><command>pkg_info</command></primary>
@@ -437,9 +405,8 @@
 cvsup-16.1          A general network file distribution system optimized for CV
 docbook-1.2         Meta-port for the different versions of the DocBook DTD
 ...</screen>
-      <para>&man.pkg.version.1; is a utility that summarizes the
-        versions of all installed packages.  It compares the package 
-        version to the current version found in the ports tree.
+      <para>&man.pkg.version.1; hOCXҦww˪n骩C
+        |ܤw˪HΥثeW port tree tC
       </para> 
       <indexterm>
         <primary><command>pkg_version</command></primary>
@@ -449,9 +416,7 @@
 docbook                     =
 ...</screen>
 
-      <para>The symbols in the second column indicate the relative age
-        of the installed version and the version available in the
-        local ports tree.</para>
+      <para>ĤG檺ŸܡGww˪n骩PثeW port tree tC</para>
 
       <informaltable frame="none" pgwide="1">
         <tgroup cols="2">
@@ -464,27 +429,22 @@
 
  	  <tbody>
   	    <row>
-	    <entry>=</entry> <entry>The version of the
-	    installed package matches the one found in the
-	    local ports tree.</entry>
+	    <entry>=</entry> <entry>w˪PثeW port tree OP@C
+	    </entry>
   	    </row>
  
         <row><entry>&lt;</entry>
-	<entry>The installed version is older than the one available
-	in the ports tree.</entry>
+	<entry>PثeW port tree ۤ_ӡAw˪¡C</entry>
 	</row>
 
-        <row><entry>&gt;</entry><entry>The installed version is newer
-          than the one found in the local ports tree. (The local ports
-          tree is probably out of date.)</entry></row>
-
-        <row><entry>?</entry><entry>The installed package cannot be
-	  found in the ports index.  (This can happen, for instance, if an
-	  installed port is removed from the Ports Collection or
-	  renamed.)</entry></row>
+        <row><entry>&gt;</entry><entry>PثeW port tree ۤ_ӡA
+	  w˪sC(iOثeW port tree |sC)</entry></row>
+
+        <row><entry>?</entry><entry>w˪nb ports ޤLơC
+	  (q`iOA|ҨӻGww˪ port wq Ports Collection ΧWFC)
+	  </entry></row>
 
-        <row><entry>*</entry><entry>There are multiple versions of the
-        package.</entry></row>
+        <row><entry>*</entry><entry>ӳnPɦ\hC</entry></row>
 
 	</tbody>
 	</tgroup>
@@ -557,41 +517,37 @@
 
 	  <para>Ч
 	    <replaceable>cvsup.tw.FreeBSD.org</replaceable> Ч令A() 
-	    <application>CVSup</application> ServerC
+	    <application>CVSup</application> DC
 	    oiHѾ\㪺 <link linkend="cvsup-mirrors">CVSup mirror</link> C(<xref
 	    linkend="cvsup-mirrors">)C</para>
 
 	  <note>
-	    <para>One may want to use his own
-	      <filename>ports-supfile</filename>, for example to avoid
-	      the need of passing the <application>CVSup</application>
-	      server on the command line.</para>
+	    <para>YQΦۤv] 
+	      <filename>ports-supfile</filename>ApAQCoOӫwҨϥΪ 
+	      <application>CVSup</application> DC</para>
 
 	    <procedure>
 	      <step>
-		<para>In this case, as <username>root</username>, copy
+		<para>oرpUAХH <username>root</username> v 
 		  <filename>/usr/share/examples/cvsup/ports-supfile</filename>
-		  to a new location, such as
-		  <filename>/root</filename> or your home
-		  directory.</para>
+		  ƻsLmAp  
+		  <filename>/root</filename> Ϊ̦ۤvbaؿC</para>
 	      </step>
 
 	      <step>
-		<para>Edit <filename>ports-supfile</filename>.</para>
+		<para>קs <filename>ports-supfile</filename> ɡC</para>
 	      </step>
 
 	      <step>
-		<para>Change
+		<para> 
 		  <replaceable>CHANGE_THIS.FreeBSD.org</replaceable>
-		  to a <application>CVSup</application> server near
-		  you.  See <link linkend="cvsup-mirrors">CVSup
-		  Mirrors</link> (<xref linkend="cvsup-mirrors">) for
-		  a complete listing of mirror sites.</para>
+		  אּA() <application>CVSup</application> DC
+		  oiHѾ\㪺 <link linkend="cvsup-mirrors">CVSup
+		  Mirrors</link> (<xref linkend="cvsup-mirrors">) C</para>
 	      </step>
 
 	      <step>
-		<para>And now to run <command>cvsup</command>, use the
-		  following:</para>
+		<para>MN}lHUCO] <command>cvsup</command>G</para>
 
 		<screen>&prompt.root; <userinput>cvsup -L 2 <replaceable>/root/ports-supfile</replaceable></userinput></screen>
 	      </step>
@@ -600,52 +556,47 @@
 	</step>
 
 	<step>
-	  <para>Running the &man.cvsup.1; command later will download and apply all
-	    the recent changes to your Ports Collection, except
-	    actually rebuilding the ports for your own system.</para>
+	  <para> &man.cvsup.1; AN|}ls Ports CollectionC
+	    Loʧ@uOyszäOyɯšzA|w˪n魫ssĶBɯšC</para>
 	</step>
       </procedure>
 
       <procedure>
 	<title>Portsnap 覡</title>
 
-	<para>&man.portsnap.8; is an alternative system for distributing the
-	  Ports Collection.  It was first included in &os;&nbsp;6.0.  On older
-	  systems, you can install it from <filename
-	  role="package">sysutils/portsnap</filename> port:</para>
+	<para>&man.portsnap.8; ]Os Ports Collection 覡@C
+	  &os;&nbsp;6.0 _}l Portsnap AӸªtΡAhizL <filename
+	  role="package">sysutils/portsnap</filename> port ӦwˡG</para>
 
 	<screen>&prompt.root; <userinput>pkg_add -r portsnap</userinput></screen>
 
-	<para>Please refer to <link linkend="portsnap">Using Portsnap</link>
-	  for a detailed description of all <application>Portsnap</application>
-	  features.</para>
+	<para><application>Portsnap</application> Ӹ`\AаѾ\ 
+	  <link linkend="portsnap">Portsnap ϥνg</link>C</para>
 
 	<step>
-	  <para>Create an empty directory <filename
-	    role="directory">/usr/ports</filename> if it does not exists.</para>
+	  <para>Y <filename
+	    role="directory">/usr/ports</filename> ؿsbܡANإߤ@UaG</para>
 
 	  <screen>&prompt.root; <userinput>mkdir /usr/ports</userinput></screen>
 	</step>
 
 	<step>
-	  <para>Download a compressed snapshot of the Ports Collection into
-	    <filename role="directory">/var/db/portsnap</filename>.  You can
-	    disconnect from the Internet after this step, if you wish.</para>
+	  <para>UӡAUY Ports Collection wsɨ 
+	    <filename role="directory">/var/db/portsnap</filename> ؿC
+	    UAn_uP_iHC</para>
 
 	  <screen>&prompt.root; <userinput>portsnap fetch</userinput></screen>
 	</step>
 
 	<step>
-	  <para>If you are running <application>Portsnap</application> for the
-	    first time, extract the snapshot into <filename
-	    role="directory">/usr/ports</filename>:
+	  <para>YOĤ@] <application>Portsnap</application> ܡAhݭn <filename
+	    role="directory">/usr/ports</filename>G
 	  </para>
 
 	  <screen>&prompt.root; <userinput>portsnap extract</userinput></screen>
 
-	  <para>If you already have a populated <filename
-	    role="directory">/usr/ports</filename> and you are just updating,
-	    run the following command instead:</para>
+	  <para>Yw <filename
+	    role="directory">/usr/ports</filename> ӥBuOQsӤwANӤU@G</para>
 
 	  <screen>&prompt.root; <userinput>portsnap update</userinput></screen>
 	</step>
@@ -655,55 +606,51 @@
       <procedure>
 	<title>Sysinstall 覡</title>
 
-	<para>This method involves using <application>sysinstall</application>
-	  to install the Ports Collection from the installation media.  Note
-	  that the old copy of Ports Collection from the date of the release
-	  will be installed.  If you have Internet access, you should always
-	  use one of the methods mentioned above.</para>
+	<para>o覡n <application>sysinstall</application> zLw˨ӷӸ Ports CollectionC
+	  Ъ`NGҦw˪ Ports Collection uO release oGɪӤwAӫD̷sC
+	  YW(Internet)ܡAШϥΤWz覡@|nC</para>
 
 	<step>
-	  <para>As <username>root</username>, run
-	    <command>sysinstall</command>
-	    (<command>/stand/sysinstall</command> in &os;
-	    versions older than 5.2) as shown below:</para>
+	  <para>H <username>root</username> v
+	    <command>sysinstall</command> 
+	    (b &os; 5.2 ehO <command>/stand/sysinstall</command>)A覡pUG</para>
 
 	  <screen>&prompt.root; <userinput>sysinstall</userinput></screen>
 	</step>
 
 	<step>
-	  <para>Scroll down and select <guimenuitem>Configure</guimenuitem>,
-	    press <keycap>Enter</keycap>.</para>
+	  <para>ХHV䲾ʿܶءA <guimenuitem>Configure</guimenuitem>AM 
+	    <keycap>Enter</keycap> C</para>
 	</step>
 
 	<step>
-	  <para>Scroll down and select
-	    <guimenuitem>Distributions</guimenuitem>, press
-	    <keycap>Enter</keycap>.</para>
+	  <para>
+	    <guimenuitem>Distributions</guimenuitem>AM 
+	    <keycap>Enter</keycap> C</para>
 	</step>
 
 	<step>
-	  <para>Scroll down to <guimenuitem>ports</guimenuitem>, press
-	    <keycap>Space</keycap>.</para>
+	  <para> <guimenuitem>ports</guimenuitem>AM 
+	    <keycap>Space</keycap> C</para>
 	</step>
 
 	<step>
-	  <para>Scroll up to <guimenuitem>Exit</guimenuitem>, press
-	    <keycap>Enter</keycap>.</para>
+	  <para> <guimenuitem>Exit</guimenuitem>AM 
+	    <keycap>Enter</keycap> C</para>
 	</step>
 
 	<step>
-	  <para>Select your desired installation media, such as CDROM,
-	    FTP, and so on.</para>
+	  <para>ܭnΪw˨ӷApGCDROM()BFTP 覡C</para>
 	</step>
 
 	<step>
-	  <para>Scroll up to <guimenuitem>Exit</guimenuitem> and press
-	    <keycap>Enter</keycap>.</para>
+	  <para> <guimenuitem>Exit</guimenuitem>AM
+	    <keycap>Enter</keycap> C</para>
 	</step>
 
 	<step>
-	  <para>Press <keycap>X</keycap> to exit
-	    <application>sysinstall</application>.</para>
+	  <para>U <keycap>X</keycap> Ni}
+	    <application>sysinstall</application> {C</para>
 	</step>
       </procedure>
     </sect2>
@@ -715,113 +662,88 @@
         <primary>ports</primary>
         <secondary>installing</secondary>
       </indexterm>
-      <para>The first thing that should be explained when it comes to
-        the Ports Collection is what is actually meant by a
-        <quote>skeleton</quote>.  In a nutshell, a port skeleton is a
-        minimal set of files that tell your FreeBSD system how to
-        cleanly compile and install a program.  Each port skeleton
-        includes:</para>
+      <para> Ports CollectionAnOG <quote>skeleton</quote>C
+        ²Aport skeleton NOnpb FreeBSD QsĶBw˪̰ɮײզXC
+        C port skeleton 򥻤W|G</para>
 
       <itemizedlist>
 	<listitem>
-	  <para>A <filename>Makefile</filename>.  The
-	    <filename>Makefile</filename> contains various statements
-	    that specify how the application should be compiled and
-	    where it should be installed on your system.</para>
+	  <para><filename>Makefile</filename> ɡC
+	    o <filename>Makefile</filename> e\hA
+	    OΨӫwnpsĶAHθӸ˦btΪBC</para>
 	</listitem>
 
 	<listitem>
-	  <para>A <filename>distinfo</filename> file.  This file
-	    contains information about the files that must be
-	    downloaded to build the port and their checksums, to
-	    verify that files have not been corrupted during the
-	    download using &man.md5.1;.</para>
+	  <para><filename>distinfo</filename> ɡC  
+	    sĶӳnһݤUɮסBchecksum(ɮץ)|OboɡA
+	    ÷| &man.md5.1; uӽTOҤUɮ׬OTL~C</para>
 	</listitem>
 	
 	<listitem>
-	  <para>A <filename>files</filename> directory.  This
-	    directory contains patches to make the program compile and
-	    install on your FreeBSD system.  Patches are basically
-	    small files that specify changes to particular files.
-	    They are in plain text format, and basically say
-	    <quote>Remove line 10</quote> or <quote>Change line 26 to
-	    this ...</quote>.  Patches are also known as
-	    <quote>diffs</quote> because they are generated by the
-	    &man.diff.1; program.</para>
+	  <para><filename>files</filename> ؿC oؿ񪺬On饿`sĶBw˪ patch ɡC
+	    Patches ɰ򥻤WO@ǤpɮסAðwSwɮרӰקABO¤rɮ榡A
+	    򥻤Weq`|O <quote>Remove line 10(R 10 )</quote> 
+	    <quote>Change line 26 to this ...( 26 אּ...)</quote> C
+	    o Patches q`]٬ <quote>diffs</quote>
+	    A]O &man.diff.1; {ҲͪC</para>
 
-	  <para>This directory may also contain other files used to build
-	    the port.</para>
+	  <para>~Aؿ]i|@ǨUsĶ port ɮסC</para>
 	</listitem>
 
 	<listitem>
-	  <para>A <filename>pkg-descr</filename> file.  This is a more
-	    detailed, often multiple-line, description of the program.</para>
+	  <para><filename>pkg-descr</filename> ɡAeOԲӪn餶СAq`|gohC</para>
 	</listitem>
 	
 	<listitem>
-	  <para>A <filename>pkg-plist</filename> file.  This is a list
-	    of all the files that will be installed by the port.  It
-	    also tells the ports system what files to remove upon
-	    deinstallation.</para>
+	  <para><filename>pkg-plist</filename> ɡA port |w˪ҦɮײMC
+	    ]OiDtΦb port ɡAݭnRɮסC</para>
 	</listitem>
       </itemizedlist>
 
-      <para>Some ports have other files, such as
-        <filename>pkg-message</filename>.  The ports system uses these
-        files to handle special situations.  If you want more details
-        on these files, and on ports in general, check out the <ulink
+      <para> port ٷ|LɮסAO <filename>pkg-message</filename> ɡC
+        port tΦb@ǱpɡA|γoɮסC
+        pGQDoɮתhӸ`γ~AH port @ΪkAаѾ\ <ulink
         url="&url.books.porters-handbook;/index.html">FreeBSD Porter's
-        Handbook</ulink>.</para>
+        Handbook</ulink>C</para>
 
-      <para>The port includes instructions on how to build source
-        code, but does not include the actual source code.  You can
-        get the source code from a CD-ROM or from the Internet.
-        Source code is distributed in whatever manner the software
-        author desires.  Frequently this is a tarred and gzipped file,
-        but it might be compressed with some other tool or even
-        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>port gOiDtΦpsĶ source code OAäOu source codeC
+         source code iHqЩκ(Internet)ӨoA
+        ӳn}o̥i| source code HUخ榡ӵoGC
+        q`OH tar H gzip o̤u@_YɮסA]iOHLuYAήڥSYC
+	ӳn骺 source code L׬OH@YɫAAڭ̳٤ <quote>distfile</quote>C
+        UNШئw &os; port 覡C</para>
 
       <note>
-        <para>You must be logged in as <username>root</username> to
-          install ports.</para>
+        <para>nw port ܡAаȥ <username>root</username> C</para>
       </note>
 
       <warning>
-	<para>Before installing any port, you should be sure to have
-	  an up-to-date Ports Collection and you should check <ulink
-	  url="http://vuxml.freebsd.org/"></ulink> for security issues
-	  related to your port.</para>
-
-	<para>A security vulnerabilities check can be automatically
-	  done by <application>portaudit</application> before any new
-	  application installation.  This tool can be found in the
-	  Ports Collection (<filename
-	  role="package">security/portaudit</filename>).  Consider
-	  running <command>portaudit -F</command> before installing a
-	  new port, to fetch the current vulnerabilities database.  A
-	  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>bw˥ port eAаȥT{s Ports Collection ̷sA
+	  ~˾\ <ulink
+	  url="http://vuxml.freebsd.org/"></ulink> ˬdҭn˪ port 
+	  O_w|}ĳDݭn`NC</para>
+
+	<para><application>portaudit</application> |bw˥ port eA
+	  ۰ˬdO_ww|}CoӤub Ports Collection 
+	  (<filename role="package">security/portaudit</filename>)C
+	  bw port eAiH] <command>portaudit -F</command> OA
+	  p@ӴN|̷sw|}Ʈw^ӮֹC
+	  CѪtΩww˷|۰ʧsƮwAç@w]֡C
+	  ԱаѾ\ &man.portaudit.1; H &man.periodic.8; uWC</para>
       </warning>
 
-      <para>The Ports Collection makes an assumption that you have a working
-	Internet connection.  If you do not, you will need to put a copy of the
-	distfile into <filename>/usr/ports/distfiles</filename>
-	manually.</para>
+      <para>Ports Collection |]AOi`suC
+        pGSܡAݤʧһݪ distfile ɽƻs 
+	<filename>/usr/ports/distfiles</filename> ~C</para>
 
-	<para>To begin, change to the directory for the port you want to
-	  install:</para>
+	<para>}lާ@eAniJw˪ port ؿG</para>
 
         <screen>&prompt.root; <userinput>cd /usr/ports/sysutils/lsof</userinput></screen>
 
-        <para>Once inside the <filename>lsof</filename> directory, you
-	  will see the port skeleton.  The next step is to compile, or
-	  <quote>build</quote>, the port.  This is done by simply
-	  typing <command>make</command> at the prompt.  Once you have
-	  done so, you should see something like this:</para>
+        <para>@iJ <filename>lsof</filename> ؿANiHݨo port  skeleton cC
+	  UӡANOsĶA]NO <quote>build</quote> o portC
+	  u²J <command>make</command> OANiPsĶC
+	  AӥiHݨUTG</para>
 
         <screen>&prompt.root; <userinput>make</userinput>
 &gt;&gt; lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
@@ -843,11 +765,9 @@
 ...
 &prompt.root;</screen>
 
-        <para>Notice that once the compile is complete you are
-	  returned to your prompt.  The next step is to install the
-	  port.  In order to install it, you simply need to tack one word
-	  onto the <command>make</command> command, and that word is
-	  <command>install</command>:</para>
+        <para>Ъ`NGsĶAN|^촣ܦC(prompt)CUӴNOw˸ port FA
+	  n˪ܡAuݦb쥻 <command>make</command> O᭱A[W@ӦrYiA
+	  ӦrNO <command>install</command>G</para>
 
         <screen>&prompt.root; <userinput>make install</userinput>
 ===&gt;  Installing for lsof-4.57
@@ -862,42 +782,35 @@
       increased privileges.
 &prompt.root;</screen>
 
-        <para>Once you are returned to your prompt, you should be able to
-          run the application you just installed.  Since 
-	  <command>lsof</command> is a
-	  program that runs with increased privileges, a security
-	  warning is shown.  During the building and installation of
-	  ports, you should take heed of any other warnings that
-	  may appear.</para>
-
-	<para>It is a good idea to delete the working subdirectory,
-	  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>@^촣ܦC(prompt)ANiH˪{FC
+	  t~A] <command>lsof</command> o{ɷ|B~vA
+	  ҥH|X{wĵiCbsĶBw port ɭԡA
+	  ЯdNX{ĵiC</para>
+
+	<para>~AĳRsĶΪu@ؿ(w]O <filename>work</filename>)A
+	  oؿbsĶL{ҥΨ쪺@{ɮסA
+	  oɮפuwЪŶAӥB]i|b port ɯŷsɡA
+	  ynxZC</para>
 
 	<screen>&prompt.root; <userinput>make clean</userinput>
 ===&gt;  Cleaning for lsof-4.57
 &prompt.root;</screen>
 
         <note>
-          <para>You can save an extra step by just running <command>make
-	    install clean</command> instead of <command>make</command>,
-	    <command>make install</command> and <command>make clean</command>
-	    as three separate steps.</para>
+          <para> <command>make install clean</command> NiH@f𧹦һ 
+	    <command>make</command>B<command>make install</command>B
+	    <command>make clean</command> oTӨBJFC</para>
 	</note>
 
 	<note>
-	  <para>Some shells keep a cache of the commands that are
-	    available in the directories listed in the
-	    <envar>PATH</envar> environment variable, to speed up
-	    lookup operations for the executable file of these
-	    commands.  If you are using one of these shells, you might
-	    have to use the <command>rehash</command> command after
-	    installing a port, before the newly installed commands can
-	    be used.  This command will work for shells like
-	    <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>
+	  <para> shell |̾ <envar>PATH</envar> ܼƪ|A
+	    ⨺Ǹ| cache _ӡAӥ[tjMɡC
+	    pGAΪOo shellAb˧ port ݭn 
+	    <command>rehash</command> OA~s˪ɡA 
+	    <command>rehash</command> OiHb <command>tcsh</command> 
+	     shell WϥΡAYO <command>sh</command> ܡAhO 
+	    <command>hash -r</command>C
+	    ԱаѾ\AҨϥΪ shell C</para>
 	</note>
 
 	<para>Some third party DVD-ROM products such as the FreeBSD Toolkit
--- zh_TW.Big5.20060805_5.diff ends here ---


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: vanilla 
State-Changed-When: Sat Aug 5 05:10:48 UTC 2006 
State-Changed-Why:  
Committed, thanks. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=101392 
>Unformatted:
