Originally Posted by pali

Yes, but it is bad to tell that this is vmlinuz if in fact it is zImage. (As I wrote I do not like some stupid hacks this type). Why multiboot does not work if file has normal zImage name??

# vmlinuz searchlist
VMLINUZ_SEARCH="boot/multiboot/vmlinuz- boot/multiboot/zImage- boot/vmlinuz- boot/zImage-"

ITEM_NAME="Maemo kernel-power46-pali1"
ITEM_KERNEL="2.6.28.10pali1"
ITEM_MODULES=ext3

1.Configuration
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~

The configuration files are in /etc/multiboot.d/

Each file named <whatever>.item represents a bootable configuration,
which can be selected from the bootup menu.


1.1 Item file format
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~

A line starting with # is a comment

All other lines must be like the following:-

ITEM_ID="..."
A short name for this configuration.
No spaces, no special characters, max 6 characters long.

ITEM_NAME="..."
A description string for this configuration.
Shown on the bootmenu screen.

ITEM_KERNEL="..."
Kernel version to run in this configuration.
If the running kernel is not correct, multiboot will reflash
the device and reboot automatically.

ITEM_MODULES="..."
A list of kernel modules required to boot this configuration.
E.g. "ext2 ext3 fat vfat"

ITEM_DEVICE="..."
Root partition device name.
Use ${EXT_CARD} to point to the external MMC,
and ${INT_CARD} for internal.
E.g. "${EXT_CARD}p2" for partition 2 in removable MMC.

ITEM_FSTYPE="..."
Filesystem type for the root fs.
Usually ext2 or ext3.
Also, you must have the fs module loaded.

ITEM_FSOPTIONS="..."
Filesystem options for root fs. Typically,
for ext2/ext3:
"rw,noatime,errors=remount-ro"

ITEM_INITRC="..."
Init program to execute when switching over to root.
Optional, default is to search the usual locations.

ITEM_INITFS="..."
Locations where the Maemo root fs is moved after pivot.
Typically "initrd" or "mnt/initfs"
Defaults to "mnt/initfs"