OmniBoot v1.5

OmniBoot

is distributed as a seed of 4-5 MB that is meant to be grown by a script to the full OmniBoot directory tree with the help of a virtual machine and a live linux OS - and of course an internet connection. The seed contains all necessary configuration files to allow an included script to download all kinds of distros and tools, mod some of them and rearrange all files in an OmniBoot root folder tree. This tree then is the source for e.g. a bootable USB-Stick, for writing various bootable isos or it can be served on a LAN as pxe-boot-source. (Even the web would be possible with certain limitations)

You can download OmniBoot in two download-versions, one is a compressed folder tree, the other one is a vhd-file containing this folder tree. The size of this virtual disk image is currently about 700MB (if unpacked, and allmost empty) while it is configured to grow to a maximum size of 256GB, so use a partition with sufficient space for it. For ease of access also in Windows the disk is formatted with NTFS.

The script requires linux.
If you have an installed linux operating system (see recommended versions below!) you could try the tgz-version right away.
If you use Windows, you must download a virtual machine software like Virtual Box, VMware or MS-Virtual-PC and use the unpacked vhd file as HDD-Image for a virtual machine. Best results need a CPU with modern virtualization technology and require at least 2 cores and 3GB of RAM for your virtual machine. You boot this virtual machine with live CDs/DVDs of Knoppix 7.2, Debian 7.x/8.x or openSUSE 13.x.
Of course you can host your VM on any linux-host too.
If you have none of the recommended linux-versions installed and also don't want to use a VM, you can boot a physical system with one of these live distros as well.

Other distros as Mint 16/17, Ubuntu 14.x/15.x, Bodhi 3.1, Fedora 19-23, System Rescue CD 4.x and Slitaz 4/5 have also been tested to work quite well. Debian, Mint, Ubuntu and Bodhi only lack one optional dependency (vdfuse, which is only required for creating the OmniBoot seed vhd). Fedora and System Rescue CD miss two optional dependencies (cloop, which is only required for pxe booting of Knoppix, and vdfuse).
Slitaz is also recognized by the script but should only be regarded as experimental. For any other linux distro you need to install possibly missing tools yourself, the script will only inform but has no setup know-how.

The clear recommendations here are VirtualBox and Knoppix 7.2.

All named distros will automatically detect the virtual harddisk and except clicking on it in a GUI-filemanager no further mount operations by the user are required (exception: System Rescue CD).

To start the build you open the filemanager for easy navigation, all distros have a GUI file-manager that will show the virtual HDD (actually the partition label), its name is OmniWork. On OmniWork you navigate to the folder ...boot/make/omniboot and open a shell in that folder. Those GUI file-manager offer this access to the shell at the location of a viewed folder one way or the other easily, either in context menu or in the top menu.

Now you need to make sure to run the script with root privileges, only some minor functions don't necessarily require this. Either the life-OS allows you to say "su root" without any password (e.g. Knoppix, openSUSE) or you just prefix "sudo" to your command (Debian). Alternatively you can also do "sudo su" to gain root privileges.

The actual command to start everything is "bash ./om ch" or "sudo bash ./om ch", and note again that this must be done at the path of the script. This will build the whole project including the content table of the info site.

If you only do sudo "bash ./om" without any option you get a help page that shows you all functions of the OmniBoot script. As for instance "sudo bash ./om s" for status, which will only check for required programs for the script, report about available modules and missing downloadable files.