OmniBoot v1.5

The OmniBoot-Management-script, /boot/make/omniboot/om - linux-shell only, is used to build the whole OmniBoot-filesystem, to create all the different isos and to write bootable drives. It's the real essential core of OmniBoot. There is next to no inline documentation but variables are named intelligibly, obscure code is avoided as possible and a lot of echos explain what's currently happening.

It (re)writes most of the heavily redundant syslinux-config-files and also the content- and the language-table of this info-site.
It downloads specific missing files from the original author's mirrors and even rebuilds initial ramdisks, if the code is provided in the module's main config-file.
There is a basic help-function explaining the syntax and a status report about available modules.
A synchronizing functions allows to rsync another writable copy of OmniBoot as e.g. on a USB-drive and make that drive bootable.

To run the script you must cd to its directory /boot/make/omniboot/ and not move it from there, otherwise it complains and tries to cd there itself because all relative paths would be wrong elsewhere. Also it only finds its own config "om.cfg" there. And it must be placed as deep inside a work-folder tree as in the two delivered versions (vhd, tgz). So never move the whole filesystem of OmniBoot out e.g. to the root-folder of an installed linux. However the script checks for this environmental condition and exits verbally on error.

The script should run on most current linux-distros, however it checks the required programs and complains if something mandatory or optional is missing. It has been tested in Knoppix, openSUSE, Debian, Fedora, SystemRescue CD and Slitaz - so it knows the setup commands for these distros. But only the first 3 named (Knoppix, openSUSE and Debian) in their life versions can automatically be completed to fully meet all software requirements.

If you hit e.g. Ctrl-C to interrupt the script, please be patient and wait for the clean-up process. During execution you can monitor the script's activities in the subfolder "omrun" in the script's folder. This folder is a small ram-drive containing some empty files. The filenames are indicators for the script itself what all spawned sub-scripts are doing. Basically downloads and currently manufactured modules are indicated with their process-ID as file-extension. And there is also a folder "open" showing a virtual copy of the OmniBoot-filetree with respect to files the script regards as currently open. These open files are deleted on e.g. Ctrl-C.

Root privileges are required for most important script functions. Learn more how the om-script is used on tab Build.