Man page 8 : initramfs-tools

• \fB\fI init= "<path to real init>"
      the binary to hand over execution to on the root fs after the initramfs scripts are done.
• \fB\fI root= "<path to blockdevice>"
      the device node to mount as the root file system. The recommended usage is to specify the UUID as followed "root=UUID=xxx".
• \fB\fI rootfstype
      set the root file system type.
• \fB\fI rootdelay
      set delay in seconds. Determines how long mountroot waits for root to appear. The default is 180 seconds.
• \fB\fI rootflags
      set the file system mount option string.
• \fB\fI nfsroot
      can be either "auto" to try to get the relevant information from DHCP or a string of the form NFSSERVER:NFSPATH or NFSSERVER:NFSPATH:NFSOPTS. Use root=/dev/nfs for NFS to kick to in. NFSOPTS can be looked up in nfs(5).
• \fB\fI ip
      tells how to configure the ip address. Allows to specify an different NFS server than the DHCP server. See Documentation/filesystems/nfsroot.txt in any recent Linux source for details. Optional parameter for NFS root.
• \fB\fI BOOTIF
      is a mac address in pxelinux format with leading "01-" and "-" as separations. pxelinux passes mac address of network card used to PXE boot on with this bootarg.
• \fB\fI boot
      either local or NFS (affects which initramfs scripts are run, see the "Subdirectories" section under boot scripts).
• \fB\fI resume
      On install initramfs-tools tries to autodetect the resume partition. On success the RESUME variable is written to /etc/initramfs-tools/conf.d/resume. The boot variable noresume overrides it.
• \fB\fI resume_offset
      Specify the offset from the partition given by "resume=" at which the swap header of the swap file is located.
• \fB\fI quiet
      reduces the amount of text output to the console during boot.
• \fB\fI ro
      mounts the rootfs read-only.
• \fB\fI rw
      mounts the rootfs read-write.
• \fB\fI blacklist
      disables load of specific modules. Use blacklist=module1,module2,module3 bootparameter.

• \fB\fI panic
      sets an timeout on panic. panic=<sec> is a documented security feature: it disables the debug shell.
• \fB\fI debug
      generates lots of output. It writes a log to /dev/.initramfs/initramfs.debug. Instead when invoked with an arbitrary argument output is written to console. Use for example "debug=vc".
• \fB\fI break
      spawns a shell in the initramfs image at chosen run-time (top, modules, premount, mount, mountroot, bottom, init). The default is premount without any arg. Beware that if both "panic" and "break" are present, initramfs will not spawn any shells but reboot instead.
• \fB\fI netconsole
      loads netconsole linux modules with the chosen args.
• \fB\fI all_generic_ide
      loads generic IDE/ATA chipset support on boot.

These are used when an initramfs image is created and not included in the image itself. They can however cause files to be included in the image. Hook scripts are executed under errexit. Thus a hook script can abort the mkinitramfs build on possible errors (exitcode != 0).

These are included in the initramfs image and normally executed during kernel boot in the early user-space before the root partition has been mounted. Hooks can be found in two places: /usr/share/initramfs-tools/hooks and /etc/initramfs-tools/hooks. They are executed during generation of the initramfs-image and are responsible for including all the necessary components in the image itself. No guarantees are made as to the order in which the different scripts are executed unless the prereqs are setup in the script.

In order to support prereqs, each script should begin with the following lines:

#!/bin/sh
PREREQ=""
prereqs()
{
	echo "$PREREQ"
}
case $1 in
prereqs)
	prereqs
	exit 0
	;;
esac
\fR. /usr/share/initramfs-tools/hook-functions
# Begin real processing below this line

For example, if you are writing a new hook script which relies on lvm, the line starting with PREREQ should be changed to PREREQ="lvm" which will ensure that the lvm hook script is run before your custom script.

/usr/share/initramfs-tools/hook-functions contains a number of functions which deal with some common tasks in a hook script:

• \fB\fI
      manual_add_modules adds a module (and any modules which it depends on) to the initramfs image.

Example: manual_add_modules isofs

• \fB\fI
      add_modules_from_file reads a file containing a list of modules (one per line) to be added to the initramfs image. The file can contain comments (lines starting with #) and arguments to the modules by writing the arguments on the same line as the name of the module.

Example: add_modules_from_file /tmp/modlist

• \fB\fI
      force_load adds a module (and its dependencies) to the initramfs image and also unconditionally loads the module during boot. Also supports passing arguments to the module by listing them after the module name.

Example: force_load cdrom debug=1

• \fB\fI
      copy_modules_dir copies an entire module directory from /lib/modules/KERNELVERSION/ into the initramfs image.

Example: copy_modules_dir kernel/drivers/ata

If you need to copy binaries to the initramfs module, a command like this should be used:

copy_exec /sbin/mdadm /sbin mkinitramfs will automatically detect which libraries the executable depends on and copy them to the initramfs. This means that most executables, unless compiled with klibc, will automatically include glibc in the image which will increase its size by several hundred kilobytes.

mkinitramfs sets several variables for the hook scripts environment.

• \fB\fI MODULESDIR
      corresponds to the linux-2.6 modules dir.
• \fB\fI version
      is the $(uname -r) linux-2.6 version against mkinitramfs is run.
• \fB\fI CONFDIR
      is the path of the used initramfs-tools configurations.
• \fB\fI DESTDIR
      is the root path of the newly build initramfs.
• \fB\fI DPKG_ARCH
      allows arch specific hook additions.
• \fB\fI verbose
      corresponds to the verbosity of the update-initramfs run.
• \fB\fI KEYMAP
      sets if a keymap needs to be added to initramfs.
• \fB\fI MODULES
      specifies which kind of modules should land on initramfs. This setting shouldn't be overridden by hook script, but can guide them on how much they need to include on initramfs.

Like for hook scripts, there are no guarantees as to the order in which the different scripts in one subdirectory (see "Subdirectories" below) are executed. In order to define a certain order, a similar header as for hook scripts should be used:

#!/bin/sh
PREREQ=""
prereqs()
{
	echo "$PREREQ"
}
case $1 in
prereqs)
	prereqs
	exit 0
	;;
