path: root/patches/source/mkinitrd/mkinitrd.conf.5
diff options
Diffstat (limited to 'patches/source/mkinitrd/mkinitrd.conf.5')
1 files changed, 244 insertions, 0 deletions
diff --git a/patches/source/mkinitrd/mkinitrd.conf.5 b/patches/source/mkinitrd/mkinitrd.conf.5
new file mode 100644
index 00000000..65c18018
--- /dev/null
+++ b/patches/source/mkinitrd/mkinitrd.conf.5
@@ -0,0 +1,244 @@
+.\" mkinitrd.5 Robby Workman <>
+.\" 28 August 2010 "
+.TH MKINITRD.CONF 5 "27 March 2010" "Slackware 13.1"
+.B mkinitrd.conf(5)
+.B mkinitrd.conf - optional configuration file for
+.I mkinitrd(8)
+.I mkinitrd.conf
+file contains options to be passed to
+.I mkinitrd(8)
+on every run if mkinitrd is executed with the -F flag.
+It is intended as a fast and easy way for the system administrator to
+pass options to mkinitrd without having to type them on each execution.
+Options passed to
+.I mkinitrd(8)
+on the command line will override any
+values set in the config file.
+All options are in the format of OPTION="value"
+Unset variables have no effect.
+.TP 5
+This is the location for the initrd's source tree.
+Defaults to "/boot/initrd-tree"
+.TP 5
+This option specifies whether to clear the initrd source tree prior to
+creating the initrd.
+This requires a value of either "0" or "1" where 0=no and 1=yes
+CLEAR_TREE="0" # Do not clear initrd tree first
+CLEAR_TREE="1" # Clear initrd tree first
+It is recommended to leave this unset and pass "-c" on the command line
+when clearing the tree is desired. Clearing the tree is not desirable
+if you wish to build support for more than one kernel into the initrd
+.TP 5
+This is the location for the initrd image that is created.
+Defaults to "/boot/initrd.gz"
+.TP 5
+This is the kernel version for which the initrd should be created.
+Defaults to "$(uname -r)"
+.TP 5
+This is the custom keyboard map that should be loaded instead of the
+default 'us' keymap.
+The file /usr/share/mkinitrd/keymaps.tar.gz contains all possible keymaps
+to choose from (omit the '.bmap' extension in the mkinitrd command)
+Example: KEYMAP="nl"
+.TP 5
+This should be a colon-separated list of modules you wish to be included
+in the initrd image.
+Example: MODULE_LIST="ext3:mbcache:jbd"
+If you have loadtime options that you need to specify when loading kernel
+modules, those can be added here as well.
+Example: MODULE_LIST="module1:module2 option=1:module3"
+.TP 5
+Contains a colon (:) delimited list of luks encrypted block devices to be
+unlocked by the initrd using cryptsetup. All devices that must be unlocked
+in order to access the root filesystem must be specified.
+Example: LUKSDEV="/dev/sda2:/dev/sda3"
+Each unlocked device will be assigned an automatically generated luks device
+name of the form luks<device> where '<device>' will be the basename of the
+encrypted device. e.g.
+ /dev/mapper/lukssda2
+As a convenience to users, if
+(see below) specifies one of the device names listed in the
+option, then it will be automatically adjusted to use the correct luks
+device name. i.e. when specifying
+.I "LUKSDEV=/dev/sda2"
+.I "ROOTDEV=/dev/sda2"
+.I "ROOTDEV=/dev/mapper/lukssda2"
+are equivalent.
+.TP 5
+When using cryptsetup to encrypt your partition, you can use a keyfile instead
+of a passphrase to unlock the LUKS volume. The LUKSKEY variable holds the
+filename of a keyfile, as well as the label (or uuid) of the partition this
+file is on. This way, you can unlock your computer automatically if you have a
+USB stick with your LUKS key inserted at boot. A passphrase will still be asked
+if the LUKS key can not be found.
+For example, if your USB thumb drive has a FAT partition with label
+"TRAVELSTICK" and the actual keyfile is called "/keys/alien.luks", then
+you need to set:
+.TP 5
+Contains a colon (:) delimited list of luks encrypted block devices to be
+passed the "--allow-discards" option when unlocked by the initrd using
+cryptsetup. This has the effect of allowing TRIM on SSD drives. Be sure
+your SSD supports this feature (correctly) before enabling it.
+See fstrim(8) for more information.
+Example: LUKSTRIM="/dev/sda2:/dev/sda4"
+.TP 5
+The device on which your root filesystem is located.
+Example: ROOTDEV="/dev/sda2"
+If you are using cryptsetup and an encrypted root filesystem, be sure to
+read the option above for LUKSDEV or Bad Things will happen.
+.TP 5
+The filesystem type of your root filesystem
+Example: ROOTFS="ext3"
+.TP 5
+This option adds the mdadm binary to the initrd to support RAID.
+Additional modules may be required, depending on your kernel
+configuration. If you wish to add LVM support to the initrd, then
+set this to 1; otherwise, leave it unset or set it to 0.
+RAID="0" # Do not add RAID support to initrd
+RAID="1" # Add RAID support to initrd
+.TP 5
+This option adds support for LVM partitions into the initrd.
+If you wish to add LVM support to the initrd, then set this to 1;
+otherwise, leave it unset or set it to 0.
+LVM="0" # Do not add LVM support to initrd
+LVM="1" # Add LVM support to initrd
+.TP 5
+Use UDEV in the initrd.
+UDEV="0" # Do not use udev in the initrd
+UDEV="1" # Use udev in the initrd (this is the default)
+.TP 5
+This defines the time to wait, in seconds, until all disks are detected.
+This is useful for allowing extra time that might be needed for slow usb disks or systems with large amounts of storage to become ready.
+If not defined, the default is 1 second.
+.TP 5
+The swap partition holding your hibernation image.
+Example: RESUMEDEV="/dev/sda2"
+.TP 5
+This option defines whether to copy the module-init-tools config files
+from /etc/modprobe.d/ into the initrd. This will not usually be necessary,
+but if you need certain modules to be loaded with special options, and you
+have this configured in a file in /etc/modprobe.d/, this is one way to
+accomplish the desired goal.
+MODCONF="0" # Do not add /etc/modprobe.d/* to the initrd
+MODCONF="1" # Add /etc/modprobe.d/* to the initrd
+.TP 5
+This option specifies a cpio archive containing updated microcode for your CPU.
+CPU manufacturers occasionally release such updates to fix bugs in the microcode
+currently embedded in the CPU. The microcode archive will be prepended to the
+output initrd, where the kernel will find it for early patching.
+.I /etc/mkinitrd.conf
+See /etc/mkinitrd.conf.sample
+.BR mkinitrd "(8)"
+None known :-)
+Support for mkinitrd.conf was added in mkinitrd-1.3.0