My name is Klaikong Vaidhyakarn from Thailand. I attended two SourceCamps in Asia Source I and Asia Source II.

The source camp has been made friendship among geeks and social practitioners until now, we still in touch through the mailing lists.

The important thing the source camps was inspired me to organize the Mekong ICT Camp in February 2008. Because the source camp methodology that make all participants sharing their experience about technology and build good network between participants.

The Mekong ICT Camp was followed the instruction in this site. The information in this site is very useful for anyone who want to organize the activity like "Source Camp". I would like to thank Tactical Tech Collective not only the wonderful event like Asia Souce but also the great knowledge in this site that make us accomplish our event.

Klaikong

Metche is a simple step up from a basic Changelog - providing emailing of diff files:

wget https://poivron.org/dev/metche/attachment/wiki/WikiStart/metche-1.1.tar.gz

tar zxvf metche-1.1.tar.gz

cd metche-1.1

sudo cp metche /usr/local/sbin/

sudo cp metche.8 /usr/local/man/man8/

sudo cp metche.conf.default /etc/metche.conf

sudo vi /etc/metche.conf

DO_DETAILS="yes"
STABLE_TIME="1"
EMAIL_ADDRESS="changelog@localhost"

sudo vi /etc/aliases

changelog: admin1@internet.address,admin2@address2

newaliases

Procedure for use? Simply add changes to:

/root/Changelog

Continue with the rest of the detailed Step-by-Step Installation Guide

The Wordpress Blog has an out-dated Ubuntu packge, so we install from source.

sudo addgroup wordpressadmins

cd /opt

sudo wget http://wordpress.org/wordpress-2.1.2.tar.gz

sudo tar zxvf wordpress-2.1.2.tar.gz

sudo ln -s wordpress-2.1.2 wordpress

Add plugins desired by Facilitators:

http://wordpress.org/extend/plugins/

sudo chgrp -R wordpressadmins /opt/wordpress

Configure MySQL:

Configure Apache:

sudo vi /etc/apache2/conf/sites-available/wordpress

cd /etc/apache2/conf/sites-active

sudo ln -s ../sites-available/wordpress

sudo /etc/init.d/apache2 reload 

Continue with the rest of the detailed Step-by-Step Installation Guide

MediaWiki has an out-dated Ubuntu packge, so we install from source.

sudo addgroup mediawikiadmins

cd /opt 

sudo wget http://kent.dl.sourceforge.net/sourceforge/wikipedia/mediawiki-1.9.3.tar.gz

sudo tar zxvf mediawiki-1.9.3.tar.gz

sudo ln -s mediawiki-1.9.3 mediawiki

Add extensions desired by Facilitators:
http://www.mediawiki.org/wiki/Category:Extensions

sudo chgrp -R mediawikiadmins /opt/mediawiki

Configure MySQL:

Configure Apache:

sudo vi /etc/apache2/conf/sites-available/mediawiki

cd /etc/apache2/conf/sites-active

sudo ln -s ../sites-available/mediawiki

sudo /etc/init.d/apache2 reload

Continue with the rest of the detailed Step-by-Step Installation Guide

The Drupal CMS has an out-dated Ubuntu packge, so we install from source.

We use Drupal mainly as a Blog

sudo addgroup drupaladmins

cd /opt

sudo wget http://ftp.osuosl.org/pub/drupal/files/projects/drupal-5.1.tar.gz

sudo tar zxvf drupal-5.1.tar.gz

sudo ln -s drupal-5.1 drupal

Add modules desired by Facilitators:
http://drupal.org/project/Modules

sudo chgrp -R drupaladmins /opt/drupal

Configure MySQL:

Configure Apache:

sudo vi /etc/apache2/conf/sites-available/drupal

cd /etc/apache2/conf/sites-active

sudo ln -s ../sites-available/drupal

sudo /etc/init.d/apache2 reload 

Continue with the rest of the detailed Step-by-Step Installation Guide

The Ubunutu package for the Plone CMS is not currently up to date. (2.5.1 vs 3.0.1). However, it is quicker/easier to use than installing from source.

sudo apt-get install plone-site

set password for 'admin' user to same as MySQL root (can grant priviliges to user accounts later)
8081 is fine for default port
Keep data for plone-site on package purge? No

