Multibooting
From OESF
m (New article on multibooting) |
(Trying to update and give more information) |
||
Line 1: |
Line 1: | ||
| - | + | = Concept = | |
| - | + | ||
| - | + | On Zaurus there is a bootloader, this will select the device to boot, load a kernel and start the system. uboot is a bootloader. | |
| - | you can | + | |
| - | + | The Angstrom project developed a tool called kexec that allows you to switch to another kernel from a running system. You can also make a kexec boot selector to choose from kernels stored on various media such as NAND, HDD, or memory card. | |
| + | |||
| + | == kexec Bootloader == | ||
| + | |||
| + | kexec probe all bootable devices and look for a directory /boot containing the following 3 files | ||
| + | # zImage (the kernel) | ||
| + | # image.nfo (One line description of the kernel, for the menu) | ||
| + | # kernel-cmdline (kernel command line parameters) | ||
| + | |||
| + | The probe stage can be quite slow, it may be quicker to boot a distribution using a standard bootloader and then run kexec on the command line to switch to the other kernel. | ||
Note that Angstrom has the altboot utility that also allows multibooting. | Note that Angstrom has the altboot utility that also allows multibooting. | ||
| - | + | ||
| - | + | == Sharp ROM/Cacko == | |
| + | |||
| + | The Sharp ROM and Cacko both have restrictions: | ||
| + | # The NAND has the original layout. | ||
| + | # The hard drive on SL-C3xxx must have specific partitioning and files. | ||
| + | |||
| + | The Sharp kernel is based on 2.4 and does not read command line parameters, that's why some of these things are hard coded, such as drive layout. | ||
| + | |||
| + | The hard drive requirement may be removed from Cacko, using [http://www.oesf.org/forum/index.php?act=attach&type=post&id=5405 this script] by ZDevil. | ||
| + | |||
| + | == Android == | ||
| + | |||
| + | [http://www.omegamoon.com/blog/static.php?page=ZaurusAndroid Cortez's Android] uses altboot, a tool from OpenEmbedded to set up a root filesystem after booting with the Poky kernel. | ||
| + | |||
| + | == Andromeda (Debian) == | ||
| + | |||
| + | Andromeda can be run via the kexec bootloader. | ||
| + | |||
| + | == Zubuntu == | ||
| + | |||
| + | Zubuntu comes ready to run via the kexec bootloader. | ||
Revision as of 22:06, 1 June 2010
Contents |
Concept
On Zaurus there is a bootloader, this will select the device to boot, load a kernel and start the system. uboot is a bootloader.
The Angstrom project developed a tool called kexec that allows you to switch to another kernel from a running system. You can also make a kexec boot selector to choose from kernels stored on various media such as NAND, HDD, or memory card.
kexec Bootloader
kexec probe all bootable devices and look for a directory /boot containing the following 3 files
- zImage (the kernel)
- image.nfo (One line description of the kernel, for the menu)
- kernel-cmdline (kernel command line parameters)
The probe stage can be quite slow, it may be quicker to boot a distribution using a standard bootloader and then run kexec on the command line to switch to the other kernel.
Note that Angstrom has the altboot utility that also allows multibooting.
Sharp ROM/Cacko
The Sharp ROM and Cacko both have restrictions:
- The NAND has the original layout.
- The hard drive on SL-C3xxx must have specific partitioning and files.
The Sharp kernel is based on 2.4 and does not read command line parameters, that's why some of these things are hard coded, such as drive layout.
The hard drive requirement may be removed from Cacko, using this script by ZDevil.
Android
Cortez's Android uses altboot, a tool from OpenEmbedded to set up a root filesystem after booting with the Poky kernel.
Andromeda (Debian)
Andromeda can be run via the kexec bootloader.
Zubuntu
Zubuntu comes ready to run via the kexec bootloader.

