mkiso script will use venom rootfs tarball image (venom-rootfs.txz) in current directory to create the iso. If venom rootfs tarball image does not exist in current directory it will download from venom’s sourceforge page. You can use custom venom’s rootfs tarball image or directory (in case you need customize it first) by appending to mkiso script. Eg: # ./mkiso mycustomvenom.txz or # ./mkiso /path/to/venomfs.

  ./mkiso [options] <venom source>

  -p <path>           set packages cache directory
  -s <path>           set sources cache directory
  -P <pkg1 pkgN ...>  package to install into iso
  -i <initrd>         use custom initrd
  -k <kernel>         use custom kernel
  -o <name.iso>       output name for iso
  -h                  show this help msg

  'venom source' should be a rootfs directory or rootfs tarball image
  if not define, it will download prebuilt one


Create base venom iso with custom output name

# ./mkiso -o venomlinux.iso

Create venom iso with some extra package

# ./mkiso -P nano mc xorg

Create venom iso using your own created initrd/kernel (make sure you know what you doing)

# ./mkiso -i /path/to/initrd -k /path/to/kernel

Create venom iso using existing custom venom’s rootfs

# ./mkiso custom-venom-rootfs.txz

Create venom iso using custom packages path (its save you compile time, if you already use Venom Linux as host OS :D)

# ./mkiso -p /path/to/packagedir

You can use these options altogether, eg:

# ./mkiso -p /var/cache/packages -s /var/cache/sources -P xorg xfce4 lxdm -o venom-xfce4-custom.iso

Note: Be careful when adding custom packages, adding non-existing packages may cause build error. Look in ports for exist packages.