AMule Project FAQ - User contributions [en]

Talk:HowTo Compile In Debian/Ubuntu

2005-07-08T11:19:14Z

83.35.60.241:

To successully compile aMule in my Sarge I had to create a link like this:

''ln -s /usr/include/crypto++ /usr/include/cryptopp''

because the make process searchs for config.h in cryptopp directory, not in crypto++.

'''They might have hanged the pathnames again. Thanks for the info :-)<br>'''
'''The problem is that both crypto++ and Debian's crypto++ package have been changing the pathnames in order to suit, and this has become a mess. hehehe<br>'''
'''Anyway, since next [[aMule]] release (it is currenly already implemented into aMule CVS) crypto++ will no longer be needed since it's necessary functions have been coded into aMule.<br>'''
'''Again, thanks for the info!'''

----

28/09/04 - stk : A small error in step 8 : remplace "ls -s /usr/include/crypto++ /usr/include/cryptopp" by "ln -s /usr/include/crypto++ /usr/include/cryptopp" ;)

'''Thanx a lot! Fixed.'''

----

other info : In my Sarge, with libcrypto++5.1_5.1-5_i386.deb and libcrypto++-dev_5.1-5_i386.deb package, I have an error : ld cannot find lcryptopp..

so, I have made a link with this command : "ln -s /usr/lib/libcrypto++5.1.so /usr/lib/libcryptopp.so" and run ldconfig -> it work !

'''I completly forgot to answer to you :-( i added your comment to the howto some long time ago. thanks :)'''

----

jeremie :

Installing 200rc6 is a piece of cake with your advices. (sarge on 20041019)

No more fuss about crypto++ and so on, just apt-get the packages, then configure / make / make install.

It takes 5 minutes.

Thanks for the names of the dependancies.

'''Very much thanks for your words! Makes me feel batter :)'''

----

Works just fine in Ubuntu

I just wanted to let you know that this HowTo also applies just fine to "HowTo Compile in Unbuntu". Sure, anyone would have probably guessed that, but I can confirm it now... :-)

'''Hey! Thanx! THat is indeed an important note since Ubunto is being so successful and popular lately. I'll try to fix it somewhere to link ubunto users there too :)'''

----

Hi, I had problems with the ''libcurl2-dev''. Is ''libcurl3-dev'' the actual package?

'''Yes, you can use libcurl3-dev without any problems. In fact, thatnks for the note, i just changed it to point to liburl3 in the guide ;-)'''

-----

17/05/2005
Hi, I don't want compile amule :-), so I add ''deb http://www.vollstreckernet.de/debian/ testing amule'' and
''deb http://www.vollstreckernet.de/debian/ testing wx'' in my /etc/apt/sources.list. But ''apt-get update && apt-get install amule'' don't work... I find an error in ''http://www.vollstreckernet.de/debian/dists/testing/amule/binary-i386/Packages.gz
''. In fact, Packages.gz is broken!!!

'''Please contact Vollstrecker in http://forum.amule.org or mail him. He is the deb packager for CVS builds. Thanks :-)'''
---------------
22/05/05
When I run (Debian Sarge and Amule 2.0.1)

cd ~/aMule-compilation/aMule-2.0.1/ && ./configure && make

I get (after compilation process):

#bash: make: command not found

And I cannot execute make install....

I warn you that I did the compilation following absolutely all the steps that this page says: http://www.amule.org/wiki/index.php/HowTo_Compile_In_Debian
??????

Thanks in advance

Richard

'''Heh, well, you're right, I didn't think anyone would not have ''make'' installed ;-)'''

'''Ok, so just ''apt-get install make'''''

'''Now follow the article again, it will work now (I guess. If it still doesn't, please ask again :-))'''

