Editing Advanced booting
Warning: You are not logged in.
Your IP address will be recorded in this page's edit history.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 5: | Line 5: | ||
== Multi-boot == | == Multi-boot == | ||
- | The process for setting up a multi-boot is similar to [[Booting from a flash card]]. | + | The process for setting up a multi-boot is very similar to [[Booting from a flash card]]. |
- | It's a good idea to | + | It's a good idea to makes sure the first partition is a fat/data partition - this keeps things simple. |
- | A sample partition layout on an 8Gb card | + | A sample partition layout on an 8Gb card may be: |
* 2GB primary vfat data | * 2GB primary vfat data | ||
* 2GB primary everyday | * 2GB primary everyday | ||
Line 16: | Line 16: | ||
* 512MB logical test3 (diablo) | * 512MB logical test3 (diablo) | ||
- | Be aware that the kernel initfs supports a limited number of partitions; this can be extended to 6 but no further. This requires editing /home/user/local/bin/initfs_flasher/initfs.bootmenu.jffs2 to add the dev nodes using mknod | + | Be aware that the kernel/initfs only supports a limited number of partitions; this can easily be extended to 6 but no further. This requires editing /home/user/local/bin/initfs_flasher/initfs.bootmenu.jffs2 to add the dev nodes using mknod |
(eg: mknod -m600 initfs/dev/mmcblk0p5 b 254 5) | (eg: mknod -m600 initfs/dev/mmcblk0p5 b 254 5) | ||
Learn more about Contributing to the wiki.