BitlBee-1.0.4 - An IRC to other chat networks gateway
-------------------------------------------------------
---
Copyright (C) 2002-2007 Wilmer van der Gaast <wilmer@gaast.net> and others.
*** PLEASE READ THE AMIGA NOTES BELOW BEFORE DOING ANYTHING.
*** DO NOT START THIS PROGRAM FROM SHELL/WB, IT IS NOT SAFE TO DO SO!
---
NOTES:
[*]
Requires 68020+ with FPU, 1 meg+ of memory, ixemul 48+, ixnet 48+, libiconv.ixlibrary
and/or libiconv_cr.ixlibrary 1.9.2, amitcp 30b2+ and some irc client.
[*]
Components used in this build are as follows:
- libglib 2.4.4
- libgpg-error 1.5
- libgrypt 1.2.4
- libgnutls 1.6.3
- libz 1.2.3
- libiconv 1.9.2 (shared)
All the things above are available on Aminet. You will be needing 'iconv' archive
for sure as I used shared library that must be present in 'LIBS:' at runtime.
[*]
Now some words about the binary flavours, there are 4 compiles:
- bitlbee[j-nossl-iconv_cr] = no ssl support and only jabber protocol
- bitlbee[joy-nossl-iconv_cr] = no ssl, jabber, oscar and yahoo
- bitlbee[joym-gnutls-iconv] = ssl, jabber, oscar, yahoo, msn and full iconv
- bitlbee[joym-gnutls-iconv_cr] = ssl and all protocols with crippled iconv
Basically if you are low on memory and plan to use only jabber then you want
the first one(jabber alone with ssl is only ~200 kilos smaller than the full
release so no point adding it, use 'joym' build in such case).
[*]
If you have ever used the development version(1.1 or maybe 1.0.1) then you will
notice that you need to add your accounts once again as this version stores user
data in a different way(everything encrypted).
[*]
If such message: "[] FATAL: no entropy gathering module detected" will appear
then you need to go see a doctor ;) or... you just need to generate pseudo
entropy pool first, see INSTALLATION.
[*]
PEOPLE! Please send me your bug reports, i wont bite you! Last version i have
uploaded to Aminet was downloaded ~230 times and no one has reported that the ssl
is not functional! Thats right, all Aminet releases of 'OpenSSL' dont work like
they should to... From now on i would like to receive mails from you, even if
you succeeded with the installation - just send me simple: "bitlbee? fuck yeah!"
in the topic.
Important! I have tested only 'jabber' so far, so i dont know if other
protocols do work - please give me some feedback, thank you!
---
INSTALLATION:
- if you got no "dev/" directory in your GG env then:
> makedir gg:dev
- if you got no "DEV:" assign in your startup then add it:
> assign dev: gg:dev
- if you do not have GG at all then(firstly download and install ixemul 48.0):
> makedir sys:gg
> cd bitlbee-1.0.4-bin-m68k
> copy #? sys:gg/ all
- choose the desired version of binary by renaming one of 4 available
to 'bitlbee' like in this example:
> cd sys:gg/usr/local/bin
> rename bitlbee[j-nossl-iconv_cr] bitlbee
- add the following lines to the 'startup-sequence'(without '>') somewhere
after the default system assigns:
> assign gg: sys:gg
> assign usr: gg:usr
> assign dev: gg:dev
> assign var: gg:var
- generate pseudo entropy with 'prng' that can be found in 'c/' - i recommend
to copy it to your 'C:' for further use:
> cd bitlbee-1.0.4-bin-m68k
> copy c/prng c:
> prng dev:random
> prng dev:urandom
- add this to the 'services' of your TCP/IP stack(you can change the port number):
bitlbee 6668/tcp bitlbee
- add this to the 'inetd'('MiamiDX' users must remove '/stack=131072'):
bitlbee stream tcp nowait/stack=131072 nobody usr:local/bin/bitlbee bitlbee
- if you are 'MiamiDX' user then change the priority in 'Database/SysCtl'
and dont forget to save the settings preferably as default:
inetd.processpri 0
- 'MiamiDX' users must also do the following(this will set the new initial
stack size inside the binary file):
> stack 131072
> ixstack 131072 usr:local/bin/bitlbee
- if you are 'AmiTCP' user then perhaps you know what you are doing, anyway
dont forget to (re)start 'inetd' !
---
RUNNING:
Start your favourite irc client and connect to 'localhost' on port 6668 or
the one you have specified instead of the default. After you login follow
the instructions sent by the 'bitlbee' or read the manual.
---
TIPS:
You can add more entries to the 'inetd', so that each port will be assigned
to the particular build. For example connecting on port 6668 will result
in launching the first compile, but connecting on 6669 will give you full
functionality with the full release.
---
TROUBLESHOOTING:
[*]
Script called 'prng' requires ARexx, you do not need to worry about anything
if your system has original 'startup-sequence', but when you encounter some
runtime troubles then these steps may help:
- go 'sys:system/' and start 'RexxMast' manually
> sys:system/rexxmast
- call the 'prng' with 'rx' at the beggining
> rx prng ...
- or if it still doesnt work call it with 'sys:rexxc/rx':
> sys:rexxc/rx prng ...
- if still no success check if you got essential stuff:
+ libs:rexxsyslib.library
+ libs:rexxsupport.library
+ libs:mathieeedoubbas.library (it may be that you got 040 build while
running on something else, try with original)
+ sys:rexxc/rx or c:rx
+ sys:system/rexxmast
[*]
'MiamiDx' users must set the stack size using 'ixstack' that is a part of 'ixemul'
package. This is rather important since 'bitlbee' must be having some stack size
(128 kilos absolute minimum) or otherwise it will trash innocent memory blocks
and your system might/will crash!
---
megacz@usa.com
|
aminet net>