Mmmmmmmm.... what ganso I am... You were right, I had not installed make (installed Sarge with manual selection of packages... and... you know, are a few and one gets dizzy...).
But now I request another aid to you that will serve, I suppose, for many users. Tell me exactly how to share in a same PC downloads of Win's emule in Linux's amule and vice versa...
Because I have put in a partition FAT32 the directories "incoming" and "temp" of Emule and I have mounted those same directories in Sarge (those directories are NOT mounted in the default folder of Amule, but in "/" (like this: /amule/incoming/temp).
But when I watch in "Traffic" of Amule does not see any of downloads that are in the directories mounted from FAT32....
Regards
Richard

'''Well, there's no trick. Just make sure aMule -> Preferences -> Directories points to the right directories ;-) Also take a look at [[FAQ_aMule#Can_I_use_eMule's_files_and_settings_and_vice-versa?]]'''

'''Please refer to http://forum.amule.org for non Debian-article-related stuff ;-) So any further questions regarding using your eMule files, please post them at the forums :-)'''

'''Greets.'''

== Problem with wxWidgets and GTK2 ==

When i configure amule 2.0.3 in my sarge
i see this line
checking if wxWidgets was linked with GTK2... no

And when configure script finish i watch that

"Configure script has finished system check.

Configured aMule 2.0.3 for 'i686-pc-linux'.

aMule enabled options:

**** aMule Core ****
Prefix where aMule should be installed? /usr/local
Should aMule be compiled with i18n support? yes
Should aMule be compiled in debug mode? yes
Should aMule be compiled with profiling? no
Should aMule be compiled with optimizations? no
Should aMule be compiled with taskbar icon support? yes
Should aMule be compiled with old GTK taskbar icon? yes
Should aMule be compiled with UTF-8 taskbar icon support? no
Should aMule be linked against patched gsocket? yes
Should aMule monolithic application be built? yes
Should aMule daemon version be built? no
Should aMule remote gui be built? (EXPERIMENTAL) no
Crypto++ library/headers style? embedded

**** aMule TextClient ****
Should aMule Command Line Client be built? no
Should aMule GUI Client be built? no

**** aMule WebServer ****
Should aMule WebServer be built? no
Should aMule WebServer GUI be built? no

**** aMule ED2K Links Handler ****
Should aMule ED2K Links Handler be built? yes

**** aMuleLinkCreator ****
Should aMuleLinkCreator GUI version (alc) be built? no
Should aMuleLinkCreator for console (alcc) be built? no

**** aMule Statistics ****
Should C aMule Statistics (CAS) be built? no
Should aMule GUI Statistics (wxCas) be built? no

**** General Libraries and Tools ****
Should ccache support be enabled? no
Libraries aMule will use to build:
wxWidgets 2.4.2
GTK Not detected
crypto++ embedded
zlib 1.2.2

WARNING! gd-lib >= 2.0.0, or a functional gd.h (from gd-devel) not found.
amuleweb will be compiled but file download progress bar images will NOT be generated.
See the above error on gd check for solutions.
"
How can I fix it?

'''There's nothing to fix. Just run ''make'' now. It didn't detect the GTK version but that doesn't prevent it from compiling as long as it detected wxGTK correctly.'''

IPFilter

2005-07-08T02:02:20Z

83.35.60.241:

== Description ==

The [[IP]] Filter blocks traffic from/to IPs and ranges of [[IP]]s with our [[client]]. This means that those [[IP]]s which get blocked will not be able neither to upload to us nor to download from us.

This filter is read from [[ipfilter.dat_file|''~/.aMule/ipfilter.dat'']] which is a file which's contents describes the valid and blocked [[IP]] ranges.

== [[ipfilter.dat file]] ==

The information and details about the [[ipfilter.dat file]] can be found [[ipfilter.dat file|here]].

== Using the [[IP]] Filter in [[aMule]] ==

The ''Access level'' of the [[IP]] filter is selected in [[aMule]] through "Preferences" -> "Security" -> "IP Filtering" -> "Filtering level" (in [[aMule]] versions up to 2.0.0-rc8 it is under "Server", instead of "Security").

'''NOTE:''' [[aMule]]'s ''ipfilter.dat'' file is 100% compatible with [[eMule]]'s ([[eMule]]'s [http://www.methlabs.org/methlabs.htm PeerGuardian] format, which is the most popular. The ''antip2p.txt'' format isn't yet supported).

== [[IP]] Filter sources ==

http://www.emulext.net/seguridad/Mc4TuTi/ipfilter.dat (last update February 2005)

http://www.morph-mod.de/morph/ipfilter/ipfilter.dat (last update 28. May 200'''4''')

http://emulepawcio.sourceforge.net/nieuwe_site/Ipfilter_fakes/ipfilter.dat (last update 17 June 2005)

http://www.openmedia.info/p27.html (last update 30. April 2005)
== Hard coded [[IP]] filter in [[aMule]] ==

[[aMule]] has a range of [[IP]]s which it filters by default following the [http://www.rfc-editor.org/rfc/rfc3330.txt RFC 3330] document. This ranges are:

<pre>
Address Block Present Use Reference
----------------------------------------------------------------------
"0.0.0.0/8", // "This" Network [RFC1700, page 4]
"10.0.0.0/8", // Private-Use Networks [RFC1918]
"14.0.0.0/8", // Public-Data Networks [RFC1700, page 181]
"24.0.0.0/8", // Cable Television Networks --
"39.0.0.0/8", // Reserved but subject
// to allocation [RFC1797]
"127.0.0.0/8", // Loopback [RFC1700, page 5]
"128.0.0.0/16", // Reserved but subject
// to allocation --
"169.254.0.0/16", // Link Local --
"172.16.0.0/12", // Private-Use Networks [RFC1918]
"191.255.0.0/16", // Reserved but subject
// to allocation --
"192.0.0.0/24", // Reserved but subject
// to allocation --
"192.0.2.0/24", // Test-Net
"192.88.99.0/24", // 6to4 Relay Anycast [RFC3068]
"192.168.0.0/16", // Private-Use Networks [RFC1918]
"198.18.0.0/15", // Network Interconnect
// Device Benchmark Testing [RFC2544]
"223.255.255.0/24",// Reserved but subject
// to allocation --
"224.0.0.0/4", // Multicast [RFC3171]
"240.0.0.0/4" // Reserved for Future Use [RFC1700, page 4]
</pre>

However, you can un-filter this range of [http://www.faqs.org/rfcs/rfc791.html IP]s by unchecking "Preferences"->"Security"->"IP-filtering"->"Always filter bad IPs" (on [[aMule]] versions up to 2.0.0-rc8, this option can be found in "Preferences"->"Server"->"Always filter bad IPs").

Ipfilter.dat file

2005-07-08T01:57:55Z

83.35.60.241:

== File ==

'''Name:''' ''onlinesig.dat''

'''Location:''' ''~/.aMule/''

== Description ==

The usefullness of this file is described in the [[IPFilter|IP Filter article]].

== Format ==

The format of the ''ipfilter.dat'' file is as follows:

'''[[IP]]s range , Access level , Description'''

''Access level'' values '''lower than 127''' are ''blocked [[IP]]s''' and values '''over 127''' are '''allowed [[IP]]s'''.

''[[IP]]s range'' values are described by an initial [[IP]] a dash and the ending [[IP]] of tha range (the dash must be separated from the [[IP]]s by a single space character).

== Example ==

''000.000.000.000 - 000.255.255.255 , 000 , "This" Network [RFC1700, page 4]''<br>
''169.254.0.0 - 169.254.0.255 , 000 , Link local''<br>
''192.168.0.0 , 192.168.255.255 , Optionally block my LAN''<br>
''127.0.0.0 , 127.255.255.255 , Optionally block localhost (Loopback)''

HowTo Compile In Debian/Ubuntu

2005-07-07T17:36:45Z

83.35.60.241:

HowTo compile [[aMule]] in [[Debian]] or [http://www.ubuntulinux.org Ubuntu] by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

You can just install latest [[aMule CVS]] through debs adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule
deb http://www.vollstreckernet.de/debian/ testing wx

'''NOTE:''' The second line is necessary for Sarge users and strongly recommended for Sid users.

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:
*amule
*amule-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

''apt-get install amuleweb''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

== Notes before starting ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be unable to install the wxGTK, wxbase and Crypto++ libraries since they were not available in the current minimum compatible versions (2.4.2 and 2.5.1 respectively) when Woody was released.''

''The best for Woody users is to switch to the Sarge or Sid branch. That can be done with the following command (again, you must be root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''or''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''to switch to the Sarge/testing branch, or with''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''or''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''to switch to the Sid/unstable branch.''

''If Woody users are not be interested in switching to Sarge they will need to download Woody-backported debian packages by adding the following line to /etc/apt/sources.list (remember to <code>"apt-get update"</code> after adding this line):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''What's more, [http://www.thermoman.de thermoman] stopped working on the [[aMule]] backports for [http://www.debian.org Woody] on the [[aMule]] 2.0.0-rc5 release, so newer [[aMule]] releases backports are unavailable. Sorry.''

'''''Note 3:''' Sarge users won't have any dependecy problems any longer, since both crypto++ and wxWidgets have both been in Sarge for some time now. So there's no longer any need to update ''sources.list'' on Debian Sarge distributions.''

'''''Note 4:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

'''''Note 7:''' Woody users will most probably be unable to get libgd2-xpm-dev and libcurl3-dev since those packages aren't available for Woody. For libcurl3-dev you can just install libcurl2-dev and go on, everything will be ok For libgd2-xpm, at the moment there is no backport available but, since this library is only used by CAS (and suggested, not even required), it won't give any problems on compilation time. Just be aware that <code>cas -o</code> won't work.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 8:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 1.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 9:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 10:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 11:''' Please take a look at the [[configure|configure article]].''

'''''Note 12:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 13:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

HowTo Compile In Debian/Ubuntu

2005-07-07T17:35:59Z

83.35.60.241:

HowTo compile [[aMule]] in [[Debian]] or Ubuntu by ''[[User:Jacobo221|Jacobo221]]'' and [http://www.gnu.org GNU] [http://www.kernel.org Linux] helpers

Very special thanks to ''darknox'', ''Arathornz'', ''guest234'', ''parasito'', ''maya'' and ''klando'' for their tests!

'''NOTE:''' This howto will also work for [http://www.ubuntulinux.com Ubuntu Linux].

== Are you sure you want to compile? ==

You can just install latest [[aMule CVS]] through debs adding the following lines into your ''/etc/apt/sources.list'' file:

deb http://www.vollstreckernet.de/debian/ testing amule
deb http://www.vollstreckernet.de/debian/ testing wx

'''NOTE:''' The second line is necessary for Sarge users and strongly recommended for Sid users.

Now run ''apt-get update && apt-get install amule''

You might also want to take a look at the other available [[aMule]] utilities:
*amule
*amule-common
*amuled
*amule-remote-gui
*amuleweb
*amulewebdlg
*amule-cas
*amule-wxcas
*amule-xas
*amule-utils

For example, if you think [[aMule]]'s [[Webserver|Web interface]] rocks and you want to have it too, enter this line after the one above:

''apt-get install amuleweb''

If you still want to compile [[aMule]] instead of just installing a binary, keep reading...

== Notes before starting ==

'''Important:''' Have in mind that this HowTo was done having in mind aMule 2.0.0 or greater in [[Debian]] 3.0 (Woody/Sarge/Sid).

This HowTo is based on using the apt-get package installer tool, which means you'll have to be able to get super-user (root) access. Also, apt-get requires a perfect packet dependencies installed system. If you usually use apt-get for installing any application, skip this and go to the next section. If you rarely use apt-get but, instead, use dpkg, you can;

A) (Recommended) Solve all the dependencies problems on your system. This can be done by taking a look at the <code>"dpkg -C"</code> output and installing/removing/updating the packages it mentions depending on what's required. This option is the recommended since it will not only ensure your aMule compilation will be most surely correct, but it will also make your system the most stable it can possibly be and from now on you'll be able to use apt-get to not only make easier installations, but also to easily upgrade your system.

B) Force apt-get to ignore the dependencies problems using the -f or --fix-broken switches (just one of them, since they're exactly the same, so that'd be, for example, <code>"apt-get install -f ..."</code>). This option may cause a corrupt installation of some packages which may cause the apps not to work. Also have in mind that using this switch in a system with dependencies problems may cause the system to completely break if the package being installed is a base package (although this is not the case).

C) Follow this instructions but, instead of using <code>"apt-get install foo"</code>, use <code>"dpkg -i foo"</code> where foo is the package to install. Remember the packages must be already on the system when installing packages with dpkg. Remember also to download any "Depends" package since it most-surely will be necessary for successfully compiling [[aMule]]. Avoid using whichever of the following dpkg switches: --force-all --force-depends-version --force-depends --force-conflicts

If you usually install applications from source, read deltaHF's [[Compilation_Installation|"aMule compilation / installation HowTo"]] since your system might not be complying the Debian aMule package dependencies although <code>"dpkg -C"</code> shows no errors.

== The easiest: Preparing the system ==

Once you decided to use apt-get, you must make sure you'll be downloading the latest versions of the packages (aMule team has discovered bugs in some deb packages that would make aMule impossible to compile on Debian without compiling some other libraries too. This bugs have been mostly fixed in those affected debian packages, so it is very important to be sure to have the packages up to date). This is done by issuing:

apt-get update && apt-get dist-upgrade

'''''Note 1:''' You must be root user to do this. Log in as root or <code>"su"</code> or use <code>"sudo"</code>. NB: <code>"sudo"</code> must be specified on both apt-get commands, that is:''

sudo apt-get update && sudo apt-get dist-upgrade

''<code>"sudo"</code> is not a base command, so it may not be installed on your system, although it most probably will. Be aware that following this HowTo entirely as root may bring some problems later such as being unable to delete certain files as a normal user, so please only use root priviledges when necessary.''

'''''Note 2:''' Woody users (that is, people stuck in the stable Debian 3.0 branch) will be unable to install the wxGTK, wxbase and Crypto++ libraries since they were not available in the current minimum compatible versions (2.4.2 and 2.5.1 respectively) when Woody was released.''

''The best for Woody users is to switch to the Sarge or Sid branch. That can be done with the following command (again, you must be root)''

perl -pi.$$ -e "s/(\bstable|woody)/testing/g" /etc/apt/sources.list

''or''

perl -pi.$$ -e "s/(\bstable|woody)/sarge/g" /etc/apt/sources.list

''to switch to the Sarge/testing branch, or with''

perl -pi.$$ -e "s/(\bstable|woody)/unstable/g" /etc/apt/sources.list
''or''

perl -pi.$$ -e "s/(\bstable|woody)/sid/g" /etc/apt/sources.list

''to switch to the Sid/unstable branch.''

''If Woody users are not be interested in switching to Sarge they will need to download Woody-backported debian packages by adding the following line to /etc/apt/sources.list (remember to <code>"apt-get update"</code> after adding this line):''

deb <nowiki>http://debian.thermoman.de/</nowiki> woody wxwindows2.4 libcrypto++

''What's more, [http://www.thermoman.de thermoman] stopped working on the [[aMule]] backports for [http://www.debian.org Woody] on the [[aMule]] 2.0.0-rc5 release, so newer [[aMule]] releases backports are unavailable. Sorry.''

'''''Note 3:''' Sarge users won't have any dependecy problems any longer, since both crypto++ and wxWidgets have both been in Sarge for some time now. So there's no longer any need to update ''sources.list'' on Debian Sarge distributions.''

'''''Note 4:''' Sid users (that is, people holding the cutting-edge unstable Debian 3.0 branch) could suffer problems from packages not completely implemented or with broken dependencies (both are normal issues in the unstable branch). It is very important to keep this in mind since a compiler (g++) will be installed so it could also be broken and, with it, most applications compiled with it (once upgraded, of course). If a package was broken, to downgrade you can use the --force-downgrade switch with dpkg.''

If for whatever reason you think this is too much of a complication, you can just wait a few days until the aMule binary version comes out for your architecture (that is, a .deb file).

== The fastest: Installing the necessary packages ==
Remember you need to be root to install applications using apt-get, since apt-get installs system-wide applications. So, log in as root, use "su" or add "sudo" before every command shown here.

The following are the packages which must be installed:

1) Install the latest stable g++ compiler and the C++ Standard Library

apt-get install g++

the required libraries for compiling [[aMule]] (wxbase is not really a requiered packet to compile aMule but, unless you know what you're doing, be sure you install it. I won't show in this this guide how to force aMule's compilation without wxbase):

apt-get install libwxbase2.4-dev libcurl3-dev libgtk1.2-dev libwxgtk2.4-dev

Alternatively you can use <code>apt-get build-dep amule</code> to get all the required depencies for compilation. Anyway, this last method is not sure to work, since it will depend on the latest version on the Debian repository and later versions or CVS versions might have different dependencies.
And the required utilities for compiling [[aMule]]:

apt-get install gettext make

'''''Note 5:''' This can all be done in a single command line, which might be more handy for users using <code>"sudo"</code> to gain root priviledges:''

apt-get install g++ libwxbase2.4-dev libcurl3-dev libgtk1.2-dev gettext make

'''''Note 6:''' From aMule 2.0.0-rc1 to aMule 2.0.0-rc5 (inclusive) the package ''libcrypto++-dev'' was necessary for compiling aMule, so if you are compiling any of such versions, apt-get libcrypto++-dev too.

Also, you might be interested in installing libgd2-noxpm-dev if you plan to compile CAS. It is not a required library for compiling CAS, this library is only used by CAS for creating images (since v2.0.0-rc3) on the current aMule status (by running <code>cas -o</code>). If you plan to use this feature of CAS, you need to install LibGD2. Anyway, CAS will compile perfectly well even if LibGD2 isn't installed, since it detects, on compilation time, if this library is installed.''

'''''Note 7:''' Woody users will most probably be unable to get libgd2-xpm-dev and libcurl3-dev since those packages aren't available for Woody. For libcurl3-dev you can just install libcurl2-dev and go on, everything will be ok For libgd2-xpm, at the moment there is no backport available but, since this library is only used by CAS (and suggested, not even required), it won't give any problems on compilation time. Just be aware that <code>cas -o</code> won't work.''

2) Download the latest released [[aMule]] source code from [http://www.amule.org/files/files.php?cat=6 here] (or look [[AMule_CVS|here]] for an up-to-date link).

'''''Note 8:''' From now on, I will suppose we are installing aMule 2.0.0-rc3''

3) Fix Crypto++ Library 5.1 if using it.

From [[aMule]] 2.0.0-rc1 to a aMule 1.0.0-rc5 (inclusive) this library is required because [[aMule]] is now supporting SecureIdent (remember, since aMule 2.0.0-rc6, libcrypto++ is optional and not needed by default), but the [[Libcrypto|Crypto++]] [[Debian]] package has had lots of compiling bugs and still has one (although the rest have been fixed after aMule team's reports). Remember you should have update and dist-upgraded apt-get before installing any [[Debian]] package in this HowTo, otherwise, you could be installing (or already have installed) a buggy Crypto++ package and this fix will not suit your needs. To fix the latest [[Libcrypto|crypto++]] [[Debian]] package only a symbolic link is needed:''

ln -s /usr/include/crypto++/cryptopp_config.h /usr/include/crypto++/config.h

''If you still can't compile crypto++, try compiling it after running the following command:''

ln -s /usr/include/crypto++ /usr/include/cryptopp

'''''Note 9:''' Since this link needs write permissions in /usr/lib, super-user (root) priviledges are needed. Again, this can be done easily with <code>"su"</code> or <code>"sudo"</code>.''

== The hardest: Compiling [[aMule]] ==

4) Extract the sources. The following will create a folder on your user's home directory where it will extract the sources with the -C switch into it (the following command understands that [[aMule]]'s sources are on the current directory):

mkdir ~/aMule-compilation/ && tar xzfv aMule-2.0.0rc3.tar.gz -C ~/aMule-compilation/ && cd ~/aMule-compilation/

'''''Note 10:''' Remember I'm supposing you are extracting [[aMule]] 2.0.0-rc3. Change the file name if it doesn't correspond to the actual packed source code filename.''

5) Compile [[aMule]]! The following command will actually switch to the directory containing [[aMule]] 2.0.0rc3 and compile it:

cd ~/aMule-compilation/aMule-2.0.0rc3/ && ./configure && make

'''''Note 11:''' Please take a look at the [[configure|configure article]].''

'''''Note 12:''' You should check the output of
./configure --help | more
to see if there is any configure switch which might be of your interest, such as --disable-debug --enable-optimise or --bindir= ''

'''''Note 13:''' if you get an error message, while compiling, similar to: "In file included from /usr/include/wx/***:***, [...] /usr/include/wx/******:***: internal compiler error: Segmentation fault", then you most probably have problems with wxWidgets. Try with''

apt-get install --reinstall wxwin2.4-headers libwxbase2.4 libwxgtk2.4-dev

''which will reinstall wxWidgets and will most probably fix the compilation error.''

== Meeting satisfaction: Installing aMule! ==

8) What's left? Install aMule (remember you must be root, so log in as root or use <code>"su"</code> or <code>"sudo"</code>):

make install

Now you can remove the sources so you free up space in your hard disk by running:

rm -rf ~/aMule-compilation/

== The end: Final checks ==

If you have sometime installed aMule from the Debian packages (no matter if the package came from http://gunnm.org/~soda ), you will have aMule binaries installed in /usr/bin. But <code>"make install"</code> installs binnaries in /usr/local/bin (unless --prefix= is set in configure). This leads us to the point that when typing "amule" anyone of the two installed aMule versions might be invoked (which one is executed will depend on the $PATH environment variable. You can check it by typing <code>"type amule"</code>). The walk around is very easy: remove the aMule installed through [[Debian]] package. You can do this with the command "apt-get remove amule" (do not use <code>"apt-get remove --purge"</code> or you might loose your [[aMule]] settings) or with <code>"dpkg --remove amule"</code> (again, never ever use <code>"dpkg --purge"</code> or you might loose your [[aMule]] settings). apt-get will remove aMule-utils if you have them installed (only available as a separate package in Sid, in Sarge and Woody aMule utils are included in the base aMule package) while dpkg will leave aMule-utils installed on the system (which, in general, is a bad idea).

Also, if you installed xmule sometime or you are planing to install it, have in mind that the [[ed2k command]] exists both in [[aMule]] and [[xMule]]. You might want to run `type ed2k` to see which [[ed2k command]] will be executed and rename the other so you make sure it's never executed by mistake.

== You're done... ==

That's it! Your own compiled [[aMule]] is installed on your system and ready to go.

To run [[aMule]], just type <code>"amule"</code>. You can check if everything worked by typing <code>"amule -v"</code> and check if the displayed version corresponds with the one you were compiling/installing.

If this HowTo didn't help, you have a rare problem on your system ;-) Take a look at http://www.amule.org ([http://www.amule.org/amule aMule Forums] at http://forum.amule.org ) or visit us in #amule on irc.freenode.net and (don't doubt) we'll try to do our best to help you.

== Final notes ==

If you are in one of those rare cases when you wish to compile [[aMule]] statically, install also ''libtiff4-dev'' (through ''apt-get install libtiff4-dev''). Anyway, this is '''NOT''' recommended and, in fact, will probably not do any better or even, not work at all.

Getting Started-es

2005-07-07T17:34:59Z

83.35.60.241:

<center>
[[Getting_Started|English]] | [[Getting_Started-fr|Français]] | [[Getting_Started-nl|Nederlands]] | '''Español''' | [[Getting_Started-de|Deutsch]]

<h2>(Traducido por ''[[User:Kno|KNO]]'')</h2>
</center>
== Qué es [[aMule]] ==

[[aMule]] es un cliente para la red de [[P2P|peer-to-peer]] [[FAQ_eD2k-Kademlia|eD2k]] comúnmente llamada [[FAQ_eD2k-Kademlia|red eDonkey]], o red ed2k ([[eDonkey2000]]). Esta guía no requiere que estes familiarizado con esta otra red (pero ayuda), pero sí es necesario que tengas instalado [[aMule]] en tu ordenador.
Si no tienes instalado [[aMule]] todavía, ve a la página de guía de instalación para tu sistema. Puedes encontrar los enlaces en la [[Main_Page|página principal]].

== Ejecutando [[aMule]] por primera vez ==
Comienza ejecutando [[aMule]]. Normalmente ésto se puede hacer ejecutando el comando ''amule'' en una ventana de consola o con cualquier otro método que te permita tu distribución y tu entorno gráfico.

Una vez iniciado, si estás usando una versión [http://www.gnu.org/software/cvs CVS], [[aMule]] te sacará un mensaje que te dice que estás ejecutándolo por primera vez. ''Read this to learn what you are getting yourself into ;)''

=== Configurando [[aMule]] ===
En la parte de arriba de la ventana de [[aMule]], hay una fila de iconos con texto. Pincha en el que pone preferencias para entrar en la ventana de configuración. Antes de comenzar a descargar ficheros, necesitas configurar correctamente la velocidad de tu conexión y posiblemente otras cosas.

==== Velocidad de Conexión ====
Tienes que saber que los clientes eDonkey obligan a compartir, esto significa que para poder descargar cosas, tienes que compartir fichero tú mismo (no te preocupes si no tienes nada para compartir). Esta oblicación se hace de dos maneras:
* Tu velocidad de descarga depende de cómo de rápido compartas. Si tu velocidad de subida está en algo inferior a 10 tu velocidad máxima de descarga será 3 o cuatro veces la de subida (lee [[FAQ_eD2k-Kademlia-es#¿Hay alguna limitación en la red ED2K?|esto]] para saber más acerca de esta limitación), así que si limitas la velocidad de subida a 5kb/s, solo podrás descargar a 20kb/s.
* Los ficheros parcialmente descargados también serán compartidos. Automaticamente, comienzas a compartir un fichero una vez que has recibido al menos un [[FAQ_eD2k-Kademlia-es#¿Qué es un chunk?|chunk]] (un [[FAQ_eD2k-Kademlia-es#¿Qué es un chunk?|chunk]] es una parte de 9.28Mb de un fichero).

Nota: Si entras en el [http://forum.amule.org aMule foro] o en el [[IRC|canal de IRC]] para quejarte de esto o pedir que cambiemos el ratio, te daré caza y me comeré tu bazo. -- [[User:Xaignar|Xaignar]]

Cuando abres por primera vez la ventana de Preferencias, la página mostrada será "General", que contiene algunos ajustes generales, como el [[nickname|alias]] que verán los demas cuando estan descargando de ti o dandote ficheros.
Para seguir, pincha en la pestaña llamada "Conexion":

http://www.amule.org/dev-up/Limits.png

Los únicos ajustes importantes para esta guía están dentro del marco "Límites" señalados como "Descargar" y "Subida". No es necesario meter un máximo en la velocidad de descarga, pero es recomendable que pongas el máximo de la velocidad de subida en torno al 80% de la capacidad subida de tu conexión, ya que si no, ésto puede causar descargas mas lentas.

Una vez que has introducido los valores adecuados, puedes explorar el resto de los ajustes. Para salvar los cambios, simplemente haz click en el botón "OK".

=== Conectando a un Servidor ===

Ahora deberías estar viendo la ventana de servidores:

http://www.amule.org/dev-up/ServerDlg.png

La lista vacía normalmente contiene los servidores que conoces, pero como es la primera vez que ejecutas [[aMule]], no hay ninguno. Para remediar esta situación, simplemente haz click en el campo de texto que pone ''http://www.srv1000.com/azz/server.met'' y pulsa enter.
Se abrirá una ventana y se cerrará de nuevo cuando la descarga de la lista de servidores haya terminado.

Ahora deberias tener una lista llena de servidores, si no es así busca en [http://www.google.es/search?hl=es&q=server.met&btnG=B%C3%BAsqueda+en+Google&meta= google] ''server.met'' y colocarlo en el directorio ''.aMule'' de tu home. La lista debe ser como esta:

http://www.amule.org/dev-up/ServerList.png

Lo siguiente que necesitas es conectarte a un [[server|servidor]]. Normalmente es una buena idea conectarte a uno que tenga el máximo de usuarios posible, pero por ahora, solo pincha en el botón "Conectar" que está cerga de la esquina superior izquierda de la ventana. Esto te conectará a un servidor de forma aleatoria. Espera mientras [[aMule]] contacta con los servidores e intenta establecer una conexión. Una vez que ésto pase, procede a la siguiente sección.

=== [[FAQ_eD2k-Kademlia-es#¿Qué es ID baja e ID alta?|ID baja e ID alta]] ===
Dado que las redes [[P2P|p2p]] trabajan contactando [[Client|clients]] directamente unos con otros, estar detrás de un cortafuegos o un router puede causar verdaderos problemas. Si no sabes si estás o no detrás de un cortafuegos, simplemente mira el icono en la esquina inferior izquierda de la ventana. Si es verde, entonces tienes [[FAQ_eD2k-Kademlia-es#¿Qué es ID baja e ID alta?|ID baja e ID alta]] y puedes seguir, pero si es amarillo, necesitas mirar la página [[Firewall|Firewalls]] y/o [[AMule_problems-es#aMule se conecta a los servidores, pero siempre obtiene LowID. ¿Por que? Y, ¿Puedo hacer algo al respecto?|problemas comunes]], ya que tener [[FAQ_eD2k-Kademlia-es#¿Qué es ID baja e ID alta?|ID baja e ID alta]] significa reducir muchisimo las capacidades de descarga.

== Uso Básico ==
Esto cubre el uso básico de [[aMule]].

=== Buscando y Descargando ===
Bien, es sobre lo que va lo del [[P2P|p2p]]: descargar ficheros.
Es la causa de esta guia. Supón que lo que realmente quieres descargar es la última versión en CD de [http://www.knoppix.org Knoppix] (¿quién no?). Para descargar esto, lo primero es asegurarte de que estás conectado a un servidor. Después pincha en el botón "Búsquedas".

Te saldrá una ventana como esta:

http://www.amule.org/dev-up/SearchDlg.png

Como solo nos importan las imágenes de CD, pinchamos en "Opciones Extendidas" y seleccionamos "Imágenes de CD" en la lista "Tipo". Dejamos seleccionado "Búsqueda [[Search#Local_search|Local]]", ya que solo queremos buscar en el [[server|servidor]] al que nos hemos conectado.
Ahora metemos ''Knoppix'' en el campo "Nombre" que esa arriba y pulsa enter o en el boton "Comenzar". Deberías tener la lista llena de resultados:

http://www.amule.org/dev-up/SearchResults.png

Ordenemos la lista por número de [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] pinchando dos veces en la columna llamada "Fuentes" para encontrar de forma fácil el fichero que más gente tiene. El segundo parece interesante, así que pinchamos dos veces sobre él (o pinchamos una vez y luego en el botón "Descargar"). Con esto el fichero pasará a la cola de descargas.

Los resultados se verán en diferentes colores, que significan lo siguiente:
* Azul representa el número de fuentes, cuanto mas oscuro es el azul mas fuentes.
* Rojo representa los archivos que estas descargando.
* Verde son los archivos que ya has descargado o compartido antes, es decir, archivos que ya tienes.

=== La Cola de Descargas ===
Pincha en el botón "Tráfico" para obtener una lista de los archivos que están en la cola para descargar:

http://www.amule.org/dev-up/DownloadQueue.png

Si tienes suerte, la barra de probreso se convertirá en azul oscuro, que significa que mucha gente tiene ese fichero (lee [[FAQ_aMule-es#¿Qué significan los colores de la barra de progreso?|esto]] para saber más sobre ello).
Preocupate por los archivos con partes en rojo, ya que significa que nadie tiene este fichero y casi seguro que no serás capaz de descargarlo completamente.

Si haces doble click en un archivo, podrás ver las [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] que has encontrado para ese archivo.

==== Sobre Filas y Columnas ====
Estas son las columnas en la Cola de Descargas:

; ''Nombre de Archivo'' : El nombre del archivo
; ''Tamaño'' : El tamaño del archivo. La red eDonkey2000 soporta archivos de hasta 4GB (lee [[FAQ_eD2k-Kademlia-es# ¿Hay alguna limitación en la red ED2K?|más]] sobre esto).
; ''Transferido'' : Muestra cuanto has descargado.
; ''Completado'' : Esta columna muestra cuanto del archivo has completado. Fijate que puede ser distinto de la columna Transferido debido a las perdidas por corrupción y/o ganancias por la compresión que usan los [[Client|clientes] *Mule (lee [[FAQ_aMule-es#¿Cual es la diferencia entre Transferido y Completado en la ventana de Tráfico?|más]] sobre esta diferencia).
; ''Progreso'' : Esta barra muestra el progreso actual del archivo, los colores signican lo siguiente ([[FAQ_aMule-es#¿Qué significan los colores de la barra de progreso?|recurso]] alternativo):
* Azul: Cuantas fuentes tienen esta parte, cuanto mas oscuro mas fuentes la tienen.
* Rojo: No hay [[FAQ_eD2k-Kademlia-es# ¿Qué es una fuente?|fuentes]] conocidas para esta parte.
* Negro: Ya tienes esta parte.
* Amarillo: Te estás descargando esta parte.
: Una pequeña barra verde encima de la barra grande indica el % de descarga.
; ''Fuentes'' : Hay tres campos en esta columna, aunque la mayor parte de las veces solo se muestran dos ([[FAQ_aMule#What_do_all_those_numbers_in_the_sources_column_in_the_transfers_window_mean?|recurso]]) alternativo:
: <[[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]] Pedidas>[/<Todas Las [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]]>] [+ <[[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]] [[FAQ_aMule-es#¿Qué_es_A4AF?|A4AF]]> ] [(<[[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]] Transfiriendo>)]
: '[[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]] Pedidas' son aquellas a las que se ha pedido el archivo.
: 'Todas Las [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]]' son todas las [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] de el archivo. Pedidas o no.
: '[[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]] [[FAQ_aMule-es#¿Qué_es_A4AF?|A4AF]]' son [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] que ofrecen ese archivo, pero a las que se ha pedido otro archivo.
: '[[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|Fuentes]] Transfiriendo' son [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] que te están transfiriendo el archivo en este momento.
; ''Prioridad'' : La prioridad del archivo. Por defecto, la prioridad se establece a "automática", es decir, que [[aMule]] modificará las prioridades según convenga para optimizar las descargas. La prioridad afecta al modo en que [[aMule]] escoge las [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] para cada archivo de aquellas [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] que proveen mas de un archivo requerido por nosotros, de manera que los archivo con prioridad alta obtienen más [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]]. Lea [[FAQ_aMule#What_do_all_those_numbers_in_the_priority_column_in_the_extended_transfers_window_mean?|esto]] para más información.
; ''Estado'' : El estado actual del archivo. "Esperando" significa que estás esperando alguna [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuentes]] que empiece a enviar el archivo.
; ''Tiempo Restante'' : Una noción de cuanto puede tardar el archivo en completarse. Solo aparece cuando está siendo transferido.
; ''Último visto completo'' : Esto muestra la última vez que se ha visto una [[FAQ_eD2k-Kademlia-es#¿Qué es una fuente?|fuente]] con el archivo completo.
; ''Última Recepción'' : Esto muestra la última vez que se ha descargado algo de ese archivo.

=== La cola de Subidas ===
Puedes encontrar la cola de subidas justo debajo de la cola de descargas, y muestra quién se está descargando archivos de tu ordenador (puedes querer leer [[FAQ_aMule-es#¿Por qué hay dos tasas de transferencia en la lista de subidas?|esto]]). Si te lo estás preguntando, no, no puedes parar las subidas. Si pinchas en el icono azul con el texto "Subidas" podrás ver quién está esperando en la cola para descargarse desde tu ordenador, en vez de los que se están descargando en este momento.

=== El significado de los Iconos ===
Estos son los iconos que se pueden encontrar en la ventana de Tráfico.

* '''Estado de una Fuente'''
** http://www.amule.org/dev-up/Source_1.png - [[Cliente]] cliente que te está enviando un archivo o parte de él.
** http://www.amule.org/dev-up/Source_2.png - Estás en la cola de éste [[Cliente]] o preguntandole por un archivo.
** http://www.amule.org/dev-up/Source_3.png - Te estás conectando a este [[cliente]]
** http://www.amule.org/dev-up/Source_4.png - Has pedido otro archivo al [[cliente]] o no tiene ninguna parte necesaria o no puedes conectar con él debido a [[FAQ_eD2k-Kademlia-es#¿Qué es ID baja e ID alta?|ID Baja]].
** http://www.amule.org/dev-up/Source_5.png - Estado desconocido.

* '''eDonkey Clients'''
** http://www.amule.org/dev-up/Client_aMule.png - [[aMule]]
** http://www.amule.org/dev-up/Client_eDonkey.png - [[eDonkey2000]]
** http://www.amule.org/dev-up/Client_eMule.png - [[eMule]]
** http://www.amule.org/dev-up/Client_Friend.png - El [[cliente]] es un [[Amigo]]
** http://www.amule.org/dev-up/Client_Lphant.png - [[lphant]]
** http://www.amule.org/dev-up/Client_MLDonkey.png - [[mlDonkey]]
** http://www.amule.org/dev-up/Client_Shareaza.png - [[Shareaza]]
** http://www.amule.org/dev-up/Client_Unknown.png - [[Cliente]] desconocido
** http://www.amule.org/dev-up/Client_xMule.png - [[xMule]]

* '''Modificadores'''
** http://www.amule.org/dev-up/Client_Mod_eMuleProt.png - [[Cliente]] que soporta el protocolo extendido de [[eMule]], comparticíon de fuentes y eso.
** http://www.amule.org/dev-up/Client_Mod_GoodCredit.png - [[Cliente]] que tiene buen [[FAQ_eD2k-Kademlia-es#¿Qué es todo esto de créditos, tasa y puntuación?|ratio de créditos]].
** http://www.amule.org/dev-up/Client_Mod_NormCredit.png - [[Cliente]] que tiene un [[FAQ_eD2k-Kademlia-es#¿Qué es todo esto de créditos, tasa y puntuación?|ratio de créditos]] normal.
** http://www.amule.org/dev-up/Client_Mod_SecId_Good.png - [[Cliente]] identificado [[Secure_User_Identification|de forma segura]].
** http://www.amule.org/dev-up/Client_Mod_SecId_Bad.png - [[Cliente]] que ha sido identificado como un [[chico malo]] por alguna razón.

* '''[[comment|Comentarios]] de los Archivos'''
** http://www.amule.org/dev-up/File_Comment.png - Este archivo ha sido [[comment|comentado]] o clasificado por alguien.
** http://www.amule.org/dev-up/File_Comment_Bad.png - Este archivo ha sido clasificado como [[Fake]] por al menos una persona.

=== ¿Donde están los Archivos? ===
Una vez que [[aMule]] comienza a descargar un archivo, crearán unos cuantos ficheros para hacer un seguimiento de cada descarga. Estos ficheros se encuentran en el directorio ''.aMule/Temp'' de tu directorio home (''~.aMule/Temp''), pero casi nunca hay que tocarlos.

Si tienes descargas incompletas de [[eMule]], puedes simplemente poner los ficheros temporales en el directorio ''~.aMule/Temp'' si quieres que [[aMule]] continue descargandolos.

Sin embargo, una vez que un archivo ha sido completado, se moverá de ''~/.aMule/Temp'' a ''~/.aMule/Incoming'' donde se colocan por defecto todos los archivos completados. Puedes cambiar ambas rutas en las preferencias si lo deseas.

Ten en cuenta también que el directorio ''.aMule'' es un directorio oculto, asi que debes configurar tu gestor de ficheros para que muestre los archivos ocultos.

== Conclusion ==
Esperamos que esta pequeña introducción te haya dado una idea de como trabaja [[aMule]].
Si te parece que falta algo en esta guía, por favor, haznoslo saber o añadelo tu mismo.