esac

Where PREREQ is modified to list other scripts in the same subdirectory if necessary.

A number of functions (mostly dealing with output) are provided to boot scripts in /scripts/functions:

• \fB\fI
      log_success_msg Logs a success message

Example: log_success_msg "Frobnication successful"

• \fB\fI
      log_failure_msg Logs a failure message

Example: log_failure_msg "Frobnication component froobz missing"

• \fB\fI
      log_warning_msg Logs a warning message

Example: log_warning_msg "Only partial frobnication possible"

• \fB\fI
      log_begin_msg Logs a message that some processing step has begun
• \fB\fI
      log_end_msg Logs a message that some processing step is finished

Example:

log_begin_msg "Frobnication begun"
# Do something
log_end_msg

• \fB\fI
      panic Logs an error message and executes a shell in the initramfs image to allow the user to investigate the situation.

Example: panic "Frobnication failed"

Both /usr/share/initramfs-tools/scripts and /etc/initramfs-tools/scripts contains the following subdirectories.

• \fB\fI
      init-top the scripts in this directory are the first scripts to be executed after sysfs and procfs have been mounted. It also runs the udev hook for populating the /dev tree (udev will keep running until init-bottom).
• \fB\fI
      init-premount happens after modules specified by hooks and /etc/initramfs-tools/modules have been loaded.
• \fB\fI
      local-top OR nfs-top After these scripts have been executed, the root device node is expected to be present (local) or the network interface is expected to be usable (NFS).
• \fB\fI
      local-premount OR nfs-premount are run after the sanity of the root device has been verified (local) or the network interface has been brought up (NFS), but before the actual root fs has been mounted.
• \fB\fI
      local-bottom OR nfs-bottom are run after the rootfs has been mounted (local) or the NFS root share has been mounted.
• \fB\fI
      init-bottom are the last scripts to be executed before procfs and sysfs are moved to the real rootfs and execution is turned over to the init binary which should now be found in the mounted rootfs. udev is stopped.

• \fB\fI
      /conf/param.conf allows boot scripts to change exported variables that are listed on top of init. Write the new values to it. It will be sourced after an boot script run if it exists.

An example hook script would look something like this (and would usually be placed in /etc/initramfs-tools/hooks/frobnicate):

#!/bin/sh
# Example frobnication hook script
PREREQ="lvm"
prereqs()
{
	echo "$PREREQ"
}
case $1 in
prereqs)
	prereqs
	exit 0
	;;
esac
\fR. /usr/share/initramfs-tools/hook-functions
# Begin real processing below this line
if [ ! -x "/sbin/frobnicate" ]; then
	exit 0
fi
force_load frobnicator interval=10
cp /sbin/frobnicate "${DESTDIR}/sbin"
exit 0

An example boot script would look something like this (and would usually be placed in /etc/initramfs-tools/scripts/local-top/frobnicate):

#!/bin/sh
# Example frobnication boot script
PREREQ="lvm"
prereqs()
{
	echo "$PREREQ"
}
case $1 in
prereqs)
	prereqs
	exit 0
	;;
esac
\fR. /scripts/functions
# Begin real processing below this line
if [ ! -x "/sbin/frobnicate" ]; then
	panic "Frobnication executable not found"
fi
if [ ! -e "/dev/mapper/frobb" ]; then
	panic "Frobnication device not found"
fi
log_begin_msg "Starting frobnication"
/sbin/frobnicate "/dev/mapper/frobb" || panic "Frobnication failed"
log_end_msg
exit 0

init sets several variables for the boot scripts environment.

• \fB\fI ROOT
      corresponds to the root boot option. Advanced boot scripts like cryptsetup or live-initramfs need to play tricks. Otherwise keep it alone.
• \fB\fI ROOTDELAY, ROOTFLAGS, ROOTFSTYPE, IP
      corresponds to the rootdelay, rootflags, rootfstype or ip boot option.
• \fB\fI DPKG_ARCH
      allows arch specific boot actions.
• \fB\fI blacklist, panic, quiet, resume, noresume, resume_offset
      set according relevant boot option.
• \fB\fI break
      Useful for manual intervention during setup and coding an boot script.
• \fB\fI REASON
      Argument passed to the panic helper function. Use to find out why you landed in the initramfs shell.
• \fB\fI init
      passes the path to init(8) usually /sbin/init.
• \fB\fI readonly
      is the default for mounting the root corresponds to the ro bootarg. Overridden by rw bootarg.
• \fB\fI rootmnt
      is the path where root gets mounted usually /root.
• \fB\fI debug
      indicates that a debug log is captured for further investigation.