📄 userguide.html
字号:
<!-- $Id: userguide.html,v 1.47 2004/05/06 06:52:44 selinger Exp $ --><title>Linux Napster Client: User Guide</title><body bgcolor=#ffffff><h1>Linux Napster Client: User Guide</h1><h2>Peter Selinger (selinger@users.sourceforge.net)</h2><p>Created March 28, 2001. Updated May 6, 2004 for nap version 1.5.3.<p><hr><i>This document describes the linux napster client "nap". Itcovers basic installation, configuration, and usage, as well as somefiner points.</i><hr><h2>1. <a href=#1.>General</a></h2><ul><li><a href=#1.1.>1.1. Introduction</a><li><a href=#1.2.>1.2. Brief history</a><li><a href=#1.3.>1.3. Reporting bugs</a></ul><h2>2. <a href=#2.>Author and copyright</a></h2><h2>3. <a href=#3.>Downloading and installation</a></h2><ul><li><a href=#3.1.>3.1. Source distribution</a><li><a href=#3.2.>3.2. Linux precompiled distribution</a><li><a href=#3.3.>3.3. RPM package</a><li><a href=#3.4.>3.4. Debian package</a><li><a href=#3.5.>3.5. OpenBSD package</a><li><a href=#3.6.>3.6. Windows precompiled distribution</a><li><a href=#3.7.>3.7. Binary distributions with ncurses</a><font size=3 color=#00ff00><b>[new 1.5.1]</b></font><li><a href=#3.8.>3.8. Other formats</a><li><a href=#3.9.>3.9. "What if I don't have root privileges on my machine?"</a></ul><h2>4. <a href=#4.>Basic nap usage</a></h2><ul><li><a href=#4.1.>4.1 Starting nap</a><li><a href=#4.2.>4.2. Simple searches and downloads</a><li><a href=#4.3.>4.3. The download/upload screen</a><li><a href=#4.4.>4.4. Browsing another user's files</a><li><a href=#4.5.>4.5. Where your music files go</a><li><a href=#4.6.>4.6. Navigating the main screen</a><li><a href=#4.7.>4.7. Quitting nap</a><li><a href=#4.8.>4.8. Napster vs. OpenNap</a><li><a href=#4.9.>4.9. News about new releases</a><li><a href=#4.10.>4.10. If you are behind a firewall</a></ul><h2>5. <a href=#5.>More on searching and downloading</a></h2><ul><li><a href=#5.1.>5.1. Advanced searches</a><font size=3 color=#00ff00><b>[updated 1.5.1]</b></font><li><a href=#5.2.>5.2. Pings</a><li><a href=#5.3.>5.3. Advanced navigation of the search result screen</a><li><a href=#5.4.>5.4. Shortcut searches</a><li><a href=#5.5.>5.5. Incomplete downloads and turds</a><li><a href=#5.6.>5.6. Upload and download limits and queueing</a><li><a href=#5.7.>5.7. Purging and retrying failed items</a><li><a href=#5.8.>5.8. Limiting bandwidth</a><li><a href=#5.9.>5.9. Direct browsing</a><li><a href=#5.10.>5.10. Sharing non-music files</a><li><a href=#5.11.>5.11. Managing uploads and downloads from the main screen</a></ul><h2>6. <a href=#6.>Messages, channels, and hotlists</a></h2><ul><li><a href=#6.1.>6.1. Private messages</a><li><a href=#6.2.>6.2. Napster channels</a><li><a href=#6.3.>6.3. Creating your own channel</a><li><a href=#6.4.>6.4. IRC channels</a><li><a href=#6.5.>6.5. The hotlist</a></ul><h2>7. <a href=#7.>Configuration and user variables</a></h2><ul><li><a href=#7.1.>7.1. The configuration files</a><li><a href=#7.2.>7.2. User variables</a><font size=3 color=#ff0000><b>[updated 1.5.2]</b></font><li><a href=#7.3.>7.3. Meta-servers</a><font size=3 color=#ff0000><b>[updated 1.5.3]</b></font><li><a href=#7.4.>7.4. Http proxies</a><li><a href=#7.5.>7.5. Building your library</a><li><a href=#7.6.>7.6. "Some files in my upload directory don't show up on napster."</a></ul><h2>8. <a href=#8.>Advanced features</a></h2><ul><li><a href=#8.1.>8.1. User defined commands and handlers</a><li><a href=#8.2.>8.2. Daemon mode</a><li><a href=#8.3.>8.3. Running nap as a nohup process</a></ul><h2>9. <a href=#9.>Obsolete features</a></h2><ul><li><a href=#9.1.>9.1. Creating a new napster account</a></ul><h2>10. <a href=#10.>Summary of command line options</a> <font size=3 color=#00ff00><b>[updated 1.5.1]</b></font></h2><h2>11. <a href=#11.>Summary of nap commands</a></h2><hr><!----------------------------------------------------------------------><h2><a name=1.></a>1. General</h2><h4><a name=1.1.></a>1.1. Introduction</h4><b>Nap</b> is a console napster client for linux and other operatingsystems, written by Kevin Sullivan. This user guide summarizes some ofits most important features, from a user's point of view. Additionsand corrections are welcome.<h4><a name=1.2.></a>1.2. Brief history</h4>Nap, written by Kevin Sullivan sometime in 1999, was one of the firstnapster clients besides Shawn Fanning's original Windows client. Itwas also the first client that ran on Linux. Kevin learned much aboutthe inner workings of the napster protocol by collaborating withJordan Ritter, who was one of the co-founders of Napster and its chiefserver architect at the time.<p>After a period of inactivity, development of nap resumed in early2001, when I took over the project. Since then, nap has been polished,and many new features have been added, while the original "look andfeel" has been preserved as much as possible. Today, nap is one of themost reliable and stable napster clients. Nap has been packaged for avariety of popular platforms, and it is shipped with distributions ofsome operating systems such as Debian Linux and OpenBSD.<h4><a name=1.3.></a>1.3. Reporting bugs</h4>Nap has a <a href=https://sourceforge.net/projects/nap/>sourceforgeproject page</a>. You are encouraged to use sourceforge's facilitiesfor bug reports, feature requests etc. You can also send me bugreports by email. When you report a bug, please be as specific as youcan about what happened and what you were doing when the bug occurred.<!----------------------------------------------------------------------><h2><a name=2.></a>2. Author and copyright</h2>This user guide can be freely copied, modified, and distributedunder the <a href="http://www.gnu.org/copyleft/gpl.html">GNU publiclicense</a>.<p>The nap software is copyrighted by Kevin Sullivan, under conditions setforth in the file <a href=COPYRIGHT>COPYRIGHT</a>.<!----------------------------------------------------------------------><h2><a name=3.></a>3. Downloading and installation</h2>The current release of nap is available from <a href="http://nap.sourceforge.net/">http://nap.sourceforge.net/</a>.You can download nap in one of several formats. In the following,<code>XXX</code> stands for a version number.<h4><a name=3.1.></a>3.1. Source distribution</h4>This is the most complete distribution of nap, since it contains allthe source code necessary to compile nap. On the other hand, thismeans you have to compile it yourself. This is not very difficult, butif nap is available in precompiled form for your platform, you mightfind that easier.<p>Instructions: download the file <code>nap-XXX.tar.gz</code>. Thefollowing sequence of commands should compile and install nap.<p><pre> tar -zxf nap-XXX.tar.gz cd nap-XXX ./configure make su (type root password) make install</pre><h4><a name=3.2.></a>3.2. Linux precompiled distribution</h4>Instructions: download the file <code>nap-XXX.linux-i386.tar.gz</code>.Install nap as follows:<p><pre> tar -zxf nap-XXX.linux-i386.tar.gz cd nap-XXX.linux-i386 su (type root password) cp nap napping /usr/local/bin chmod 0755 /usr/local/bin/nap chmod 4755 /usr/local/bin/napping</pre>If you are running Linux on a different architecture, such as Alpha, just substitute "alpha" for "i386" in the above instructions.<p>Napping is a helper application for nap which can be safely installedsuid (with permissions 4755). For more on napping, see <ahref=#5.2.>5.2. Pings</a>.<h4><a name=3.3.></a>3.3. RPM package</h4>RPM is the Redhat Package Manager. It allows for easy installation ofpackages on Redhat Linux systems, and on other systems where it isavailable.Instructions: download the file <code>nap-XXX.i386.rpm</code>. As root, install nap with the single command<p><pre> rpm -ivh nap-XXX.i386.rpm</pre><h4><a name=3.4.></a>3.4. Debian package</h4>A nap package is distributed with the next relase (2.3) of<a href="http://www.debian.org/">Debian</a>. To install nap on aproperly configured Debian system you should use the "apt-get" command:<p><pre> apt-get install nap</pre>Alternatively you can download the latest <code>nap_XXX.deb</code>package from the Debian <a href="http://packages.debian.org/unstable/net/nap.html">nap page</a>and install it manually with the "dpkg" command:<p><pre> dpkg -i nap_XXX.deb</pre>You must be root to do this. If you are not root, read section<a href=#3.9.>3.9</a>.<h4><a name=3.5.></a>3.5. OpenBSD package</h4>Instructions: download the file <code>nap-XXX.tgz</code>. Install it with the single command<p><pre> pkg_add nap-XXX.tgz</pre>Note: this file is an OpenBSD Package, not a regular tar archive. Itshould be installed with "pkg_add". If you unpack it with "tar", doit in an empty directory, as it will spill some files into the currentworking directory. If you do unpack this as a tar file, you will findan executable binary in the "bin" subdirectory.<h4><a name=3.6.></a>3.6. Windows precompiled distribution</h4>Instructions: download the file <code>nap-XXX.cygwin32.zip</code>.Unpack it with<p><pre> pkunzip nap-XXX.cygwin32.zip</pre>(Note: pkunzip is a relatively dumb program. My version of it, whichcame with Windows 98, does not understand long filenames, and you mayhave to type something of the form "pkunzip nap-1.~1.zip". Instead ofcreating a directory, it may decide to dump the files in the currentworking directory, and it may rename them. Use "unzip" instead of"pkunzip" if it is available.) Among the unpacked files, you will findan executable file nap.exe and two DLL's (dynamically linkedlibraries): cygncurses5.dll and cygwin1.dll. You need to put theseDLL's in a place where Windows can find them, before runningnap.exe. One way to do this is to copy the two "*.dll" files to alocation (such as C:\WINDOWS) where Windows looks for DLL's. Anotherway is to amend your PATH environment variable, by adding somethinglike the following line to C:\AUTOEXEC.BAT: <p><pre> PATH=%PATH%;C:\DIRECTORY\WHERE\DLLS\ARE</pre>Special care is needed with nap for Windows regarding the location ofthe configuration files. Nap normally looks for its configurationfiles in a directory called ".nap" in the user's home directory. UnderWindows, there is no such thing as a user's home directory, and napwill by default look for the .nap directory in the <i>current workingdirectory</i>. You can change this behavior by defining an environmentvariable HOME. I do this by something like the line<p><pre> set HOME=C:\SOME\DIRECTORY</pre>in the file C:\AUTOEXEC.BAT. This will cause nap to look for (andcreate) its configuration files in the directoryC:\SOME\DIRECTORY\.nap.<p>See also the file README.win which comes with the distribution.<h4><a name=3.7.></a>3.7. Binary distributions with ncurses <font size=3 color=#00ff00><b>[new 1.5.1]</b></font></h4>Some binary distributions for operating systems which do not normallyship with the ncurses library, such as Solaris, come with a file<code>ncurses.so.5</code> or similar. If nap complains that it cannotfind this file, you need to put it somewhere where the dynamic linkercan find it. You need to do one of two things:<ul><li>put the file <code>ncurses.so.5</code> in a standard directorywhere dynamically linked libraries are kept, typically<code>/usr/lib</code> or <code>/usr/local/lib</code>, or<li> set the <code>LD_LIBRARY_PATH</code> environment variable tocontain a path to the directory which contains the<code>ncurses.so.5</code> file. Suppose the file<code>ncurses.so.5</code> is in a directory <i>path</i>. Then you needto issue one of the following two commands, depending on theshell that you use:<p><pre> export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:<i>path</i>" (for sh and bash) setenv LD_LIBRARY_PATH "$LD_LIBRARY_PATH:<i>path</i>" (for csh and tcsh)</pre>Note that this must be done every time you run nap. You might want to putthe above lines in your <code>.bashrc</code> or <code>.tcshrc</code> file.</ul>Important: the ncurses.so.5 file distributed with nap assumes that⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -