aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/books/handbook/ports/chapter.xml
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/ports/chapter.xml')
-rw-r--r--en_US.ISO8859-1/books/handbook/ports/chapter.xml104
1 files changed, 51 insertions, 53 deletions
diff --git a/en_US.ISO8859-1/books/handbook/ports/chapter.xml b/en_US.ISO8859-1/books/handbook/ports/chapter.xml
index f00a54b828..39d26ffa0a 100644
--- a/en_US.ISO8859-1/books/handbook/ports/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/ports/chapter.xml
@@ -347,22 +347,19 @@ Info: Lists information about open files (similar to fstat(1))</screen>
<title>Using Binary Packages</title>
- <para>There are several different tools used to manage packages on
- &os;:</para>
-
- <itemizedlist>
- <listitem>
- <para>The <command>sysinstall</command> utility can be invoked
- on a running system to install, delete, and list available
- and installed packages. For more information, see
- <xref linkend="packages"/>.</para>
- </listitem>
-
- <listitem>
- <para>The package management command line tools, which are
- the subject of the rest of this section.</para>
- </listitem>
- </itemizedlist>
+ <para>At the present time, &os; is transitioning toward a new
+ method of package management. Users of the latest releases
+ may wish to investigate the benefits of using
+ <link linkend="pkgng-intro">PKGng</link> to manage third
+ party software on &os;. For those not yet migrated to the
+ <application>pkgng</application> tool, the tools discussed
+ here may be used for managing the package database. For
+ simplicity, the <command>sysinstall</command> utility is
+ also available post-install for package management.</para>
+
+ <para>All package installation files are stored in the
+ package database directory,
+ <filename class="directory">/var/db/pkg</filename>.</para>
<sect2>
<title>Installing a Package</title>
@@ -579,14 +576,6 @@ docbook =
<para>in this case, all packages whose names start with
<literal>xchat</literal> will be deleted.</para>
</sect2>
-
- <sect2>
- <title>Miscellaneous</title>
-
- <para>All package information, including the file list and
- descriptions of each installed package is stored within the
- <filename>/var/db/pkg</filename> directory.</para>
- </sect2>
</sect1>
<sect1 id="pkgng-intro">
@@ -1800,32 +1789,40 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</sect1>
<sect1 id="ports-nextsteps">
- <title>Post-installation Activities</title>
-
- <para>After installing a new application you will normally want to
- read any documentation it may have included, edit any
- required configuration files, and ensure that the
- application's service starts at boot time.</para>
-
- <para>The exact steps you need to take to configure each
- application will obviously be different. However, if you have
- just installed a new application and are wondering
- <quote>What now?</quote> these tips might help:</para>
+ <title>Working With Installed Ports</title>
+
+ <para>Most third party applications will need some level of
+ configuration after they were installed. This may be a simple
+ configuration file alteration, or perhaps the application will
+ just generate a configuration file. Most applications will
+ have documentation installed into
+ <filename class="directory">/usr/local/share/doc</filename> and
+ manual pages. This documentation should be consulted before
+ continuing. Some applications run services which must be added
+ to the <filename>/etc/rc.conf</filename> file before
+ starting.</para>
+
+ <para>The following list contains useful information for
+ post-install port management. In several cases, finding
+ the location of binaries if they were installed outside
+ of the <envar>PATH</envar>. Users of &man.csh.1; should run
+ <command>rehash</command> to rebuild the known binary
+ list in the shells <envar>PATH</envar>.</para>
<itemizedlist>
<listitem>
- <para>Use &man.pkg.info.1; to find out which files were
- installed, and where. For example, if you have just
- installed FooPackage version 1.0.0, then this command</para>
+ <para>The &man.pkg.info.1; command will print all installed
+ files and their location. For example, if the FooPackage
+ version 1.0.0 was just installed, then the following
+ command will show all the files installed with the
+ package.</para>
- <screen>&prompt.root; <userinput>pkg_info -L foopackage-1.0.0 | less</userinput></screen>
+ <screen>&prompt.root; <userinput>pkg_info -L <replaceable>foopackage-1.0.0</replaceable> | less</userinput></screen>
- <para>will show all the files installed by the package. Pay
- special attention to files located in
- <filename>man/</filename>, which will be manual pages,
- <filename>etc/</filename>, which will be configuration
- files, and <filename>doc/</filename>, which will be more
- comprehensive documentation.</para>
+ <para>Configuration files are always installed in
+ <filename class="directory">/usr/local/etc</filename>
+ and should definitely be consulted before attempting
+ to use the new application.</para>
<para>To determine which version of the application was
installed:</para>
@@ -1839,17 +1836,18 @@ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
</listitem>
<listitem>
- <para>Once you have identified where the application's manual
- pages have been installed, review them using &man.man.1;.
- Review the sample configuration files and any additional
- documentation that may have been provided.</para>
+ <para>These commands will also show the names of any manual
+ pages installed with the application. This additional
+ documentation will now be available to the &man.man.1;
+ command.</para>
</listitem>
<listitem>
- <para>If the application has a web site, check it for
- additional documentation, frequently asked questions, and so
- forth. If you are not sure of the web site address it may
- be listed in the output from</para>
+ <para>If the application has a web site, consult it for
+ additional documentation or a frequently asked questions
+ page. If the website is unknown, the following command
+ will be useful to print out this information if it's
+ available.</para>
<screen>&prompt.root; <userinput>pkg_info <replaceable>foopackage-1.0.0</replaceable></userinput></screen>