OmniBoot v1.5

Most computers today boot from USB and a USB-Stick usually is much larger than an optical drive. So booting from USB is a major topic when it comes to live operating systems or multi-boot live-OS like OmniBoot. However for the boot process we are basically not looking at USB or SATA/IDE but we focus partitions with filesystems.

So in despite this information here is filed under "USB" it applies basically to any writable partition attached to the system. It can be an USB-stick with a FAT32 partition (and yes, this is the most recommende method!) or a built in SATA-drive with an ext3 Linux-partition (possible filesystems are FAT16/32, NTFS, ext2/3/4).

The om-script is only able to find a partition with a certain label attached to the system. The name must be "OMNIBOOT" and is case sensitive. Make sure you only have one such partition attached when setting up OmniBoot to a bootdrive.

The om script does not create nor format nor label partions. You need to provide this bootpartion labelled "OMNIBOOT" on your chosen boot-drive yourself. On live-linux you will mostly find gparted to easily accomplish this task.

The om script can copy or synchronize changes of the whole filesystem with the commandbash ./om r aTo not only copy the filesystem but also make sure the partition is activated and to make it bootable you dobash ./om r fYou can also only synchronize files up to 1MB in size withbash ./om r sor only make sure the partition is activated and bootable withbash ./om r b

Note that in order to make the drive bootable you should at least have copied the folder "boot" to the drive first. Actually to be precise, an existing folder boot/syslinux would be sufficient, but just copy "boot" for convenience. Otherwise syslinux will fail to write the bootloader which has been defined to sit in that folder within OmniBoot.