AMule Project FAQ - User contributions [en]

Configure

2005-06-04T14:02:15Z

80.58.35.237:

{| width="90%" align="left"
|
== Introduction ==

''configure'' configures [[aMule]] to adapt to many kinds of systems.

Its purpose is to make it easy to port it to many platforms and to compile it and use it in all platforms in the very same way.

You can set lots of parameters in it to adapt it to your system and to tweak its features.

'''NOTE:''' This article is focused in [[aMule]]'s ''configure''. Other ''configure'' scripts work in a similar way, but their options will differ. This article might be useful for them as well, but have in mind that they might have options not listed here and lack some listed here too.

== Main usage ==

Its usage is ''./configure [OPTION]... [VARIABLE=VALUE]...''

So, as you can see, you can define its behaviour both through [[#Options|options]] and through [[#Variables|variables]]

== Options ==

You can define one or more options. The available options in [[aMule]]'s ''configure'' are listed below. To better understand their meaning, they have been grouped into several tables with options which affect the behaviour of ''configure'' in a similar way.

Please note that ''configure'' will (in most cases) not complain if you enter an invalid option or variable. So make sure you enter the options correctly (no typos) or they will have no effect and configure won't behave in the way you expected.

=== Main options ===

These options should exist in any ''configure'' script around the world. They won't run the ''configure'' script to configure your application's compilation, but only output information you might need.

{| border=1
|+ Basic options
|''-h'' or ''--help'' || This will display a help message summing up all ''configure'' options
|-
|''-V'' or ''--version'' || This will display the version information
|}

=== Non-compilation common options ===

These options should also exist on any ''configure'' script around the world. They will set some non-compilation related preferences.

{| border=1
|+ Options directly related to the ''configure'' script
|''-q'' or ''--quiet'' or ''--silent'' || Do not print the `checking...' messages, only the final summed up ouput
|-
|''--cache-file=FILE'' || Store the checkings' ouputs in '''FILE''' in a script format, so you can reuse without the need to rerun ''configure'' (read the cached file for more information)
|-
|''-C'' or ''--config-cache || Same as ''--cache-file=config.cache''
|-
|''-n'' or ''--no-create || Just run ''configure'', but do not create any files
|-
|''--srcdir=DIR'' || Look for the sources in '''DIR'''. By default, the ''configure'' dir or its parent (''../'')
|}

=== Common options ===

These options should also exist on any ''configure'' script around the world. This time, these ones will affect the compilation of the application, so be careful when using them. You should take a close look at the application's ''README'' document (if available) if you want to use any of them (and even if you don't, still take a look at it, since you might '''have''' to use some).

{| border=1
|+ Installation directories options
| ''--prefix=PREFIX'' || Set where to install architecture-independent files (data) in '''PREFIX'''. By dafault, this is set to ''/usr/local''
|-
| --exec-prefix=EPREFIX || Set where to install architecture-dependent files (mainly binaries) in '''EPREFIX'''. By default, this is set to the same value as '''PREFIX'''.
|}

{| border=1
|+ Advanced installation directories options
| ''--bindir=DIR'' || Where to store user executables. By default, '''''EPREFIX'''/bin''
|-
| ''--sbindir=DIR'' || Where to store system administrator executables. By default, '''''EPREFIX'''/sbin''
|-
| ''--libexecdir=DIR'' || Where to store program executable. By default '''''EPREFIX'''/libexeec''
|-
| ''--datadir=DIR'' || Where to store read-only architecture independent data. By default, '''''EPREFIX'''/share''
|-
| ''--sysconfdir=DIR'' || Where to install read-only single-machine data. By default, '''''PREFIX'''/etc''
|-
| ''--sharedstatedir=DIR'' || Where to store modifiable architacture-independent data. By default '''''PREFIX'''/com''
|-
| ''--localstatedir=DIR'' || Where to store modifiable single-machine data. By default, '''''PREFIX'''/var''
|-
| ''--libdir=DIR || Where to search libs object code libraries. By default, '''''EPREFIX'''/lib''
|-
| ''--includedir=DIR'' || Directory containing the [http://en.wikipedia.org/wiki/C_programming_language C] header files. By default, '''''PREFIX'''''/include''
|-
| ''--oldincludedir=DIR'' || Directory containing [http://en.wikipedia.org/wiki/C_programming_language C] header files for non-GCC. By default, ''/usr/include''
|-
| ''--infodir=DIR'' || Where to store info and documentation files. By default, '''''EPREFIX'''/info''
|-
| ''--mandir=DIR'' || Where to store man pages. By default, '''''EPREFIX'''/man
|}

{| border=1
|+ General rule to program enabling and dirs specification
| ''--PROGRAM-prefix=PREFIX'' || Prepend '''PREFIX''' to installed '''PROGRAM''' directories
|-
| ''--PROGRAM-suffix=SUFFIX'' || Append '''SUFFIX''' to installed '''PROGRAM''' directories
|-
| ''--PROGRAM-transform-name=SUBST'' || Run ''[http://www.gnu.org/software/sed/sed.html sed] '''SUBST''''' on installed '''PROGRAM''' names
|}

{| border=1
|+ General rule to enabling or disabling features (sometimes it enables or disables the compilation of a program)
| ''--disable-FEATURE'' || Do not include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=no'' (see below)
|-
| ''--enable-FEATURE'' || Include '''FEATURE'''. Equivalent to ''--enable-'''FEATURE'''=yes'' (see below)
|-
| ''--enable-FEATURE=VALUE'' || Include '''FEATURE''' and specify it's value to '''VALUE'''. The meaning of the value should be explained in the ''configure --help'' output of the script
|}

{| border=1
|+
| ''--without-PACKAGE'' || Do not use '''PACKAGE'''. Equivalent to ''--with-'''PACKAGE'''=no'' (see below)
|-
| ''--with-PACKAGE'' || use PACKAGE. Equivalent to ''--with-'''PACKAGE'''=yes'' (see below)
|-
| ''--with-PACKAGE=VALUE'' || Use '''PACKAGE''' and set its value to '''VALUE'''
|}

{| border=1
|+ System specifications
| ''--build=BUILD'' || Configure for building on '''BUILD''' platform. By default, it guesses the platform it is being run on
|-
| ''--host=HOST'' || Cross-compile to build programs to run on '''HOST''' platforms. By default, same as '''BUILD'''
|-
| ''--target=TARGET'' || Configure for building compilers for '''TARGET''' platfroms. By default, same as '''HOST'''
|}

=== Very-common options ===

In most ''configure'' scripts you will also be able to use these options.

{| border=1
|+ Quite common compiler options
| ''--with-gnu-ld'' || Use the [http://www.gnu.org/software/binutils/manual/ld-2.9.1/ld.html GNU ld] as linker, without testing if it is the default linker in the system
|}

{| border=1
|+ X directory specifications
| ''--with-x'' || Use the [http://www.xfree86.org X Window System]
|-
| ''--x-includes=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s include files
|-
| ''--x-libraries=DIR'' || '''DIR''' contains [http://www.xfree86.org X]'s libraries
|}

=== [[aMule]] options ===

The following options are specific to [[aMule]]'s ''configure'' script. They will allow you to enable and disable them, so you should really take a look at them or you might sadly find out you lack things you would like to have in your [[aMule]] system ;-)

{| border=1
|+ Developer options
|-
| ''--enable-maintainer-mode'' || Activate some extra instructions only useful for developers (and totaly non-recommended to normal users)
|-
| ''--disable-dependency-tracking'' || Makes the application compile faster, but causes problems if you change the source code and try to compile again. Dependency tracking allows the make process to know which things to rebuild when something changes. If you do not plan to compile the application again with those same sources, you can safely use this option
|-
| ''--enable-dependency-tracking'' || Keep track of the dependencies so that on next build, only changed files will be recompiled. It slows down the compilation a little. This is the default
|-
| ''--enable-ccache'' || Enable [http://ccache.samba.org ccache]. This will make following compilations faster since only the non-modified bits of code will be recompiled. If you don't plan to compile [[aMule]] very often, don't enable this, since it takes longer to compile on the first compilation and it requires lots of disk space
|-
| ''--enable-profile'' || Enable code profiling (which allows to see how much time and resources are spent on each part of the code, though it will make [[aMule]] run much slower, so, in most cases, don't use it). The output file is ''gmon.out'' and can be viewed with ''gprof''. For more information, ''man [http://www.cs.utah.edu/dept/old/texinfo/as/gprof_toc.html gprof]'' and ''man [http://gcc.gnu.org gcc]'' (in the man pages of ''[http://gcc.gnu.org gcc]'', search for the command line option ''-pg'')
|}

{| border=1
|+ Compilation tweaks
| ''--disable-debug'' || Disables outputing information of the application execution. This information is useful to track bugs, so you might not want to use this option or you will not be able to report bugs properly
|-
| ''--enable-optimize'' || Optimizes the code to run (a little) faster. Using this option will not allow you to create useful bug reports so you might not want to enable it
|-
| ''--enable-optimise'' || Same as ''--enable-optimize'', but is deprecated (it is still there for backwards compatibility only)
|-
| ''--disable-rpath'' || Do not write the libraries' path into the binary. Useful only if you plan to move the binary to other systems or if you move your libraries often. Only use it if you know what you're doing, since it will make [[aMule]] run slower
|-
| ''--enable-static'' || Creates statically linked executables, which means that they will need no libraries since any needed library will be included in the executable file. The executable might run faster, and will be easily portable between systems using the same platform, but will be incredibly bigger in size
|}

{| border=1
|+ Compilation of external libraries
| ''--disable-embedded_crypto'' || Do not use [[aMule]]'s cryptography code, instead, use external libraries' code. This option is not recommended and it could possibly break the compilation
|-
| ''--disable-gsocket'' || Do not use [[aMule]]'s ''gsocket.c'' implementation. Do not use it unless you are '''very''' sure of what you are doing! (On [[wxWidgets]] 2.4, the default ''gsocket.c'' code gives [[Low ID]]s on restart)
|-
| ''--disable-nls'' || Do not use [http://www.vitavoom.com/postgresql-docs/nls.html Native Language Support]. This way [http://www.gnu.org/software/gettext gettext] won't be required, but translations will be disabled
|}

{| border=1
|+ Compilation hardcodings
| ''--disable-systray'' || Do not include a SysTray into the [[aMule]] build. Only [[wxWidgets]] 2.4.2 users with no [http://www.gtk.org GTK] should use it. Others should disable SysTray in [[aMule]]'s preferences
|-
| ''--enable-utf8-systray'' || Use [http://www.unicode.org UTF-8] encoded strings in [[aMule]]'s SysTray. Only affects [[wxWidgets]] 2.4
|}

{| border=1
|+ [[aMule]] binaries selection
| ''--disable-monolithic'' || disable building of the [[aMule|monolithic aMule]] app. This is normally not recommended, unless you really know what you are doing (e.g. to compile only the [[aMuled|daemon]])
|-
| ''--enable-amule-daemon'' || Compile [[aMuled|aMule daemon]]
|-
| ''--enable-amulecmd'' || Compile the [[aMuleCMD|aMule command line client]]
|-
| ''--enable-amulecmdgui'' || Compile [[aMuleCMDDLG|aMule command line client (GUI version)]]
|-
| ''--enable-webserver'' || Compile [[aMuleWeb|aMule's WebServer]]
|-
| ''--enable-webservergui'' || Compile [[aMuleWebDLG|aMule's WebServer (GUI version)]]
|-
| ''--enable-amule-gui'' || Compile [[aMuleGUI|aMule remote GUI]]
|-
| ''--enable-cas'' || Compile [[CAS|C aMule Statistics]]
|-
| ''--enable-wxcas'' || Compile [[wxCAS|aMule GUI Statistics]]
|-
| ''--disable-ed2k'' || Don't compile [[ed2k command|aMule's ed2k links handler]]
|-
| ''--enable-alc'' || Compile [[aLinkCreator|aMuleLinkCreator GUI version]]
|-
| ''--enable-alcc'' || Compile [[aLinCreatorConsole|aMuleLinkCreator for console]]
|}

{| border=1
|+ Configure tweaks
| ''--disable-gtktest'' || Do not try to compile a test [http://www.gtk.org GTK] (either [http://www.gtk.org GTK]1 or [http://www.gtk.org GTK]2 depending on your system's configuration) program to see if your system has a proper [http://www.gtk.org GTK] configuration. This will make the ''configure'' script run a (very) little faster, but you should still not use it unless you know what you are doing, since the ''configure'' script could miss some tests.
|}

=== [[aMule]] compilation settings ===

This options are specific to [[aMule]]'s configure script, but they are not directly related to [[aMule]]. They just tell were some libraries or headers are located in your system, so that [[aMule]] can find them when compiling. Use them if you have those files in non-standard paths or when you know what you are doing.

To better understand these options, take a look at the [[#Common options|common options]] chapter in this article.

{| border=1
|+ [http://www.gzip.org/zlib zLib]
| ''--with-zlib=PREFIX'' || Look for [http://www.gzip.org/zlib zLib] files in '''PREFIX'''
|}

{| border=1
|+ [http://curl.haxx.se Curl]
| ''--with-curl-config=CONFIG'' || '''CONFIG''' is the path of ''curl-config''
|}

{| border=1
|+ [http://www.boutell.com/gd LibGD]
| ''--with-gdlib-prefix=PREFIX'' || Look for [http://www.boutell.com/gd LibGD] files in '''PREFIX'''
|-
| ''--with-gdlib-exec-prefix=PREFIX'' || Look for GDLib libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gdlib-exec-prefix''
|-
| ''--with-gdlib-config=CONFIG'' || '''CONFIG''' is the path of ''gdlib-config''
|}

{| border=1
|+ [http://www.libpng.org LibPNG]
| ''--with-libpng-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] files in '''PREFIX'''
|-
| ''--with-libpng-exec-prefix=PREFIX'' || Look for [http://www.libpng.org LibPNG] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-libpng-exec-prefix''
|-
| ''--with-libpng-config=CONFIG'' || '''CONFIG''' is the path of ''libpng-config''
|}

{| border=1
|+ [[wxWidgets]]
| ''--with-wx-prefix=PREFIX'' || Look for [[wxWidgets]] files in '''PREFIX'''
|-
| ''--with-wx-exec-prefix=PREFIX'' || Look for [[wxWidgets]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wx-exec-prefix''
|-
| ''--with-wx-config=CONFIG'' || '''CONFIG''' is the path of ''wx-config''
|}

{| border=1
|+ [[wxBase]]
| ''--with-wxbase-prefix=PREFIX'' || Look for [[wxBase]] files in '''PREFIX'''
|-
| ''--with-wxbase-exec-prefix=PREFIX'' || Look for [[wxBase]] libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-wxbase-exec-prefix''

|-
| ''--with-wxbase-config=CONFIG'' || '''CONFIG''' is the path of ''wxbase-config''
|}

{| border=1
|+ [http://www.gtk.org GTK]
| ''--with-gtk-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) files in '''PREFIX'''
|-
| ''--with-gtk-exec-prefix=PREFIX'' || Look for [http://www.gtk.org GTK] (not [http://www.gtk.org GTK]2) libraries in '''PREFIX'''. By default, looks for them in the path specified in ''--with-gtk-exec-prefix''
|}

{| border=1
|+ [http://www.openssl.org/docs/crypto/crypto.html Crypto++]
| ''--with-crypto-prefix=PREFIX'' || Look for [http://www.openssl.org/docs/crypto/crypto.html Crypto++] files in '''PREFIX'''
|}

{| border=1
|+ [http://www.gnu.org/software/libiconv LibIConv]
| ''--with-libiconv-prefix=PREFIX'' || Look for [http://www.gnu.org/software/libiconv LibIConv] files in '''''PREFIX'''/include'' and '''''PREFIX'''/lib''
|-
| ''--without-libiconv-prefix'' || Don't search for [http://www.gnu.org/software/libiconv LibIConv] in includedir and libdir
|}

{| border=1
|+ [http://www.gnu.org/software/gettext gettext]
| ''--with-included-gettext'' || Use the [http://www.gnu.org/software/gettext GNU gettext] library included in the ''intl/'' directory instead of the system's. This is only for strange systems where [http://www.gnu.org/software/gettext gettext], for some reason, will not handle [[aMule]]'s catalog files
|}

{| border=1
|+ [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl]
| ''--with-libintl-prefix=PREFIX'' || Look for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] files in '''''PREFIX'''/include''' and '''''PREFIX'''/lib''''
|-
| ''--without-libintl-prefix'' || Don't search for [http://gnuwin32.sourceforge.net/packages/libintl.htm LibIntl] in includedir and libdir
|}

{| border=1
|+ [http://ccache.samba.org ccache]
| ''--with-ccache-prefix=PREFIX'' || Look for [http://ccache.samba.org ccache] files in '''PREFIX'''
|}

== Variables ==

Before you take a look at the [[#Variables and what they mean|variables and what they mean]], you must take a look at the two variable [[#Usage types|usage types]] available.

=== Usage types ===

You can either use [[#Environment variables|environment variables]] or you can [[#Configure variables|enter variables directly into the ''configure'' command]].

==== Environment variables ====

If you plan to use environment variables, you will affect the behaviour of ''configure'' and any other program you run in that same shell until you end your session. You must set them '''before''' running configure. To set them, run

export ''VAR=VALUE'''

where ''VAR'' is the name of the environmental variable and ''VALUE'' is it's value.

==== Configure variables ====

If you don't want to use environment variables, you can pass them into the ''configure'' command, this way:

configure VAR=VALUE

where ''VAR'' stands for the variable name and ''VALUE'' is its value.

=== Variables and what they mean ===

Do '''NOT''' touch these variables if you don't know what you are doing!

This are some of the most commonly used variables for ''configure'':

{| border=1
|+ Variables
| ''CC'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler command to use
|-
| ''CXX'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler command to use (e.g. ''[http://gcc.gnu.org g++]'')
|-
| ''CPP'' || [http://en.wikipedia.org/wiki/C_programming_language C] preprocessor command to use
|-
| ''CFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C] compiler flags
|-
| ''CXXCPP'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor command to use
|-
| ''CXXFLAGS'' || [http://en.wikipedia.org/wiki/C_Plus_Plus C++] compiler flags
|-
| ''LDFLAGS'' || Linker flags. Usually used to specify additional library directories (e.g. ''LDFLAGS="-L/usr/lib"'')
|-
| ''CPPFLAGS'' || [http://en.wikipedia.org/wiki/C_programming_language C]/[http://en.wikipedia.org/wiki/C_Plus_Plus C++] preprocessor flags (e.g. ''CPPFLAGS="-I/usr/include"'')
|}

== More information ==

This article is mainly an explanation (dummy-proof) of the output of ''configure --help''.

Anyway, it could (rarely) be out of date. So, if there's something you want to do with ''configure'' that is not listed here, run ''configure --help'' and see if it is listed there.

Of course, you can always take a look at the [http://www.airs.com/ian/configure GNU configure page].
|
|}

FAQ eD2k-Kademlia

2005-05-17T00:05:51Z

80.58.35.237:

<center>
<h4>F.A.Q. on eD2k-Kademlia</h4>

'''English''' | [[FAQ_eD2k-Kademlia-es|Español]] | [[FAQ_eD2k-Kademlia-it|Italiano]] | [[FAQ_eD2k-Kademlia-de|Deutsche]] | [[FAQ_ed2k-fr|Français]] | [[FAQ_eD2k-Kademlia-nl|Nederlands]]
</center>

== What is ED2K? ==
ED2K is a protocol originally used by the P2P (Peer-to-Peer) client [[eDonkey2000]], which is where the name comes from. It is a server-client based protocol, with the ability to exchange sources between clients.

The ED2K network is server based like many other P2P networks such as [[Kazaa]] (Kazaa is server based, but hides the server connection from the user), which means that the first thing you do when you run [[aMule]] is to connect to a server (either manually or automatically).

Once successfully connected to a server, the client can search, either locally (the connected server) or globally (all servers), for any file and the servers asked will provide the client with a list of all the files which match search parameters.

If the user starts a download, the client will then ask the server for sources, which the server will return in the form of IP addresses for the clients that have told the server that they have the specific file.

Then the remote client will begin to upload a whole chunk to your client as soon as you are the first in the queue, read [[FAQ_eD2k-Kademlia#What_is_all_that_credits,_rate_and_score_stuff_about?|What_is_all_that_credits,_rate_and_score_stuff_about?]] and, when the chunk has been completly sent, you will be taken back to it's upload queue. This way different chunks get spread around the ED2K network, so that, although no-one may have at a same given moment the complete file, it may be completed by downloading the different chunks from different people (it is well known that users tend to stop sharing a file once it has been completed). 
Note that clients upload only '''one''' chunk at a time to another client. Even if a client is in the upload queue of two different files of a same user and gets to the top of both, that user will only upload one of the files to that client (the other upload, depending on the ED2K application the client uses, will probably remain as a maximum priority upload, but will not begin until the other chunk has been successfully uploaded).

If both users have HighID (see [[FAQ_eD2k-Kademlia#What_is_LowID_and_HighID?|What is LowID and HighID?]]) the transfer will be done directly from client to client (Peer-to-Peer), but if one of the clients have LowID, the connection will be established through the server, since LowID cannot accept incoming connections. As a result, two LowID clients '''cannot''' connect to each other.

== What is Kademlia? ==
Kademlia is a natural evolution of the ED2K network. Kademlia is the future. See [[FAQ_eD2k-Kademlia#Are_there_any_limitations_on_the_ED2K_network?|Are there any limitations on the ED2K network?]] for more information on why Kademlia is necessary.

Since Kademlia is a decentralized network, it removes the bottleneck that was previously caused by the need for servers (though [[Lugdunum]] has done great work in reducing this bottleneck). Now, instead of connecting to a server, you just connect to a client (with a known IP-address and port), which supports the network [[Kademlia]]. This is called the Boot Strapping.

Once connected, depending on your ability to accept incoming connections, you are given either "open" or "firewalled" status, which is similar to the HighID and LowID of the ED2K network. Then you are given an ID.

At the moment, "firewalled" users aren’t supported by the Kademlia network, and therefore won’t be given an ID and will be unable to connect. Firewalled support will be added later.

When searching, each client acts as a small server and is given responsibility for certain keywords or sources. This adds to the complexity of finding sources, as you no longer have a central server to ask, but instead will have to propagate the query through the network.

Currently, Kademlia isn't supported by aMule, but it will be soon.

TODO: Does Kademlia remove the 4 GB file size limit ?

== Is Kademlia the same as Overnet? ==
Short and clear: No. Overnet is the natural serverless evolution of the eDonkey software, while Kademlia is the natural serverless evolution of *Mule clients. SO, it's the same philosophy, but different rules. To learn about how Overnet works, refer to http://www.edonkey2000.com/documentation/how_on.html but, have in mind, Overnet's development is closed untill it reaches version 1.0, while Kademlia's development is completly open from the very beginning.

== What is a chunk? ==
In the ED2K protocol, to avoid sharing corrupt files, each file is divided into various parts, which are known as chunks, and then each chunk is hashed (read below to know what a [[FAQ_eD2k-Kademlia#What_is_a_hash?|hash]] is). Each chunk is 9.28MB in size, so a 15MB file will be divided into two chunks (9.28MB + 5.72MB), a 315KB file will be a single chunk and a 100MB file will be divided into 11 chunks (10x9.28MB + 7.2MB).

== What is a hash? ==
Dividing each file into chunks (see [[FAQ_eD2k-Kademlia#What_is_a_chunk?|What is a chunk?]]) will avoid the problem of downloading a whole corrupted file since only the corrupted chunk will have to be downloaded again, but a method to identify corrupted chunks is needed. This is done by using MD4 hashes.

A [[MD4 hash]] is a unique value each chunk is given and is the result of a mathematical operation on every single bit on the chunk. This means that modifying a single bit in a chunk would result in a completely different hash. That means that the [[client]] needs to verify the integrity of each part of a file as it is downloaded.

Not only are the chunks hashed but also, in order to get a file-hash, all chunks's hashes are concatenated one after the other in their file order (that is: chunk1's_hash+chunk2's_hash+chunk3's_hash+...) and the resulting string is hashed. This way, each file on the ED2K network has a unique identifier. The file hash isn't taken from hashing the whole file, but from hashing the value of the the chunk's hashes.

In reality, you need both the hash of a file and its size. These pieces of information is embedded in the ED2k URLs found in many places.

Take this for example: 
ed2k://|file|eMule0.42f-Sources.zip|2407949|CC8C3B104AD58678F69858F1F9B736E9|/

The interesting parts are the fifth part, "2407949", which is the size of the file in bytes and the last part, "CC8C3B104AD58678F69858F1F9B736E9", which is the hash itself, stored as hex-decimals, 32 letters long.

The filename itself is irrelevant in the process of identifying the file.

== Why after searching, some files which are the same appear as a different file in the results, although they even have the same name? ==
If you understood "What is a hash" you will understand this quickly. When a search is started, the server tells the ED2K client the filename of the found file and the hash of the complete file for each file which matches the search. If two files, although being the same, have some difference in their content, no matter if it's big or small, the hash is different, so they are considered as a different file. That's also the reason why two file with different file name appear as the same file: on the ED2K network, the filename isn't important, the hash is.

== What is LowID and HighID? ==
Each client is assigned an identifying number, an ID, which will be unique and will distinguish him from any other client on the server. If this ID is below 16777216 (16 million) then you have a LowID. If it's over, then you have a HighID. To be given a high or low ID will only depend on having TCP port 4662 (or the one set up in Preferences) opened. If you understood "What is ED2K" you might understand that chances are that clients on LowID may be unable to connect to many other clients (all those on LowID) so will have a lower transfer rate. That's why having port 4662 TCP (or the one set in Preferences) is so important. Also, some big servers refuse clients on LowID to connect to them since LowID clients have data transfered through the server and so, those big servers could be overcharged. 
For HighID clients, their ID is the result of a mathematical operation with their IP which corresponds to A + 256*B + 256*256*C + 256*256*256*D, where the IP is A.B.C.D. Also have in mind that this ID has identification purposes, nothing else, so apart from having and ID over or under the 16777216 number, it does not matter if the ID is bigger or smaller. This means a client with an ID like 50000000 isn't better than a client with an ID like 49999999. 
There's still an exception. Sometimes badly configured or very busy servers give LowID to some clients although the 4662 TCP port is opened. This are rare exceptions, but it might happen sometime. 
Check [http://www.amule.org/testport.php here] if you have your ports opened.

== Which ports do I have to configure in a firewall or router to run aMule? ==
aMule works even with no specific ports opened, but you won't get a HighID in this case. As mentioned above, to be given a HighID, port 4662 TCP (or the one set in the Preferences) must be listening (i.e. opened in your firewall and forwarded in your router). 
Apart from that port, to have an optimal ED2K experience, two more ports should be enabled as well. First, the UDP port 4672 (which can also be changed to any other number in the Preferences) and secondly, the secondary UDP port which can't be set in the Preferences. This UDP port is your TCP port + 3 (e.g.: TCP=4662 then UDP=4665).

== What does each port do? ==
Well, since most ports can be configured to be set to any other number, the defaults will be listed:

; 4662 TCP: Client to client transfers.
; 4665 UDP: Opened on client, used for global server searches and global source queries. This is always Client TCP port + 3.
; 4672 UDP: Extended eMule protocol, Queue Rating, File Reask Ping
; 4661 TCP: Opened on server. Allows connection to server.
; 4665 UDP: Opened on server. Allows asking for sources. It is always Server TCP port + 4.
; 4711 TCP: WebServer listening port.
; 4712 TCP: External Connection port. Used to communicate aMule with other applications such as aMule WebServer or aMuleCMD.

== Are there any limitations on the ED2K network? ==
Not much, but yes, there are: two natural limits and a "forced" limitation. The two natural limits have already been mentioned before. First, the issues on LowID users (their transfers involve data through the server and two LowID clients can't share between them). The second, although ED2K is a p2p protocol, it needs servers to establish the p2p connection. This latter one is solved in the Kademlia protocol. 
About the "forced" limitation, it's only a limit to make sure that clients share so that the ED2K network will not disappear: clients which have an upload limit of X KBps, where X is between 0 and 3.99 (both included) can download at a maximum of X*3 KBps. Clients which have an upload limit of Y KBps, where Y is Between 4 and 9.99 (both included) can download at a maximum of Y*4 KBps. Clients with an upload limit of 10KBps or more have no downloading limitations. This restriction is set in the client application so it could be by-passed by hacking the code, but that would probably result in being banned from the servers you connect to. 
Also, any client is forced to allow at least three upload slots, so it's not possible to allow more than upload_limit/3 KBps per slot. 
There is one last limit: Network file limit is 4GB. 
Additionally, this is not an eD2k limitation but a server limitation, servers will only send 300 results for your searches, so don't expect any more results.

== In search window, what filter stands for which filetype? ==
Have in mind that the filters in the search window don't depend on the file type, but on the extensions of the filenames, in the following way: 
Archive: .ace .arj .rar .tar.bz2 .tar.gz .zip .Z 
Audio: .aac .ape .au .mp2 .mp3 .mp4 .mpc .ogg .wav .wma 
CDImage: .bin .ccd .cue .img .iso .nrg .sub 
Picture: .bmp .gif .jpeg .jpg .png .tif 
Program: .com .exe 
Video: .avi .divx .mov .mpeg .mpg .ogg .ram .rm .vivo .vob 
So, a movie which's filename is "Birthday.zip" will appear in the Archive filter, but not in the Video filter.

== What is a source? ==
A source is a client which is sharing some chunk in some file you have in your downloading queue which you still have not completed. Obviously, the more sources you can get for a given file, the more possibilities you have to download the file and the quicker you'll download it. Have in mind that there's a difference between "sources" and "available sources" if you're on LowID, since "sources"s stands for clients sharing a chunk or file you still haven't completed, while "available sources" stands for clients sharing a chunk or file you still haven't completed and from who you can download (that is, a source who is on HighID).

== What is all that credits, rate and score stuff about? ==
All three concepts have to do with the way in which the ED2K network establishes the uploading queues preferences. 
The score is the most important value: the client with the higher score will be the next client which you'll provide a slot to. The way in the score value is set is this: score = rate x time_waiting_in_seconds / 100
So, to understand this, we must known what rate is. 
Rate is can be understood as an objective preference. This is, the preference which a client is given without caring how much time it's been waiting. When a client is added to the uploading queue, it gets a rate of 100. This value is modified following according to this: 
According to the amount of credits, the rate will be multiplied by 1x to 10x.
Depending on the file priority, it will be multiplied by 0.2x to 1.8x (Release 1.8x, High 0.9x, Normal 0.7x, Low 0.6x, Very Low: 0.2x). 
Users on specific old clients which load too much the network traffic will get penalized by multiplying their rate by 0.5x. 
Banned clients will instantly get no rate (that is, their rate will by multiplied by 0). 
This multiplying values are known as "modifiers". Clients with a modifier value strictly bigger than 1 will be marked as yellow in the icon. 
So we only have credits left to known. Credits are a prize you get for uploading files to a specific user. Credits are exchanged between two specific clients, they are not global, so your own credits can't be viewed, although you can know the credits any other user has on you (that is, the credits you owe that client). Since credits are managed by the uploading client, you might be uploading to some client with no credits support, so you will gain no credits on him, although that client will actually get credits on you if it uploads to you, since you do have credits support. This credits are stored in clients.met file. 
The credits modifier used by rate is the lower between these two: (upload_total x 2)/download_total or sqrt(upload_total+2) where both upload_total and download_total are measured in MBs. 
If the result is lower than 1, then it is set to 1 and if it is bigger than 10, it is set to 10. In addition, if the uploaded total is less than 1MB, the modifier is set to 1 and if the downloaded total is equal to 0, then the modifier is set to 10. 

== What is a slot? ==
When uploading files, your upload bandwidth (which may vary depending on the upload limit or the natural connection-type upload limit) will be divided into slots. So, each slot is an amount of KBps which will be assigned to each client who tries to download from you.

Talk:Shareddir.dat file

2005-05-17T00:03:05Z

80.58.35.237:

In the GUI, it's now possible to specify a rescursive shared dir....
Is it possible to do the same in Shareddir.dat ???

'''No it is not. That GUI function actually adds all files one by one.'''

User:OlegPopov

2005-05-03T19:53:54Z

80.58.35.237:

Hello!

My name '''Oleg Ivanovich Popov'''.

I live in Russia. My adress: Ryazan, RO 123056,
Ul. Raketnaya D.85 Kv.13.

'''Education:''' Moscow State Institute of International Relations
(University), 1992 to 1997 International Law School including three foreign languages:
English, German, and Afrikaans. High Level Diploma - "Several Aspects of International
Copyright". Work Experience: Lawyer, International Law Firm Baker & McKenzie,
October 1998 to Present.

'''Skills & Interests:''' Fluent in English, proficient in German,
some knowledge of French and Afrikaans. Computer literate, large working
experience on both PC (Windows and DOS) and Macintosh, have one of each at home.
Some programming experience. I have 24/7 access to the Internet and my favourite hobby
to read and study wiki sites :)

'''PS:''' I have the catalogue wiki sites - http://wiki4all.com/ and I shall be very
grateful to the manager of this wiki site, if it will add wiki in my catalogue with
the small description... :)

'''Computers -> Software: "Wiki about aMule: The all-platform Mule"'''

'''Your wiki requires login, so sorry ;-) Plese add it yourself :-)'''

'''Greets'''