From 0c1370b5f1b3e8abc934ea913a4377f05f32e4a9 Mon Sep 17 00:00:00 2001 From: Yuval Adam <_@yuv.al> Date: Mon, 7 Aug 2017 22:05:24 +0300 Subject: Initial static build --- docs/wiki/Initramfs-development/index.html | 86 ++++++++++++++++++++++++++++++ 1 file changed, 86 insertions(+) create mode 100644 docs/wiki/Initramfs-development/index.html (limited to 'docs/wiki/Initramfs-development/index.html') diff --git a/docs/wiki/Initramfs-development/index.html b/docs/wiki/Initramfs-development/index.html new file mode 100644 index 0000000..7e36025 --- /dev/null +++ b/docs/wiki/Initramfs-development/index.html @@ -0,0 +1,86 @@ + + +
+ + +
+ postmarketOS
+ After the installation, you will have two initramfs files in your device's /boot folder.
% ls ~/.local/var/pmbootstrap/chroot_rootfs_samsung-i9100/boot
+initramfs-samsung-i9100 initramfs-samsung-i9100-extra vmlinuz-samsung-i9100
+
+
+Regular Linux distributions only have one initramfs file. We have split it into two to work around the size limitations, that some devices have. The regular initramfs is relatively small (~1.5 mb, and we could make it smaller if necessary!) and loads the contents of the initramfs-extra from the pmOS boot partition during the boot process.
+The pmOS boot partition is a subpartition of the system partition (SD cards: simply a real partition on the SD card), so we can make it almost as big as we want.
+pmbootstrap initfs, pmbootstrap flasher flash_kernel)When you change too much, it will simply not work and you most likely will have no idea why it does not work. Go back to the last working version and do smaller changes at a time.
+pmbootstrap initfs can do more than rebuilding the initramfs:% pmbootstrap initfs --help
+usage: pmbootstrap initfs [-h]
+ {hook_ls,hook_add,hook_del,ls,build,extract} ...
+
+positional arguments:
+ {hook_ls,hook_add,hook_del,ls,build,extract}
+ hook_ls list available and installed hook packages
+ hook_add add a hook package
+ hook_del uninstall a hook package
+ ls list initramfs contents
+ build (re)build the initramfs
+ extract extract the initramfs to a temporary folder
+
+optional arguments:
+ -h, --help show this help message and exit
+
+
+This is probably caused by a syntax error. Use shellcheck to check your scripts for syntax errors. You could also loop forever or spawn a shell (if you have a hardware keyboard or serial cable connected) at some point for debugging (while true; do sleep 1; done) and use the telnet shell to test the commands, that are failing, interactively.
By default, all output from the initramfs get redirected to /pmOS_init.log. If you want the output through the debug cable you need to add PMOS_NO_OUTPUT_REDIRECT to your kernel command line.