uBering customization

The uBering distribution boot from a Read Only media and then copy everthing into RAM disk. At the end the media from which it was booted is forgotten.
The customization process is made of the following steps:

• build a minix filesystem of size sufficient to store all needed packages and relative modules;
• copy the lrp packages from Bering/uClibx_*_iso_bering-uclibc-iso.bin into above filesystem;
• add a custom package to configure the uBering box for the virtual environment. This package is named "customvm.lrp" and must be loaded as last lrp package.

uBering virtual machine startup

In the summer 2006 we moved the startup script from the low level netkit interface named "v-command" to a more high level netkit interface named "l-command". The l-command uses the lab.conf file to configure the startup of any virtual machine. For example:

# lab.conf
[...]
fw[0]="A"
fw[1]="B"
fw[k]="/usr/local/netkit/kernel/ub.krnl"
fw[mem]=32
fw[append]=LRP=root,config,etc,local,iptables,shorwall,ulogd,libz,libcrpto,customvm
[...]

Building customvm.lrp

The next example shows how to build a customvm.lrp file with a /etc/network/interfaces copied from $repository directory and store the customvm.lrp file in the same directory. Note: we strongly suggest to use "root" account because it is important that the files have the right permissions.

# mkdir /tmp/$mountPoint
# cd /tmp/$mountPoint
# mkdir -p etc/network
# cp $repository/interfaces etc/network/interfaces
# tar czf $repository/customvm.lrp *
# cd -

Sandro Doro (email me)
Ultima modifica: $Date: 2006-10-18 15:09:16 $