Tagged ncftp.xml.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@3852 af4574ff-66df-0310-9fd7-8a98e5e911e0
This commit is contained in:
Manuel Canales Esparcia 2005-04-29 19:24:38 +00:00
parent 782471963d
commit ef3ec4505b

View File

@ -14,148 +14,223 @@
]>
<sect1 id="ncftp" xreflabel="NcFTP-&ncftp-version;">
<sect1info>
<othername>$LastChangedBy$</othername>
<date>$Date$</date>
</sect1info>
<?dbhtml filename="ncftp.html"?>
<?dbhtml filename="ncftp.html"?>
<sect1info>
<othername>$LastChangedBy$</othername>
<date>$Date$</date>
</sect1info>
<title>NcFTP-&ncftp-version;</title>
<indexterm zone="ncftp">
<primary sortas="a-NcFTP">NcFTP</primary>
</indexterm>
<sect2 role="package">
<title>Introduction to NcFTP</title>
<sect2>
<title>Introduction to
<application>Nc<acronym>FTP</acronym></application></title>
<para>The <application>NcFTP</application> package contains
a powerful and flexible interface to the Internet standard File Transfer
Protocol. It is intended to replace or supplement the stock
<command>ftp</command> program.</para>
<bridgehead renderas="sect3">Package Information</bridgehead>
<itemizedlist spacing="compact">
<listitem>
<para>Download (HTTP): <ulink url="&ncftp-download-http;"/></para>
</listitem>
<listitem>
<para>Download (FTP): <ulink url="&ncftp-download-ftp;"/></para>
</listitem>
<listitem>
<para>Download MD5 sum: &ncftp-md5sum;</para>
</listitem>
<listitem>
<para>Download size: &ncftp-size;</para>
</listitem>
<listitem>
<para>Estimated disk space required: &ncftp-buildsize;</para>
</listitem>
<listitem>
<para>Estimated build time: &ncftp-time;</para></listitem>
</itemizedlist>
</sect2>
<sect2 role="installation">
<title>Installation of NcFTP</title>
<para>The <application>Nc<acronym>FTP</acronym></application> package contains
a powerful and flexible interface to the Internet standard File Transfer
Protocol. It is intended to replace or supplement the stock
<command>ftp</command> program.</para>
<para>There are two ways to build <application>NcFTP</application>.
The first (and optimal) way builds most of the functionality as a shared library
and then builds and installs the program linked against this library. The
second method simply links all of the functionality into the binary statically.
This doesn't make the dynamic library available for linking by other applications.
You need to choose which method best suits you. Note that the second method
does <emphasis>not</emphasis> create an entirely statically linked binary;
only the <filename class="libraryfile">libncftp</filename> parts are statically
linked in, in this case. Be aware that building and using the shared library is
covered by the Clarified Artistic License; however, developing applications that
utilize the shared library is subject to a different license.</para>
<para>To install <application>NcFTP</application> using the
first (and optimal) method, run the following commands:</para>
<sect3><title>Package information</title>
<itemizedlist spacing='compact'>
<listitem><para>Download (HTTP): <ulink
url="&ncftp-download-http;"/></para></listitem>
<listitem><para>Download (FTP): <ulink
url="&ncftp-download-ftp;"/></para></listitem>
<listitem><para>Download MD5 sum: &ncftp-md5sum;</para></listitem>
<listitem><para>Download size: &ncftp-size;</para></listitem>
<listitem><para>Estimated disk space required:
&ncftp-buildsize;</para></listitem>
<listitem><para>Estimated build time:
&ncftp-time;</para></listitem></itemizedlist>
</sect3>
</sect2>
<sect2>
<title>Installation of
<application>Nc<acronym>FTP</acronym></application></title>
<para>There are two ways to build
<application>Nc<acronym>FTP</acronym></application>. The first
(and optimal) way builds most of the functionality as a shared library and
then builds and installs the program linked against this library. The second
method simply links all of the functionality into the binary statically. This
doesn't make the dynamic library available for linking by other
applications. You need to choose which method best suits you. Note
that the second method does <emphasis>not</emphasis> create an entirely
statically linked binary; only the
<filename class="libraryfile">libncftp</filename> parts are
statically linked in, in this case. Be aware that building and using the shared
library is covered by the Clarified Artistic License; however, developing
applications that utilize the shared library is subject to a different
license.</para>
<para>To install <application>Nc<acronym>FTP</acronym></application> using the
first (and optimal) method, run the following commands:</para>
<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
<screen><userinput>./configure --prefix=/usr &amp;&amp;
make -C libncftp shared &amp;&amp;
make -C libncftp soinstall &amp;&amp;
make &amp;&amp;
make install</command></userinput></screen>
make install</userinput></screen>
<para>To install <application>Nc<acronym>FTP</acronym></application> using the
second method (with the <filename class="libraryfile">libncftp</filename>
functionality linked in statically) run the following commands:</para>
<para>To install <application>NcFTP</application> using the
second method (with the <filename class="libraryfile">libncftp</filename>
functionality linked in statically) run the following commands:</para>
<screen><userinput><command>./configure --prefix=/usr &amp;&amp;
<screen><userinput>./configure --prefix=/usr &amp;&amp;
make &amp;&amp;
make install</command></userinput></screen>
make install</userinput></screen>
</sect2>
<sect2 role="commands">
<title>Command Explanations</title>
</sect2>
<para><command>make -C ... &amp;&amp; make -C ...</command>:
These commands make and install the dynamic library <filename
class="libraryfile">libncftp</filename> which is then used to link
against when compiling the main program.</para>
</sect2>
<sect2 role="configuration">
<title>Configuring NcFTP</title>
<sect3 id="ncftp-config">
<title>Config Files</title>
<para><filename>~/.ncftp/*</filename>; especially
<filename>~/.ncftp/prefs_v3</filename></para>
<indexterm zone="ncftp ncftp-config">
<primary sortas="e-AA.ncftp/*">~/.ncftp/*</primary>
</indexterm>
</sect3>
<sect3>
<title>Configuration Information</title>
<sect2>
<title>Command explanations</title>
<para>Most <application>NcFTP</application> configuration
is done while in the program, and the configuration files are dealt with
automatically. One exception to this is <filename>~/.ncftp/prefs_v3</filename>.
There are various options to alter in there, including:</para>
<para><screen><command>make -C libncftp shared
make -C libncftp soinstall</command></screen>
These commands make and install the dynamic library <filename
class="libraryfile">libncftp</filename> which is then used to link
against when compiling the main program.</para>
</sect2>
<sect2>
<title>Configuring <application>Nc<acronym>FTP</acronym></application></title>
<sect3><title>Config files</title>
<para><filename>~/.ncftp/*</filename>; especially
<filename>~/.ncftp/prefs_v3</filename></para>
</sect3>
<sect3><title>Configuration Information</title>
<para>Most <application>Nc<acronym>FTP</acronym></application> configuration
is done while in the program, and the configuration files are dealt with
automatically. One exception to this is <filename>~/.ncftp/prefs_v3</filename>.
There are various options to alter in there, including:</para>
<para><screen><userinput>yes-i-know-about-NcFTPd=yes</userinput></screen>
This disables the splash screen advertising the
<application>NcFTPd</application> server.</para>
<para>There are other options in the <filename>prefs_v3</filename> file. Most
of these are self-explanatory.</para>
</sect3>
</sect2>
<sect2>
<title>Contents</title>
<para>The <application>Nc<acronym>FTP</acronym></application> package
contains <filename class="libraryfile">libncftp</filename>,
<command>ncftp</command>, <command>ncftpbatch
</command>, <command>ncftpbookmarks</command>,
<command>ncftpget</command>, <command>ncftpls</command>,
<command>ncftpput</command> and <command>ncftpspooler</command>.</para>
</sect2>
<sect2><title>Description</title>
<sect3><title>ncftp</title>
<para>A browser program for File Transfer Protocol.</para></sect3>
<sect3><title>ncftpbatch</title>
<para>Individual batch <acronym>FTP</acronym> job processor.</para></sect3>
<sect3><title>ncftpbookmarks</title>
<para><application>NcFTP</application> Bookmark Editor
(<application>NCurses</application>-based).</para></sect3>
<sect3><title>ncftpget</title>
<para>Internet file transfer program for scripts.</para></sect3>
<sect3><title>ncftpls</title>
<para>Internet file transfer program for scripts.</para></sect3>
<sect3><title>ncftpput</title>
<para>Internet file transfer program for scripts.</para></sect3>
<sect3><title>ncftpspooler</title>
<para>Global batch <acronym>FTP</acronym> job processor daemon.</para></sect3>
</sect2>
<screen><literal>yes-i-know-about-NcFTPd=yes</literal></screen>
<para>This disables the splash screen advertising the
<application>NcFTPd</application> server.</para>
<para>There are other options in the <filename>prefs_v3</filename> file. Most
of these are self-explanatory.</para>
</sect3>
</sect2>
<sect2 role="content">
<title>Contents</title>
<segmentedlist>
<segtitle>Installed Programs</segtitle>
<segtitle>Installed Library</segtitle>
<segtitle>Installed Directories</segtitle>
<seglistitem>
<seg>ncftp, ncftpbatch, ncftpbookmarks, ncftpget,
ncftpls, ncftpput, and ncftpspooler</seg>
<seg>libncftp</seg>
<seg>None</seg>
</seglistitem>
</segmentedlist>
<variablelist>
<bridgehead renderas="sect3">Short Descriptions</bridgehead>
<?dbfo list-presentation="list"?>
<?dbhtml list-presentation="table"?>
<varlistentry id="ncftp-prog">
<term><command>ncftp</command></term>
<listitem>
<para>a browser program for File Transfer Protocol.</para>
<indexterm zone="ncftp ncftp-prog">
<primary sortas="b-ncftp">ncftp</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="ncftpbatch">
<term><command>ncftpbatch</command></term>
<listitem>
<para>individual batch FTP job processor.</para>
<indexterm zone="ncftp ncftpbatch">
<primary sortas="b-ncftpbatch">ncftpbatch</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="ncftpbookmarks">
<term><command>ncftpbookmarks</command></term>
<listitem>
<para><application>NcFTP</application> Bookmark Editor
(<application>NCurses</application>-based).</para>
<indexterm zone="ncftp ncftpbookmarks">
<primary sortas="b-ncftpbookmarks">ncftpbookmarks</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="ncftpget">
<term><command>ncftpget</command></term>
<listitem>
<para>internet file transfer program for scripts.</para>
<indexterm zone="ncftp ncftpget">
<primary sortas="b-ncftpget">ncftpget</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="ncftpls">
<term><command>ncftpls</command></term>
<listitem>
<para>internet file transfer program for scripts.</para>
<indexterm zone="ncftp ncftpls">
<primary sortas="b-ncftpls">ncftpls</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="ncftpput">
<term><command>ncftpput</command></term>
<listitem>
<para>internet file transfer program for scripts.</para>
<indexterm zone="ncftp ncftpput">
<primary sortas="b-ncftpput">ncftpput</primary>
</indexterm>
</listitem>
</varlistentry>
<varlistentry id="ncftpspooler">
<term><command>ncftpspooler</command></term>
<listitem>
<para>global batch FTP job processor daemon.</para>
<indexterm zone="ncftp ncftpspooler">
<primary sortas="b-ncftpspooler">ncftpspooler</primary>
</indexterm>
</listitem>
</varlistentry>
</variablelist>
</sect2>
</sect1>