sudo addgroup ploneadmins
sudo chgrp -R ploneadmins /usr/share/zope
sudo chmod g+w -R /usr/share/zope

Configure Apache to Proxy to Plone:

sudo a2enmod rewrite
sudo a2enmod proxy

sudo vi /etc/apache2/sites-available/plone

(paste in contents of attached file)

sudo ln -s /etc/apache2/sites-available/plone /etc/apache2/sites-enabled
sudo /etc/init.d/apache2 restart

Instantiate Plone site:

http://plone:8081/manage

Plone site

Id: camp

Add Plone Site

Additional modules can simply be untarred in:

/usr/share/zope/Products

This can be left to users if their logins are added to the plone admins group:

sudo vi /etc/group

ploneadmins:x:1002:login_name

Continue with the rest of the detailed Step-by-Step Installation Guide

FTP server is used as an easy way for anyone to upload any Files they wish to share with the rest of the camp, such as Photos or ISO images. These files can be downloadable either via FTP or by simply using a Web Browser.

sudo apt-get install proftpd

Standalone
Ignore: "IPv6 getaddrinfo 'camp.asiasource2' error: Name or service not known"

sudo vi /etc/proftpd/proftpd.conf

(Add the pasted contents of the attachment to what's already there)

sudo /etc/init.d/proftpd force-reload

sudo vi /home/ftp/welcome.msg

Welcome, user %U@%R !

The local time is: %T

This is the Camp FTP server. If you have any unusual problems,
please report them via e-mail to .

sudo mkdir /home/ftp/photos
sudo chown ftp /home/ftp/photos
sudo ln -s /home/ftp/photos /var/www
sudo mkdir /home/ftp/iso
sudo chown ftp /home/ftp/iso
sudo ln -s /home/ftp/iso /var/www

Continue with the rest of the detailed Step-by-Step Installation Guide

Allows us to monitor the quality of the ISP connection with historic graphs (much better than snapshots taken with manual pings & all can see the results from 1 set of pings)

sudo apt-get install smokeping

sudo mkdir /var/run/smokeping
sudo chown smokeping /var/run/smokeping
vi /etc/smokeping/config

owner = Admin
contact = admin@internet.address
cgiurl = http://smokeping/cgi-bin/smokeping.cgi
mailhost = mail
to = admin@internet.address
from = smokealert@asiasource2
remark = Welcome to the SmokePing website of AsiaSource II
+ ISP
menu = ISP
title = Localloop to ISP
host = smtp.isp.net
+ Google
menu = Google
title = Google
host = google.co.uk

sudo /etc/init.d/smokeping restart

Configure Apache to allow a shortcut:

cd /etc/apache2/sites-available

sudo vi smokeping

(Paste in contents of attached file)

cd ../sites-enabled
sudo ln -s ../sites-available/smokeping
sudo /etc/init.d/apache2 restart

Continue with the rest of the detailed Step-by-Step Installation Guide

Provides database back-end for LAMP applications

Security: configured to use a different user account for each application - this account can only access that application's database(s). User account has same name as application.

sudo apt-get install mysql-server

Configure root password:

mysqladmin -u root password notthisbutsomethingsecure

Install phpMyAdmin to allow for easier administration:

sudo apt-get install phpmyadmin libapache2-mod-php5

sudo vi /etc/apache2/sites-available/phpmyadmin

(paste in contents of attached file)

sudo ln -s /etc/apache2/sites-available/phpmyadmin /etc/apache2/sites-enabled

sudo /etc/init.d/apache2 restart

Continue with the rest of the detailed Step-by-Step Installation Guide

Needed for Admin alerts & for Applications' mail functionality. Also useful for POP-3/IMAP users.

NB Debian (& hence Ubuntu) have a unique way of configuring Exim: http://pkg-exim4.alioth.debian.org/

sudo apt-get install exim4

sudo dpkg-reconfigure exim4-config

split into small files? No
configuration: mail sent by smarthost; received via SMTP or fetchmail
system mail name: mail.asiasource2
Listen on: 127.0.0.1:192.168.1.1:192.168.2.1
Other destinations: camp.asiasource2:blog.asiasource2:wiki.asiasource2
Machines to relay mail for: 127.0.0.1:192.168.1.0/24:192.168.2.0/24
Smarthost: smtp.eclipse.net.uk
Hide local: Yes
visible name: mail.asiasource2
Dial on demand: No
mbox format in /var/mail/

sudo vi /etc/aliases

root: admin@internet.mail
webmaster: root

sudo newaliases 

sudo /etc/init.d/exim4 restart

Continue with the rest of the detailed Step-by-Step Installation Guide

sudo apt-get install squid

Configure Squid for Transparent Proxy:

sudo vi /etc/squid/squid.conf

http_port 192.168.1.1:3128 transparent
icp_port 0
always_direct allow all
acl our_networks src 192.168.1.0/24 192.168.2.0/24
http_access allow our_networks

sudo /etc/init.d/squid restart

Configure Firewall for Transparent Proxy:

sudo vi /etc/shorewall/rules

REDIRECT loc 3128 tcp www - !192.168.1.1

sudo /etc/init.d/shorewall restart

Advert blocking:

A simple hosts file serves pages faster than DansGuardian

wget http://www.mvps.org/winhelp2002/hosts.zip
unzip hosts.zip
sed '/127.0.0.1 / s/127.0.0.1 //g' HOSTS > adservers
vi adservers

# Delete all the top comments & the line 'localhost'

sudo mv adservers /etc/squid 

sudo vi /etc/squid/squid.conf

acl ads dstdomain "/etc/squid/adservers"
http_access deny ads

sudo /etc/init.d/squid restart

Add SARG for log analysis:

sudo apt-get install sarg

Continue with the rest of the detailed Step-by-Step Installation Guide

We use Shorewall as it simplifies Firewall setup & has excellent documentation.

sudo apt-get install shorewall

sudo vi /etc/default/shorewall

startup=1

NB We assume that there is a WAN router plugged into the LAN2 ethernet port (eth1). If using a USB ADSL modem then replace 'eth1' with 'ppp0'.

sudo cp /usr/share/doc/shorewall/examples/three-interfaces/* /etc/shorewall/

sudo gunzip /etc/shorewall/interfaces.gz /etc/shorewall/masq.gz /etc/shorewall/rules.gz /etc/shorewall/policy.gz 

sudo vi /etc/shorewall/interfaces

net eth1 detect tcpflags,dhcp,routefilter,norfc1918,nosmurfs,logmartians
loc eth0 detect tcpflags,detectnets,nosmurfs

sudo vi /etc/shorewall/shorewall.conf

IP_FORWARDING=On

sudo vi /etc/shorewall/masq

eth1 eth0
eth1 eth2

sudo vi /etc/shorewall/policy

$FW net ACCEPT
dmz net ACCEPT
dmz $FW ACCEPT
dmz loc ACCEPT

sudo vi /etc/shorewall/rules

#SSH/ACCEPT loc dmz
#DNS/ACCEPT dmz net
# Allow connections to the Server
DNS/ACCEPT loc $FW
ACCEPT loc $FW tcp 21
ACCEPT loc $FW tcp 25
ACCEPT loc $FW tcp 80
ACCEPT loc $FW tcp 8081
# Reject ICMP from LAN to Internet (we provide Smokeping instead)
REJECT loc net icmp

sudo /etc/init.d/shorewall restart

Provide priority access via LAN3:

sudo vi /etc/network/interfaces

# LAN3 (DMZ)
auto eth2
iface eth2 inet static
address 192.168.2.1
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255

sudo /etc/init.d/networking restart

Download Wondershaper & Tune:

wget http://lartc.org/wondershaper/wondershaper-1.1a.tar.gz

tar zxvf wondershaper-1.1a.tar.gz

sudo cp wondershaper-1.1a/wshaper /etc/shorewall/tcstart

sudo vi /etc/shorewall/tcstart

DOWNLINK=256
UPLINK=128
DEV=eth1
NOPRIOHOSTSRC= 192.168.1.0/24
#echo Please read the documentation in 'README' first :-\)
#exit

sudo vi /etc/shorewall/shorewall.conf

TC_ENABLED=Yes

sudo /etc/init.d/shorewall restart

Continue with the rest of the detailed Step-by-Step Installation Guide

Provides caching to speed up queries & save bandwidth for other tasks
Provides simple aliases for local services: wiki, blog, photos, etc
Security: chrooted, bound only to internal interfaces

sudo apt-get install bind9

sudo vi /etc/default/bind9

OPTIONS="-u bind -t /var/lib/named"

sudo mkdir -p /var/lib/named/etc

sudo mkdir /var/lib/named/dev

sudo mkdir -p /var/lib/named/var/cache/bind

sudo mkdir -p /var/lib/named/var/run/bind/run

sudo mv /etc/bind /var/lib/named/etc

sudo ln -s /var/lib/named/etc/bind /etc/bind

sudo mknod /var/lib/named/dev/null c 1 3

sudo mknod /var/lib/named/dev/random c 1 8

sudo chmod 666 /var/lib/named/dev/null /var/lib/named/dev/random

sudo chown -R bind:bind /var/lib/named/var/*

sudo chown -R bind:bind /var/lib/named/etc/bind

sudo vi /etc/init.d/sysklogd

SYSLOGD="-u syslog -a /var/lib/named/dev/log"

sudo /etc/init.d/sysklogd restart

Configure to use ISP's Resolvers as Forwarders:

sudo vi /var/lib/named/etc/bind/named.conf.options

listen-on {
127.0.0.1;
192.168.1.1;
192.168.2.1;
};

forwarders {
x.x.x.x;
x.x.x.x;
};

// listen-on-v6 { any; };

Configure local aliases:

sudo vi /var/lib/named/etc/bind/db.asiasource2

(Paste in contents of attached file)

sudo vi /var/lib/named/etc/bind/named.conf.local

zone "asiasource2" {
type master;
file "/etc/bind/db.asiasource2";
};

sudo /etc/init.d/bind9 restart

Configure server to use itself as resolver:

sudo vi /etc/resolv.conf

nameserver 127.0.0.1

Continue with the rest of the detailed Step-by-Step Installation Guide

Whilst we could use dnsmasq to provide DHCP & DNS caching, this doesn't allow us to add aliases, so we use the full daemon:

sudo apt-get install dhcp

sudo vi /etc/default/dhcp

INTERFACES="eth0"

sudo vi /etc/dhcpd.conf

option domain-name "asiasource2";
option domain-name-servers 192.168.1.1;
option subnet-mask 255.255.255.0;
default-lease-time 36000;
max-lease-time 36000;
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.11 192.168.1.211;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
}

sudo /etc/init.d/dhcp start

Continue with the rest of the detailed Step-by-Step Installation Guide

See: http://www.howtoforge.com/local_debian_ubuntu_mirror

sudo apt-get install apt-mirror

(replace 'gb' with local country)

sudo vi /etc/apt/mirror.list 

deb http://gb.archive.ubuntu.com/ubuntu feisty main restricted universe
deb http://gb.archive.ubuntu.com/ubuntu feisty-updates main restricted universe
deb http://gb.archive.ubuntu.com/ubuntu feisty-security main restricted universe
clean http://gb.archive.ubuntu.com/ubuntu

sudo apt-mirror

sudo bash /var/spool/apt-mirror/var/clean.sh

NB For a short camp, we don't need to schedule fresh updates. Longer installs should:

sudo vi /etc/cron.d/apt-mirror

Configure Apache to serve the repository to clients:

sudo apt-get install apache2

sudo ln -s /var/spool/apt-mirror/mirror/gb.archive.ubuntu.com/ubuntu /var/www

Configure server to use local mirror:

sudo vi /etc/apt/sources.list

deb http://127.0.0.1/ubuntu/ feisty main restricted universe
deb http://127.0.0.1/ubuntu/ feisty-updates main restricted universe
deb http://127.0.0.1/ubuntu/ feisty-security main restricted universe

sudo apt-get update
sudo apt-get upgrade

Workstation Configuration

These can be configured by simply pointing to the 'ubuntu' alias:

sudo vi /etc/apt/sources.list

deb http://ubuntu/ubuntu/ feisty main restricted universe
deb http://ubuntu/ubuntu/ feisty-updates main restricted universe
deb http://ubuntu/ubuntu/ feisty-security main restricted universe

sudo apt-get update
sudo apt-get upgrade

Continue with the rest of the detailed Step-by-Step Installation Guide

Configure static IP

sudo vi /etc/network/interfaces

# LAN1 (LAN)
auto eth0
iface eth0 inet static
address 192.168.1.1
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255

# LAN2 (WAN)

# example - depends on the WAN router details (which could even be ppp0 if using a USB ADSL modem)

auto eth1
iface eth1 inet static
address 172.16.3.1
netmask 255.255.255.0
network 172.16.3.0
broadcast 172.16.3.255
gateway 172.16.3.254

 sudo vi /etc/hosts

127.0.0.1 localhost.localdomain localhost
192.168.1.1 camp.asiasource2 camp

sudo echo camp.asiasource2 > /etc/hostname

sudo shutdown -r now

Configure DNS resolver

use ISP's until our own DNS service is configured

sudo vi /etc/resolv.conf

nameserver x.x.x.x
nameserver x.x.x.x

Install OpenSSH

After this, all admin can be done remotely via SSH :)

(Use the local country repo instead of 'gb')

sudo vi /etc/apt/sources.list

#deb cdrom:[Ubuntu 7.04 _Feisty Fawn_ - Release i386 (20070415)]/ feisty main restricted

deb http://gb.archive.ubuntu.com/ubuntu/ feisty universe

sudo apt-get update

sudo apt-get install openssh-server

Disable IPv6

sudo vi /etc/modprobe.d/bad_list

alias net-pf-10 off

Time Synchronisation

Need to ensure that Blog/Wiki posts appear properly!

sudo ntpdate ntp0.pipex.net

sudo vi /etc/rc.local

ntpdate ntp0.pipex.net

Replace dash with bash

sudo ln -sf /bin/bash /bin/sh

Continue with the rest of the detailed Step-by-Step Installation Guide

This can allow a number of low-end refurbished PCs to run a modern distribution, such as Ubuntu by using a powerful server (with 50Mb RAM/workstation +256Mb RAM for the server => 3Gb for 50 workstations, or a 1Gb server per lab: http://wiki.ltsp.org/twiki/bin/view/Ltsp/ServerSizing)

For use at SourceCamps, most facilitators are happiest with Ubuntu:

https://help.ubuntu.com/community/UbuntuLTSP

AMD Geode LX 500 Mhz
256 MB RAM
40 GB 2.5" HDD or 2 GB flash storage
4 x USB 2.0, VGA, Mic, Speaker out

They run on 12 VDC and draw less then 8 Watt.

Without LCD these cost USD 299

With 15" XGA 12 VDC / 11 Watt LCD bundled the cost is 469 USD.

Install OS

Boot off Ubuntu 7.04 'Alternate' CD (normal CD fails on Via processors as they don't support the optional i686 cmov instruction).

Install a command-line system
Do not configure the network at this time (since we don't want to download security updates multiple times)
Hostname: camp
username: tempinstaller
password: delete&replacewithnamed
Guided - use entire disk
System clock set to UTC

Initial Configuration

Mirror Setup

Add useful packages:

sudo apt-get install build-essential
sudo apt-get install cvs subversion unzip traceroute

DHCP

DNS

Firewall

Squid Proxy

SMTP

MySQL

Smokeping

FTP

Applications

Some applications can be installed from Ubuntu packages, however most require installing from source to get a recent enough version. Each application has a usergroup which can administer it's section of the filesystem for configuration (inc theming) & addition of modules.

Install pre-cursors:

sudo apt-get install php5-gd imagemagick

Plone

Drupal

MediaWiki

WordPress

Photos

A simple script to allow nice browsing of the Photos which have been uploaded via FTP (& also uploading some too?)

Change Control

It should house as much local content as possible in order to reduce the load on the fragile Internet connection.

This should include the camp Wiki (disable the public one for the duration of the camp), a camp Blog (a separate Public one should also be available, but participants should focus on the local one) & a system for sharing Photos.

Software to be installed (check with facilitators what they need for their sessions):

• Blog: Drupal & Wordpress (easier/more well-known than Gadgets?)
  
• Wiki: MediaWiki (easier/more well-known than Gadgets?)
• CMS: Plone

The Ubuntu packages for these applications may or may not be recent enough to be usable (e.g. MediaWiki package is very out of date!). Facilitators are also likely to want to add modules/plugins.

In order to be able to allow applications to be maintained separately from the core system, groups are created which have permissions to the applications:

• drupaladmins
• wordpressadmins
• ploneadmins
• mediawikiadmins
  

Core Network services:

• Gateway
• iptables providing NAT, QoS & filtering out icmp to prevent users wastefully testing performance (Smokeping provided instead)
  
• Proxy
• Squid for caching + advert filtering
  
• DHCP
  
• DNS
• Caching & also having simple aliases for internal services ('blog', 'wiki', 'photos', etc)
  
• SMTP Server
• Ubuntu package repository
• 15Gb so download beforehand on a fast connection!

A key requirement is to allow for priority Internet access for key tasks (such as downloading a missing application or updating the external Blog). This is achieved by having 3 NICs on the Gateway: WAN, LAN1 (Labs) & LAN2 (Priority). Wondershaper can be used to reduce the priority of LAN1.

Potential Hardware for the Server:

• http://www.lex.com.tw:8080/product/LIGHT.htm
• This was used at AfricaSource II
• Disadvantage: USB 1.1 ports (slow for external USB HDDs)
  
• http://www.mini-box.com/HYBRID-C7-1-2G?sc=8&category=99
• This is used for Inveneo's HubStation
  
• http://www.soekris.com/net5501.htm

Another alternative approach is to split the Gateway from the Server. The Gateway could then be a Linksys WRT54g running OpenWRT or a m0n0wall box. A Linksys can be known to drop connections &/or reduce throughput when scaling to more than 30-40 users.

A server may also be required to support LTSP for some Lab configurations.

Detailed Step-by-Step Installation Guide

These are organised into Labs of 12-16 terminals linked together by a Network.

The number of labs depends on the number of different content tracks of the programme.

The exact lab configuration should be defined by working with the facilitators before the workshop to ascertain requirements.

There are 2 approaches to the hardware used for the terminals:

1. Use low-end refurbished PCs & a single powerful server all running LTSP.
2. Use low-power PCs & hence only need a low-power server.
   

The latter seems generally preferable as:

• keeps Power consumption down
• means less reliance on the Server/Network
• reduces the impact of rain on exposed plug-boards.
  

If facilitators could agree cross-track when they needed access to PCs & when they were just doing theory, then it might be possible to reduce the number of computers required. This would help save Power. However it would be hard to co-ordinate, especially as the agenda can be flexible to respond to new needs.

Setting up the computer labs

• Please plan sufficient time to set-up the labs. It always takes longer than you think!
• The configuration of the labs should not be changed by participants. In some occasions participants bring interesting applications or have good suggestions on what software to add or how to reconfigure the computers. However, in order to ensure that the labs remain operational, these changes should only be done by the technical staff in charge of the labs
  

A good power system design can be used as a training aid during sessions.

Low-power

The best way to reduce overload is to reduce power consumption (which is also Green!).

The rule is: "Spend a little extra money on low-power appliances to save a lot of money on power generation/storage."

The best way to ensure clean stable power to appliances is to run off Batteries - 12V truck batteries are cheap & easily sourced locally (no need for expensive gel batteries for a 10 day camp!).

If batteries are not used then power from either the mains or generator needs to be stablised. This is best done centrally at source rather than through outlet-based protection. However if it's not possible to sufficiently clean the source then protecting outlets with surge-protectors may be the only option.

In addition, it is advisable to bring spare power supplies - especially for key network equipment (switches & wireless APs)

Ideally everything would run off 12V (including lighting), rather than needing to be inefficiently converted to 110/240V using an Inverter.

However some low-power Inverters may be useful for items without appropriate 12V inputs/adapters.

A 12 V distribution network would also negate the need for lots of plug-boards (trailing sockets). This is big win as they're decidedly not rain-proof!

Ensure sufficient plug-boards are available for whichever design is chosen - ideally those which can support multiple plug shapes (such as WonPro's WE-3A6R3-E105). Otherwise bring several adapters.

Batteries

Gel batteries provide the best long-term performance/reliability however for a short-term camp, cheap locally-available truck batteries are fine.

Batteries can be mounted in

• Series (+ linked to -).
  Add up the Voltages, so 2x12V => 24V.
  Ah lifetime as per 1, so 2x 120Ah => 120Ah
• or Parallel (+ linked to +).
  Constant voltage, so 2x12V => 12V.
  Ah lifetime added together, so 2x 120Ah => 240Ah
  

Charging the batteries

Ideally this can be done from the mains supply, as this is likely to be the cheapest source. Where this is not available then ideally a renewable energy source, such as Solar would make for a Greener camp. If this is too expensive (even for rental) then a Generator may be needed.

Generators

Generally generators produce dirty output, which needs proper stabilisation. (some generators come with this facility in-built)

When sizing a generator to match a load, remember that the load is usually measured in Watts, whilst the generator is sized in VA (Volt Amps). A rough approximation to convert between these is: 1 (K)VA = 0.8 (K)W.

Full details for those interested:

• http://www.plexoft.com/SBF/K01.html#KVA
• http://www.apcmedia.com/salestools/SADE-5TNQYF_R0_EN.pdf

Solar

The output from Solar Panels needs to go through a Charge Controller on the way to the batteries.

Mounting angle needs to be set correctly to maximise the charge.

Panels should be kept clean.

Calculations - Sizing

See attached spreadsheet for a tool to size batteries/solar charging for different loads.

One way to reduce power requirements would be if facilitators could agree cross-track when they needed access to PCs & when they were just doing theory, so that it might be possible to reduce the number of computers required.However it would be hard to co-ordinate, especially as the agenda can be flexible to respond to new needs.

ToDo:

• might be worth finding some universal power supplies that have been tested in tough environments and with power surges, and that have simple fuses, and using those for all equipment instead of the power supplies that come with the cheap stuff.

A good network design can be used as a training aid during sessions.

The usual KISS (Keep It Simple, Stupid!) rules apply

• Internet connectivity
• This will necessarily be location specific. We can neutralise this difference by simply getting an ethernet feed from the WAN router to our internal server/gateway.
  
• Server
• Gateway/Proxy
• Applications: Wiki, Blog, Photos
  
• LAN Equipment
• Hubs/Switches for __ Labs with __ computers each
  
• Cat 5 patch cables for __ Computers
• Cat 5 trunks for __ labs
  
• Wireless Access Points

Bring enough tools, especially crimping tools. There was only one crimping tool at AfricaSource II, which caused a bottleneck.

Connectivity

In many countries connectivity is expensive and poor. Managing the use of connectivity can be a key priority. For example, at Africa Source 2 a 3GB cap on monthly traffic was imposed by the local ISP (and was almost before the camp had even begun). To save bandwidth, bring as much software and documentation on CDs as you can, and create local repositories for storing a wiki, and uploading photos.

Useful guidance: http://bwmo.net/

Documentation

The hub of IT activity should be the server room. This is also where all network configuration will happen. Make sure to document how the network works, including all relevant IP addresses etc. As most of this documentation is crucial to the set-up and operation of the network make sure it is always available to the technical staff. Rather than having electronic documentation, it might make more sense to keep the technical details in a small notebook in the server room. Make sure everyone knows where the notebook is, and that is is not removed!

Change control is important - see Metche for a project to enhance a basic ~root/Changelog.txt

While I already have deep experience with using Free and Open Source Software and even involved in some project directly, participating in the Source Camp was unexpectedly life-changing.

The camp goes beyond the technicalities and philosophies of F/OSS. I've learned to respect and love people from all walks of life, different culture, different beliefs, but we are all the same in goal and aspirations in life. The camp gave me a bigger network - not technical but social. I've earned more than I expected from the camp. Thanks for the memories and it will never be forgotten.

My thanks also to Tactical Tech for giving us the chance to experience and work with you guys. Most especially to Dirk, our track 3 facilitator who is a real hero.

Variatio Delectat,

Jerome
http://jerome.gotangco.com

I want to thank Tachtical tech for great work they’re doing to spread the gospel of Open source especially to the developing world, we all believe that this is immense contribution to liberate developing counties to improve our economies through use of cheap and sustainable resources and F/LOSS.

My Name is Nashon Onyalo and I took part in Africa source2 in kalangala Uganda, My unselfish opinion is that the event’s experience was beyond imagination; can you for a moment think of meeting people all over the world, with different technical expertise, skills, knowledge and characters in one small beautiful beach in a remote village?

Source events are beyond description, you would probably say it’s all you would need in one box.What makes this event different to me is simply "People” I wonder how they are chosen, its one out of a million events one would wish to attend. It’s a place where you learn everything at ago from how to open a bottle of bear with a mere paper to constructing a huge cheap network or may be building your own multi-million FM station with $30.

I want to say big "kudos" to the organizers, they must be inspired by some hidden energies and the fact that they are now willing to share these energies in public is great news to everyone.

Thanks and Regards

Nashon Onyalo