AMule Project FAQ - User contributions [en]

Geaiez

2004-10-29T23:07:28Z

217.82.179.128: "copyrighted" is misleading, as nearly everything is copyrighted, especially copyleft-stuff (which is free to share)

Geaiez is known to be a [[client]] which repeteadly requests for you shared files list. It has been often rumoured to be a [http://www.riaa.com/default.asp RIAA]/[http://www.mpaa.org MPAA]/[http://www.cia.gov CIA]/[http://www.fbi.gov FBI] [[client]] trying to get (illegally) a list of illegally shared files and the [http://www.ietf.org/rfc/rfc0791.txt IP]s of the people shareing them.

In fact, it has been concluded that is false. Or at least not absolutely true.

It seems that [http://www.morpheus.com Morpheus] [[client]]s, based on [[mlDonkey]], instead of generating a random 6 characters long username by default, it uses a specific username as default (just as [[aMule] uses ''http://www.amule.org'' or [[eMule]] uses ''http://emule-project.net'') which is (guess what?) '''geaiez'''. Not only that, but also, [[mlDonkey]] [[client]]s apparently request for all shared files to all those [[client]]s they connect to.

So, what seems to be like a single [[client]] requesting repeatedly for your shared files list, is in fact many [[client]]s requesting for your shared files list every time they connect to you.

Anyway, allthough there are no proves which lead to assure there is some government behind those [[client]]s, you should keep your eyes wide-open: don't allow other [[client]]s to get a list of your shared files if you have anything private being shared (we already assume you do '''not''' share stuff your are not allowed to share!).

Using another wxinstall

2004-10-29T22:51:48Z

217.82.179.128:

If there's already a version of [[wxWidgets]] installed, but you want [[aMule]] to use another (probably newer) one, here are the steps to follow:

First, create the target directory, where [[wxWidgets]] and [[aMule]] will reside (they don't need to be in the same dir, but it makes life easier). Then configure [[wxWidgets]] and [[aMule]] accordingly (assuming [[wxWidgets]] 2.5.3 and current (=>rc7) aMule).

in [[wxWidgets]] source dir (don't forget to install the patch!):
''<pre>
mkdir ~/aMule
./configure --prefix=~/aMule --disable-gtk2 --with-gtk --enable-debug --enable-debug_gdb
make && make install
</pre>''

In [[aMule]] source dir:
''<pre>
export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH
./configure --prefix=~/aMule/ --enable-debug --with-wx-prefix=~/aMule --with-wx-config=~/aMule/bin/wx-config
make && make install
</pre>''

To start [[aMule]], you need to explicitely specifiy the LD path each time you run it:

''<pre>
export LD_LIBRARY_PATH=~/aMule/lib:$LD_LIBRARY_PATH
export LC_ALL=en_EN.UTF-8
gdb ~/aMule/bin/amule
gdb>handle SIGPIPE nostop noprint pass
gdb>handle SIG32 nostop noprint pass
gdb>set height 0
gdb>run
</pre>''

After aMule crashed, generate a backtrace and post it in the aMule forum:

''<pre>
...
Program received signal SIGSEGV, Segmentation fault.

gdb>bt
gdb>bt full
</pre>''

Using another wxinstall

2004-08-16T19:56:31Z

217.82.179.128:

If there's already a version of [[wxWidgets]] installed, but you want [[aMule]] to use another (probably newer) one, here are the steps to follow:

First, create the target directory, where [[wxWidgets]] and [[aMule]] will reside (they don't need to be in the same dir, but it makes life easier). nb: If you use the recommened /home/muli, you will most probably need root rights for that, everything else is done as regular user (remember: NEVER work as root!). Then configure [[wxWidgets]] and [[aMule]] accordingly (assuming [[wxWidgets]] 2.5.2 and current (=>20040801) [[aMule CVS]]).

in [[wxWidgets]] source dir:
''<pre>
mkdir /home/muli/BUILD
./configure --prefix=/home/muli/BUILD --enable-unicode --enable-gtk2
make && make install
</pre>''

In [[aMule]] source dir:
''<pre>
export LD_LIBRARY_PATH=/home/muli/BUILD/lib:$LD_LIBRARY_PATH
./configure --prefix=/home/muli/BUILD --enable-debug --with-wx-prefix=/home/muli/BUILD --with-wx-config=/home/muli/BUILD/bin/wxgtk2u-2.5-config
make && make install
</pre>''

To start [[aMule]], you need to explicitely specifiy the LD path each time you run it:

''<pre>
export LD_LIBRARY_PATH=/home/muli/BUILD/lib:$LD_LIBRARY_PATH
export LC_ALL=en_EN.UTF-8
gdb /home/muli/BUILD/bin/amule
gdb>handle SIGPIPE nostop noprint pass
gdb>handle SIG32 nostop noprint pass
gdb>run
</pre>''