ejemplos:


if you are using Porteus-1.2 then:
a) please extract vmlinuz and initrd.xz from Porteus ISO to /HBCD/Porteus-1.2/boot folder
b) please put Porteus ISO in /HBCD/Porteus-1.2 folder
c) please use this config:

Code: Select all

    title Porteus 1.2\nBest distro ever.
    find --set-root --ignore-floppies /HBCD/Porteus-1.2/boot/initrd.xz
    kernel /HBCD/Porteus-1.2/boot/vmlinuz iso-scan/filename=/HBCD/Porteus-1.2/Portueus-v1.2-i486.iso **from_iso**=/HBCD/Porteus-1.2/Portueus-1.2-i486.iso --
    initrd /HBCD/Porteus-1.2/boot/initrd.xz

if your are using Porteus-2.x then:
a) please extract vmlinuz and initrd.xz from Porteus ISO to /HBCD/Porteus-2.0/syslinux/boot folder
b) please put Porteus ISO in /HBCD/Porteus-2.0 folder
c) please use this config:


    title Porteus 2.0\nBest distro ever.
    find --set-root --ignore-floppies /HBCD/Porteus-2.0/boot/syslinux/initrd.xz
    kernel /HBCD/Porteus-2.0/syslinux/boot/vmlinuz **iso-scan**/filename=/HBCD/Porteus-2.0/Portueus-v2.0-i486.iso from=/HBCD/Porteus-2.0/Portueus-v2.0-i486.iso --
    initrd /HBCD/Porteus-2.0/boot/syslinux/initrd.xz

Booting grml small iso from grub2

Grml can also be booted from grub2. Note that it uses **findiso** option instead of iso-scan/filename option, indicating that Booting from iso is implemented as different options in different distributions.

(menuentry "Grml small 2009.10" {
  loopback loop /boot/iso/grml-small_2009.10.iso
  linux (loop)/boot/grmlsmall/linux26 findiso=/boot/iso/grml-small_2009.10.iso apm=power-off lang=us vga=791 boot=live nomce noeject noprompt --
  initrd (loop)/boot/grmlsmall/initrd.gz
}




Distros with a GRUB configuration (GRML)

Some live distros include a GRUB configuration specifically made foor loopback boot. This is true, for example, for GRML. You recognize this when you see a /boot/grub/loopback.cfg file in the ISO image. The GRUB stance will then look like that:

	menuentry "GRML 2010.12 i386" {
	  iso_path=/boot/grml_2010.12.iso
	  export iso_path
	  loopback loop $iso_path
	  set root=(loop)
	  configfile /boot/grub/loopback.cfg
	}
	

Casper-based distros (Ubuntu)

A lot of live distros use the Casper boot system. This apply especially to the Ubuntu live systems.
(inside the iso there is a "casper" folder)

Casper includes support for loopback boot, it only requires the name of the ISO image. The GRUB stance will look like that:

	menuentry "Ubuntu 10.04 Netbook i386" {
	  loopback loop /boot/ubuntu-10.04-netbook-i386.iso
	  set root=(loop)
	  echo "Loading kernel..."
	  linux /casper/vmlinuz boot=casper iso-scan/filename=/boot/ubuntu-10.04-netbook-i386.iso
	  echo "Loading initrd..."
	  initrd /casper/initrd.lz
	  echo "Booting..."
	  boot
	}
	

===== ejemplos configuracion avanzada grub4dos =====

====== ejemplo 1 ======

    set ISOx=elementaryos.iso
    set ISO31=Porteus-LXQT-v3.1-x86_64-nu.iso
    set ISO30i=Porteus-RazorQT-v3.0.1-i486-nu.iso
    set ISO30=Porteus-RazorQT-v3.0.1-x86_64-nu.iso
    set ISO21=Porteus-RazorQT-v2.1-x86_64.iso

    # menu entries

    title Porteus 3.1   changes=EXIT  \n186MB\n %ISO31%  
    find --set-root                       /ISOs/%ISO31%
    map --heads=0 --sectors-per-track=0   /ISOs/%ISO31% (0xff) 
    map --hook
    root (0xff)
    kernel /boot/syslinux/vmlinuz    from=/ISOs/%ISO31% changes=EXIT:/porteus3.1/changes/porteussave.dat extramod=/porteus3.1/Modules volume=40 ramsize=80%  
    initrd /boot/syslinux/initrd.xz

    title Windows 7 System Repair Disc - 64-bit\n 187MB\n\ When prompted press Enter to boot disc.
    find --set-root /ISOs/repair_disc_windows_7_64_bit.iso
    map /ISOs/repair_disc_windows_7_64_bit.iso (hd32)
    map --hook
    root (hd32)
    chainloader (hd32)