Run mk-sysimage

Once the master image has been created, the mk-sysimage script (section 6.1) must be run to prepare the image for use. This script alters the filesystem of the master image so that each node effectively sees a different `view' of the image.

As described in the `Implementation' section, mk-sysimage alters any files listed as a LINK* directive to enable the image to serve as the root filesystem for as many nodes with potentially many different functional roles. It will convert the distribution to be used as a read-only root filesystem. As a convenience, it will also remove (backup) any configuration files that try to mount local disk devices or configure network interfaces, or any other configuration files that would create problems for client nodes.

On some distributions at may be desirable to manually alter the network configuration after mk-sysimage has run. For example, on an Ubuntu system, if network-manager is not disabled it may attempt to reconfigure your primary boot interface and the root filesystem could become unaccessible. To prevent this one could either disable network-manager (preferred) or try to tell network-manager to not touch your boot interface by adding the following to the /etc/network/interfaces file:

auto eth0

iface eth0 inet manual

Procedure 3   Run mk-sysimage on your image

 $\bullet$ Define your distribution

Edit /etc/sysimage.conf in the image to reflect the linux distribution being used.
Add the appropriate DISTRO directive.

 $\bullet$ Run mk-sysimage

This will prepare the image to be used as a shared root filesystem for many nodes. It may be desirable to run with the -dryrun option the first time to see if the distribution patch will apply cleanly. The effects of mk-sysimage can always be reverted with the -revert option.
# mk-sysimage /var/lib/oneSIS/image