Process for manually installing Byzantium.: Difference between revisions
From HacDC Wiki
(Created page with "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, installed, and ena...") |
No edit summary |
||
| Line 6: | Line 6: | ||
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). | 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). | ||
* | * mkdir -p /srv/controlpanel | ||
* | * cp -rv Byzantium/control_panel/srv/controlpanel/* /srv/controlpanel | ||
* | * mkdir /etc/controlpanel | ||
* | * cp Byzantium/control_panel/etc/controlpanel/* /etc/controlpanel | ||
* | * mkdir -p /var/db/controlpanel | ||
* | * cp -rv Byzantium/control_panel/var/db/controlpanel/* /var/db/controlpanel | ||
* | * cp Byzantium/scripts/traffic_stats.sh /usr/local/bin | ||
* | * cp -rv Byzantium/control_panel/etc/rc.d/* /etc/rc.d | ||
Note: Porteus does not make sudo available! I wrote it this way because I admin way too many Ubuntu machines at work. | Note: Porteus does not make sudo available! I wrote it this way because I admin way too many Ubuntu machines at work. | ||
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. | 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. | ||
Revision as of 21:56, 16 October 2011
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, installed, and enabled them.
- 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).
- mkdir -p /srv/controlpanel
- cp -rv Byzantium/control_panel/srv/controlpanel/* /srv/controlpanel
- mkdir /etc/controlpanel
- cp Byzantium/control_panel/etc/controlpanel/* /etc/controlpanel
- mkdir -p /var/db/controlpanel
- cp -rv Byzantium/control_panel/var/db/controlpanel/* /var/db/controlpanel
- cp Byzantium/scripts/traffic_stats.sh /usr/local/bin
- cp -rv Byzantium/control_panel/etc/rc.d/* /etc/rc.d
Note: Porteus does not make sudo available! I wrote it this way because I admin way too many Ubuntu machines at work.
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.