HacDC Wiki - User contributions [en]

User:Drwho

2014-11-26T05:10:18Z

Drwho:

Name: Bryce A. Lynch
Handle: The Doctor [412/724/301/703]
Website: [http://drwho.virtadpt.net/ Antarctica Starts Here.]
PGP key: [http://drwho.virtadpt.net/gpgkey.txt 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1]

Likes
*Anonymity preserving technologies
*Bandwidth
*Blogging
*Books
*Chiptunes
*Cognitive liberty
*Constructive irrationality
*Cryptography
*Dancing
*Hacking
*Morphological freedom
*Music
*Neurology
*Privacy preserving technologies
*Programming
*RPGs
*Solitude
*Steampunk
*Transhumanism
*Writing

Dislikes:
*Dead batteries
*Faulty wetware
*Inferior organic components
*Stupidity
*Wasting time
*Wasting energy
*Surveillance

Projects:
*[[Byzantium | Project Byzantium]]
*Carved bone walking stick
*Hacking the [http://www.ocztechnology.com/products/ocz_peripherals/nia-neural_impulse_actuator OCZ Neural Impulse Actuator]
*RFID body jewelry
*Steampunk sonic screwdriver
*[http://zerostate.net/ The Zero State]

Notes:
*Shy. Slightly agoraphobic.
*Finally joined HacDC after four years.
*Thinks that the performance of an experiment is just as important as the results collected.
*[http://www.creativecommons.org/ Creative Commons] advocate.
*[http://eclipsephase.org Eclipse Phase] political faction: [https://secure.wikimedia.org/wikipedia/en/wiki/JASON_%28advisory_group%29 Argonaut]
*Rumored to be the illegitimate lovechild of Luna Lovegood and Wintermute.

Quotes:
*"Nothing says you can't."
*"Aw, hell."
*"Hey, ya'all, watch this!"
*"What did you say your username was again?"
*"We're now twenty minutes into the future. Unfortunately we got some ''Videodrome'' along with ''Max Headroom''."
*"I hate it when people use CamelCase in their code. It makes the statements read like Vanilla Ice lyrics."

First amateur radio contact: NA1SS (Thanks to N3FZX for the opportunity!)

[[Category:Friends]]

Items Borrowed from the HacDC Space

2013-08-14T18:41:23Z

Drwho:

''Add new entries to the top of the list!''

14 August 2013 - [[User:Drwho|The Doctor]] 
* Macbook Pro (for Byzantium development)

April 21, 2013 - [[User:Mirage335|mirage335]] 
Prusa Mendel, PLA feedstock, M3 screws, some tape, some tools. Emergency maintenance in progress, ETA return Thursday, April 24, 2013. EDIT: Returned a while ago, seems the information was lost on wiki.

April 4, 2013 - [[User:Nocko|nocko]] 
Diligent Spartan-3E Starter Board (Labeled HacDC #12). I want to see if the SUMP logic analyser HDL can be modified and installed on this board.

December 18, 2012 - [[User:Mirage335|mirage335]] 
Project Salvage components. Most should become valuable electronic test equipment at HacDC and absolutely must not be trashed. EDIT: Returned a while ago to the test cart. Connectorization of some parts (eg. mixers) still progressing.

July 21, 2012 - [[User:Mirage335|mirage335]] 
Borrowing Ham radio gear this weekend, as described in the previous struck through entry. EDIT: Returned. Awesome data obtained.

June 29, 2012 - [[User:Mirage335|mirage335]] 
<s>Borrowing Ham radio gear tomorrow. Specifically, IC-718 radio, antenna tuner, RF power meter, balun (if available), PSU, some feedline, some wire, and a measuring tape (if >12'). Will also borrow some of my own objects at the space, specifically a UPS (for its 12V battery) and a magnetic loop antenna. Leaving my name and number on the ham radio cart in case anyone needs the radio or has questions. This is exclusively for the purpose of diagnosing HacDC's ham radio issues as documented on the mailing list.</s> Postponed due to severe weather and power disruption. Radio not borrowed yet.

May 30, 2012 - [[User:Mirage335|mirage335]] 
- Ancient (20 years+) semi-working AM/FM/WB/CB radio.
Found in basement. AM function never worked, in sorry shape, needs repair, so I'm going to try repairing it as far as possible. Will be back at the space in ~2 weeks. EDIT: Returned. After mostly mechanical repairs, AM, FM, CB functions work well.

April 2012 - [[User:Tslagle]] 
- IBM Thinkpad T43 laptop from David Whiteis. Wiped, installed Windows 7 and MATLAB on it, used it for USA Science & Engineering Fest booth demo ("Mug Plot")

18:00, 29, January 2011 (PST) - [[User:Williamgibb|Williamgibb]]
- Stanford Research Systems DG535 Pulse Generator

20:30, 1314, November 2010 (PST) - [[User:Williamgibb|Williamgibb]]
- Digilent FX2 Expansion board for Spartan3E FPGA Starter Kit.

17:20, 13 July 2010 (UTC) - [[User:DLotts|DLotts]]
- One OLPC XO with charge cord. It calls itself HacDC OLPC #3.

December 15, 2009 - [[User:timball|timball]]
- one black soldering iron + stand

[[User:DLotts|DLotts]] 08:41, 29 October 2009 (UTC)
- A230 Micro Game Station with labeled problem: "Raster screen" AKA white screen of death with stripes.

June 2, 2009 - Derek Cooper - 
- Infrared night vision goggles 

June 2, 2009 - David Lotts - 
- Infrared night vision goggles (EyeClops) 

June 2, 2009 - [[User:Drwho|The Doctor]] - 
- Infrared night vision goggles 
'cause, you know, all the cool kids were doing it. 
I discovered that the unit I borrowed is flaky - after a few seconds of wearing it while powered up the display flickers and goes dead. I think that the cable leading from the power pack to the visor has a bad connection. When I get time I'll tear this one down and see if I can repair it. 

January 13, 2009 - Derek Cooper - 
- CEN-TECH Digital Multimeter (red) Item#90899 

December 22, 2008 - [[User:Myself|Nate]] - 
JC Penney component stereo cassette deck 

 Nov 13, 2008 Mac G4 usb keyboards (x2) - member28 

August 7, 2008 - [[User:Ben|Ben]] 
- Beginning Electronics book

July 25, 2008 - Q (andrew@i11industries.com) - 

June 30, 2008 - Q (andrew@i11industries.com) - 
- 1x Digital Multimeter (Yellow) 

June 19, 2008 - Richard Bewley (rbewley@gmail.com) - Not Returned / Outstanding 
- 1x Lineman's handset

June 1, 2008 - Tino (oberoc@yahoo.com) - 
Small Form Factor PCs book 

<h2>Items Returned to the HacDC Space</h2>

June 15, 2008 - Tino (oberoc@yahoo.com) - 
Small Form Factor PCs book 

July 25, 2008 - Q (andrew@i11industries.com) - 
- Reflow Station 

[[Category:Materiel]]

Notes on Soundmodem

2013-06-11T00:47:41Z

Drwho:

[[Category:Byzantium]]
[http://www.baycom.org/~tom/ham/soundmodem/ Soundmodem] emulates a hardware TNC in software, vis a vis a daemon running in userspace.

v0.18 is the latest (as of June 2013), I recommend using that. It now only depends on two things, audiofile and gtk2.

Soundmodem will either turn your soundcard into a KISS radiomodem (serial modem) or an AX.25 network interface. We're going to be using it to create AX.25 network interfaces (/sm[0-9]*/ or /ax[0-9]*/).

= Installation =

== From Source: Ubuntu Karmic and Lucid ==
<pre>
wget http://www.baycom.org/~tom/ham/soundmodem/soundmodem-0.18.tar.gz
sudo apt-get install libasound2-dev libxml2-dev libgtk2.0-dev libaudiofile-dev

tar xvzf soundmodem-0.18.tar.gz
cd soundmodem-0.18
./configure && sudo make install
sudo mkdir /etc/ax25 ## or else it won't be able to save your configurations
</pre>

Configure it by running (as root) /usr/local/bin/soundmodemconfig. It will open a window on your desktop with nothing in it. Click File, New, Configuration. Give your configuration a name (I used 'sm0').

== Apt-Get: Ubuntu Lucid and Up ==
Gets you version 0.13 on Lucid, and 0.15 on Maverick and Natty

As root do the following
<pre>
apt-get install soundmodem
mkdir /etc/ax25
soundmodemconfig /etc/ax25/soundmodem.conf #see below for configs
soundmodem /etc/ax25/soundmodem.conf -R -M >/dev/null 2>/dev/null& #this makes an awful noise when it works
</pre>

==On Fedora==
???

==Arch Linux==
<pre>
sudo packer -S soundmodem ax25-apps ax25-tools
</pre>
==On Slackware (current?)==
<pre>
wget http://www.baycom.org/~tom/ham/soundmodem/soundmodem-0.18.tar.gz

if [[ "$ARCH" == "x86_64" ]] ;then
LIBDIRSUFFIX="64"
fi
mkdir soundmodem-0.18-pkg

tar xvzf soundmodem-0.18.tar.gz
cd soundmodem-0.18
./configure --prefix=/usr --libdir=/usr/lib${LIBDIRSUFFIX}
sudo make install DESTDIR=../soundmodem-0.18-pkg
cd ../soundmodem-0.18-pkg
makepkg -l y -c n /tmp/soundmodem-0.18-$ARCH-1_local.tgz
sudo mkdir /etc/ax25 ## or else it won't be able to save your configurations
</pre>

= Configuration =
== IO Tab ==
On the I/O tab, choose your sound driver (out of soundcard, file, simulation, and alsa, I picked alsa). You'll have to play around with the value of the ALSA Audio Driver field to get one that works. On Windbringer, I used plughw:0,0. Check half duplex for now. Leave the Capture Channel field set to 'mono'. Set the PTT Driver field to 'none' so Soundmodem will assume VOX.

Haxwithaxe, Dan, and Mirage are working on PTT circuits for our radios. It hasn't been an easy process because the Baofengs seem to kick out just enough EMI to make the circuits act weird as-is. We have a few [https://drwho.virtadpt.net/archive/2013/05/31/project-byzantium-milestone-three-in-progress partial solutions] at this time.

== Channel Access Tab ==
Don't change the settings on the Channel Access tab.

== Channel 0 ==
Right below the name of your configuration in the tree you will see a new entry, Channel 0. If you select it you'll be presented with three new tabs on the right.

=== Modulator Tab ===
The possible values for the Mode selector are Off, fsk, afsk, pam, psk, and newqpsk. I picked fsk because it grants the highest effective bit rate (9600 bps). The values for Frequency 0 (1200), Frequency 1 (2200), and Filter (df9ic/g3ruh) were left set to defaults. Leave Differential Encoding checked.

=== Demodulator Tab ===
On the Demodulator tab (which governs decoding audio signals into bits) the options are much the same because they match the modulation scheme by default. This is what we want.

=== Packet IO Tab ===
On the Packet IO tab, the network/non-serial side of soundmodem is configured. Pick an IP address, netmask, and broadcast addres for a regular network interface. There are two options in the Mode selector, KISS and MKISS. I went with the default (MKISS). The network settings we used are:
* IP address: 44.x.y.z (pick something)
* Netmask: 255.0.0.0
* Broadcast: 44.255.255.255

We're using the [https://en.wikipedia.org/wiki/AMPRNet AMPRnet] IP block which was set aside for amateur radio use. We should probably use the private subnet of that, 44.128/16 because it's akin to the RFC-1918 subnets and is used for experimentation in this area.

=== Audio settings ===
From alsamixer:
* Master: 100
* Headphone: 100
* Speaker: 55
* PCM: 55
* Mic: 55
* Mic Boost: 0

If these settings are any more quiet, the radios' PTT circuits won't trip.

We also suggest setting the volume to between 60% and 100%.

= Theory =
When running the soundmodem utility ('''soundmodem /etc/ax25/soundmodem.conf &'''), the daemon configures the sound card to send and receive bitstreams encoded as audio through the jacks in the soundcard. It allocates a virtual network interface (sm0) which has a callsign associated with it which serves as the MAC address (relevant for ham radio, not so much for other applications) as well as an IP address, network mask, and broadcast address. The idea is that whatever packets are sent through that network interface will be transparently converted into sound and transmitted using whatever device is connected to the headphone and microphone jacks of the computer. Conversely, any data received by the broadcast device (ham radio, laser, etc) is demodulated into bits, encapsulated into network frames, and made available to the OS.

In theory, it's just like a regular network connection, with all of the dynamics you'd expect from IPv4. This means that we can do things like IP multicasting over these links. We discovered, through analyzing the code for a utility called [http://www.w1hkj.com/EasyPacket.html easypacket] that the Linux kernel treats AX.25 interfaces as real network interfaces, so much so that it sets up some iptables rules to prevent arbitrary traffic from being routed over them because there isn't much bandwidth. We'll have to add that to our rules. We tried setting up IPv6 addressing on some AX.25 interfaces and weren't able to.

= Diagnostics, Testing, and Configuration =
As root:

Note: you can connect two computers mic->headset to help check things are working before they hit the radio. ping and netcat (with -u option) are decent options for quick checks on rough sanity (the config not you :P). Here's how we did it:
* Run a UDP server on one machine: '''ncat -n -l -v -u 5000'''
** -n == No DNS resolution
** -l == Listen for incoming connections (server mode)
** -v == Verbose
** -u == UDP
** 5000 == port number to listen on
* Connect to it from the other machine: '''ncat -u 44.x.y.z 5000'''
* Type something. If it worked you'll see whatever the client typed showing up in the terminal on the server.
* Run a TCP server on one machine: '''ncat -n -l -v 8080'''
* Do the same thing for TCP (i.e., no -u options)

How to use '''listen''' from the ax25-apps distribution:
* '''listen -a -c -r -t'''
** -a == Monitor outgoing frames as well as incoming ones
** -c == Colorize output
** -r == Display in a human-readable format
** -t == Timestamp every frame displayed

Keep the volume low at first to avoid accidental overload of the other machine. 50% for every channel is a good place to start.

Here's where you debug your configuration. It's going to take some flipping back and forth between tabs to get right the first time.

soundmodemconfig now pops open windows with error output.

The Diagnostics menu only appears when you have a channel (Channel 0) highlighted.

The first option is Scope, for oscilloscope. To get a test signal, click the PTT button (make sure your speakers are turned down!)

The second option is Spectrum, for spectrum analyzer of the signal being send to the sound card. To get a test signal, click the PTT button (again, make sure your speakers are turned down!)

The third option, Modem, dumps the raw bitstreams that your soundcard-emulating-a-modem is sending and receiving. Seeing strings of bits (even when disconnected) means that you have probably configured soundmodem correctly.

I do not know what the AO40-P3D option does. (It's an amateur satellite protocol thingy. We don't need it?)

To save your config file, use the File, Quit option. It'll save it automagically to /etc/ax25/soundmodem.conf.

=So, how is this supposed to work, anyway?=

==Assumptions==
* Assume that you have a computer running Linux (or Windows if you dare) and soundmodem (aka '''PC'''). That has a pair of audio i/o:
** headphone ('''PC speaker''')
** microphone/line in ('''PC mic''')
* Assume that soundmodem is configured correctly.
* Assume that you have a transceiver (aka '''radio''') - a black box that:
** That can receive and broadcast signals
** Has a pair of audio i/o:
*** speaker/headphone (aka '''radio speaker''')
*** microphone (aka '''radio mic''')
* Assume a method of PTT as described below is setup.

===PTT===
Further assume that there is a mechanism to switch the radio from receive to transmit. Known here as '''PTT circuit''' for the purposes of brevity. This may be:
* the built in VOX circuit
* an external VOX circuit
* or a serial PTT circuit
Whenever a signal is sent to the PTT circuit, the black box stops receiving and transmits whatever signal it gets through its microphone jack.
Alternatively two radios one transmitting only and one receiving only (possibly on different channels) such that there is no need for drivers or a switching mechanism.

===Hook-up===
* Connect radio speaker to PC mic.
* Then connect PC speaker to radio mic.
* If applicable: Attach the PTT circuit as appropriate.

Whenever a packet (say an ICMP4 echo request) is transmitted to the IP address of the AX.25 interface on PC, it is converted by soundmodem into modulated sound (aka '''audio data''') which goes out through PC speaker to the radio mic. The PTT circuit engages and the radio stops receiving and begins transmitting. The radio receives the audio data and transmits it. When the transmission is done the PTT circuit disengages and the radio stops transmitting and begins receiving. Conversely, whenever the radio receives a signal, it converts it into audio data, which then goes through radio speaker into PC mic. After the audio data is received by the PC soundmodem demodulates it into bits, packages them into IP packets, and drops it into the networking subsystem of the kernel.

By using soundmodem we'll be setting up an AX.25 network interface that, insofar as we're concerned, acts just like an ethernet interface (just crazy slow, 9600bps at best 1200bps likely). We can use ifconfig, route, and ip to configure it, IPtables to filter traffic, and /proc/net/ipv4/* to tweak it (and set up packet forwarding). IPv6 is not currently supported on AX.25 in the linux kernel (~v3.8.x).

= Other resources =
*[http://www.febo.com/packet/layer-one/transmit.html Setting your TNC's audio drive level] (In other words, fix your volume!)
*[http://www.qbjnet.com/packet.html#soundmodem Using soundmodem with AX.25]
**Are we really going to bother with AX.25?
***AX.25 is used to transport TCP/IP over not-Ethernet. It doesn't look that difficult to configure.
***What about using PPP?
**Has a few things about building PTT circuits.
**Has some notes on how to tune your laptop's sound levels for optimal operation.
*[https://wiki.archlinux.org/index.php/Amateur_Radio Amateur radio nodes] in the [https://wiki.archlinux.org/ Arch Linux wiki]
* Alternatives
** hardware [[HAM_TNC|TNC]]

Notes on Soundmodem

2013-06-10T17:26:13Z

Drwho: /* Diagnostics, Testing, and Configuration */

[[Category:Byzantium]]
[http://www.baycom.org/~tom/ham/soundmodem/ Soundmodem] emulates a hardware TNC in software, vis a vis a daemon running in userspace.

v0.18 is the latest (as of June 2013), I recommend using that. It now only depends on two things, audiofile and gtk2.

Soundmodem will either turn your soundcard into a KISS radiomodem (serial modem) or an AX.25 network interface. We're going to be using it to create AX.25 network interfaces (/sm[0-9]*/ or /ax[0-9]*/).

= Installation =

== From Source: Ubuntu Karmic and Lucid ==
<pre>
wget http://www.baycom.org/~tom/ham/soundmodem/soundmodem-0.18.tar.gz
sudo apt-get install libasound2-dev libxml2-dev libgtk2.0-dev libaudiofile-dev

tar xvzf soundmodem-0.18.tar.gz
cd soundmodem-0.18
./configure && sudo make install
sudo mkdir /etc/ax25 ## or else it won't be able to save your configurations
</pre>

Configure it by running (as root) /usr/local/bin/soundmodemconfig. It will open a window on your desktop with nothing in it. Click File, New, Configuration. Give your configuration a name (I used 'sm0').

== Apt-Get: Ubuntu Lucid and Up ==
Gets you version 0.13 on Lucid, and 0.15 on Maverick and Natty

As root do the following
<pre>
apt-get install soundmodem
mkdir /etc/ax25
soundmodemconfig /etc/ax25/soundmodem.conf #see below for configs
soundmodem /etc/ax25/soundmodem.conf -R -M >/dev/null 2>/dev/null& #this makes an awful noise when it works
</pre>

==On Fedora==
???

==Arch Linux==
<pre>
sudo packer -S soundmodem ax25-apps ax25-tools
</pre>
==On Slackware (current?)==
<pre>
wget http://www.baycom.org/~tom/ham/soundmodem/soundmodem-0.18.tar.gz

if [[ "$ARCH" == "x86_64" ]] ;then
LIBDIRSUFFIX="64"
fi
mkdir soundmodem-0.18-pkg

tar xvzf soundmodem-0.18.tar.gz
cd soundmodem-0.18
./configure --prefix=/usr --libdir=/usr/lib${LIBDIRSUFFIX}
sudo make install DESTDIR=../soundmodem-0.18-pkg
cd ../soundmodem-0.18-pkg
makepkg -l y -c n /tmp/soundmodem-0.18-$ARCH-1_local.tgz
sudo mkdir /etc/ax25 ## or else it won't be able to save your configurations
</pre>

= Configuration =
== IO Tab ==
On the I/O tab, choose your sound driver (out of soundcard, file, simulation, and alsa, I picked alsa). You'll have to play around with the value of the ALSA Audio Driver field to get one that works. On Windbringer, I used plughw:0,0. Check half duplex for now. Leave the Capture Channel field set to 'mono'. I don't know what to set the PTT Driver field to yet, so I left it set to 'none'. My radios do VOX so I've been experimenting with that.

Haxwithaxe, Dan, and Mirage are working on PTT circuits for our radios. It hasn't been an easy process because the Baofengs seem to kick out just enough EMI to make the circuits act weird as-is. We have a few [https://drwho.virtadpt.net/archive/2013/05/31/project-byzantium-milestone-three-in-progress partial solutions] at this time.

== Channel Access Tab ==
Don't change the settings on the Channel Access tab.

== Channel 0 ==
Right below the name of your configuration in the tree you will see a new entry, Channel 0. If you select it you'll be presented with three new tabs on the right.

=== Modulator Tab ===
The possible values for the Mode selector are Off, fsk, afsk, pam, psk, and newqpsk. I picked fsk because it grants the highest effective bit rate (9600 bps). The values for Frequency 0 (1200), Frequency 1 (2200), and Filter (df9ic/g3ruh) were left set to defaults. Leave Differential Encoding checked.

=== Demodulator Tab ===
On the Demodulator tab (which governs decoding audio signals into bits) the options are much the same because they match the modulation scheme by default. This is what we want.

=== Packet IO Tab ===
On the Packet IO tab, the network/non-serial side of soundmodem is configured. Pick an IP address, netmask, and broadcast addres for a regular network interface. There are two options in the Mode selector, KISS and MKISS. I went with the default (MKISS). The network settings we used are:
* IP address: 44.x.y.z (pick something)
* Netmask: 255.0.0.0
* Broadcast: 44.255.255.255

We're using the [https://en.wikipedia.org/wiki/AMPRNet AMPRnet] IP block which was set aside for amateur radio use. We should probably use the private subnet of that, 44.128/16 because it's akin to the RFC-1918 subnets and is used for experimentation in this area.

=== Audio settings ===
From alsamixer:
* Master: 13
* Headphone: 100
* Speaker: 94
* PCM: 76
* Mic: 37
* Mic Boost: 0

= Theory =
When running the soundmodem utility ('''soundmodem /etc/ax25/soundmodem.conf &'''), the daemon configures the sound card to send and receive bitstreams encoded as audio through the jacks in the soundcard. It allocates a virtual network interface (sm0) which has a callsign associated with it which serves as the MAC address (relevant for ham radio, not so much for other applications) as well as an IP address, network mask, and broadcast address. The idea is that whatever packets are sent through that network interface will be transparently converted into sound and transmitted using whatever device is connected to the headphone and microphone jacks of the computer. Conversely, any data received by the broadcast device (ham radio, laser, etc) is demodulated into bits, encapsulated into network frames, and made available to the OS.

In theory, it's just like a regular network connection, with all of the dynamics you'd expect from IPv4. This means that we can do things like IP multicasting over these links. We discovered, through analyzing the code for a utility called [http://www.w1hkj.com/EasyPacket.html easypacket] that the Linux kernel treats AX.25 interfaces as real network interfaces, so much so that it sets up some iptables rules to prevent arbitrary traffic from being routed over them because there isn't much bandwidth. We'll have to add that to our rules. We tried setting up IPv6 addressing on some AX.25 interfaces and weren't able to.

= Diagnostics, Testing, and Configuration =
As root:

Note: you can connect two computers mic->headset to help check things are working before they hit the radio. ping and netcat (with -u option) are decent options for quick checks on rough sanity (the config not you :P). Here's how we did it:
* Run a UDP server on one machine: '''ncat -n -l -v -u 5000'''
** -n == No DNS resolution
** -l == Listen for incoming connections (server mode)
** -v == Verbose
** -u == UDP
** 5000 == port number to listen on
* Connect to it from the other machine: '''ncat -u 44.x.y.z 5000'''
* Type something. If it worked you'll see whatever the client typed showing up in the terminal on the server.
* Run a TCP server on one machine: '''ncat -n -l -v 8080'''
* Do the same thing for TCP (i.e., no -u options)

How to use '''listen''' from the ax25-apps distribution:
* '''listen -a -c -r -t'''
** -a == Monitor outgoing frames as well as incoming ones
** -c == Colorize output
** -r == Display in a human-readable format
** -t == Timestamp every frame displayed

Keep the volume low at first to avoid accidental overload of the other machine. 50% for every channel is a good place to start.

Here's where you debug your configuration. It's going to take some flipping back and forth between tabs to get right the first time.

soundmodemconfig now pops open windows with error output.

The Diagnostics menu only appears when you have a channel (Channel 0) highlighted.

The first option is Scope, for oscilloscope. To get a test signal, click the PTT button (make sure your speakers are turned down!)

The second option is Spectrum, for spectrum analyzer of the signal being send to the sound card. To get a test signal, click the PTT button (again, make sure your speakers are turned down!)

The third option, Modem, dumps the raw bitstreams that your soundcard-emulating-a-modem is sending and receiving. Seeing strings of bits (even when disconnected) means that you have probably configured soundmodem correctly.

I do not know what the AO40-P3D option does. (It's an amateur satellite protocol thingy. We don't need it?)

To save your config file, use the File, Quit option. It'll save it automagically to /etc/ax25/soundmodem.conf.

=So, how is this supposed to work, anyway?=

==Assumptions==
* Assume that you have a computer running Linux (or Windows if you dare) and soundmodem (aka '''PC'''). That has a pair of audio i/o:
** headphone ('''PC speaker''')
** microphone/line in ('''PC mic''')
* Assume that soundmodem is configured correctly.
* Assume that you have a transceiver (aka '''radio''') - a black box that:
** That can receive and broadcast signals
** Has a pair of audio i/o:
*** speaker/headphone (aka '''radio speaker''')
*** microphone (aka '''radio mic''')
* Assume a method of PTT as described below is setup.

===PTT===
Further assume that there is a mechanism to switch the radio from receive to transmit. Known here as '''PTT circuit''' for the purposes of brevity. This may be:
* the built in VOX circuit
* an external VOX circuit
* or a serial PTT circuit
Whenever a signal is sent to the PTT circuit, the black box stops receiving and transmits whatever signal it gets through its microphone jack.
Alternatively two radios one transmitting only and one receiving only (possibly on different channels) such that there is no need for drivers or a switching mechanism.

===Hook-up===
* Connect radio speaker to PC mic.
* Then connect PC speaker to radio mic.
* If applicable: Attach the PTT circuit as appropriate.

Whenever a packet (say an ICMP4 echo request) is transmitted to the IP address of the AX.25 interface on PC, it is converted by soundmodem into modulated sound (aka '''audio data''') which goes out through PC speaker to the radio mic. The PTT circuit engages and the radio stops receiving and begins transmitting. The radio receives the audio data and transmits it. When the transmission is done the PTT circuit disengages and the radio stops transmitting and begins receiving. Conversely, whenever the radio receives a signal, it converts it into audio data, which then goes through radio speaker into PC mic. After the audio data is received by the PC soundmodem demodulates it into bits, packages them into IP packets, and drops it into the networking subsystem of the kernel.

By using soundmodem we'll be setting up an AX.25 network interface that, insofar as we're concerned, acts just like an ethernet interface (just crazy slow, 9600bps at best 1200bps likely). We can use ifconfig, route, and ip to configure it, IPtables to filter traffic, and /proc/net/ipv4/* to tweak it (and set up packet forwarding). IPv6 is not currently supported on AX.25 in the linux kernel (~v3.8.x).

= Other resources =
*[http://www.febo.com/packet/layer-one/transmit.html Setting your TNC's audio drive level] (In other words, fix your volume!)
*[http://www.qbjnet.com/packet.html#soundmodem Using soundmodem with AX.25]
**Are we really going to bother with AX.25?
***AX.25 is used to transport TCP/IP over not-Ethernet. It doesn't look that difficult to configure.
***What about using PPP?
**Has a few things about building PTT circuits.
**Has some notes on how to tune your laptop's sound levels for optimal operation.
*[https://wiki.archlinux.org/index.php/Amateur_Radio Amateur radio nodes] in the [https://wiki.archlinux.org/ Arch Linux wiki]
* Alternatives
** hardware [[HAM_TNC|TNC]]

Notes on Soundmodem

2013-06-02T21:42:51Z

Drwho:

[[Category:Byzantium]]
[http://www.baycom.org/~tom/ham/soundmodem/ Soundmodem] emulates a hardware modulator/demodulator in software, vis a vis a daemon running in userspace.

v0.18 is the latest, I recommend using that. It now only depends on two things, audiofile and gtk2.

Soundmodem will either turn your soundcard into a KISS radiomodem or an AX.25 network interface. We're going to be using it to create AX.25 network interfaces (/sm[0-9]*/).

= Installation =

== From Source: Ubuntu Karmic and Lucid ==
<pre>
wget http://www.baycom.org/~tom/ham/soundmodem/soundmodem-0.18.tar.gz
sudo apt-get install libasound2-dev libxml2-dev libgtk2.0-dev libaudiofile-dev

tar xvzf soundmodem-0.18.tar.gz
cd soundmodem-0.18
./configure && sudo make install
sudo mkdir /etc/ax25 ## or else it won't be able to save your configurations
</pre>

Configure it by running (as root) /usr/local/bin/soundmodemconfig. It will open a window on your desktop with nothing in it. Click File, New, Configuration. Give your configuration a name (I used 'sm0').

== Apt-Get: Ubuntu Lucid and Up ==
Gets you version 0.13 on Lucid, and 0.15 on Maverick and Natty

As root do the following
<pre>
apt-get install soundmodem
mkdir /etc/ax25
soundmodemconfig /etc/ax25/soundmodem.conf #see below for configs
soundmodem /etc/ax25/soundmodem.conf -R -M >/dev/null 2>/dev/null& #this makes an awful noise when it works
</pre>

==On Fedora==
???

==Arch Linux==
<pre>
sudo packer -S soundmodem ax25-apps ax25-tools
</pre>

= Configuration =
== IO Tab ==
On the I/O tab, choose your sound driver (out of soundcard, file, simulation, and alsa, I picked alsa). You'll have to play around with the value of the ALSA Audio Driver field to get one that works. On Windbringer, I used plughw:0,0. Check half duplex for now. Leave the Capture Channel field set to 'mono'. I don't know what to set the PTT Driver field to yet, so I left it set to 'none'. My radios do VOX so I've been experimenting with that.

Haxwithaxe, Dan, and Mirage are working on PTT circuits for our radios. It hasn't been an easy process because the Baofengs seem to kick out just enough EMI to make the circuits act weird as-is. We have a few [https://drwho.virtadpt.net/archive/2013/05/31/project-byzantium-milestone-three-in-progress partial solutions] at this time.

== Channel Access Tab ==
Don't change the settings on the Channel Access tab.

== Channel 0 ==
Right below the name of your configuration in the tree you will see a new entry, Channel 0. If you select it you'll be presented with three new tabs on the right.

=== Modulator Tab ===
The possible values for the Mode selector are Off, fsk, afsk, pam, psk, and newqpsk. I picked fsk because it grants the highest effective bit rate (9600 bps). The values for Frequency 0 (1200), Frequency 1 (2200), and Filter (df9ic/g3ruh) were left set to defaults. Leave Differential Encoding checked.

=== Demodulator Tab ===
On the Demodulator tab (which governs decoding audio signals into bits) the options are much the same because they match the modulation scheme by default. This is what we want.

=== Packet IO Tab ===
On the Packet IO tab, the network/non-serial side of soundmodem is configured. Pick an IP address, netmask, and broadcast addres for a regular network interface. There are two options in the Mode selector, KISS and MKISS. I went with the default (MKISS). The network settings we used are:
* IP address: 44.x.y.z (pick something)
* Netmask: 255.0.0.0
* Broadcast: 44.255.255.255

We're using the [https://en.wikipedia.org/wiki/AMPRNet AMPRnet] IP block which was set aside for amateur radio use. We should probably use the private subnet of that, 44.128/16 because it's akin to the RFC-1918 subnets and is used for experimentation in this area.

=== Audio settings ===
From alsamixer:
* Master: 13
* Headphone: 100
* Speaker: 94
* PCM: 76
* Mic: 37
* Mic Boost: 0

= Theory =
When running the soundmodem utility ('''soundmodem /etc/ax25/soundmodem.conf &'''), the daemon configures the sound card to send and receive bitstreams encoded as audio through the jacks in the soundcard. It allocates a virtual network interface (sm0) which has a callsign associated with it which serves as the MAC address (relevant for ham radio, not so much for other applications) as well as an IP address, network mask, and broadcast address. The idea is that whatever packets are sent through that network interface will be transparently converted into sound and transmitted using whatever device is connected to the headphone and microphone jacks of the computer. Conversely, any data received by the broadcast device (ham radio, laser, etc) is demodulated into bits, encapsulated into network frames, and made available to the OS.

In theory, it's just like a regular network connection, with all of the dynamics you'd expect from IPv4. This means that we can do things like IP multicasting over these links. We discovered, through analyzing the code for a utility called [http://www.w1hkj.com/EasyPacket.html easypacket] that the Linux kernel treats AX.25 interfaces as real network interfaces, so much so that it sets up some iptables rules to prevent arbitrary traffic from being routed over them because there isn't much bandwidth. We'll have to add that to our rules. We tried setting up IPv6 addressing on some AX.25 interfaces and weren't able to.

= Diagnostics, Testing, and Configuration =
Here's where you debug your configuration. It's going to take some flipping back and forth between tabs to get right the first time.

soundmodemconfig now pops open windows with error output.

The Diagnostics menu only appears when you have a channel (Channel 0) highlighted.

The first option is Scope, for oscilloscope. To get a test signal, click the PTT button (make sure your speakers are turned down!)

The second option is Spectrum, for spectrum analyzer of the signal being send to the sound card. To get a test signal, click the PTT button (again, make sure your speakers are turned down!)

The third option, Modem, dumps the raw bitstreams that your soundcard-emulating-a-modem is sending and receiving. Seeing strings of bits (even when disconnected) means that you have probably configured soundmodem correctly.

I do not know what the AO40-P3D option does. (It's an amateur satellite protocol thingy. We don't need it?)

To save your config file, use the File, Quit option. It'll save it automagically to /etc/ax25/soundmodem.conf.

= So, how is this supposed to work, anyway? =
Assume that you have a laptop running Linux (or Windows if you dare) and soundmodem. Assume that soundmodem is configured correctly. Assume that you have a transceiver - a black box that has a pair of audio jacks (speaker and microphone) on the back, can receive signals, and can broadcast signals.

Further assume that there is a third jack on the black box which plugs into the USB port of a computer. Whenever a signal is sent to that jack, the black box stops receiving and transmits whatever signal it gets through its microphone jack. Alternatively two radios one transmitting only and one receiving only (possibly on different channels) such that there is no need for drivers or a switching mechanism.

You'd connect the speaker jack on the black box into the microphone jack on your laptop. You would then connect the headphone jack of your laptop into the microphone jack of the black box. Then plug the push-to-talk USB jack of the black box into a USB port on your laptop.

Whenever a packet (say an ICMP4 echo request) is transmitted to the IP address of device sm0 on your laptop, it is converted by the soundmodem daemon into modulated sound which goes out through the headphone jack to the black box. The push-to-talk circuit engages and the black box stops receiving and goes into transmit mode. The black box receives that modulated static and broadcasts it. When the broadcast is done the PTT disengages and the black box goes back into receive mode. Conversely, whenever the black box picks up a signal it converts it into modulated static, which then goes out through its speaker jack into the microphone jack of your laptop. After the signal hits the mic jack, the soundmodem daemon demodulates the static into bits, packages them into an IP packet, and drops it into the networking subsystem of the kernel.

By using soundmodem we'll be setting up a virtual AX.25 network interface that, insofar as we're concerned, acts just like an ethernet interface. We can use ifconfig, route, and ip to configure it, IPtables to filter traffic, and /proc/net/ipv4/* to tweak it (and set up packet forwarding).

= Other resources =
*[http://www.febo.com/packet/layer-one/transmit.html Setting your TNC's audio drive level] (In other words, fix your volume!)
*[http://www.qbjnet.com/packet.html#soundmodem Using soundmodem with AX.25]
**Are we really going to bother with AX.25?
***AX.25 is used to transport TCP/IP over not-Ethernet. It doesn't look that difficult to configure.
***What about using PPP?
**Has a few things about building PTT circuits.
**Has some notes on how to tune your laptop's sound levels for optimal operation.
*[https://wiki.archlinux.org/index.php/Amateur_Radio Amateur radio nodes] in the [https://wiki.archlinux.org/ Arch Linux wiki]

Notes on Soundmodem

2013-06-02T18:25:18Z

Drwho:

[[Category:Byzantium]]
[http://www.baycom.org/~tom/ham/soundmodem/ Soundmodem] emulates a hardware modulator/demodulator in software, vis a vis a daemon running in userspace.

v0.18 is the latest, I recommend using that. It now only depends on two things, audiofile and gtk2.

Soundmodem will either turn your soundcard into a KISS radiomodem or an AX.25 network interface. We're going to be using it to create AX.25 network interfaces (/sm[0-9]*/).

= Installation =

== From Source: Ubuntu Karmic and Lucid ==
<pre>
wget http://www.baycom.org/~tom/ham/soundmodem/soundmodem-0.18.tar.gz
sudo apt-get install libasound2-dev libxml2-dev libgtk2.0-dev libaudiofile-dev

tar xvzf soundmodem-0.18.tar.gz
cd soundmodem-0.18
./configure && sudo make install
sudo mkdir /etc/ax25 ## or else it won't be able to save your configurations
</pre>

Configure it by running (as root) /usr/local/bin/soundmodemconfig. It will open a window on your desktop with nothing in it. Click File, New, Configuration. Give your configuration a name (I used 'sm0').

== Apt-Get: Ubuntu Lucid and Up ==
Gets you version 0.13 on Lucid, and 0.15 on Maverick and Natty

As root do the following
<pre>
apt-get install soundmodem
mkdir /etc/ax25
soundmodemconfig /etc/ax25/soundmodem.conf #see below for configs
soundmodem /etc/ax25/soundmodem.conf -R -M >/dev/null 2>/dev/null& #this makes an awful noise when it works
</pre>

==On Fedora==
???

==Arch Linux==
<pre>
sudo packer -S soundmodem ax25-apps ax25-tools
</pre>

= Configuration =
== IO Tab ==
On the I/O tab, choose your sound driver (out of soundcard, file, simulation, and alsa, I picked alsa). You'll have to play around with the value of the ALSA Audio Driver field to get one that works. On Windbringer, I used plughw:0,0. Check half duplex for now. Leave the Capture Channel field set to 'mono'. I don't know what to set the PTT Driver field to yet, so I left it set to 'none'. My radios do VOX so I've been experimenting with that.

Haxwithaxe, Dan, and Mirage are working on PTT circuits for our radios. It hasn't been an easy process because the Baofengs seem to kick out just enough EMI to make the circuits act weird as-is. We have a few [https://drwho.virtadpt.net/archive/2013/05/31/project-byzantium-milestone-three-in-progress partial solutions] at this time.

== Channel Access Tab ==
Don't change the settings on the Channel Access tab.

== Channel 0 ==
Right below the name of your configuration in the tree you will see a new entry, Channel 0. If you select it you'll be presented with three new tabs on the right.

=== Modulator Tab ===
The possible values for the Mode selector are Off, fsk, afsk, pam, psk, and newqpsk. I picked fsk because it grants the highest effective bit rate (9600 bps). The values for Frequency 0 (1200), Frequency 1 (2200), and Filter (df9ic/g3ruh) were left set to defaults. Leave Differential Encoding checked.

=== Demodulator Tab ===
On the Demodulator tab (which governs decoding audio signals into bits) the options are much the same because they match the modulation scheme by default. This is what we want.

=== Packet IO Tab ===
On the Packet IO tab, the network/non-serial side of soundmodem is configured. Pick an IP address, netmask, and broadcast addres for a regular network interface. There are two options in the Mode selector, KISS and MKISS. I went with the default (MKISS). The network settings we used are:
* IP address: 44.x.y.z (pick something)
* Netmask: 255.0.0.0
* Broadcast: 44.255.255.255

We're using the [https://en.wikipedia.org/wiki/AMPRNet AMPRnet] IP block which was set aside for amateur radio use. We should probably use the private subnet of that, 44.128/16 because it's akin to the RFC-1918 subnets and is used for experimentation in this area.

= Theory =
When running the soundmodem utility ('''soundmodem /etc/ax25/soundmodem.conf &'''), the daemon configures the sound card to send and receive bitstreams encoded as audio through the jacks in the soundcard. It allocates a virtual network interface (sm0) which has a callsign associated with it which serves as the MAC address (relevant for ham radio, not so much for other applications) as well as an IP address, network mask, and broadcast address. The idea is that whatever packets are sent through that network interface will be transparently converted into sound and transmitted using whatever device is connected to the headphone and microphone jacks of the computer. Conversely, any data received by the broadcast device (ham radio, laser, etc) is demodulated into bits, encapsulated into network frames, and made available to the OS.

In theory, it's just like a regular network connection, with all of the dynamics you'd expect from IPv4. This means that we can do things like IP multicasting over these links. We discovered, through analyzing the code for a utility called [http://www.w1hkj.com/EasyPacket.html easypacket] that the Linux kernel treats AX.25 interfaces as real network interfaces, so much so that it sets up some iptables rules to prevent arbitrary traffic from being routed over them because there isn't much bandwidth. We'll have to add that to our rules. We tried setting up IPv6 addressing on some AX.25 interfaces and weren't able to.

= Diagnostics, Testing, and Configuration =
Here's where you debug your configuration. It's going to take some flipping back and forth between tabs to get right the first time.

soundmodemconfig now pops open windows with error output.

The Diagnostics menu only appears when you have a channel (Channel 0) highlighted.

The first option is Scope, for oscilloscope. To get a test signal, click the PTT button (make sure your speakers are turned down!)

The second option is Spectrum, for spectrum analyzer of the signal being send to the sound card. To get a test signal, click the PTT button (again, make sure your speakers are turned down!)

The third option, Modem, dumps the raw bitstreams that your soundcard-emulating-a-modem is sending and receiving. Seeing strings of bits (even when disconnected) means that you have probably configured soundmodem correctly.

I do not know what the AO40-P3D option does. (It's an amateur satellite protocol thingy. We don't need it?)

To save your config file, use the File, Quit option. It'll save it automagically to /etc/ax25/soundmodem.conf.

= So, how is this supposed to work, anyway? =
Assume that you have a laptop running Linux (or Windows if you dare) and soundmodem. Assume that soundmodem is configured correctly. Assume that you have a transceiver - a black box that has a pair of audio jacks (speaker and microphone) on the back, can receive signals, and can broadcast signals.

Further assume that there is a third jack on the black box which plugs into the USB port of a computer. Whenever a signal is sent to that jack, the black box stops receiving and transmits whatever signal it gets through its microphone jack. Alternatively two radios one transmitting only and one receiving only (possibly on different channels) such that there is no need for drivers or a switching mechanism.

You'd connect the speaker jack on the black box into the microphone jack on your laptop. You would then connect the headphone jack of your laptop into the microphone jack of the black box. Then plug the push-to-talk USB jack of the black box into a USB port on your laptop.

Whenever a packet (say an ICMP4 echo request) is transmitted to the IP address of device sm0 on your laptop, it is converted by the soundmodem daemon into modulated sound which goes out through the headphone jack to the black box. The push-to-talk circuit engages and the black box stops receiving and goes into transmit mode. The black box receives that modulated static and broadcasts it. When the broadcast is done the PTT disengages and the black box goes back into receive mode. Conversely, whenever the black box picks up a signal it converts it into modulated static, which then goes out through its speaker jack into the microphone jack of your laptop. After the signal hits the mic jack, the soundmodem daemon demodulates the static into bits, packages them into an IP packet, and drops it into the networking subsystem of the kernel.

By using soundmodem we'll be setting up a virtual AX.25 network interface that, insofar as we're concerned, acts just like an ethernet interface. We can use ifconfig, route, and ip to configure it, IPtables to filter traffic, and /proc/net/ipv4/* to tweak it (and set up packet forwarding).

= Other resources =
*[http://www.febo.com/packet/layer-one/transmit.html Setting your TNC's audio drive level] (In other words, fix your volume!)
*[http://www.qbjnet.com/packet.html#soundmodem Using soundmodem with AX.25]
**Are we really going to bother with AX.25?
***AX.25 is used to transport TCP/IP over not-Ethernet. It doesn't look that difficult to configure.
***What about using PPP?
**Has a few things about building PTT circuits.
**Has some notes on how to tune your laptop's sound levels for optimal operation.
*[https://wiki.archlinux.org/index.php/Amateur_Radio Amateur radio nodes] in the [https://wiki.archlinux.org/ Arch Linux wiki]

Anti-Harassment Policy

2013-03-13T00:57:48Z

Drwho:

''The policies below are proposals that we hope to have in a form that can be approved by member vote at the 2013 annual meeting. Discussion is encouraged, particularly on the members@hacdc.org mailing list.''

== Proposal 1 - Katie ==
''This anti-harassment policy is based on [http://geekfeminism.wikia.com/wiki/Conference_anti-harassment the example policy from the Geek Feminism wiki], created by the Ada Initiative and other volunteers.''

HacDC is dedicated to being a harassment-free hackerspace for everyone. We do not tolerate harassment of members or visitors in any form.

Harassment includes but is not limited to offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, or religion; sexual images in public spaces; deliberate intimidation, stalking, following, harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; unwelcome sexual attention; or violation of any applicable laws. Members and visitors asked to stop any harassing behavior are expected to comply immediately.

If a member or visitor engages in harassing behavior, the board of directors or event organizer may take any action they deem appropriate, including warning the offender or expulsion from the space or event with no refund. Members violating these rules may be subject to termination of their HacDC membership. If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of the board of directors or the event organizer immediately.

Members of the board of directors and event organizers will happily help members and visitors contact building security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe and prevent harassment for the duration of their visit at HacDC. We value your attendance.

bod@hacdc.org
Building security guard hours: Monday - Thursday 6pm - 10pm; Saturday 9am - 2pm
DC emergency services: 911
National sexual assault hotline: 1-800-656-HOPE
DC Rape Crisis Center: 202-333-RAPE
DC Yellow Cab: 202-TAXICAB
[http://huhealthcare.com Howard University Hospital]: (202)865-6100 / 2041 Georgia Avenue NW
[http://gwhospital.com GWU Hospital]: (202) 715-4000 / 900 23rd Street NW

We expect members and visitors to follow these rules at all HacDC-organized events, in the space itself, and in our online spaces including mailing lists and the official IRC channel.

== Proposal 2 - Loki ==
If you feel you are being harassed, please inform those around you. If you are uncomfortable informing those around you, or If this does not resolve the issue, you may bring the issue to the attention of the Board of Directors. The Board of Directors are empowered to take any actions they deem necessary, up to and including recommending the revocation of membership status.

If you feel a crime has occurred, please contact the police immediately.

Example of harassment may include, but are not limited to:
* Persistant offensive speech directed at you;
* Deliberate intimidation, stalking, following, harassing photography or recording;
* Sustained disruption of talks or other events;
* Intentional inappropriate physical contact;
* Unwelcome sexual attention;
* Violation of any applicable laws.

== Proposal Gimel - Discussion of topics ==
It has been suggested that future discussion of the topic of harassment and the harassment policy at HacDC use a similar strategy applied to such topics (including harassment, assault, and sexual abuse) in other communities, that called Buddhist Right Speech. Following are a few links to what this is and where it's been applied.

* [http://ieet.org/index.php/IEET/more/5911 'Right Speech' Policy at ieet.org]
* [http://buddhism.about.com/od/theeightfoldpath/a/rightspeech.htm About Right Speech]
* [http://www.thebigview.com/buddhism/eightfoldpath.html#Right_Speech Right Speech]

Hardware compatibility list

2012-06-23T21:46:40Z

Drwho:

[[Category:Byzantium]]
*Dell Inspiron 1520
** Intel 3945 wireless chipset
** Broadcom BCM4401-B0 ethernet chipset
*Asus EeePC 900
** Atheros AR5001 rev. 01 wireless chipset
** Atheros L2 Fast Ethernet rev. a0 ethernet chipset
*HP Pavilion dv6000
** Atheros AR242x rev. 01 wireless chipset
** nVidia MCP67 rev. a2 ethernet chipset
*Novatech generic laptop
** Atheros AR9285 rev. 01 wireless chipset
** USB tether to Smartphone for Internet uplink (usb0, reported as a wireless device but still was able to configure as the gateway device).
*Sony Viao PCG 71312M
**Atheros AR285 Wireless
**Marvell Yukon 88E8059 Gigabit ethernet
*IBM Thinkpad, model unknown
**Intel Advanced-N 6200 wireless chipset (added firmware to Byzantium Linux)
**Intel 82755LM Gigabit ethernet chipset

Process for manually installing Byzantium.

2012-05-26T02:59:29Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** boost
** celt
** CherryPy
** cryptoki
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mumble
** mysql
** ngircd
** node
** pcre
** php
** protobuf
** pyOpenSSL
** pysetuptools
** python-twisted
** qt
** qwebirc
** rrdtool
** speex
** sudo
** truecrypt
** t1lib
** vim
** wxGTK
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../service_directory
* cp index.html /tmp/fakeroot/srv/httpd/htdocs
* cp services.py /tmp/fakeroot/srv/httpd/cgi-bin
* chmod 0755 /tmp/fakeroot/srv/httpd/cgi-bin/services.py
* rm /tmp/fakeroot/srv/httpd/cgi-bin/printenv /tmp/fakeroot/srv/httpd/cgi-bin
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp sudo/etc/sudoers /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc
* chmod 0440 /tmp/fakeroot/etc
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow /tmp/fakeroot/etc/hosts /tmp/fakeroot/etc/HOSTNAME /tmp/fakeroot/etc/inittab
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp mop_up_dead_clients.py /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

{{Template:Byzantium}}

Process for manually installing Byzantium.

2012-05-20T16:47:46Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** boost
** celt
** CherryPy
** cryptoki
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mumble
** mysql
** ngircd
** node
** pcre
** php
** protobuf
** pyOpenSSL
** pysetuptools
** python-twisted
** qt
** qwebirc
** rrdtool
** speex
** sudo
** truecrypt
** t1lib
** vim
** wxGTK
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp sudo/etc/sudoers /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc
* chmod 0440 /tmp/fakeroot/etc
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow /tmp/fakeroot/etc/hosts /tmp/fakeroot/etc/HOSTNAME /tmp/fakeroot/etc/inittab
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp mop_up_dead_clients.py /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

{{Template:Byzantium}}

Process for manually installing Byzantium.

2012-05-20T16:36:00Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** boost
** celt
** CherryPy
** cryptoki
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mumble
** mysql
** ngircd
** node
** pcre
** php
** protobuf
** pysetuptools
** python-twisted
** qt
** qwebirc
** rrdtool
** speex
** sudo
** truecrypt
** t1lib
** vim
** wxGTK
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp sudo/etc/sudoers /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc
* chmod 0440 /tmp/fakeroot/etc
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow /tmp/fakeroot/etc/hosts /tmp/fakeroot/etc/HOSTNAME /tmp/fakeroot/etc/inittab
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp mop_up_dead_clients.py /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

{{Template:Byzantium}}

Process for manually installing Byzantium.

2012-05-20T00:35:30Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** boost
** celt
** CherryPy
** cryptoki
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mumble
** mysql
** ngircd
** node
** pcre
** php
** protobuf
** pysetuptools
** python-twisted
** qt
** qwebirc
** rrdtool
** speex
** sudo
** truecrypt
** t1lib
** vim
** wxGTK
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow /tmp/fakeroot/etc/hosts /tmp/fakeroot/etc/HOSTNAME /tmp/fakeroot/etc/inittab
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp mop_up_dead_clients.py /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

{{Template:Byzantium}}

Process for manually installing Byzantium.

2012-05-20T00:18:11Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** boost
** celt
** CherryPy
** cryptoki
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mumble
** mysql
** ngircd
** node
** pcre
** php
** protobuf
** pysetuptools
** python-twisted
** qt
** qwebirc
** rrdtool
** speex
** sudo
** truecrypt
** t1lib
** vim
** wxGTK
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp mop_up_dead_clients.py /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

{{Template:Byzantium}}

Process for manually installing Byzantium.

2012-05-19T18:14:38Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** boost
** celt
** CherryPy
** cryptoki
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mumble
** mysql
** ngircd
** node
** pcre
** php
** protobuf
** pysetuptools
** python-twisted
** qt
** qwebirc
** rrdtool
** speex
** sudo
** truecrypt
** t1lib
** vim
** wxGTK
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

{{Template:Byzantium}}

Category:Byzantium

2012-05-04T16:02:32Z

Drwho: /* Press */

This project was launched with a sprint on Feb 25-27, 2011.
Sprints will be held the last weekend of every month.

The development wiki page is [[Byzantium_Live_Distro|here]].

The official mailing list is [http://groups.google.com/a/hacdc.org/group/Byzantium/?hl=en here].

The official Github organization page is [https://github.com/Byzantium/Byzantium here].

'''NOTICE: If you've downloaded Byzantium v0.1a, you need to re-download it immediately due to a major bug in the 10 January 2012 release! This is critical!'''
[[Downloading_Byzantium|Where to download Byzantium.]]

== Project Goals ==
The goal of Project Byzantium is to develop a communication system by which users can connect to each other and share information in the absence of convenient access to the Internet.

The use cases for such a system would be:
# The infrastructure for accessing the internet has become damaged or inaccessible. (Eg, a natural disaster such as Hurricane Katrina.)
# A central authority has decided to explicitly block or shutdown key infrastructure. (Eg, Egypt's recent internet blackout.)
# A zombie apocalypse in which the personnel responsible for maintaining key infrastructure have all been turned.

The project aims to develop and publish the necessary documentation, best practices, and software to construct and support such a system. Our current approach is to start by investigating and documenting the existing technologies which would support such a system. In particular, mesh networking protocols, wireless networking technologies, and decentralized (or less-centralized) alternatives to internet addressing/naming systems such as DNS. In designing the system, we aim to reduce the dependency on exotic hardware or skill sets so that the system can be deployed quickly and easily by average internet users.

An additional goal is that users not actively participating in the mesh network (i.e., not running mesh routing software on their devices) can make use of the network without having to install anything new, jailbreak their phone, or pry the information out of a hacker infected with the Exsurgent virus.

==Parts==
[[Byzantium_InterMesh|InterMesh]]
[[Byzantium_Distributed_DNS|Distributed DNS]]
[[Byzantium_Live_Distro|Live Distro]]

== Sprints ==
[[Byzantium Sprint 1|Sprint 1 Details]] [http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 Write up.]
[[Byzantium Sprint 2|Sprint 2 Details]] [http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 Write up.]
[[Byzantium Sprint 3|Sprint 3 Details]]
[[Byzantium Sprint 4|Sprint 4 Details]]
Individual sprint reports have been replaced with the [[Byzantium Action Log|Action Log]] since the sprints have become slightly less structured as we delve into the minutia of the project.

== Presentations and PR ==
[http://www.novalug.org/node/176 Ben and the Doctor will be presenting at NOVALUG!] - 14 May 2011
[http://contactcon.com/project-byzantium The Doctor will be presenting at ContactCon!] - 20 October 2011
[http://www.broadbandbridge.org/ Ben and the Doctor presented at DC Broadband Bridge!] - 5 November 2011 ([https://drwho.virtadpt.net/images/byzantium_presentation-20111105.pdf presentation])
[http://drwho.virtadpt.net/archive/2011/08/08/frequently-needed-answers-for-project-byzantium Unofficial Frequently Asked Questions.]
[http://www.hacdc.org/content/byzantium-v01a-scarab-released Release announcement for v0.1a!]
[https://drwho.virtadpt.net/archive/2012/04/30/hacdc-at-the-usa-science-and-engineering-festival Byzantium Linux was distributed and field tested at the USA Science and Engineering Festival!]
[https://drwho.virtadpt.net/archive/2012/04/20/not-dead-only-busy Project Byzantium will be presenting at CarolinaCon and HOPE Number Nine!]

== Press ==
[http://www.fastcompany.com/1750215/how-hackerspaces-can-do-good-for-the-world Fast Company: 28 April 2011]
[https://chronicle.com/article/College-20-Fear-of/129049/ College v2.0: Fear of Repression Spurs Scholars and Activists to Build Alternate Internets]
[http://www.shareable.net/blog/10-projects-to-liberate-the-web 10 Projects to Liberate the Web]
[http://blog.makezine.com/archive/2011/10/project-byzantium-aims-to-avoid-internet-outages.html Make Magazine]
[http://www.reddit.com/r/darknetplan/comments/l9tko/make_at_washington_dcs_hackerspace_hacdc_a_team/ Make article linked on /r/darknetplan]
[http://www.tendencias21.net/Ciberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Ciberactivistas crean un Internet alternativo por miedo a la represión] [http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=ISO-8859-1&layout=2&eotf=1&u=http%3A%2F%2Fwww.tendencias21.net%2FCiberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Google Translation]
[http://www.fastcoexist.com/1677951/hackerspaces-hubs-for-tech-minded-do-gooders Hackerspaces: Hubs for Tech-Minded do-Gooders?]
[http://www.disinfo.com/2012/03/interview-with-telecomix-hacktivists-peter-fein-and-the-doctor/ Interview with DisinfoTV at ContactCon]
[http://www.theglobalmail.org/feature/iran-not-tweeting-hacking/165/ Iran: Not Tweeting, Hacking]; Byzantium-related stuff near the end of the article, some inaccuracies.
[https://www.npr.org/internedition/spring12/?p=168 NPR Intern Edition: Hacking to Byzantium]

[[Category:Ongoing_Projects]]

<DynamicPageList>
category = Byzantium
order = ascending
mode = inline
addfirstcategorydate = true
</DynamicPageList>

Byzantium Live Distro

2012-04-30T21:32:22Z

Drwho: /* Timeline */

==Description==
We are building a portable live Linux distribution based on [http://porteus.org/ Porteus Linux]. Porteus itself is a fork of Slax that has been brought up to date with Slackware 13.37 and uses a 2.6.38.8 kernel. Porteus can use binary packages from Slackware 13.37 after conversion to Porteus' native format.

==Code Repositories==
[https://github.com/Byzantium/Byzantium Github page]

[http://svn.virtadpt.net/byzantium/ Subversion repo for Porteus packages]

==Goals==
* Make it possible for people in emergency situations to communicate and collaborate.
* Make it possible for people in areas where the communications infrastructure is compromised to communicate and collaborate.
* Provide services to support communication and collaboration.
* Will be secure out of the box.
** Best practices for isolating running services will be followed.
** Best practices for configuration web applications will be followed.
** Least privilege will be followed wherever possible.
* Will be extensively documented.
** A Creative Commons-licensed book will be made available with the Byzantium distribution as well as separately
** Will explain the finer points of setting up a mesh, as well as accompanying projects (such as dialup gateways and long-haul transports).
** Will be translated into as many languages as possible.
* Widely compatible.
** Users need to be able to boot their desktop/laptop/netbook from Byzantium media and set up a node.
** As little fiddling with network drivers as possible.
* Rapidly deployable.
** Users need to be able to configure their Byzantium node rapidly and with little assistance.
** Emergency situations.
** Control panel aims to be as self-documenting as possible.
* Aims to protect confidentiality of traffic.
** Opportunistic IPsec?
** All services default to SSLv3/TLSv1.
* Aims to protect integrity of traffic.
** SSLv3/TLSv1.
* Meshes should grow without the direction of a central authority.
** Anyone can set up a mesh node.
** Anyone can set up services on the mesh.
** Services packaged by default can be managed (activated and deactivated) from the control panel
** Services packaged by default will come preconfigured with secure defaults and a mobile-friendly theme where appropriate.
** This is a calculated risk. The threat models of Tor and I2P take this into account as well.
* Byzantium nodes need to be rapidly clonable.
** One copy of the live distribution needs to become many on demand.
** Nodes need to be clonable without taking the node down.
* Persistent storage has to be an option.
** Built into [http://porteus.org Porteus].
*** save.dat file
*** removable media
*** media Porteus is installed to
* Dependencies will be automatically managed by the control panel.

==Features==
* Can support multiple mesh routing protocols.
* Modular configuration back end.
* Multiple pre-packaged, pre-configured web applications for communication and collaboration.
* All services can be independently activated and deactivated.
* Aims for security by default.
** Services are not active unless explicitly triggered.
** Services are configured using best practices for security.
** Services support strong cryptography by default.
* Supports gatewaying from the mesh to the Net over a live connection.
* Supports persistent (encrypted) storage on demand (not default).
** Note: When creating a save.dat file under Porteus, if the drive it's on is formatted FAT-32 or less, the file MUST be <1024MB, else, the /linuxrc script that forms the core of the distro will pretend that it can't locate the file, regardless of where you put it. This drove me bonkers for two months!
*** If possible we should try to make save.dat a second partition on the thumbdrive (ala casper-rw for ubuntu liveUSBs) there are some big benefits to this:
**** it makes it harder for windows users to see that there is a second partition in case big brother decides to inspect the contents of all thumbdrives.
**** it means we won't have to worry about file size limits.

===ToDo===
*<strike>[[Byzantium_Live_Distro_CP|Node Control Panel]]</strike> - DONE!
*<strike>[[Byzantium_Live_Distro_Captive_Portal|Captive Portal]]</strike> -DONE!
*[[Byzantium_Live_Distro_Service_Announce|Provided Services Announcement]]
*[[Byzantium_Live_Distro_Wiki|Wiki]] - suspended notion
*<strike>[[Byzantium_Live_Distro_Microblog|Microblog]]</strike> - DONE!
*[[Byzantium_Live_Distro_FileDump|File dump/Twitpic work-alike]]
*[[Byzantium_Live_Distro_Tel|Voice chat/telephony server]]
*<strike>[[Byzantium_Live_Distro_Chat|Clientless web chat]]</strike> - DONE!
*<strike>[[Byzantium_Live_Distro_Microblog|Blog]]</strike> - see Microblog
*<strike>[[Byzantium_Live_Distro_EPad|EtherPad-like thing]]</strike> - DONE!
*[[Byzantium_Live_Distro_StreamingMediaSrv|Streaming media server]]
*[[Byzantium_Live_Distro_WebProxy|HTTP caching proxy]]
*[https://www.torproject.org/ Tor]
*[[IPset]]

Pick a web server to host applications:
* Converted the Apache, apr*, and PHP packages of Slackware v13.37 into Porteus modules. They Just Worked(tm).

<strike>We need to figure out how to properly install the control panel app on a new system. The process should be as pythonic as possible.</strike>

We need to figure out how to bundle the already configured and populated MySQL databases for the web apps!
* Packaging them into a module and activating it didn't work.
* <strike>Write a script that detects the presence or absence of /var/lib/db/*/ and restores them from .sql dumps at boot-time.</strike>

[[The Doctor's to-do list]]

==Packages built for Byzantium==
* babeld - For great mesh routing.
* batman-adv - Kernel module which implements mesh routing at OSI layer 2. We may not use it but it's there if we need it.
* batctl - Utility for configurating and manipulating batman-adv.
** Dependency of batman-adv.
* olsrd - from olsr.org
* ahcpd - For configuring mesh nodes that don't want to use the random RFC-1918 IP address generator.
* CherryPy - Python module that implements a fast multi-threaded HTTP (web application) server.
** Without this, there is no control panel.
* pySetupTools - Required for installing some Python modules.
* Mako - Python HTML templating system.
** Dependency of the control panel.
* MarkupSafe - Python library that implements a Unicode string that is aware of HTML escaping rules and does automatic string escaping.
** Dependency of Mako.
* Git - Converted Slackware v13.37 package.
** Necessary for checking code out and into Github.
* Curl - Converted Slackware v13.37 package.
** Dependency of git.
** Note: To make git work without "error setting certificate verify locations" errors, you need to run the following command as the root user: git config --system http.sslcainfo /usr/share/curl/ca-bundle.crt
* rrdtool - Used by traffic_stats.sh to monitor network traffic and build graphs.
* sqlitebrowser - Used to develop SQLite database schemas and debug database access code. Will not be in OS release.
* <strike>nginx - Lightweight, fast HTTP(S) server. Much more lightweight than Apache, at any rate. Custom build for Byzantium.</strike>
** Enough!
* gd - Dependency of PHP.
** Used for server side image manipulation.
* libmcrypt - Dependency of PHP.
* icu4c - International Components for Unicode. i18n dependency of PHP.
* openldap-client - Dependency of PHP to make it compile. Not pleased by having to package it, but it won't build without it.
** Can we get away with not having it because I didn't have to compile it for Apache? Let's try it!
* php - Converted Slackware v13.37 package.
* httpd - Apache v2.2.17. Converted Slackware v13.37 package.
** ..and then stuff started working!
* apr-util - Converted Slackware v13.37 package.
** Utility used for compiling Apache modules.
* apr - Converted Slackware v13.37 package.
** Package used for compiling Apache modules.
* t1lib - Converted Slackware v13.37 package. Used for font manipulation.
* pcre - Converted Slackware v13.37 package.
** Perl Compatible Regular Expression library.
** Unicode aware for i18n support. status.net requires this for basic functionality, whcih means that we get i18n for free.
* <strike>Firefox v6.0.2</strike>
** Do not use! i_can_haz_firefox.sh builds a package with bad symlinks. Haven't bothered to fix it so far.
* node - An event-driven I/O server-side JavaScript environment based on V8. (from website and wikipedia).
** Required by Etherpad-lite.
* dnsmasq - All-in-one DHCP and caching DNS server.
** Much easier to work with in circumstances like this than ISC BIND or even djbdns.
* ipcalc - Command-line IP networking calculator. Will be needed by the control panel shortly.
** Removed the CGI-BIN script from the package when it was built.
* ngircd - Lightweight IRC server.
** Back-end for web chat application.
** Somehow we need to figure out a way to make them automagically hook together into an IRC network. But that can wait.
* zope.interface - Required by Twisted.
* Twisted - Required by qwebirc.
** Satisfies the clientless web chat requirement.

==Links==
Place links relevant to any part of the process of making the live distro here.

[http://porteus.org/ Porteus Official Website]

[[Processes for building Porteus packages.]]

[[Process for manually installing Byzantium.]]

[[Byzantium 101]] - How to get yourself set up.

[[Hardware compatibility list]]

[[User Feedback on Byzantium 0.1a]]

==Timeline==
* .....uhh....
* 20 October 2011 - Live demo, presentation, and networking at [http://contactcon.com/ ContactCon].
* 12 May 2012 @ 1400 EST5EDT: Project Byzantium presentation at [http://carolinacon.org/ CarolinaCon].
* 13-15 July 2012 @ TBA: Project Byzantium presentation at [http://www.hopenumbernine.net/ HOPE Number Nine].

==Stuff==
<strike>Need to edit /etc/hosts, add 'byzantium' to 127.0.0.1 so that the web server will start up.</strike>

[[Mobile devices and IPv6.]]

<strike>[http://thekelleys.org.uk/dnsmasq/doc.html DNSmasq]</strike>
* <strike>One nice thing about DNSmasq is the -H option, for additional /etc/hosts-like files. We could use those to cache the IP addresses of other Byzantium nodes, and then query them for the services they run.</strike>
** Hostnames are IPv6 addresses of nodes.
*** ifconfig wlan0 | grep inet6 | awk '{print $3}' | sed 's/:/-/g' | sed 's/\/64$//' | sed 's/$/.byzantium.mesh/' == fe80--21c-bfff-fe35-84c2.byzantium.mesh
** <strike>Put IP addresses and hostnames in /etc/hosts.mesh.</strike>
** This could also be used for status.net federation and IRC network construction.
* <strike>Move the '''server=/byzantium.mesh/...''' line into the generated DNSmasq include file?</strike>
** <strike>Make the '...' the mesh interface's IP address?</strike>

* <strike>Consulted with an expert about IP addressing. At first scratch, it might be a good idea to stick wtih pseudo-randomly chosen 10/8's. Configure the mesh interface for the .1 and give the clients .2-.254. I'll re-work the control panel to do that.</strike>

Need to account for [http://www.webopedia.com/TERM/A/APIPA.html APIPA] addressing in the initial set of routes.

* <strike>Added for the purpose of making networkconfiguration.py [http://www.cyberciti.biz/faq/linux-duplicate-address-detection-with-arping/ detect whether or not the proposed IP address for the mesh interface is in use].</strike>
** Byzantium does this now. It works like a champ.

List of public DNSes that we may wish to fall back upon in the event a node is made into a gateway:
* [https://code.google.com/speed/public-dns/ Google Public DNS]
* [http://www.tech-faq.com/public-dns-servers.html Public DNS servers]
* [https://www.opendns.com/ OpenDNS]

[[Packaging NPM.]]

[[Finding neighboring mesh nodes]]

[[Fully distributed services]]

==Stuff to consider for later==
* Consider adding [http://code.kryo.se/iodine/ Iodine] to Byzantium to help tunnel gatewayed traffic onto the Net.
** Gateway nodes in hostile areas could use Iodine to tunnel traffic out.
** Gateway nodes in non-hostile areas could accept Iodine connections to help less fortunate nodes evade censorship.
* Consider adding (http|proxy)tunnel with simplified usage of some kind to allow encapsulating arbitrary data streams in http streams.
* Firewall evasion aids that will work well even in established internet censorship systems?

{{Template:Byzantium}}

Byzantium Live Distro

2012-04-30T21:29:37Z

Drwho: /* Links */

==Description==
We are building a portable live Linux distribution based on [http://porteus.org/ Porteus Linux]. Porteus itself is a fork of Slax that has been brought up to date with Slackware 13.37 and uses a 2.6.38.8 kernel. Porteus can use binary packages from Slackware 13.37 after conversion to Porteus' native format.

==Code Repositories==
[https://github.com/Byzantium/Byzantium Github page]

[http://svn.virtadpt.net/byzantium/ Subversion repo for Porteus packages]

==Goals==
* Make it possible for people in emergency situations to communicate and collaborate.
* Make it possible for people in areas where the communications infrastructure is compromised to communicate and collaborate.
* Provide services to support communication and collaboration.
* Will be secure out of the box.
** Best practices for isolating running services will be followed.
** Best practices for configuration web applications will be followed.
** Least privilege will be followed wherever possible.
* Will be extensively documented.
** A Creative Commons-licensed book will be made available with the Byzantium distribution as well as separately
** Will explain the finer points of setting up a mesh, as well as accompanying projects (such as dialup gateways and long-haul transports).
** Will be translated into as many languages as possible.
* Widely compatible.
** Users need to be able to boot their desktop/laptop/netbook from Byzantium media and set up a node.
** As little fiddling with network drivers as possible.
* Rapidly deployable.
** Users need to be able to configure their Byzantium node rapidly and with little assistance.
** Emergency situations.
** Control panel aims to be as self-documenting as possible.
* Aims to protect confidentiality of traffic.
** Opportunistic IPsec?
** All services default to SSLv3/TLSv1.
* Aims to protect integrity of traffic.
** SSLv3/TLSv1.
* Meshes should grow without the direction of a central authority.
** Anyone can set up a mesh node.
** Anyone can set up services on the mesh.
** Services packaged by default can be managed (activated and deactivated) from the control panel
** Services packaged by default will come preconfigured with secure defaults and a mobile-friendly theme where appropriate.
** This is a calculated risk. The threat models of Tor and I2P take this into account as well.
* Byzantium nodes need to be rapidly clonable.
** One copy of the live distribution needs to become many on demand.
** Nodes need to be clonable without taking the node down.
* Persistent storage has to be an option.
** Built into [http://porteus.org Porteus].
*** save.dat file
*** removable media
*** media Porteus is installed to
* Dependencies will be automatically managed by the control panel.

==Features==
* Can support multiple mesh routing protocols.
* Modular configuration back end.
* Multiple pre-packaged, pre-configured web applications for communication and collaboration.
* All services can be independently activated and deactivated.
* Aims for security by default.
** Services are not active unless explicitly triggered.
** Services are configured using best practices for security.
** Services support strong cryptography by default.
* Supports gatewaying from the mesh to the Net over a live connection.
* Supports persistent (encrypted) storage on demand (not default).
** Note: When creating a save.dat file under Porteus, if the drive it's on is formatted FAT-32 or less, the file MUST be <1024MB, else, the /linuxrc script that forms the core of the distro will pretend that it can't locate the file, regardless of where you put it. This drove me bonkers for two months!
*** If possible we should try to make save.dat a second partition on the thumbdrive (ala casper-rw for ubuntu liveUSBs) there are some big benefits to this:
**** it makes it harder for windows users to see that there is a second partition in case big brother decides to inspect the contents of all thumbdrives.
**** it means we won't have to worry about file size limits.

===ToDo===
*<strike>[[Byzantium_Live_Distro_CP|Node Control Panel]]</strike> - DONE!
*<strike>[[Byzantium_Live_Distro_Captive_Portal|Captive Portal]]</strike> -DONE!
*[[Byzantium_Live_Distro_Service_Announce|Provided Services Announcement]]
*[[Byzantium_Live_Distro_Wiki|Wiki]] - suspended notion
*<strike>[[Byzantium_Live_Distro_Microblog|Microblog]]</strike> - DONE!
*[[Byzantium_Live_Distro_FileDump|File dump/Twitpic work-alike]]
*[[Byzantium_Live_Distro_Tel|Voice chat/telephony server]]
*<strike>[[Byzantium_Live_Distro_Chat|Clientless web chat]]</strike> - DONE!
*<strike>[[Byzantium_Live_Distro_Microblog|Blog]]</strike> - see Microblog
*<strike>[[Byzantium_Live_Distro_EPad|EtherPad-like thing]]</strike> - DONE!
*[[Byzantium_Live_Distro_StreamingMediaSrv|Streaming media server]]
*[[Byzantium_Live_Distro_WebProxy|HTTP caching proxy]]
*[https://www.torproject.org/ Tor]
*[[IPset]]

Pick a web server to host applications:
* Converted the Apache, apr*, and PHP packages of Slackware v13.37 into Porteus modules. They Just Worked(tm).

<strike>We need to figure out how to properly install the control panel app on a new system. The process should be as pythonic as possible.</strike>

We need to figure out how to bundle the already configured and populated MySQL databases for the web apps!
* Packaging them into a module and activating it didn't work.
* <strike>Write a script that detects the presence or absence of /var/lib/db/*/ and restores them from .sql dumps at boot-time.</strike>

[[The Doctor's to-do list]]

==Packages built for Byzantium==
* babeld - For great mesh routing.
* batman-adv - Kernel module which implements mesh routing at OSI layer 2. We may not use it but it's there if we need it.
* batctl - Utility for configurating and manipulating batman-adv.
** Dependency of batman-adv.
* olsrd - from olsr.org
* ahcpd - For configuring mesh nodes that don't want to use the random RFC-1918 IP address generator.
* CherryPy - Python module that implements a fast multi-threaded HTTP (web application) server.
** Without this, there is no control panel.
* pySetupTools - Required for installing some Python modules.
* Mako - Python HTML templating system.
** Dependency of the control panel.
* MarkupSafe - Python library that implements a Unicode string that is aware of HTML escaping rules and does automatic string escaping.
** Dependency of Mako.
* Git - Converted Slackware v13.37 package.
** Necessary for checking code out and into Github.
* Curl - Converted Slackware v13.37 package.
** Dependency of git.
** Note: To make git work without "error setting certificate verify locations" errors, you need to run the following command as the root user: git config --system http.sslcainfo /usr/share/curl/ca-bundle.crt
* rrdtool - Used by traffic_stats.sh to monitor network traffic and build graphs.
* sqlitebrowser - Used to develop SQLite database schemas and debug database access code. Will not be in OS release.
* <strike>nginx - Lightweight, fast HTTP(S) server. Much more lightweight than Apache, at any rate. Custom build for Byzantium.</strike>
** Enough!
* gd - Dependency of PHP.
** Used for server side image manipulation.
* libmcrypt - Dependency of PHP.
* icu4c - International Components for Unicode. i18n dependency of PHP.
* openldap-client - Dependency of PHP to make it compile. Not pleased by having to package it, but it won't build without it.
** Can we get away with not having it because I didn't have to compile it for Apache? Let's try it!
* php - Converted Slackware v13.37 package.
* httpd - Apache v2.2.17. Converted Slackware v13.37 package.
** ..and then stuff started working!
* apr-util - Converted Slackware v13.37 package.
** Utility used for compiling Apache modules.
* apr - Converted Slackware v13.37 package.
** Package used for compiling Apache modules.
* t1lib - Converted Slackware v13.37 package. Used for font manipulation.
* pcre - Converted Slackware v13.37 package.
** Perl Compatible Regular Expression library.
** Unicode aware for i18n support. status.net requires this for basic functionality, whcih means that we get i18n for free.
* <strike>Firefox v6.0.2</strike>
** Do not use! i_can_haz_firefox.sh builds a package with bad symlinks. Haven't bothered to fix it so far.
* node - An event-driven I/O server-side JavaScript environment based on V8. (from website and wikipedia).
** Required by Etherpad-lite.
* dnsmasq - All-in-one DHCP and caching DNS server.
** Much easier to work with in circumstances like this than ISC BIND or even djbdns.
* ipcalc - Command-line IP networking calculator. Will be needed by the control panel shortly.
** Removed the CGI-BIN script from the package when it was built.
* ngircd - Lightweight IRC server.
** Back-end for web chat application.
** Somehow we need to figure out a way to make them automagically hook together into an IRC network. But that can wait.
* zope.interface - Required by Twisted.
* Twisted - Required by qwebirc.
** Satisfies the clientless web chat requirement.

==Links==
Place links relevant to any part of the process of making the live distro here.

[http://porteus.org/ Porteus Official Website]

[[Processes for building Porteus packages.]]

[[Process for manually installing Byzantium.]]

[[Byzantium 101]] - How to get yourself set up.

[[Hardware compatibility list]]

[[User Feedback on Byzantium 0.1a]]

==Timeline==
* .....uhh....
* 20 October 2011 - Live demo, presentation, and networking at [http://contactcon.com/ ContactCon].

==Stuff==
<strike>Need to edit /etc/hosts, add 'byzantium' to 127.0.0.1 so that the web server will start up.</strike>

[[Mobile devices and IPv6.]]

<strike>[http://thekelleys.org.uk/dnsmasq/doc.html DNSmasq]</strike>
* <strike>One nice thing about DNSmasq is the -H option, for additional /etc/hosts-like files. We could use those to cache the IP addresses of other Byzantium nodes, and then query them for the services they run.</strike>
** Hostnames are IPv6 addresses of nodes.
*** ifconfig wlan0 | grep inet6 | awk '{print $3}' | sed 's/:/-/g' | sed 's/\/64$//' | sed 's/$/.byzantium.mesh/' == fe80--21c-bfff-fe35-84c2.byzantium.mesh
** <strike>Put IP addresses and hostnames in /etc/hosts.mesh.</strike>
** This could also be used for status.net federation and IRC network construction.
* <strike>Move the '''server=/byzantium.mesh/...''' line into the generated DNSmasq include file?</strike>
** <strike>Make the '...' the mesh interface's IP address?</strike>

* <strike>Consulted with an expert about IP addressing. At first scratch, it might be a good idea to stick wtih pseudo-randomly chosen 10/8's. Configure the mesh interface for the .1 and give the clients .2-.254. I'll re-work the control panel to do that.</strike>

Need to account for [http://www.webopedia.com/TERM/A/APIPA.html APIPA] addressing in the initial set of routes.

* <strike>Added for the purpose of making networkconfiguration.py [http://www.cyberciti.biz/faq/linux-duplicate-address-detection-with-arping/ detect whether or not the proposed IP address for the mesh interface is in use].</strike>
** Byzantium does this now. It works like a champ.

List of public DNSes that we may wish to fall back upon in the event a node is made into a gateway:
* [https://code.google.com/speed/public-dns/ Google Public DNS]
* [http://www.tech-faq.com/public-dns-servers.html Public DNS servers]
* [https://www.opendns.com/ OpenDNS]

[[Packaging NPM.]]

[[Finding neighboring mesh nodes]]

[[Fully distributed services]]

==Stuff to consider for later==
* Consider adding [http://code.kryo.se/iodine/ Iodine] to Byzantium to help tunnel gatewayed traffic onto the Net.
** Gateway nodes in hostile areas could use Iodine to tunnel traffic out.
** Gateway nodes in non-hostile areas could accept Iodine connections to help less fortunate nodes evade censorship.
* Consider adding (http|proxy)tunnel with simplified usage of some kind to allow encapsulating arbitrary data streams in http streams.
* Firewall evasion aids that will work well even in established internet censorship systems?

{{Template:Byzantium}}

Byzantium Live Distro

2012-04-30T21:28:45Z

Drwho: /* Code Repositories */

==Description==
We are building a portable live Linux distribution based on [http://porteus.org/ Porteus Linux]. Porteus itself is a fork of Slax that has been brought up to date with Slackware 13.37 and uses a 2.6.38.8 kernel. Porteus can use binary packages from Slackware 13.37 after conversion to Porteus' native format.

==Code Repositories==
[https://github.com/Byzantium/Byzantium Github page]

[http://svn.virtadpt.net/byzantium/ Subversion repo for Porteus packages]

==Goals==
* Make it possible for people in emergency situations to communicate and collaborate.
* Make it possible for people in areas where the communications infrastructure is compromised to communicate and collaborate.
* Provide services to support communication and collaboration.
* Will be secure out of the box.
** Best practices for isolating running services will be followed.
** Best practices for configuration web applications will be followed.
** Least privilege will be followed wherever possible.
* Will be extensively documented.
** A Creative Commons-licensed book will be made available with the Byzantium distribution as well as separately
** Will explain the finer points of setting up a mesh, as well as accompanying projects (such as dialup gateways and long-haul transports).
** Will be translated into as many languages as possible.
* Widely compatible.
** Users need to be able to boot their desktop/laptop/netbook from Byzantium media and set up a node.
** As little fiddling with network drivers as possible.
* Rapidly deployable.
** Users need to be able to configure their Byzantium node rapidly and with little assistance.
** Emergency situations.
** Control panel aims to be as self-documenting as possible.
* Aims to protect confidentiality of traffic.
** Opportunistic IPsec?
** All services default to SSLv3/TLSv1.
* Aims to protect integrity of traffic.
** SSLv3/TLSv1.
* Meshes should grow without the direction of a central authority.
** Anyone can set up a mesh node.
** Anyone can set up services on the mesh.
** Services packaged by default can be managed (activated and deactivated) from the control panel
** Services packaged by default will come preconfigured with secure defaults and a mobile-friendly theme where appropriate.
** This is a calculated risk. The threat models of Tor and I2P take this into account as well.
* Byzantium nodes need to be rapidly clonable.
** One copy of the live distribution needs to become many on demand.
** Nodes need to be clonable without taking the node down.
* Persistent storage has to be an option.
** Built into [http://porteus.org Porteus].
*** save.dat file
*** removable media
*** media Porteus is installed to
* Dependencies will be automatically managed by the control panel.

==Features==
* Can support multiple mesh routing protocols.
* Modular configuration back end.
* Multiple pre-packaged, pre-configured web applications for communication and collaboration.
* All services can be independently activated and deactivated.
* Aims for security by default.
** Services are not active unless explicitly triggered.
** Services are configured using best practices for security.
** Services support strong cryptography by default.
* Supports gatewaying from the mesh to the Net over a live connection.
* Supports persistent (encrypted) storage on demand (not default).
** Note: When creating a save.dat file under Porteus, if the drive it's on is formatted FAT-32 or less, the file MUST be <1024MB, else, the /linuxrc script that forms the core of the distro will pretend that it can't locate the file, regardless of where you put it. This drove me bonkers for two months!
*** If possible we should try to make save.dat a second partition on the thumbdrive (ala casper-rw for ubuntu liveUSBs) there are some big benefits to this:
**** it makes it harder for windows users to see that there is a second partition in case big brother decides to inspect the contents of all thumbdrives.
**** it means we won't have to worry about file size limits.

===ToDo===
*<strike>[[Byzantium_Live_Distro_CP|Node Control Panel]]</strike> - DONE!
*<strike>[[Byzantium_Live_Distro_Captive_Portal|Captive Portal]]</strike> -DONE!
*[[Byzantium_Live_Distro_Service_Announce|Provided Services Announcement]]
*[[Byzantium_Live_Distro_Wiki|Wiki]] - suspended notion
*<strike>[[Byzantium_Live_Distro_Microblog|Microblog]]</strike> - DONE!
*[[Byzantium_Live_Distro_FileDump|File dump/Twitpic work-alike]]
*[[Byzantium_Live_Distro_Tel|Voice chat/telephony server]]
*<strike>[[Byzantium_Live_Distro_Chat|Clientless web chat]]</strike> - DONE!
*<strike>[[Byzantium_Live_Distro_Microblog|Blog]]</strike> - see Microblog
*<strike>[[Byzantium_Live_Distro_EPad|EtherPad-like thing]]</strike> - DONE!
*[[Byzantium_Live_Distro_StreamingMediaSrv|Streaming media server]]
*[[Byzantium_Live_Distro_WebProxy|HTTP caching proxy]]
*[https://www.torproject.org/ Tor]
*[[IPset]]

Pick a web server to host applications:
* Converted the Apache, apr*, and PHP packages of Slackware v13.37 into Porteus modules. They Just Worked(tm).

<strike>We need to figure out how to properly install the control panel app on a new system. The process should be as pythonic as possible.</strike>

We need to figure out how to bundle the already configured and populated MySQL databases for the web apps!
* Packaging them into a module and activating it didn't work.
* <strike>Write a script that detects the presence or absence of /var/lib/db/*/ and restores them from .sql dumps at boot-time.</strike>

[[The Doctor's to-do list]]

==Packages built for Byzantium==
* babeld - For great mesh routing.
* batman-adv - Kernel module which implements mesh routing at OSI layer 2. We may not use it but it's there if we need it.
* batctl - Utility for configurating and manipulating batman-adv.
** Dependency of batman-adv.
* olsrd - from olsr.org
* ahcpd - For configuring mesh nodes that don't want to use the random RFC-1918 IP address generator.
* CherryPy - Python module that implements a fast multi-threaded HTTP (web application) server.
** Without this, there is no control panel.
* pySetupTools - Required for installing some Python modules.
* Mako - Python HTML templating system.
** Dependency of the control panel.
* MarkupSafe - Python library that implements a Unicode string that is aware of HTML escaping rules and does automatic string escaping.
** Dependency of Mako.
* Git - Converted Slackware v13.37 package.
** Necessary for checking code out and into Github.
* Curl - Converted Slackware v13.37 package.
** Dependency of git.
** Note: To make git work without "error setting certificate verify locations" errors, you need to run the following command as the root user: git config --system http.sslcainfo /usr/share/curl/ca-bundle.crt
* rrdtool - Used by traffic_stats.sh to monitor network traffic and build graphs.
* sqlitebrowser - Used to develop SQLite database schemas and debug database access code. Will not be in OS release.
* <strike>nginx - Lightweight, fast HTTP(S) server. Much more lightweight than Apache, at any rate. Custom build for Byzantium.</strike>
** Enough!
* gd - Dependency of PHP.
** Used for server side image manipulation.
* libmcrypt - Dependency of PHP.
* icu4c - International Components for Unicode. i18n dependency of PHP.
* openldap-client - Dependency of PHP to make it compile. Not pleased by having to package it, but it won't build without it.
** Can we get away with not having it because I didn't have to compile it for Apache? Let's try it!
* php - Converted Slackware v13.37 package.
* httpd - Apache v2.2.17. Converted Slackware v13.37 package.
** ..and then stuff started working!
* apr-util - Converted Slackware v13.37 package.
** Utility used for compiling Apache modules.
* apr - Converted Slackware v13.37 package.
** Package used for compiling Apache modules.
* t1lib - Converted Slackware v13.37 package. Used for font manipulation.
* pcre - Converted Slackware v13.37 package.
** Perl Compatible Regular Expression library.
** Unicode aware for i18n support. status.net requires this for basic functionality, whcih means that we get i18n for free.
* <strike>Firefox v6.0.2</strike>
** Do not use! i_can_haz_firefox.sh builds a package with bad symlinks. Haven't bothered to fix it so far.
* node - An event-driven I/O server-side JavaScript environment based on V8. (from website and wikipedia).
** Required by Etherpad-lite.
* dnsmasq - All-in-one DHCP and caching DNS server.
** Much easier to work with in circumstances like this than ISC BIND or even djbdns.
* ipcalc - Command-line IP networking calculator. Will be needed by the control panel shortly.
** Removed the CGI-BIN script from the package when it was built.
* ngircd - Lightweight IRC server.
** Back-end for web chat application.
** Somehow we need to figure out a way to make them automagically hook together into an IRC network. But that can wait.
* zope.interface - Required by Twisted.
* Twisted - Required by qwebirc.
** Satisfies the clientless web chat requirement.

==Links==
Place links relevant to any part of the process of making the live distro here.

[http://porteus.org/ Porteus Official Website]
[[Processes for building Porteus packages.]]
[[Process for manually installing Byzantium.]]
[[Byzantium 101]] - How to get yourself set up.
[[Hardware compatibility list]]
[[User Feedback on Byzantium 0.1a]]
==Timeline==
* .....uhh....
* 20 October 2011 - Live demo, presentation, and networking at [http://contactcon.com/ ContactCon].

==Stuff==
<strike>Need to edit /etc/hosts, add 'byzantium' to 127.0.0.1 so that the web server will start up.</strike>

[[Mobile devices and IPv6.]]

<strike>[http://thekelleys.org.uk/dnsmasq/doc.html DNSmasq]</strike>
* <strike>One nice thing about DNSmasq is the -H option, for additional /etc/hosts-like files. We could use those to cache the IP addresses of other Byzantium nodes, and then query them for the services they run.</strike>
** Hostnames are IPv6 addresses of nodes.
*** ifconfig wlan0 | grep inet6 | awk '{print $3}' | sed 's/:/-/g' | sed 's/\/64$//' | sed 's/$/.byzantium.mesh/' == fe80--21c-bfff-fe35-84c2.byzantium.mesh
** <strike>Put IP addresses and hostnames in /etc/hosts.mesh.</strike>
** This could also be used for status.net federation and IRC network construction.
* <strike>Move the '''server=/byzantium.mesh/...''' line into the generated DNSmasq include file?</strike>
** <strike>Make the '...' the mesh interface's IP address?</strike>

* <strike>Consulted with an expert about IP addressing. At first scratch, it might be a good idea to stick wtih pseudo-randomly chosen 10/8's. Configure the mesh interface for the .1 and give the clients .2-.254. I'll re-work the control panel to do that.</strike>

Need to account for [http://www.webopedia.com/TERM/A/APIPA.html APIPA] addressing in the initial set of routes.

* <strike>Added for the purpose of making networkconfiguration.py [http://www.cyberciti.biz/faq/linux-duplicate-address-detection-with-arping/ detect whether or not the proposed IP address for the mesh interface is in use].</strike>
** Byzantium does this now. It works like a champ.

List of public DNSes that we may wish to fall back upon in the event a node is made into a gateway:
* [https://code.google.com/speed/public-dns/ Google Public DNS]
* [http://www.tech-faq.com/public-dns-servers.html Public DNS servers]
* [https://www.opendns.com/ OpenDNS]

[[Packaging NPM.]]

[[Finding neighboring mesh nodes]]

[[Fully distributed services]]

==Stuff to consider for later==
* Consider adding [http://code.kryo.se/iodine/ Iodine] to Byzantium to help tunnel gatewayed traffic onto the Net.
** Gateway nodes in hostile areas could use Iodine to tunnel traffic out.
** Gateway nodes in non-hostile areas could accept Iodine connections to help less fortunate nodes evade censorship.
* Consider adding (http|proxy)tunnel with simplified usage of some kind to allow encapsulating arbitrary data streams in http streams.
* Firewall evasion aids that will work well even in established internet censorship systems?

{{Template:Byzantium}}

Category:Byzantium

2012-04-30T21:24:15Z

Drwho: /* Presentations and PR */

This project was launched with a sprint on Feb 25-27, 2011.
Sprints will be held the last weekend of every month.

The development wiki page is [[Byzantium_Live_Distro|here]].

The official mailing list is [http://groups.google.com/a/hacdc.org/group/Byzantium/?hl=en here].

The official Github organization page is [https://github.com/Byzantium/Byzantium here].

'''NOTICE: If you've downloaded Byzantium v0.1a, you need to re-download it immediately due to a major bug in the 10 January 2012 release! This is critical!'''
[[Downloading_Byzantium|Where to download Byzantium.]]

== Project Goals ==
The goal of Project Byzantium is to develop a communication system by which users can connect to each other and share information in the absence of convenient access to the Internet.

The use cases for such a system would be:
# The infrastructure for accessing the internet has become damaged or inaccessible. (Eg, a natural disaster such as Hurricane Katrina.)
# A central authority has decided to explicitly block or shutdown key infrastructure. (Eg, Egypt's recent internet blackout.)
# A zombie apocalypse in which the personnel responsible for maintaining key infrastructure have all been turned.

The project aims to develop and publish the necessary documentation, best practices, and software to construct and support such a system. Our current approach is to start by investigating and documenting the existing technologies which would support such a system. In particular, mesh networking protocols, wireless networking technologies, and decentralized (or less-centralized) alternatives to internet addressing/naming systems such as DNS. In designing the system, we aim to reduce the dependency on exotic hardware or skill sets so that the system can be deployed quickly and easily by average internet users.

An additional goal is that users not actively participating in the mesh network (i.e., not running mesh routing software on their devices) can make use of the network without having to install anything new, jailbreak their phone, or pry the information out of a hacker infected with the Exsurgent virus.

==Parts==
[[Byzantium_InterMesh|InterMesh]]
[[Byzantium_Distributed_DNS|Distributed DNS]]
[[Byzantium_Live_Distro|Live Distro]]

== Sprints ==
[[Byzantium Sprint 1|Sprint 1 Details]] [http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 Write up.]
[[Byzantium Sprint 2|Sprint 2 Details]] [http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 Write up.]
[[Byzantium Sprint 3|Sprint 3 Details]]
[[Byzantium Sprint 4|Sprint 4 Details]]
Individual sprint reports have been replaced with the [[Byzantium Action Log|Action Log]] since the sprints have become slightly less structured as we delve into the minutia of the project.

== Presentations and PR ==
[http://www.novalug.org/node/176 Ben and the Doctor will be presenting at NOVALUG!] - 14 May 2011
[http://contactcon.com/project-byzantium The Doctor will be presenting at ContactCon!] - 20 October 2011
[http://www.broadbandbridge.org/ Ben and the Doctor presented at DC Broadband Bridge!] - 5 November 2011 ([https://drwho.virtadpt.net/images/byzantium_presentation-20111105.pdf presentation])
[http://drwho.virtadpt.net/archive/2011/08/08/frequently-needed-answers-for-project-byzantium Unofficial Frequently Asked Questions.]
[http://www.hacdc.org/content/byzantium-v01a-scarab-released Release announcement for v0.1a!]
[https://drwho.virtadpt.net/archive/2012/04/30/hacdc-at-the-usa-science-and-engineering-festival Byzantium Linux was distributed and field tested at the USA Science and Engineering Festival!]
[https://drwho.virtadpt.net/archive/2012/04/20/not-dead-only-busy Project Byzantium will be presenting at CarolinaCon and HOPE Number Nine!]

== Press ==
[http://www.fastcompany.com/1750215/how-hackerspaces-can-do-good-for-the-world Fast Company: 28 April 2011]
[https://chronicle.com/article/College-20-Fear-of/129049/ College v2.0: Fear of Repression Spurs Scholars and Activists to Build Alternate Internets]
[http://www.shareable.net/blog/10-projects-to-liberate-the-web 10 Projects to Liberate the Web]
[http://blog.makezine.com/archive/2011/10/project-byzantium-aims-to-avoid-internet-outages.html Make Magazine]
[http://www.reddit.com/r/darknetplan/comments/l9tko/make_at_washington_dcs_hackerspace_hacdc_a_team/ Make article linked on /r/darknetplan]
[http://www.tendencias21.net/Ciberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Ciberactivistas crean un Internet alternativo por miedo a la represión] [http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=ISO-8859-1&layout=2&eotf=1&u=http%3A%2F%2Fwww.tendencias21.net%2FCiberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Google Translation]
[http://www.fastcoexist.com/1677951/hackerspaces-hubs-for-tech-minded-do-gooders Hackerspaces: Hubs for Tech-Minded do-Gooders?]
[http://www.disinfo.com/2012/03/interview-with-telecomix-hacktivists-peter-fein-and-the-doctor/ Interview with DisinfoTV at ContactCon]
[http://www.theglobalmail.org/feature/iran-not-tweeting-hacking/165/ Iran: Not Tweeting, Hacking]; Byzantium-related stuff near the end of the article, some inaccuracies.

[[Category:Ongoing_Projects]]

<DynamicPageList>
category = Byzantium
order = ascending
mode = inline
addfirstcategorydate = true
</DynamicPageList>

USA Science & Engineering Festival 2012

2012-04-28T04:14:36Z

Drwho: /* Misc Stuff To Bring */

[[Category:Events]]

HacDC has a 10x20 foot booth at the [http://www.usasciencefestival.org/ 2012 USA Science & Engineering Festival], in the National Robot Fest and DIY Expo area that has been organized by Gary Mauler.

== General Info ==

Here is a [http://c3067082.r82.cf0.rackcdn.com/2012ExpoMap_Printable_web_v4.pdf map and schedule] of the entire Festival.

Here is the [[media:USSF_Robot_Fest_Floor_Plan_4-18-12.pdf‎|floorplan]] of the Robotfest/DIY Expo area. We have booths 2250 + 2252.

Here are [[media:USASEF_Webinar_PPT.pdf|slides]] from the conference call where they discussed logistics like move-in and move-out rules.

== Who Will Be Going ==

List of people who will be going, when, and whether they can sit at the HacDC booth

* Tim Slagle, at booth Saturday, going Sunday with my kids
* David Kaufman, going Saturday and Sunday
* Mark Adams
* haxwithaxe as needed
* The Doctor, Saturday and Sunday
* Anderson Ta, @booth on Saturday all day
* Martin R, Saturday & Sunday
* Nick B, Friday, Saturday & Sunday
* David Whiteis, Sunday?

== Cart Transport ==

Exhibitors will be allowed to hand-carry in one trip worth of items for their booth. You must be able to carry it by yourself with no help from people or equipment (backpacks okay). Everything else will need to be brought in from the loading dock to our booth on a cart by Hargrove, the union drayage service. We have coupons for two 3'x5' cart-loads of stuff. They will unload the stuff from our vehicle and move it (by cart) to our booth, and then we would go set it up I suppose. If you will need to haul your stuff on a cart, please sign up here:

* '''Who, What, Size (WxLxH), When'''
* Tim Slagle, Plotter, 2.5x1.5x1 feet, Friday afternoon?
* Tim Slagle, LED Message Ball in box, 1.5x1.5x2', Friday afternoon?

'''Everything going by cart will need to be labelled with HacDC and our booth number, which is 2250.'''

== Projects On Display ==

If you'd like to show something at the 2012 USASEF, feel free to ad your project info to the list below. Do it soon so we can organize the transport setup and breakdown of the booth! For each project please list info like :
* Name of project
* Contact person
* Who will be at the booth and when
* Space needed
* Equipment required
* Supplies needed
* Completion status
* Project wiki page

=== Image Plotter ===

* Contact: TimS
* Booth people: TimS all day Saturday
* Space: 4 ft of table space for plotter and PC; wall space with white background for taking images with webcam
* Equipment: Windows PC or laptop, webcam and tripod, HP7550A plotter, maybe light source
* Supplies: Paper with HacDC info, plotter pens/ink
* Status: in development

=== Trippy Video Pong ===

* Contact: BradB
* Equipment: Fast PC running Linux, webcam, video projector
* Status: under development

=== SpaceBlimp ===
* Contact: Martin R
* Staff: Martin R Sat & Sun
* Space: 2 feet of table space
* Equipment: Laptop for displaying video, SB hardware display, poster
* Status: Poster in development
* Project Wiki: [http://wiki.hacdc.org/index.php/HacDC_Spaceblimp SpaceBlimp]

=== Byzantium ===
* Contact: haxwithaxe
* staff:
** haxwithaxe (as much as possible)
** The Doctor
* Space needed: none or space for small whiteboard
** Room to set up a mesh node would be nice.
* Equipment required: small whiteboard if space allows
* Supplies needed: CD-Rs and spare USBThumbdrives ahead of time
* Completion status: impending Beta
* Project wiki page: [[Byzantium|wiki]] [http://project-byzantium.org/ project site]

=== ShapeOko ===

* Contact: Mark Adams

=== Blinky Projects ===

* Contact: David Kaufman

=== 3D Printing ===

* Contact: Anderson Ta
* Staff: Anderson Ta, Saturday
* Space: 3 feet of table space for UP!
* Supplies: Roll of Plastic, Kinect/Tripod (if we are still scanning?), Power Strip

=== Signup Kiosk ===

* Contact: ITechGeek
* Staff: (not needed?)
* Space: 2 feet of table space
* Equipment: Computer, Keyboard, Mouse, and LCD monitor

=== Ring Bubble Generator ===

* Contact: David Whiteis
* Staff: David Whiteis Sunday
* Equipment: Water tank, pump
* Space: 14" wide for tank.
* Supplies: water for tank, power

== Misc Stuff To Bring ==

A list of stuff we will want to have at the booth. If you can bring it, please sign up with your name by the item. Personal items should have your name written on them in big letters so it can be returned to you easily.

* HacDC banner for table:
* HacDC postcards: Mark Adams
* HacDC brochures? (maybe we should save these since they will all get given away)
** I picked up a bunch at the 'space tonight. I'm bringing them with me. --DrWho
* HacDC stickers: DrWho
* Power strips (at least 4 needed): Tim Slagle
* Network switch and ethernet cables to hook up PCs together: Tim Slagle
* Extension cords (2-3 needed)
* Duct tape for taping down cords: Tim Slagle
* Big bowl of Dum Dums lollipops: Tim Slagle
* LED message ball: Tim Slagle
* HacDC Tip Jar (if allowed)

USA Science & Engineering Festival 2012

2012-04-26T16:12:33Z

Drwho: /* Byzantium */

[[Category:Events]]

HacDC has a 10x20 foot booth at the [http://www.usasciencefestival.org/ 2012 USA Science & Engineering Festival], in the National Robot Fest and DIY Expo area that has been organized by Gary Mauler.

== General Info ==

Here is a [http://c3067082.r82.cf0.rackcdn.com/2012ExpoMap_Printable_web_v4.pdf map and schedule] of the entire Festival.

Here is the [[media:USSF_Robot_Fest_Floor_Plan_4-18-12.pdf‎|floorplan]] of the Robotfest/DIY Expo area. We have booths 2250 + 2252.

Here are [[media:USASEF_Webinar_PPT.pdf|slides]] from the conference call where they discussed logistics like move-in and move-out rules.

== Who Will Be Going ==

List of people who will be going, when, and whether they can sit at the HacDC booth

* Tim Slagle, at booth Saturday, going Sunday with my kids
* David Kaufman, going Saturday and Sunday
* Mark Adams
* haxwithaxe as needed
* The Doctor, Saturday and Sunday
* Anderson Ta, @booth on Saturday all day
* Martin R, Saturday & Sunday
* Nick B, Friday, Saturday & Sunday
* David Whiteis, Sunday?

== Cart Transport ==

Exhibitors will be allowed to hand-carry in one trip worth of items for their booth. You must be able to carry it by yourself with no help from people or equipment (backpacks okay). Everything else will need to be brought in from the loading dock to our booth on a cart by Hargrove, the union drayage service. We have coupons for two 3'x5' cart-loads of stuff. They will unload the stuff from our vehicle and move it (by cart) to our booth, and then we would go set it up I suppose. If you will need to haul your stuff on a cart, please sign up here:

* '''Who, What, Size (WxLxH), When'''
* Tim Slagle, Plotter, 2.5x1.5x1 feet, Friday afternoon?
* Tim Slagle, LED Message Ball in box, 1.5x1.5x2', Friday afternoon?

'''Everything going by cart will need to be labelled with HacDC and our booth number, which is 2250.'''

== Projects On Display ==

If you'd like to show something at the 2012 USASEF, feel free to ad your project info to the list below. Do it soon so we can organize the transport setup and breakdown of the booth! For each project please list info like :
* Name of project
* Contact person
* Who will be at the booth and when
* Space needed
* Equipment required
* Supplies needed
* Completion status
* Project wiki page

=== Image Plotter ===

* Contact: TimS
* Booth people: TimS all day Saturday
* Space: 4 ft of table space for plotter and PC; wall space with white background for taking images with webcam
* Equipment: Windows PC or laptop, webcam and tripod, HP7550A plotter, maybe light source
* Supplies: Paper with HacDC info, plotter pens/ink
* Status: in development

=== Trippy Video Pong ===

* Contact: BradB
* Equipment: Fast PC running Linux, webcam, video projector
* Status: under development

=== SpaceBlimp ===
* Contact: Martin R
* Staff: Martin R Sat & Sun
* Space: 2 feet of table space
* Equipment: Laptop for displaying video, SB hardware display, poster
* Status: Poster in development
* Project Wiki: [http://wiki.hacdc.org/index.php/HacDC_Spaceblimp SpaceBlimp]

=== Byzantium ===
* Contact: haxwithaxe
* staff:
** haxwithaxe (as much as possible)
** The Doctor
* Space needed: none or space for small whiteboard
** Room to set up a mesh node would be nice.
* Equipment required: small whiteboard if space allows
* Supplies needed: CD-Rs and spare USBThumbdrives ahead of time
* Completion status: impending Beta
* Project wiki page: [[Byzantium|wiki]] [http://project-byzantium.org/ project site]

=== ShapeOko ===

* Contact: Mark Adams

=== Blinky Projects ===

* Contact: David Kaufman

=== 3D Printing ===

* Contact: Anderson Ta
* Staff: Anderson Ta, Saturday
* Space: 3 feet of table space for UP!
* Supplies: Roll of Plastic, Kinect/Tripod (if we are still scanning?), Power Strip

=== Signup Kiosk ===

* Contact: ITechGeek
* Staff: (not needed?)
* Space: 2 feet of table space
* Equipment: Computer, Keyboard, Mouse, and LCD monitor

=== Ring Bubble Generator ===

* Contact: David Whiteis
* Staff: David Whiteis Sunday
* Equipment: Water tank, pump
* Space: 14" wide for tank.
* Supplies: water for tank, power

== Misc Stuff To Bring ==

A list of stuff we will want to have at the booth. If you can bring it, please sign up with your name by the item. Personal items should have your name written on them in big letters so it can be returned to you easily.

* HacDC banner for table:
* HacDC postcards: Mark Adams
* HacDC brochures? (maybe we should save these since they will all get given away)
* Power strips (at least 4 needed): Tim Slagle
* Network switch and ethernet cables to hook up PCs together: Tim Slagle
* Extension cords (2-3 needed)
* Duct tape for taping down cords: Tim Slagle
* Big bowl of Dum Dums lollipops: Tim Slagle
* LED message ball: Tim Slagle
* HacDC Tip Jar (if allowed)

USA Science & Engineering Festival 2012

2012-04-25T14:34:56Z

Drwho: /* Who Will Be Going */

[[Category:Events]]

HacDC has a 10x20 foot booth at the [http://www.usasciencefestival.org/ 2012 USA Science & Engineering Festival], in the National Robot Fest and DIY Expo area that has been organized by Gary Mauler.

== General Info ==

Here is a [http://c3067082.r82.cf0.rackcdn.com/2012ExpoMap_Printable_web_v4.pdf map and schedule] of the entire Festival.

Here is the [[media:USSF_Robot_Fest_Floor_Plan_4-18-12.pdf‎|floorplan]] of the Robotfest/DIY Expo area.

Here are [[media:USASEF_Webinar_PPT.pdf|slides]] from the conference call where they discussed logistics like move-in and move-out rules.

== Who Will Be Going ==

List of people who will be going, when, and whether they can sit at the HacDC booth

* Tim Slagle, at booth Saturday, going Sunday with my kids
* David Kaufman, going Saturday and Sunday
* Mark Adams
* haxwithaxe as needed
* The Doctor, Saturday and Sunday
* Anderson Ta, @booth on Saturday all day
* Martin R, Saturday & Sunday
* Nick B, Friday, Saturday & Sunday
* David Whiteis, Sunday?

== Cart Transport ==

Exhibitors will be allowed to hand-carry in one trip worth of items for their booth. You must be able to carry it by yourself with no help from people or equipment (backpacks okay). Everything else will need to be brought in from the loading dock to our booth on a cart by the union drayage service. We have two 3'x5' four-wheeled carts available for moving stuff from the unloading areas into the booth. If you will need to haul your stuff on a cart, please sign up here:

* '''Who, What, Size (WxLxH), When'''
* Tim Slagle, Plotter, 2.5x1.5x1 feet, Friday afternoon?
* Tim Slagle, LED Message Ball in box, 1.5x1.5x2', Friday afternoon?

== Projects On Display ==

If you'd like to show something at the 2012 USASEF, feel free to ad your project info to the list below. Do it soon so we can organize the transport setup and breakdown of the booth! For each project please list info like :
* Name of project
* Contact person
* Who will be at the booth and when
* Space needed
* Equipment required
* Supplies needed
* Completion status
* Project wiki page

=== Image Plotter ===

* Contact: TimS
* Booth people: TimS all day Saturday
* Space: 4 ft of table space for plotter and PC; wall space with white background for taking images with webcam
* Equipment: Windows PC or laptop, webcam and tripod, HP7550A plotter, maybe light source
* Supplies: Paper with HacDC info, plotter pens/ink
* Status: in development

=== Trippy Video Pong ===

* Contact: BradB
* Equipment: Fast PC running Linux, webcam, video projector
* Status: under development

=== SpaceBlimp ===
* Contact: Martin R
* Staff: Martin R Sat & Sun
* Space: 2 feet of table space
* Equipment: Laptop for displaying video, SB hardware display, poster
* Status: Poster in development
* Project Wiki: [http://wiki.hacdc.org/index.php/HacDC_Spaceblimp SpaceBlimp]

=== Byzantium ===
* Contact: haxwithaxe
* staff: haxwithaxe (as much as possible)
* Space needed: none or space for small whiteboard
* Equipment required: small whiteboard if space allows
* Supplies needed: CD-Rs and spare USBThumbdrives ahead of time
* Completion status: impending Beta
* Project wiki page: [[Byzantium|wiki]] [http://project-byzantium.org/ project site]

=== ShapeOko ===

* Contact: Mark Adams

=== Blinky Projects ===

* Contact: David Kaufman

=== 3D Printing ===

* Contact: Anderson Ta
* Staff: Anderson Ta, Saturday
* Space: 3 feet of table space for UP!
* Supplies: Roll of Plastic, Kinect/Tripod (if we are still scanning?), Power Strip

=== Signup Kiosk ===

* Contact: ITechGeek
* Staff: (not needed?)
* Space: 2 feet of table space
* Equipment: Computer, Keyboard, Mouse, and LCD monitor

=== Ring Bubble Generator ===

* Contact: David Whiteis
* Staff: David Whiteis Sunday
* Equipment: Water tank, pump
* Space: 14" wide for tank.
* Supplies: water for tank, power

== Misc Stuff To Bring ==

A list of stuff we will want to have at the booth. If you can bring it, please sign up with your name by the item. Personal items should have your name written on them in big letters so it can be returned to you easily.

* HacDC postcards: Mark Adams
* HacDC brochures? (maybe we should save these since they will all get given away)
* Power strips (at least 4 needed): Tim Slagle
* Network switch and ethernet cables to hook up PCs together: Tim Slagle
* Extension cords (2-3 needed)
* Duct tape for taping down cords: Tim Slagle
* Big bowl of dum dums lollipops: Tim Slagle
* LED message ball: Tim Slagle
* HacDC Tip Jar (if allowed)

User:Drwho

2012-04-23T03:07:15Z

Drwho:

User:Drwho

2012-04-22T06:50:17Z

Drwho:

Name: Bryce A. Lynch
Handle: The Doctor [412/724/301/703]
Website: [http://drwho.virtadpt.net/ Antarctica Starts Here.]
PGP key: [http://drwho.virtadpt.net/gpgkey.txt 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1]

Likes
*Anonymity preserving technologies
*Bandwidth
*Blogging
*Books
*Chiptunes
*Cognitive liberty
*Constructive irrationality
*Cryptography
*Dancing
*Hacking
*Morphological freedom
*Music
*Neurology
*Privacy preserving technologies
*Programming
*RPGs
*Solitude
*Steampunk
*Transhumanism
*Writing

Dislikes:
*Dead batteries
*Faulty wetware
*Inferior organic components
*Stupidity
*Wasting time
*Wasting energy
*Surveillance

Projects:
*[[Byzantium | Project Byzantium]]
*Carved bone walking stick
*Hacking the [http://www.ocztechnology.com/products/ocz_peripherals/nia-neural_impulse_actuator OCZ Neural Impulse Actuator]
*RFID body jewelry
*Steampunk sonic screwdriver
*[http://zerostate.net/ The Zero State]

Notes:
*Shy. Slightly agoraphobic.
*Finally joined HacDC after four years.
*Thinks that the performance of an experiment is just as important as the results collected.
*[http://www.creativecommons.org/ Creative Commons] advocate.
*[http://eclipsephase.org Eclipse Phase] political faction: [https://secure.wikimedia.org/wikipedia/en/wiki/JASON_%28advisory_group%29 Argonaut]
*Rumored the be the illegitimate lovehild of Luna Lovegood and Wintermute.

Quotes:
*"Nothing says you can't."
*"Aw, hell."
*"Hey, ya'all, watch this!"
*"What did you say your username was again?"
*"We're now twenty minutes into the future. Unfortunately we got some ''Videodrome'' along with ''Max Headroom''."
*"I hate it when people use CamelCase in their code. It makes the statements read like Vanilla Ice lyrics."

[[Category:Friends]]

User Feedback on Byzantium 0.1a

2012-04-08T22:04:12Z

Drwho:

* DVD .iso boots fine, but I did see some boot errors flash past before X came up
* <strike>Looked for a desktop link or Control Panel entry to start Byzantium. Didn't find any.</strike>
* I found no clear How-To or Getting Started documentation on how to get Byzantium Meshes up and running here on the Wiki or as part of the distro. Eventually found this post about running it from a USB stick http://metropioneer.com/meshnet/Bootable_USB_Stick_How-To.txt
* <strike>It would be good if Firefox opens by default to http://locahost:8080 so it is obvious for a newbie on where he has to go to configure the mesh</strike>
* <strike>The "System Status" page is basically useless as it seems to say nothing about the current mesh status.</strike>
**<strike>It is not obvious what is the status of the network i.e. ESID and channel that the network is using, and whether or not it is configured. Some wlan info here would be extremely helpful.</strike>
**It is not obvious what is the status of the mesh, i.e. is it configured or not, what IP addresses are being used, how many peers have been found. Some ifconfig info here would be extremely helpful.
**We never got around to configuring any mesh services.
*Trouble keeping an ad hoc WiFi connection to the Byzantium mesh.
**The laptops were all sitting next to each other and we were using a channel which was not being used by any other APs.
**<strike>Windows 7 and Windows XP had would take a long time (minutes) before it was working, then disconnect after a while.</strike>
**<strike>An Ubuntu netbook WiFi client seems to be a bit more reliable.</strike>
**An HTC Desire couldn't see the ad hoc network
**<strike>An iPhone 4 did seem to work.</strike>
*Also booted Byzantium in a Virtual Machine (VM)
**It would be great if there was a way to run a emulated mesh node in a VM for test and demo purposes. However, a VM can't expose or manage the host Operating System's WiFi.
***It could, actually - VirtualBox's USB passthrough functionality could expose wi-fi keys to virtual machines.
**Perhaps some sort of WiFi emulation layer that could run on eth0 inside the VM?
**It would then be comparatively easy to spin up say 100 VM mesh nodes, and see if the routing protocol scales.
***We're planning on doing a BattleMesh DC soon (v0.3? v0.4?)

{{Template:Byzantium}}

Byzantium

2012-04-02T13:54:55Z

Drwho: /* Press */

This project was launched with a sprint on Feb 25-27, 2011.
Sprints will be held the last weekend of every month.

The development wiki page is [[Byzantium_Live_Distro|here]].

The official mailing list is [http://groups.google.com/a/hacdc.org/group/Byzantium/?hl=en here].

The official Github organization page is [https://github.com/Byzantium/Byzantium here].

'''NOTICE: If you've downloaded Byzantium v0.1a, you need to re-download it immediately due to a major bug in the 10 January 2012 release! This is critical!'''
[[Downloading_Byzantium|Where to download Byzantium.]]

== Project Goals ==
The goal of Project Byzantium is to develop a communication system by which users can connect to each other and share information in the absence of convenient access to the Internet.

The use cases for such a system would be:
# The infrastructure for accessing the internet has become damaged or inaccessible. (Eg, a natural disaster such as Hurricane Katrina.)
# A central authority has decided to explicitly block or shutdown key infrastructure. (Eg, Egypt's recent internet blackout.)
# A zombie apocalypse in which the personnel responsible for maintaining key infrastructure have all been turned.

The project aims to develop and publish the necessary documentation, best practices, and software to construct and support such a system. Our current approach is to start by investigating and documenting the existing technologies which would support such a system. In particular, mesh networking protocols, wireless networking technologies, and decentralized (or less-centralized) alternatives to internet addressing/naming systems such as DNS. In designing the system, we aim to reduce the dependency on exotic hardware or skill sets so that the system can be deployed quickly and easily by average internet users.

An additional goal is that users not actively participating in the mesh network (i.e., not running mesh routing software on their devices) can make use of the network without having to install anything new, jailbreak their phone, or pry the information out of a hacker infected with the Exsurgent virus.

==Parts==
[[Byzantium_InterMesh|InterMesh]]
[[Byzantium_Distributed_DNS|Distributed DNS]]
[[Byzantium_Live_Distro|Live Distro]]

== Sprints ==
[[Byzantium Sprint 1|Sprint 1 Details]] [http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 Write up.]
[[Byzantium Sprint 2|Sprint 2 Details]] [http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 Write up.]
[[Byzantium Sprint 3|Sprint 3 Details]]
[[Byzantium Sprint 4|Sprint 4 Details]]
Individual sprint reports have been replaced with the [[Byzantium Action Log|Action Log]] since the sprints have become slightly less structured as we delve into the minutia of the project.

== Presentations and PR ==
[http://www.novalug.org/node/176 Ben and the Doctor will be presenting at NOVALUG!] - 14 May 2011
[http://contactcon.com/project-byzantium The Doctor will be presenting at ContactCon!] - 20 October 2011
[http://www.broadbandbridge.org/ Ben and the Doctor presented at DC Broadband Bridge!] - 5 November 2011 ([https://drwho.virtadpt.net/images/byzantium_presentation-20111105.pdf presentation])
[http://drwho.virtadpt.net/archive/2011/08/08/frequently-needed-answers-for-project-byzantium Unofficial Frequently Asked Questions.]
[http://www.hacdc.org/content/byzantium-v01a-scarab-released Release announcement for v0.1a!]

== Press ==
[http://www.fastcompany.com/1750215/how-hackerspaces-can-do-good-for-the-world Fast Company: 28 April 2011]
[https://chronicle.com/article/College-20-Fear-of/129049/ College v2.0: Fear of Repression Spurs Scholars and Activists to Build Alternate Internets]
[http://www.shareable.net/blog/10-projects-to-liberate-the-web 10 Projects to Liberate the Web]
[http://blog.makezine.com/archive/2011/10/project-byzantium-aims-to-avoid-internet-outages.html Make Magazine]
[http://www.reddit.com/r/darknetplan/comments/l9tko/make_at_washington_dcs_hackerspace_hacdc_a_team/ Make article linked on /r/darknetplan]
[http://www.tendencias21.net/Ciberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Ciberactivistas crean un Internet alternativo por miedo a la represión] [http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=ISO-8859-1&layout=2&eotf=1&u=http%3A%2F%2Fwww.tendencias21.net%2FCiberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Google Translation]
[http://www.fastcoexist.com/1677951/hackerspaces-hubs-for-tech-minded-do-gooders Hackerspaces: Hubs for Tech-Minded do-Gooders?]
[http://www.disinfo.com/2012/03/interview-with-telecomix-hacktivists-peter-fein-and-the-doctor/ Interview with DisinfoTV at ContactCon]
[http://www.theglobalmail.org/feature/iran-not-tweeting-hacking/165/ Iran: Not Tweeting, Hacking]; Byzantium-related stuff near the end of the article, some inaccuracies.

Byzantium

2012-04-02T13:50:41Z

Drwho: /* Press */

This project was launched with a sprint on Feb 25-27, 2011.
Sprints will be held the last weekend of every month.

The development wiki page is [[Byzantium_Live_Distro|here]].

The official mailing list is [http://groups.google.com/a/hacdc.org/group/Byzantium/?hl=en here].

The official Github organization page is [https://github.com/Byzantium/Byzantium here].

'''NOTICE: If you've downloaded Byzantium v0.1a, you need to re-download it immediately due to a major bug in the 10 January 2012 release! This is critical!'''
[[Downloading_Byzantium|Where to download Byzantium.]]

== Project Goals ==
The goal of Project Byzantium is to develop a communication system by which users can connect to each other and share information in the absence of convenient access to the Internet.

The use cases for such a system would be:
# The infrastructure for accessing the internet has become damaged or inaccessible. (Eg, a natural disaster such as Hurricane Katrina.)
# A central authority has decided to explicitly block or shutdown key infrastructure. (Eg, Egypt's recent internet blackout.)
# A zombie apocalypse in which the personnel responsible for maintaining key infrastructure have all been turned.

The project aims to develop and publish the necessary documentation, best practices, and software to construct and support such a system. Our current approach is to start by investigating and documenting the existing technologies which would support such a system. In particular, mesh networking protocols, wireless networking technologies, and decentralized (or less-centralized) alternatives to internet addressing/naming systems such as DNS. In designing the system, we aim to reduce the dependency on exotic hardware or skill sets so that the system can be deployed quickly and easily by average internet users.

An additional goal is that users not actively participating in the mesh network (i.e., not running mesh routing software on their devices) can make use of the network without having to install anything new, jailbreak their phone, or pry the information out of a hacker infected with the Exsurgent virus.

==Parts==
[[Byzantium_InterMesh|InterMesh]]
[[Byzantium_Distributed_DNS|Distributed DNS]]
[[Byzantium_Live_Distro|Live Distro]]

== Sprints ==
[[Byzantium Sprint 1|Sprint 1 Details]] [http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 Write up.]
[[Byzantium Sprint 2|Sprint 2 Details]] [http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 Write up.]
[[Byzantium Sprint 3|Sprint 3 Details]]
[[Byzantium Sprint 4|Sprint 4 Details]]
Individual sprint reports have been replaced with the [[Byzantium Action Log|Action Log]] since the sprints have become slightly less structured as we delve into the minutia of the project.

== Presentations and PR ==
[http://www.novalug.org/node/176 Ben and the Doctor will be presenting at NOVALUG!] - 14 May 2011
[http://contactcon.com/project-byzantium The Doctor will be presenting at ContactCon!] - 20 October 2011
[http://www.broadbandbridge.org/ Ben and the Doctor presented at DC Broadband Bridge!] - 5 November 2011 ([https://drwho.virtadpt.net/images/byzantium_presentation-20111105.pdf presentation])
[http://drwho.virtadpt.net/archive/2011/08/08/frequently-needed-answers-for-project-byzantium Unofficial Frequently Asked Questions.]
[http://www.hacdc.org/content/byzantium-v01a-scarab-released Release announcement for v0.1a!]

== Press ==
[http://www.fastcompany.com/1750215/how-hackerspaces-can-do-good-for-the-world Fast Company: 28 April 2011]
[https://chronicle.com/article/College-20-Fear-of/129049/ College v2.0: Fear of Repression Spurs Scholars and Activists to Build Alternate Internets]
[http://www.shareable.net/blog/10-projects-to-liberate-the-web 10 Projects to Liberate the Web]
[http://blog.makezine.com/archive/2011/10/project-byzantium-aims-to-avoid-internet-outages.html Make Magazine]
[http://www.reddit.com/r/darknetplan/comments/l9tko/make_at_washington_dcs_hackerspace_hacdc_a_team/ Make article linked on /r/darknetplan]
[http://www.tendencias21.net/Ciberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Ciberactivistas crean un Internet alternativo por miedo a la represión] [http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=ISO-8859-1&layout=2&eotf=1&u=http%3A%2F%2Fwww.tendencias21.net%2FCiberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Google Translation]
[http://www.fastcoexist.com/1677951/hackerspaces-hubs-for-tech-minded-do-gooders Hackerspaces: Hubs for Tech-Minded do-Gooders?]
[http://www.disinfo.com/2012/03/interview-with-telecomix-hacktivists-peter-fein-and-the-doctor/ Interview with DisinfoTV at ContactCon]
[http://www.theglobalmail.org/feature/iran-not-tweeting-hacking/165/ Iran: Not Tweeting, Hacking]

Process for manually installing Byzantium.

2012-03-31T21:15:47Z

Drwho: Added some more packages to the list of things required by Byzantium.

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** boost
** celt
** CherryPy
** cryptoki
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mumble
** mysql
** ngircd
** node
** pcre
** php
** protobuf
** pysetuptools
** python-twisted
** qt
** rrdtool
** speex
** sudo
** truecrypt
** t1lib
** vim
** wxGTK
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Process for manually installing Byzantium.

2012-03-31T21:02:16Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* Check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** chmod -x /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall
*** Note: This is actually a bug in Porteus v1.1. If you look at the contents of /etc/rc.d/rc.inet2, it won't actually be able to run this script. Don't worry about it.

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Byzantium

2012-03-20T12:36:19Z

Drwho:

This project was launched with a sprint on Feb 25-27, 2011.
Sprints will be held the last weekend of every month.

The development wiki page is [[Byzantium_Live_Distro|here]].

The official mailing list is [http://groups.google.com/a/hacdc.org/group/Byzantium/?hl=en here].

The official Github organization page is [https://github.com/Byzantium/Byzantium here].

'''NOTICE: If you've downloaded Byzantium v0.1a, you need to re-download it immediately due to a major bug in the 10 January 2012 release! This is critical!'''
[[Downloading_Byzantium|Where to download Byzantium.]]

== Project Goals ==
The goal of Project Byzantium is to develop a communication system by which users can connect to each other and share information in the absence of convenient access to the Internet.

The use cases for such a system would be:
# The infrastructure for accessing the internet has become damaged or inaccessible. (Eg, a natural disaster such as Hurricane Katrina.)
# A central authority has decided to explicitly block or shutdown key infrastructure. (Eg, Egypt's recent internet blackout.)
# A zombie apocalypse in which the personnel responsible for maintaining key infrastructure have all been turned.

The project aims to develop and publish the necessary documentation, best practices, and software to construct and support such a system. Our current approach is to start by investigating and documenting the existing technologies which would support such a system. In particular, mesh networking protocols, wireless networking technologies, and decentralized (or less-centralized) alternatives to internet addressing/naming systems such as DNS. In designing the system, we aim to reduce the dependency on exotic hardware or skill sets so that the system can be deployed quickly and easily by average internet users.

An additional goal is that users not actively participating in the mesh network (i.e., not running mesh routing software on their devices) can make use of the network without having to install anything new, jailbreak their phone, or pry the information out of a hacker infected with the Exsurgent virus.

==Parts==
[[Byzantium_InterMesh|InterMesh]]
[[Byzantium_Distributed_DNS|Distributed DNS]]
[[Byzantium_Live_Distro|Live Distro]]

== Sprints ==
[[Byzantium Sprint 1|Sprint 1 Details]] [http://drwho.virtadpt.net/archive/2011/03/15/project-byzantium-sprint-1 Write up.]
[[Byzantium Sprint 2|Sprint 2 Details]] [http://drwho.virtadpt.net/archive/2011/04/14/project-byzantium-development-sprint-2 Write up.]
[[Byzantium Sprint 3|Sprint 3 Details]]
[[Byzantium Sprint 4|Sprint 4 Details]]
Individual sprint reports have been replaced with the [[Byzantium Action Log|Action Log]] since the sprints have become slightly less structured as we delve into the minutia of the project.

== Presentations and PR ==
[http://www.novalug.org/node/176 Ben and the Doctor will be presenting at NOVALUG!] - 14 May 2011
[http://contactcon.com/project-byzantium The Doctor will be presenting at ContactCon!] - 20 October 2011
[http://www.broadbandbridge.org/ Ben and the Doctor presented at DC Broadband Bridge!] - 5 November 2011 ([https://drwho.virtadpt.net/images/byzantium_presentation-20111105.pdf presentation])
[http://drwho.virtadpt.net/archive/2011/08/08/frequently-needed-answers-for-project-byzantium Unofficial Frequently Asked Questions.]
[http://www.hacdc.org/content/byzantium-v01a-scarab-released Release announcement for v0.1a!]

== Press ==
[http://www.fastcompany.com/1750215/how-hackerspaces-can-do-good-for-the-world Fast Company: 28 April 2011]
[https://chronicle.com/article/College-20-Fear-of/129049/ College v2.0: Fear of Repression Spurs Scholars and Activists to Build Alternate Internets]
[http://www.shareable.net/blog/10-projects-to-liberate-the-web 10 Projects to Liberate the Web]
[http://blog.makezine.com/archive/2011/10/project-byzantium-aims-to-avoid-internet-outages.html Make Magazine]
[http://www.reddit.com/r/darknetplan/comments/l9tko/make_at_washington_dcs_hackerspace_hacdc_a_team/ Make article linked on /r/darknetplan]
[http://www.tendencias21.net/Ciberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Ciberactivistas crean un Internet alternativo por miedo a la represión] [http://translate.google.com/translate?sl=auto&tl=en&js=n&prev=_t&hl=en&ie=ISO-8859-1&layout=2&eotf=1&u=http%3A%2F%2Fwww.tendencias21.net%2FCiberactivistas-crean-un-Internet-alternativo-por-miedo-a-la-represion_a7640.html Google Translation]
[http://www.fastcoexist.com/1677951/hackerspaces-hubs-for-tech-minded-do-gooders Hackerspaces: Hubs for Tech-Minded do-Gooders?]
[http://www.disinfo.com/2012/03/interview-with-telecomix-hacktivists-peter-fein-and-the-doctor/ Interview with DisinfoTV at ContactCon]

Process for manually installing Byzantium.

2012-03-08T02:11:16Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* chown -R guest:guest /tmp/fakeroot/home/guest

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

User Feedback on Byzantium 0.1a

2012-03-08T01:24:06Z

Drwho:

* DVD .iso boots fine, but I did see some boot errors flash past before X came up
* <strike>Looked for a desktop link or Control Panel entry to start Byzantium. Didn't find any.</strike>
* I found no clear How-To or Getting Started documentation on how to get Byzantium Meshes up and running here on the Wiki or as part of the distro. Eventually found this post about running it from a USB stick http://metropioneer.com/meshnet/Bootable_USB_Stick_How-To.txt
* <strike>It would be good if Firefox opens by default to http://locahost:8080 so it is obvious for a newbie on where he has to go to configure the mesh</strike>
* The "System Status" page is basically useless as it seems to say nothing about the current mesh status.
**It is not obvious what is the status of the network i.e. ESID and channel that the network is using, and whether or not it is configured. Some wlan info here would be extremely helpful.
**It is not obvious what is the status of the mesh, i.e. is it configured or not, what IP addresses are being used, how many peers have been found. Some ifconfig info here would be extremely helpful.
**We never got around to configuring any mesh services.
*Trouble keeping an ad hoc WiFi connection to the Byzantium mesh.
**The laptops were all sitting next to each other and we were using a channel which was not being used by any other APs.
**Windows 7 and Windows XP had would take a long time (minutes) before it was working, then disconnect after a while.
**An Ubuntu netbook WiFi client seems to be a bit more reliable.
**An HTC Desire couldn't see the ad hoc network
**An iPhone 4 did seem to work.
*Also booted Byzantium in a Virtual Machine (VM)
**It would be great if there was a way to run a emulated mesh node in a VM for test and demo purposes. However, a VM can't expose or manage the host Operating System's WiFi
**Perhaps some sort of WiFi emulation layer that could run on eth0 inside the VM?
**It would then be comparatively easy to spin up say 100 VM mesh nodes, and see if the routing protocol scales.

Process for manually installing Byzantium.

2012-03-04T20:05:13Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/
* mkdir -p /tmp/fakeroot/home/guest/Desktop
* cp porteus/home/guest/Desktop/Control\ Panel.desktop /tmp/fakeroot/home/guest/Desktop
* mkdir -p /tmp/fakeroot/usr/share/pixmaps/porteus
* cp byzantium-logo.png /tmp/fakeroot/usr/share/pixmaps/porteus

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Process for manually installing Byzantium.

2012-03-04T04:41:52Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* mkdir -p /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp home/guest/.mozilla/firefox/c3pp43bg.default/prefs.js /tmp/fakeroot/home/guest/.mozilla/firefox/c3pp43bg.default
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Process for manually installing Byzantium.

2012-03-04T04:37:25Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* cp etc/HOSTNAME /tmp/fakeroot/etc
* cp etc/inittab /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Downloading Byzantium

2012-03-03T16:14:53Z

Drwho: Added the TPB link, cleaned up links to other download sites, added the PGP signature on my mirror.

[http://byzantium.virtadpt.net/byzantium.pubkey Byzantium Project] public PGP key.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1" cellpadding="5"
!Version
!Codename
!Released
!Fitness*
!Torrent
!Direct DL
!PGPSign
!Comments
|-
|0.1a
|Scarab
|2012/01/11
|0
|
*[http://linuxtracker.org/download.php?id=fcc7607270ba48897ff865ed5361013554a659eb&f=Byzantium%20Linux%20v0.1a.torrent Linux Tracker]
*[https://thepiratebay.se/torrent/7074687 The Pirate Bay]
|
* [http://linuxfreedom.com/byzantium Linux Freedom]
* [http://byzantium.virtadpt.net/v0.1a/ byzantium.virtadpt.net]
* [https://s3.amazonaws.com/byzantium/byzantium-curent.iso haxwithaxe's S3]
|
*[https://s3.amazonaws.com/byzantium/byzantium-current.iso.asc haxwithaxe's S3]
*[http://byzantium.virtadpt.net/v0.1a/byzantium-v0.1a.iso.asc byzantium.virtadpt.net]
|
*current version.
*EXTREME ALPHA!!
*focusing on functionality ''NOT security''
|-
|}
`*Fitness is a score from 0 to 5 indicating the fitness of a release for use as an '''Emergency''' networking aid. Do not let this put you off downloading it to try it out or help us by finding and reporting bug and feature requests. In order to make it to a level 5 fitness we need as many people to use it as possible so we are more likely to find bugs before they end up causing trouble for people who expect our livedistro to work in an emergency.
*0 = completely unfit (likely to do more harm than good in any emergency)
*1 = still mostly unfit (unless you are an active developer on the project you won't likely benefit from this in an emergency)
*2 = works well enough to provide basic connectivity with minimal configuration. (yeh! we're a little bit fit now! which is not to say we're fit enough to run a marathon, so don't expect to be able to do much without a regular internet connection or some sysadmin skills)
*3 = in addition to qualifying for level 2 fitness this has basic intermesh services like a built in chat server, microblog server and similar user oriented services ready to run with minimal configuration. (still needs a service to tell other mesh users and end users about the services on the mesh, aka our DNSless service distribution).
*4 = fully featured and works well enough to be used in friendly network conditions (you aren't in jeopardy of getting arrested/attacked for using it for things that are considered legal where you are using it)
*5 = fully featured and setup with best effort secure defaults and possibly other security features (this by no means should suggest that it is safe to use in an environment where there is a government or government like entity is actively trying to suppress network connectivity by means other than denial standard network connectivity)
*6 = if we find the magic sauce that can make it super hard to find users if you aren't a user and reasonably impossible to detect or decrypt traffic not sent to you, then you will see this magic number as the fitness score. Until then it is the metaphorical unicorn. It doesn't exist.
You may have noticed that the fitness list doesn't ever say it's safe to use in a hostile network. That's because it won't likely ever be safe to use in a hostile network. The best we can do is to set reasonably secure defaults and policies and try to educate users on internet hygiene so they don't let people rub malware in their face if they go someplace we can't protect them.

Packaging NPM

2012-02-25T23:03:54Z

Drwho:

* Ensure that [http://nodejs.org/ node.js] is installed and operable.
** Note that it is necessary to install node.js and npm on the build system to build the packages.** Download the latest .tar.gz tarball of the node.js source code.
** '''cd /tmp'''
** '''tar xvfz /path/to/node-vx.y.z.tar.gz'''
** '''cd node-vx.y.z'''
** '''./configure -p --prefix=/usr'''
** '''make'''
** '''make test'''
** '''make install DESTDIR=/tmp/nodejs-vx.y.z'''
** '''dir2xzm /tmp/nodejs-vx.y.z /tmp/node-x.y.z.xzm'''
* Download the source to npm [https://github.com/isaacs/npm/zipball/master from Github].
* '''unzip isaacs-npm-...zip'''
* '''cd isaacs-npm-...'''
* '''make'''
* '''make install'''
** '''mkdir -p /tmp/npm-x.y.z/usr'''
** '''export npm_config_userconfig=./npmrc'''
** '''node cli.js config set cache /tmp/npm-cache'''
** '''node cli.js config set prefix /tmp/npm-x.y.z/usr'''
** '''node cli.js config set unsafe-perm true'''
** '''node cli.js install -g .'''
** '''dir2xzm /tmp/npm-x.y.z /tmp/npm-x.y.z.xzm'''
* Everything goes in ''/usr/lib/mode_modules/npm''.
* ''/usr/bin/npm*'' are symlinked to ''/usr/lib/mode_modules/npm/bin/npm.js''.

Packaging NPM

2012-02-25T23:00:13Z

Drwho:

* Ensure that [http://nodejs.org/ node.js] is installed and operable.
** Note that it is necessary to install node.js and npm on the build system to build the packages.** Download the latest .tar.gz tarball of the node.js source code.
** '''cd /tmp'''
** '''tar xvfz /path/to/node-vx.y.z.tar.gz'''
** '''cd node-vx.y.z'''
** '''./configure -p --prefix=/usr'''
** '''make'''
** '''make test'''
** '''make install DESTDIR=/tmp/nodejs-vx.y.z'''
** ''dir2xzm /tmp/nodejs-vx.y.z /tmp/node-x.y.z.xzm'''
* Download the source to npm [https://github.com/isaacs/npm/zipball/master from Github]
* '''unzip isaacs-npm-...zip'''
* '''cd isaacs-npm-...'''
* '''make'''
* '''make install'''
** '''mkdir -p /tmp/npm-x.y.z/usr'''
** '''export npm_config_userconfig=./npmrc'''
** '''node cli.js config set cache /tmp/npm-cache'''
** '''node cli.js config set prefix /tmp/npm-x.y.z/usr'''
** '''node cli.js config set unsafe-perm true'''
** '''node cli.js install -g .'''
** ''dir2xzm /tmp/npm-x.y.z /tmp/npm-x.y.z.xzm'''
* Everything goes in /usr/lib/mode_modules/npm
* /usr/bin/npm* are symlinked to /usr/lib/mode_modules/npm/bin/npm.js

Packaging NPM

2012-02-25T21:59:06Z

Drwho:

* Ensure that [http://nodejs.org/ node.js] is installed and operable.
** Download the latest .tar.gz tarball of the node.js source code.
** '''cd /tmp'''
** '''tar xvfz /path/to/node-vx.y.z.tar.gz'''
** '''cd node-vx.y.z'''
** '''./configure -p --prefix=/usr'''
** '''make'''
** '''make install DESTDIR=/tmp/nodejs-vx.y.z'''
* Download npm: '''wget http://npmjs.org/install.sh'''
* '''mv install.sh npm-install.sh'''
* '''sh ./npm-install.sh''' (as root)
* Everything goes in /usr/lib/mode_modules/npm
* /usr/bin/npm* symlinked to /usr/lib/mode_modules/npm/bin/npm.js

Packaging NPM

2012-02-25T21:51:31Z

Drwho:

* Ensure that [http://nodejs.org/ node.js] is installed and operable.
** Download the latest .tar.gz tarball of the node.js source code.
** '''cd /tmp'''
** '''tar xvfz /path/to/node-vx.y.z.tar.gz'''
** '''cd node-vx.y.z'''
** '''./configure -p'''
** '''make'''
** '''make install DESTDIR=/tmp/nodejs-vx.y.z'''
* Download npm: '''wget http://npmjs.org/install.sh'''
* '''mv install.sh npm-install.sh'''
* '''sh ./npm-install.sh''' (as root)
* Everything goes in /usr/lib/mode_modules/npm
* /usr/bin/npm* symlinked to /usr/lib/mode_modules/npm/bin/npm.js

Process for manually installing Byzantium.

2012-02-25T21:28:37Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Process for manually installing Byzantium.

2012-02-25T21:20:37Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* cp etc/hosts /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* mkdir -p /tmp/fakeroot/tmp/fakeroot/usr/local/sbin
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Process for manually installing Byzantium.

2012-02-25T21:16:33Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* mkdir -p /tmp/fakeroot/usr/local/sbin
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* mkdir -p /tmp/fakeroot/tmp/fakeroot/usr/local/sbin
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Process for manually installing Byzantium.

2012-02-25T21:09:46Z

Drwho:

This process assumes:
* You've booted a clean copy of Porteus Linux v1.0 or later.
* You've checked the Porteus .xzm modules we built for Byzantium out of SVN into ~/byzantium.
** apr
** apr-util
** babeld
** CherryPy
** curl
** dnsmasq
** doxygen
** gd
** httpd
** icu4c
** ifplugd
** irssi
** libarchive
** libdaemon
** libmcrypt
** locales-en_US
** Mako
** MarkupSafe
** mysql
** ngircd
** node
** pcre
** php
** pysetuptools
** python-twisted
** rrdtool
** sudo
** t1lib
** vim
** zope.interface
** settings.xzm (don't forget this!)
* You've checked the source tree for Byzantium out of the Git repository.

The process of installing Byzantium has not been automated yet. These notes should be used in the development of the official installer, at least until we get the official byzantium.xzm module built. I get the feeling that it's going to be pretty big because we're going to have to package all of the dependencies along with it for efficiency's sake (at least, that's what Ben the Pyrate says because he's messed around with union mounts more than I).

Gotchas:
* On first boot, syslinux might complain that it can't find video mode number 317. Entering the hex value "F00" (text mode, 80x25) will get around this.
** At boot, you can also edit the kernel command line and change the value '791' to 'F00' prior to booting. We should make this the default.
* If the USB device is formatted with a non-Linux file system, you will see the error "A Windows Filesystem (FAT, NTFS) or other non-posix compatible filesystem has been detected on /porteus/." If you intend on creating a save.dat file, you can press 'enter' and ignore it. Or, you can format the key with a Linux file system (/EXT[1-4]/, XFS) prior to [http://porteus.org/info/docs/37-installing/114-official-porteus-installation-guide-v-10.html installing Porteus].
* On boot, Porteus Linux will mount all of the file systems it can see on the host machine. Use caution when deleting or copying files!
* '''IMPORTANT''': If your USB key is formatted with one of the FAT filesystems, you CANNOT create a persistent storage file larger than 1GB! Otherwise, you will get errors at boot-time about a missing persistent storage file! '''Set the slider no larger than 1024MB!'''
* /etc/rc.d/rc.sshd is set mode -x by default but /etc/rc.d/rc.local sets it +x so that it can be managed by the control panel. It's not executed by default, though.

These commands can be run as guest (which is logged in by default):
* The [http://wicd.sourceforge.net/ wicd] applet on the toolbar works well for setting up wireless. It's also polite enough to get out of your way once it's done. Use it to get online.
* Open Firefox and download all of the modules from [http://svn.virtadpt.net/byzantium http://svn.virtadpt.net/byzantium]. Put everything in /dev/sdb1/porteus/modules to save time and space
** It will probably be /dev/sdb if you have only one drive in the host machine.
** You will need to install the git package as well to check out the Byzantium source tree.
* Set up a persistent storage file:
** Porteus Menu -> System -> Porteus save.dat manager
** Create a new save.dat file
** Enter a filename for the persistent storage file (I like 'save' - the manager will automagically add the '.dat' extension).
** Navigate to /mnt/sdb1/porteus - this is where save.dat will go.
** The manager will confirm the location - say 'yes'.
** Select a size for the save.dat file (see the above note!)
** Wait. This can take a while. USB v2.0 isn't very fast...
** When next that USB key is booted, hit the 'tab' key to edit the kernel command line and change the 'changes=' bit to read 'changes=/mnt/sdb1/porteus/save.dat'
** Reboot.
* After rebooting, set up your network connection with wicd again, because there wasn't a way to save it before.
* After rebooting, check out the [https://github.com/Byzantium/Byzantium.git Byzantium source repository]:
** git clone https://github.com/Byzantium/Byzantium.git

All of these commands must be run as root. You should do an `su -` here and get it over with. This process assumes that a Porteus module (000-byzantium.xzm) will be created.
* cd /path/to/xzm/modules
* for i in *.xzm; do xzm2dir $i /tmp/fakeroot ; done
* rm /tmp/fakeroot/srv/httpd
* rm /tmp/fakeroot/srv/www
* mkdir -p /tmp/fakeroot/srv/httpd/databases
* cd /tmp/fakeroot/srv
* ln -s httpd www
* mkdir -p /tmp/fakeroot/srv/controlpanel/graphs
* cp -rv ~guest/Byzantium/control_panel/srv/controlpanel/* /tmp/fakeroot/srv/controlpanel
* mkdir /tmp/fakeroot/etc/controlpanel
* cp ~guest/Byzantium/control_panel/etc/controlpanel/* /tmp/fakeroot/etc/controlpanel
* mkdir -p /tmp/fakeroot/var/db/controlpanel
* cp -rv ~guest/Byzantium/control_panel/var/db/controlpanel/* /tmp/fakeroot/var/db/controlpanel
* mkdir -p /tmp/fakeroot/usr/share/wicd/cli
* cp ~guest/Byzantium/porteus/wicd/usr/share/wicd/cli/wicd-cli.py /tmp/fakeroot/usr/share/wicd/cli/
* cd ~guest/Byzantium/scripts
* mkdir -p /tmp/fakeroot/etc/udev/rules.d
* cp 11-media-by-label-auto-mount.rules /tmp/fakeroot/etc/udev/rules.d
* '''Where do the [pre,post]-disk-mount scripts go?''' --DrWho
* cp rc.local rc.mysqld rc.ssl rc.setup_mysql /tmp/fakeroot/etc/rc.d
* chmod +x /tmp/fakeroot/etc/rc.d/rc.*
* cp traffic_stats.sh /tmp/fakeroot/usr/local/bin
* cd ../control_panel
* cp *.py /tmp/fakeroot/usr/local/sbin
* cp etc/rc.d/rc.byzantium /tmp/fakeroot/etc/rc.d/
* mkdir -p /tmp/fakeroot/etc/ssl
* cp etc/ssl/openssl.cnf /tmp/fakeroot/etc/ssl
* cd ../porteus
* cp -rv apache/etc/httpd/* /tmp/fakeroot/etc/httpd
* cp babel/babeld.conf /tmp/fakeroot/etc
* cp dnsmasq/dnsmasq.conf /tmp/fakeroot/etc
* cp etherpad-lite/rc.etherpad-lite /tmp/fakeroot/etc/rc.d
* cp -rv ifplugd/etc/ifplugd/* /tmp/fakeroot/etc/ifplugd
* cp etc/passwd /tmp/fakeroot/etc
* cp etc/shadow /tmp/fakeroot/etc
* chown root:root /tmp/fakeroot/etc/passwd /tmp/fakeroot/etc/shadow
* chmod 0600 /tmp/fakeroot/etc/shadow
* cp mysql/my.cnf /tmp/fakeroot/etc
* cp ngircd/ngircd.conf /tmp/fakeroot/etc
* cp ngircd/rc.ngircd /tmp/fakeroot/etc/rc.d
* cp php/etc/httpd/php.ini /tmp/fakeroot/etc/httpd
* mkdir -p /tmp/fakeroot/opt/qwebirc
* cp qwebirc/config.py /tmp/fakeroot/opt/qwebirc
* cp qwebirc/rc.qwebirc /tmp/fakeroot/etc/rc.d
* cd ..
* cp databases/* /tmp/fakeroot/srv/httpd/databases/

* NOTE: This bit has more fail in it than I'd prefer. Unfortunately, it's unique to my development virtual machine and that really has to change.
* mkdir -p /tmp/fakeroot/srv/httpd/htdocs
* cp -rv /srv/httpd/htdocs/* /tmp/fakeroot/srv/httpd/htdocs/

* mkdir /tmp/fakeroot/var/run/ngircd
* chown ngircd.root /tmp/fakeroot/var/run/ngircd
* chmod 0750 /tmp/fakeroot/var/run/ngircd

* mkdir -p /tmp/fakeroot/srv/captiveportal
* mkdir -p /tmp/fakeroot/etc/captiveportal
* mkdir -p /tmp/fakeroot/tmp/fakeroot/usr/local/sbin
* cd ~guest/Byzantium/captive_portal
* cp captive_portal.py /tmp/fakeroot/usr/local/sbin
* cp captive-portal.sh /tmp/fakeroot/usr/local/sbin
* cp etc/captiveportal/captiveportal.conf /tmp/fakeroot/etc/captiveportal/
* cp srv/captiveportal/* /tmp/fakeroot/srv/captiveportal/

* This is to prevent the default Porteus firewall rules from interfering with the ones the control panel installs.
** /tmp/fakeroot/etc/rc.d/rc3.d/S-firewall

For the control panel to work, NO network interfaces should be configured at the outset. The Porteus configuration apps make this easy, but conflict with our needs. When testing, it's easier to shut everything down by hand and then put fresh copies of the .sqlite databases into /var/db/controlpanel.

Ideally, to do everything right you'd have to reboot at this point. That would, in theory, run the right initscripts in the right order (or skip them, as the case may be).

To build the official Byzantium module:
* dir2xzm /tmp/fakeroot /tmp/000-byzantium.xzm

Packaging NPM

2012-02-25T20:22:30Z

Drwho: Created page with "* Ensure that node.js module is enabled. * Download npm: wget http://npmjs.org/install.sh * mv install.sh npm-install.sh * sh ./npm-install.sh (as root) * Everything goes in /usr..."

* Ensure that node.js module is enabled.
* Download npm: wget http://npmjs.org/install.sh
* mv install.sh npm-install.sh
* sh ./npm-install.sh (as root)
* Everything goes in /usr/lib/mode_modules/npm
* /usr/bin/npm* symlinked to /usr/lib/mode_modules/npm/bin/npm.js

Downloading Byzantium

2012-01-28T01:06:27Z

Drwho:

[http://byzantium.virtadpt.net/byzantium.pubkey Byzantium Project] public PGP key.

{|style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #000; padding: 0" border="1" cellpadding="5"
!Version
!Codename
!Released
!Fitness*
!Torrent
!Direct DL
!PGPSign
!Comments
|-
|0.1a
|Scarab
|2012/01/11
|0
|
*[http://linuxtracker.org/download.php?id=fcc7607270ba48897ff865ed5361013554a659eb&f=Byzantium%20Linux%20v0.1a.torrent Linux Tracker]
|
* [http://linuxfreedom.com/byzantium Linux Freedom]
* [http://byzantium.virtadpt.net/ byzantium.virtadpt.net]
* [https://s3.amazonaws.com/byzantium/byzantium-curent.iso haxwithaxe's S3]
|[https://s3.amazonaws.com/byzantium/byzantium-current.iso.asc haxwithaxe's S3]
|
*current version.
*EXTREME ALPHA!!
*focusing on functionality ''NOT security''
|-
|}
`*Fitness is a score from 0 to 5 indicating the fitness of a release for use as an '''Emergency''' networking aid. Do not let this put you off downloading it to try it out or help us by finding and reporting bug and feature requests. In order to make it to a level 5 fitness we need as many people to use it as possible so we are more likely to find bugs before they end up causing trouble for people who expect our livedistro to work in an emergency.
*0 = completely unfit (likely to do more harm than good in any emergency)
*1 = still mostly unfit (unless you are an active developer on the project you won't likely benefit from this in an emergency)
*2 = works well enough to provide basic connectivity with minimal configuration. (yeh! we're a little bit fit now! which is not to say we're fit enough to run a marathon, so don't expect to be able to do much without a regular internet connection or some sysadmin skills)
*3 = in addition to qualifying for level 2 fitness this has basic intermesh services like a built in chat server, microblog server and similar user oriented services ready to run with minimal configuration. (still needs a service to tell other mesh users and end users about the services on the mesh, aka our DNSless service distribution).
*4 = fully featured and works well enough to be used in friendly network conditions (you aren't in jeopardy of getting arrested/attacked for using it for things that are considered legal where you are using it)
*5 = fully featured and setup with best effort secure defaults and possibly other security features (this by no means should suggest that it is safe to use in an environment where there is a government or government like entity is actively trying to suppress network connectivity by means other than denial standard network connectivity)
*6 = if we find the magic sauce that can make it super hard to find users if you aren't a user and reasonably impossible to detect or decrypt traffic not sent to you, then you will see this magic number as the fitness score. Until then it is the metaphorical unicorn. It doesn't exist.
You may have noticed that the fitness list doesn't ever say it's safe to use in a hostile network. That's because it won't likely ever be safe to use in a hostile network. The best we can do is to set reasonably secure defaults and policies and try to educate users on internet hygiene so they don't let people rub malware in their face if they go someplace we can't protect them.

File:Byzantium Linux v0.1a.torrent

2012-01-28T00:40:59Z

Drwho: uploaded a new version of "File:Byzantium Linux v0.1a.torrent": Users are having problems with the existing copy of this file, so I've uploaded a new one.

Torrent for Project Byzantium's LiveDistro version 0.1(Alpha) codename: Scarab

File:Byzantium Linux v0.1a.torrent

2012-01-28T00:40:04Z

Drwho: uploaded a new version of "File:Byzantium Linux v0.1a.torrent": Users are having problems with the existing .torrent, so I'm re-uploading it.

Torrent for Project Byzantium's LiveDistro version 0.1(Alpha) codename: Scarab

Byzantium Live Distro Prerelease

2012-01-22T03:24:36Z

Drwho: /* Human Environment */

==Prerelease Process==
'''DRAFT'''
On this page we have a list of things that need to happen between the '''final''' build and the publishing of software or repackaging thereof by the Byzantium Project. Unless otherwise stated all items are required to be satisfied for an individual build before being placed in another part of the project or before publishing the project.
===Build Environment===
*manifest check - make sure what you think is there is actually there. manifest files (with name <scope>.manifest) are recommended, and will be checked by the build environment once that is automated.
** Add a stanza to the Makefile (if we go that way, that is) - '''make manifest''' or '''make test''' or something like that.
*?other sanity checks?

===Runtime Environment===
*for each package/major feature set a checklist must be made that will reasonably ensure the software is behaving as expected.
* A list of packages that comprise 000-byzantium.xzm should be maintained someplace. Right now we're just eyeballing it.
* A list of files associated with each package should be maintained someplace.
** This is why I build Slackware packages (where feasible) or do a '''DEST=/tmp/SBo make install''' where there aren't any followed by a '''dir2xzm /tmp/package.xzm /tmp/SBo''' - to keep all of the files for a particular package grouped together.
** A bunch of .xzm packages are easier to keep track of than compiling stuff in sequence. Then, when it comes time to build everything the build system can check them out of SVN and use '''xzm2dir''' to unpack all of them in sequence into a fakeroot. So, I propose a two step QA sequence:
*** Make sure that some_package-rev.isi.on.xzm was compiled and checked into SVN.
*** Make sure that some_package-rev.isi.on.xzm was checked out of SVN on the build machine and '''xzm2dir'''ed into /tmp/fakeroot.
**the checklist can (and is recommended to) just say to run a script that will do the required tests and return a pass/fail status.
**if a script is used for runtime QA it should be named "runtimeQA.sh" and have 777 (a+rwx) permissions in the root directory of it's scope (eg for a package "byzantium-repo/packages/thispackagedir/runtimeQA.sh"). Also it should use paths with the expectation that the script will be run from an arbitrary directory.

===Human Environment===
*2 day cool down period between building and publishing
* No .iso image goes out without being PGP signed against key 0xD6975C17.
** While we're at it, can we get some more signatures on that key?
*** Fingerprint 93F3 8B13 B52C D8F0 FA8D 03B3 37AA 847C D697 5C17
*** I've uploaded it to a bunch of keyservers around the Net.
* The person who builds the .iso image is not the one who checks the contents of the .iso image. After you've been staring at the same thing for long enough, it all starts looking alike.
** Does the bootloader have the right porteus.cfg?
** Does the bootloader have byzantium.jpg handy?
** Does porteus/modules/000-byzantium.xzm exist?
** Do these files exist in the root directory of the .iso image?
*** README.txt
*** README.NOW
*** FAQ.txt
*** packages.txt
*** CHANGELOG
** Do all of the Porteus modules exist in porteus/base?
*** 000-kernel.xzm
*** 001-core.xzm
*** 002-xorg.xzm
*** 003-lxde.xzm
*** 004-kde.xzm
*** 005-kdeapps.xzm
*** 006-koffice.xzm
**** Do we really need to include this?
*** 007-devel.xzm
*** 008-firefox.xzm
* No .iso goes out without being tested, i.e., at least booted in a VM and put through its paces.
* We need a process for loading the mirrors from a single distribution point.
* Torrents are seeded prior to announcement.

Byzantium Live Distro Prerelease

2012-01-22T03:11:56Z

Drwho: /* Runtime Environment */