Initramfs init: Difference between revisions
m (→Usage: cmd and path templates used.) |
WhyNotHugo (talk | contribs) (→initramfs init cmdline options: remove WIP title) |
||
(9 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
[https://gitlab.alpinelinux.org/alpine/mkinitfs '''mkinitfs'''] is a tool to create initramfs images. Initramfs images are small images which contain a small filesystem with everything required to boot Alpine. For example, when booting a setup with [[Setting up encrypted volumes with LUKS|full disk encryption]], the initramfs contains the binaries required to prompt for a password and mount the encrypted disk. | |||
==Usage== | |||
== Usage == | |||
Under a running alpine machine, the following command can be used if for some reason the initramfs has not been created properly for a new kernel. | Under a running alpine machine, the following command can be used if for some reason the initramfs has not been created properly for a new kernel. | ||
{{cmd|mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b / <kernelvers>}} | {{cmd|mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b / <kernelvers>}} | ||
The script is located in {{path|/sbin/}} and is created with ash. It expects {{path|/lib/modules}} to be populated with the <kernelvers> listed. For variations on this command (e.g. for chroot) Search "mkinitfs". | The script is located in {{path|/sbin/}} and is created with ash. It expects {{path|/lib/modules}} to be populated with the <code><kernelvers></code> listed. For variations on this command (e.g. for chroot) Search "mkinitfs". | ||
== initramfs init cmdline options | == initramfs init cmdline options == | ||
In addition to the [https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html kernel boot parameters] are a number of parameters that the init script understands. | In addition to the [https://www.kernel.org/doc/html/v4.14/admin-guide/kernel-parameters.html kernel boot parameters] are a number of parameters that the init script understands. These are documented in the <code>mkinitfs-bootparam(7)</code> man page. | ||
Although you may specify your own init script when building an initramfs, these parameters allow for extensive control over the initial startup of an Alpine Linux system. | Although you may specify your own init script when building an initramfs, these parameters allow for extensive control over the initial startup of an Alpine Linux system. | ||
== See Also == | |||
* [https://wiki.postmarketos.org/wiki/The_initramfs PostmarketOS Wiki] | |||
* [https://wiki.archlinux.org/title/Arch_boot_process#initramfs ArchWiki boot process] | |||
[[category:Kernel]] | [[category:Kernel]] | ||
[[Category:Booting]] |
Latest revision as of 05:48, 12 November 2024
mkinitfs is a tool to create initramfs images. Initramfs images are small images which contain a small filesystem with everything required to boot Alpine. For example, when booting a setup with full disk encryption, the initramfs contains the binaries required to prompt for a password and mount the encrypted disk.
Usage
Under a running alpine machine, the following command can be used if for some reason the initramfs has not been created properly for a new kernel.
mkinitfs -c /etc/mkinitfs/mkinitfs.conf -b / <kernelvers>
The script is located in /sbin/ and is created with ash. It expects /lib/modules to be populated with the <kernelvers>
listed. For variations on this command (e.g. for chroot) Search "mkinitfs".
initramfs init cmdline options
In addition to the kernel boot parameters are a number of parameters that the init script understands. These are documented in the mkinitfs-bootparam(7)
man page.
Although you may specify your own init script when building an initramfs, these parameters allow for extensive control over the initial startup of an Alpine Linux system.