The mkinitrd script constructs a directory structure that can serve as an initrd root file system. It then generates an image containing that directory structure using mkcramfs(8), which can be loaded using the initrd mechanism. The kernel modules placed in the directory structure will be taken from moduledir. This is usually of the form /lib/modules/your-kernel-version.
The directory structure can be customised by placing scripts into confdir/scripts. They will be run using run-parts(8) just before the directory is fed to mkcramfs(8). You can also specify modules to load by putting them in confdir/modules, whose format is identical to that of /etc/modules, which is described in __modules(5)?__.
By default mkinitrd looks for its configuration files in /etc/mkinitrd. Use this option to override that.
Do not delete the temporary working directory that mkinitrd uses. This is useful for debugging.
This option overrides the setting of MKIMAGE in mkinitrd.conf.
This option causes mkinitrd to write the image to outfile instead of the standard output.
This file contains full paths to shared executables that should be included in the initrd image. mkinitrd will include them as well as any shared libraries that they are linked with.
This file contains full paths to files that should be included in the initrd image.
The default configuration file for the script.
All modules specified in this file will be loaded when the system boots using the generated image. However, they are not automatically included on the image. You will either have to use the appropriate MODULES setting, or copy them in using a script in /etc/mkinitrd/scripts.
lib/main.php:944: Notice: PageInfo: Cannot find action page