dag@mind.be
Since there was no information anywhere on the net for Belgian Linux users, we started to collect stuff that we thought could be important. This HOWTO aims to be the definitive list of all Belgian-related Linux information. If you think not, you have no excuse to complain and certainly not to not contribute. ;)
If you need to know more about the Linux Documentation Project or about Linux HOWTO's, feel free to contact the supervisor Tim Bynum linux-howto@sunsite.unc.edu.
Tim Bynum will post the listing to several national and international newsgroups on a monthly basis. In addition, the Belgian HOWTO can be found on the World Wide Web at http://dag.mind.be/howto/ New versions of the Belgian HOWTO are always placed at this site first, so please be sure to check if the copy you are reading is still up to date!
This document is currently translated in 3 languages (English, Dutch and French), we're trying to keep all three of them in sync, but the English version is the source-document!
The English and Dutch version are maintained by Dag Wieërs
dag@mind.be and is found
at:
http://dag.mind.be/howto/.
The French version is maintained by Dany Vanderroost
danyv@euronet.be and is
found at:
http://club.euronet.be/dany.vanderroost/howto.html.
A few people mailed us their suggestions and improvements, thanks go to:
Many thanks go to Ivo Clarysse soggie@iguana.be who started something similar earlier ( http://linbel.iguana.be/) and his project helped us a lot to get this document online.
If some information seems to be wrong, deceptive or missing, we'd appreciate if you mailed us the improvements. Since we're just human this document isn't bug-free, but your contribution can and will make a difference.
To add yourself to the Linux user groups or businesses, collect all necessary information and mail it to us.
Trademarks are owned by their owners.
Although the information given in this document is believed to be correct, the author will accept no liability for the content of this document. Use the tips and examples given herein at your own risk.
Copyright © 1998, 1999, 2000 by Dag Wieers. This document may be distributed only subject to the terms and conditions set forth in the LDP license.
There are some things I'm planning to add to this document, if you're interested be sure you're reading the most current version of this document. (This todo-list is only a reminder to myself, it is not in the translated documents!)
Linux provides 2 ways to set up your keyboard. At the console you can use
loadkeys and under XFree86 you can use xmodmap.
To use the keytable for a Belgian keyboard you can use
loadkeys be2-latin1
or
loadkeys be-latin1
The only difference between the two is that be2-latin1 add support for
twosuperior and threesuperior (keycode 41) and grave (keycode 43).
Usually loadkeys is started at boottime from the scripts located
somewhere in /etc/rc.d Different distributions handle it
differentely. But most distributions have a simple program (like
kbdconfig in RedHat or yast in SuSE) to change the
scripts.
To set your keyboard properly under XFree86 you've got more choices. By
running Xconfigurator (or a similar program) a config-file for
XFree86 is created (with some standard content). This file is called
XF86Config and is usually located in /etc or
/etc/X11
Make sure (and change otherwise) that something similar to this is given
under the Keyboard Section.
Section "Keyboard"
Protocol "Standard"
XkbRules "xfree86"
XkbModel "pc101"
XkbLayout "be"
EndSection
If you own a 'microsoft' keyboard (or the less-known penguin keyboards ;p)
you can enable those extra 3 keys by changing the "pc101" into
"pc104". (I use the extra keys as meta-keys in my windowmanager so
some shortcuts doesn't conflict with the internal ones of my wm).
To get the AltGr key to work under XFree86 simply add in the
Keyboard Section:
RightAlt ModeShift
To get some key-combinations working under X11, you might want to change in file /usr/X11R6/lib/X11/xkb/symbols/be:
key <AD11> { [ dead_circumflex, diaeresis ],
[ bracketleft ] };
key <AC11> { [ ugrave, percent ],
[ quoteright ] };
key <BKSL> { [ mu, sterling ],
[ quoteleft ] };
key <AB10> { [ equal, plus ],
[ asciitilde ] };
by
key <AD11> { [ dead_circumflex, dead_diaeresis ],
[ bracketleft ] };
key <AC11> { [ ugrave, percent ],
[ dead_acute ] };
key <BKSL> { [ mu, sterling ],
[ dead_grave ] };
key <AB10> { [ equal, plus ],
[ dead_tilde ] };
Some people prefer to use a 'compose'-key to enter their special characters, like:
<compose>'e => é
<compose>/o => ø
<compose>c, => ç
<compose>co => ©
<compose>ss => ß
Solution:
xmodmap -e "keycode xx = Multi_key"
or
xmodmap -e "keysym yy = Multi_key"
and 'xx' is the keycode and 'yy' the kesym of the key you choose to be the 'compose'-key.
(use xev to get these values)
Alternatively you can add
keycode xx = Multi_key
to your /.xmodmaprc. This way it happens automagically.
Some applications have to be compiled as 8-bit clean to work well with the European characterset. Others like to be told in advance.
You can load the ISO-8859-1 font by typing the following in console:
setfont lat1u-16.psf
mapscrn trivial
echo -ne '\033(K'
To be able to use ë, è, é or ç in console, you might want to add these to your /.inputrc:
set meta-flag on
set convert-meta off
set output-meta on
(this must be done for every user, if you want this to be default for all users you can either add this file to /etc/skel/ or you could add these lines to /etc/inputrc and add the following line to /etc/bashrc,
export INPUTRC=/etc/inputrc
)
Note: this is only useful to programs that use readline (like bash) Also set the following environment variables:
LC_CTYPE=iso-8859-1
SYSFONT=lat1u-16.psf
SYSTERM=linux
Since Europe had to invent a new character, the Euro, there's a new
standard. It's called ISO-8859-15 (aka Latin-9 or Latin-0). To add support
you need both a new font and new keymaps. This is part of every major
distribution nowadays, if you have an older distributions you probably
need a newer console-tools package.
The changes in the keymap-file consist of the following lines:
keycode 18 = +e +E currency
keycode 46 = +c +C cent
And the following environment-variable should be set:
SYSFONT=lat0-16.psf
to make sure you're using the right font.
Since Belgium is located in the Central European Time zone (aka MET) which (in the winter) is equivalent to the Greenwhich Mean Time plus 1 (GMT+1), you can simply link /usr/lib/zoneinfo/localtime/MET to /etc/localtime symbolicly like:
ln -sf /usr/lib/zoneinfo/MET /etc/localtime
or
ln -sf /usr/lib/zoneinfo/Europe/Brussels /etc/localtime
This automagically sets Daylight Savings (which is GMT+2 in the summer).
Note: that different distributions have different paths, zoneinfo can be located in /usr/share or such...
Note2: RedHat uses a tool called timeconfig, SuSE uses
yast
To change the CMOS clock and then synchronize the system time with the CMOS clock, do something like this:
hwclock --set --date="Feb 25 03:38"
clock -u -s
If your clock is set to local time (which is discouraged but if you have other OS's installed a must), you can do:
hwclock --set --date="Feb 25 04:38"
clock -s
[Noticed the 1 hour difference ? ;p]
Not much programs support locale yet, if you want to know more about locale or how to write your own programs to support it, check: [put the damn url here ;p]
Be aware that locale makes it harder to resolve problems as less people can help you !! You might understand a problem when it's in technical English, but what if it's translated in some obscure French ?!? Some obviously won't understand both. ;p
To enable support for the Dutch locale in Belgium on a system with locale support you just have to set the following environment variables:
LANG=nl
LANGUAGE=nl_BE
Try nl_BE.ISO_8859-1 if nl_BE does not work.
If you want French locale support in Belgium, set the following environment variabels:
LANG=fr
LANGUAGE=fr_BE
Try fr_BE.ISO_8859-1 if fr_BE does not work.
If you want instead German locale support in Belgium, set the following environment variabels:
LANG=de
LANGUAGE=de_BE
Try de_BE.ISO_8859-1 if de_BE does not work.
For Walloon locale support you can find files and information at: http://www.linuxi18n.org/locales/walon/. To use it set:
LANG=wa
LANGUAGE=wa_BE:fr_BE
Try wa_BE.ISO_8859-1 if wa_BE does not work.
These options add support for the Belgian characterset and codepages. If you'd like to have these, compile a kernel with these options put on. They only apply to some filesystems (FAT-based, ISO9660, ...).
< > Codepage 850 (Europe)
< > NLS ISO 8859-1 (Latin 1; Western European Languages)
< > NLS ISO 8859-15 (Latin 9; Western European Languages with Euro)
Located in Filesystems > Native Language Support
If your kernel is a modular kernel that came with your distribution (=you never compiled a kernel before), then you might want to type:
insmod nls_cp850
insmod nls_iso8859_1
insmod nls_iso8859_15
To configure PPP correctly, you should check the PPP-HOWTO. I try to explain it briefly, but if you have any questions or problems, read the HOWTO very carefully.
To configure your modem, you can alter the initstring of your modem. To learn more about your modem, check Ask Mr. Modem.
Beware: if you have a winmodem you will probably not get it to work. More information about winmodems is at: http://linmodems.org/. Work is underway, but winmodems are not as good as real modems.
Now, you need to have the ppp-package installed (check this by typing
pppd --version), make sure you have a recent one. Then you have to
make sure you've got these files:
/usr/local/bin/ppp
#!/bin/sh
case $1 in
on|start)
TELEPHONE='555-1212' # The telephone number for the connection
ACCOUNT='your_login' # The account name for logon (as in 'George Burns')
PASSWORD='your_pass' # The password for this account (and 'Gracie Allen')
INITSTRING='AT&F&C1&D2Z'# Modem initstring
IPLOCAL=0.0.0.0 # Local IP address if known. Dynamic = 0.0.0.0
IPREMOTE=0.0.0.0 # Remote IP address if desired. Normally 0.0.0.0
DEVICE=/dev/ttyS1 # Serial Device com1=ttyS0, com2=ttyS1,...
SPEED=57600 # 19200, 38400 or 57600 (don't try something different)
export TELEPHONE ACCOUNT PASSWORD INITSTRING
exec /usr/sbin/pppd $DEVICE $SPEED $IPLOCAL:$IPREMOTE \
user $ACCOUNT connect /etc/ppp/ppp-on-dialer
;;
off|stop)
if [ -r /var/run/ppp0.pid ]; then
kill -INT `cat /var/run/ppp0.pid`
if [ ! "$?" = "0" ]; then
rm -f /var/run/ppp0.pid
echo "ERROR: Removed stale pid file"
exit 1
fi
exit 0
fi
echo "ERROR: PPP link is not active on ppp0"
exit 1
;;
info|status)
/usr/sbin/pppstats
;;
*)
echo "Usage: ppp on|off|info|start|stop|status";
;;
esac
/etc/ppp/ppp-on-dialer
#!/bin/sh
exec /usr/sbin/chat -v \
REPORT CONNECTION \
REPORT CARRIER \
TIMEOUT 10 \
ABORT '\nBUSY\r' \
ABORT '\nNO ANSWER\r' \
ABORT '\nNO CARRIER\r' \
ABORT '\nNO DIALTONE\r' \
ABORT '\nRINGING\r\n\r\nRINGING\r' \
ABORT 'Invalid Login' \
ABORT 'Login incorrect' \
'' "\r$INITSTRING\r" \
'OK-+++\c-OK' 'ATH0' \
TIMEOUT 45 \
OK "ATDT$TELEPHONE" \
CONNECT '\d\c' \
ogin:--ogin: "$ACCOUNT" \
ord: "$PASSWORD"
You can remove the -v once everything looks normal.
The pppd command uses /etc/ppp/options to list its options, change these options to whatever fits. These defaults normally work in most cases.
asyncmap 20a0000
crtscts
debug
default-mru
defaultroute
detach
escape 11,13,ff
hide-password
ipcp-accept-local
ipcp-accept-remote
lcp-echo-failure 4
lcp-echo-interval 400
lock
modem
mtu 1500
netmask 255.255.255.0
noipdefault
passive
#idle 300
#kdebug 0
#-vj
Once dialing in works like a charm, you can leave debug out.
Beware: it is important to emphasize that every special character, thus every character that is not [a-ZA-Z0-9] and '_', should be escaped by preceding it with a '\'-character. Thus "e!b$l+" would become "e\!b\$l\+". Try it if you are having troubles !
If your ISP requires CHAP or PAP, you need one of these files with their proper username and password:
/etc/ppp/pap-secrets or /etc/ppp/chap-secrets
#client server secret IP
your_login * your_pass *
To configure your nameservers, change /etc/resolv.conf. If dialing in is succesfull, but you can't get it to connect to URL's: this is probably the cause.
domain domain_of_your_isp
nameserver your_primary_nameserver
nameserver your_secondary_nameserver
Before you can run a (shell)script, it must be set executable. Be sure
that you set the permissions so that other users cannot see the passwords
stored in the files. If you want other users to be able to dial in, you
might want to consider using sudo. You might want to do the
following:
chmod u+rw og-rwx -R /etc/ppp
chmod u+x /etc/ppp/ppp-on-dialer /usr/local/bin/ppp
Then if /usr/local/bin is in your PATH, you can easily
dial in with:
ppp on
and hangup with:
ppp off
and to get some statistics, you do:
ppp status
PAP
194.119.240.62
text-based
195.13.24.1
PAP
194.149.160.9, 194.149.160.1
no official support yet
text-based
proxyarp
193.74.208.135
http://www.kpnbelgium.be/support/Support.asp?ID=3&SupportID=11
text-based
noccp
62.112.0.7, 194.88.127.7
no official support yet
text-based
CHAP
194.119.232.3, 194.119.232.2
no official support yet
PAP
defaultroute
195.238.2.21, 195.238.2.22
no official support yet
PAP
194.7.1.4, 194.7.15.70
no official support yet
PAP
no official support yet
text-based
195.74.193.12, 194.134.0.12
CHAP
212.233.1.34, 212.233.2.34
no official support yet
PAP
194.109.6.66, 194.109.9.99
CHAP
no official support yet
Contributed by Christophe Lambin clambin@skynet.be
This section does not aim to be a definitive guide on ISDN for Linux. For a more detailed discussion on the topic, see Paul Slootman's ISDN4Linux HOWTO and ISDN4Linux-FAQ.
If you're using a 2.2 kernel, it's recommended to get an updated version of the ISDN code. You can retrieve the CVS at ftp://ftp.suse.com/pub/isdn4linux/. For more information, check: http://www.brisse.dk/site/linux/docs/isdn.htm
Warning: if you've recently purchased an Eicon Diva 2.0 PCI (eg, via Belgacom), there's a good chance you've actually got a Diva 2.01.In this case, you must get a version dated 1 July 1999 or later !
Once the ISDN is in place, you can start up the driver. Eg:
modprobe hisax type=11 protocol=2
Refer to the Readme's for the right parameters and values for your card.
Next, you'll need the ISDN4Linux toolkit. You can retrieve the latest version of the toolkit at: ftp://ftp.suse.com/pub/isdn4linux/
With the tools installed and configured, write a script to configure the interface, to be used for the ISDN connection. As always in Linux, there's no one correct way of doing this. I've put these in a script
/etc/rc.d/rc.isdn:
#!/bin/sh
MSNREMOTE='555-1212' # Phone number of ISP
MSNLOCAL='555-1313' # my number, without 0, with areacode
ACCOUNT='george' # The account for logon (as 'George Burns')
IPLOCAL=10.0.0.2 # my fixed IP (use 10.0.0.2 if no fixed)
IPREMOTE=0.0.0.0 # IP number of ISP
INTERFACE=ippp0
/sbin/modprobe hisax type=11 protocol=2
/sbin/isdnctrl verbose 3 system on
/sbin/isdnctrl addif $IF
/sbin/isdnctrl secure $IF on
/sbin/isdnctrl addphone $IF out $MSNREMOTE
/sbin/isdnctrl eaz $IF $MSNLOCAL
/sbin/isdnctrl huptimeout $IF 300
/sbin/isdnctrl l2_prot $IF hdlc
/sbin/isdnctrl l3_prot $IF trans
/sbin/isdnctrl encap $IF syncppp
# /sbin/isdnctrl dialmode $IF auto
/sbin/ifconfig $IF $IPLOCAL pointopoint $IPREMOTE -arp -broadcast
/sbin/ipppd /dev/ippp0 user $ACCOUNT $IPLOCAL:$IPREMOTE
To start this at boot time, make it executable and append the following to /etc/rc.d/rc.local:
if [ -x /etc/rc.d/rc.isdn ]; then
. /etc/rc.d/rc.isdn
fi
The ipppd command gets its parameters passed through a file, /etc/ppp/ioptions:
-ac
-bsdcomp
debug
defaultroute
ipcp-accept-local
ipcp-accept-remote
mru 1524
mtu 1500
noipdefault
-pc
useifip
-vj
-vjccomp
#idle 360
#persistent
Warning: do NOT specify +pap or +chap in this file. This specifies the authentication that ipppd should use for an INCOMING client. If you were to use this to connect to your ISP, ipppd would wait for the ISP to authenticate itself using the specified protocol.
Beware: it is important to emphasize that every special character, thus every character that is not [a-ZA-Z0-9] and '_' should be escaped by preceding it with a '\'-character. Thus 'e!b$l+' would become 'e\!b\$l\+'. Try it if you are having troubles !
Finally, create /etc/ppp/ip-down.local to handle the shutdown of the interface:
#!/bin/sh
/sbin/ifconfig $1 down
sleep 1
/sbin/ifconfig $1 10.0.0.2 pointopoint
Note: this is to handle some problems with routes on shutdowns. Anyone know of a clean(er) solution ?
If your ISP uses PAP or CHAP, create a file /etc/ppp/pap-secrets or /etc/ppp/chap-secrets. Its format is:
#client server secret IP
your_login * your_pass *
Not really related to ISDN, but a lot of people forget this step (too eager to try out all the stuff they typed in above ? :-)).
Anyway, you need to configure the DNS, by creating a file /etc/resolv.conf:
domain your_domain_of_your_isp
nameserver your_primary_nameserver
nameserver your_secondary_nameserver
Before you can run a (shell)script, it must be set executable. Be sure
that you set the permissions so that other users cannot see the passwords
stored in the files. If you want other users to be able to dial in, you
might want to consider using sudo. You might want to do the
following:
chmod u+rw og-rwx -r /etc/ppp
chmod u+x /etc/rc.d/rc.isdn /etc/ppp/ip.down-local /usr/local/bin/isdn
Finally, you can write a little wrapper to start and stop the ISDN connection. I've put this as /usr/local/bin/isdn:
#!/bin/bash
case $1 in
on|start)
/sbin/isdnctrl dial ippp0
;;
off|stop)
/sbin/isdnctrl hangup ippp0
;;
info|status)
/sbin/isdnctrl list ippp0
;;
*)
echo "Usage: isdn on|off|info|start|stop|status"
;;
esac
Then if /usr/local/bin is in your PATH, you can easily
dial in with:
isdn on
and hangup with:
isdn off
DHCP was designed to make life easier, and most of the times it does ;) More information to set up your DHCP client can be found at: http://www.oswg.org/oswg-nightly/DHCP.html and a list of Frequently Asked Questions at: http://web.syr.edu/~jmwobus/comfaqs/dhcp.faq.html which describes everything you need to know. Along with the information in the Cable-Modem HOWTO ( http://www.oswg.org/oswg-nightly/Cable-Modem.html).
Lots of people want to connect a whole network to their cablemodem, that's not a problem. You'll need IP-Masquerading ( http://www.linuxdoc.org/HOWTO/IP-Masquerade-HOWTO.html) and make sure the interface (that speaks to the cablemodem) has the right MAC-address !! Another solution (in case of problems) is to reset your cablemodem.
no official support yet
http://pac.pandora.be:8080
export http_proxy="http://proxy.pandora.be:8080/"
no official support yet
using DANA
no official support yet
More information can be found in the User Group HOWTO located at: http://www.linuxdoc.org/HOWTO/User-Group-HOWTO.html A complete list of Linux User Groups is at: http://www.ssc.com/linux/glue/ and at: http://limestone.uoregon.edu/woven/lugww/
Mechelbaan 260
B-3130 Begijnendijk
Paul Terweduwe paul@faes.be
13 April 1999.
Van Luppenstraat 70
B-2018 Antwerp
+32 3 218 63 54
Patrick Op de Beeck alug@pandora.be
26 December 1999.
Brussels Linux User Group (BeLUGa)
Infogroep, Building F, room 218
Vrije Universiteit Brussel
Pleinlaan 2
B-1050 Brussel
25 February 2000.
Charleroi Linux User Group (CAROLINUX)
23 September 1999.
HCC Limburgse Linux Gebruikers Groep
Andy Peeters & Bruno Tony
31 May 1999.
Diegemstraat 61
B-1930 Zaventem
Yvo Dries Yvo.Dries@village.uunet.be
2 August 1999.
Milcampslaan 101
B-1040 Schaarbeek
+32 2 657 77 36
+32 2 657 77 38
5 March 1999.
Pleinlaan 2, 5F218 (building F)
B-1050 Brussels
+32 2 629 33 56
+32 2 629 33 89
6 July 1999.
Leuvense Linux Users (L2U)
28 November 1999.
Limburgse Linux User Group (LILUG)
Frank Eersels frank.eersels@ping.be
6 May 1999.
Linux.be vzw/asbl
Non-proft organization to promote Linux in Belgium
23 September 1999.
Rue d'Aineffe 4
B-4317 Borlez Faimes
Alexandre J.D. Dulaunoy adulau@rtfm.be
25 February 1999.
Linux Gebruikers Oost-Vlaanderen
25 February 1999.
Linux User Group De Bruxelles (BxLUG)
Raphael Bauduin bxl_information@linuxbe.org
17 July 1999.
Linux User Group De Namur
17 July 1999.
Linux User Group Mons
26 May 1999.
Universiteitslaan 1, Filii Lamberti
3590 Diepenbeek
25 February 1999.
linuxbe.org
Cedric Gavage niddle@linuxbe.org
7 February 2000.
Wim Vandeputte
PB 144
B-9000 Gent 12
+32 9 240 29 17
+32 9 240 34 39
Wim Vandeputte wvdputte@reptile.rug.ac.be
4 March 1999.
Kruipstraat 14
B-1850 Grimbergen
+32 11 27 58 98
+32 11 27 03 89
Jan Vanhercke jan.vanhercke@c-cure.be
4 March 1999.
Kleinhoefstraat 4
B-2440 Geel
12 June 1999.
Tina gebruikers vraagtina@digibel.org
25 February 2000.
Blijde Inkomsstraat 21, lokaal 01.17
B-3000 Leuven
+32 16 32 48 61
http://www.ulyssis.student.kuleuven.ac.be/org/ulyssis/
25 February 1999.
Krijgslaan 281 S9
B-9000 Gent
+32 09 264 47 51
Restricted to RUG students
22 June 1999.
The Linux Documentation Project contains worldwide lists of Linux businesses, Linux Consultants HOWTO and V.A.R. HOWTO, and can be found at: http://www.linuxports.com/.
Avenue du Pesage, 31-33
B-1050 Brussels
+32 2 646 00 76
25 February 1999.
Avenue Joseph Wybranlaan 40
B-1070 Brussels
+32 2 529 59 91
+32 2 529 59 92
11 February 2000.
Geldenaakse Vest 6
3000 Leuven
+32 16 29 80 45
+32 16 29 80 46
After an onsite installation, we mainly support our customers with SSH remote administration. Most problems are reported by E-mail or by the inhouse-developped webbased supportsystem. This doesn't mean that once in a while a supportcall comes in.
Security, systemadministration and setups, security (firewalling, tigerteaming, VPN, etc.) Networkdesign, wireless networking, Troubleshooting, product development, etc. Please visit http://www.ba.be for more info.
7 March 1999.
Av. Van Goidtsnoven 33
B-1180 Uccle
25 February 1999.
Sportstraat 28
B-9000 Gent
+32 9 222 77 64
+32 9 222 49 76
Michael C. Vergallen mvergall@double-barrel.be
phone, email remote network admin, inhouse, onsite.
installation, system admin. internet and intranet connectivity, sendmail, firewalls, proxys, nameservers, troubleshooting software & hardware.
5 March 1999.
Korte Vuldersstraat
B-8000 Brugge
+32 50 344366
2 March 1999.
Mgr. Vanwaeyenberglaan 6/10
B-3000 Leuven
+32 477 57 50 71
Jasper Nuyens jasper@life.be
LIFE is the first company in Europe to provide 24/7 professional support for Linux in Europe. LIFE also provides server and desktop installation services, educational services and fixed price development. Exclusive on the Linux operating system.
Kernel driver development, database interconnectivity (VPN, wireless networking), security auditing (firewall, VPN, ethical hacking), e-commerce. See our website for more.
20 April 1999.
Vaartstraat 12
B-3000 Leuven
+32 478 274 069 or +32 476 468 405
Peter Vandenabeele peter@mind.be or Dag Wieërs dag@mind.be
Installation & configuration, auditing & consultancy, support & maintenance, training & education, research & development.
Large Linux deployements, company security and network audits, remote server maintenance, application and kernel development, cluster computing, data recovery, ... See our website.
11 February 2000.
Rue de l'autonomie 1
B-1070 Brussels
25 February 1999.
Knaptandstraat 96-98
B-9100 Sint-Niklaas
02 March 1999.
Rue Dartois 1
B-4000 Liège
+32 4 253 00 59
+32 4 253 00 49
Bruno Mairlot bruno@virgoplus.com
By phone, email, or remote networked administration, inhouse, onsite
Installation, configuration, administration of Linux, internet connection, intranet developpment, firewalls, samba, netatalk, firewalls, proxys, DNS, web server (Apache), mod_perl, MySQL, Gui interface developpment (GTK+). We have acquired a special expertise with the Red Hat distributions.
28 June 1999.
The most important collection of Linux information on the net. Please if you encounter erroneous information in one of them, do contact the author. Only that way it will be corrected and we all stand together ;)
As Dutch is less wide-spread, it is the least supported. But work is being done to resolve this ;) (and maybe *you* can help ?!?) French and German translations obviously are already taken care of.
A succesfull initiative is making progress, but there's still a lot to do. If you want to help, start translating and send it there. Check: http://nl.linux.org/doc/HOWTO/.
French translations of HOWTO's can be found at: ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/translations/french/
German translations of HOWTO's can be found at: ftp://sunsite.unc.edu/pub/Linux/docs/HOWTO/translations/german/
Most of the times, it doesn't matter where you got it from, as long as it works. But to save you some time and save us some bandwidth, it's much better to get it near you ;) Naturally I forgot some, please send your additions or corrections.
The fastest medium to get support is IRC, but beware. Because IRC is rather anonymous it's also easy to fool people.
On IRCnet there's a channel called #linux.be that is closely related to bcol and the Belgian Linux-scene. The channel is still small, but it surely will grow in time. To get help in English, there's only one place #linux.