1DRACUT.CMDLINE(7)                   dracut                   DRACUT.CMDLINE(7)
2
3
4

NAME

6       dracut.cmdline - dracut kernel command line options
7

DESCRIPTION

9       The root device used by the kernel is specified in the boot
10       configuration file on the kernel command line, as always.
11
12       The traditional root=/dev/sda1 style device specification is allowed,
13       but not encouraged. The root device should better be identified by
14       LABEL or UUID. If a label is used, as in root=LABEL=<label_of_root> the
15       initramfs will search all available devices for a filesystem with the
16       appropriate label, and mount that device as the root filesystem.
17       root=UUID=<uuidnumber> will mount the partition with that UUID as the
18       root filesystem.
19
20       In the following all kernel command line parameters, which are
21       processed by dracut, are described.
22
23       "rd.*" parameters mentioned without "=" are boolean parameters. They
24       can be turned on/off by setting them to {0|1}. If the assignment with
25       "=" is missing "=1" is implied. For example rd.info can be turned off
26       with rd.info=0 or turned on with rd.info=1 or rd.info. The last value
27       in the kernel command line is the value, which is honored.
28
29   Standard
30       init=<path to real init>
31           specify the path to the init program to be started after the
32           initramfs has finished
33
34       root=<path to blockdevice>
35           specify the block device to use as the root filesystem.
36
37           Example.
38
39               root=/dev/sda1
40               root=/dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0-part1
41               root=/dev/disk/by-label/Root
42               root=LABEL=Root
43               root=/dev/disk/by-uuid/3f5ad593-4546-4a94-a374-bcfb68aa11f7
44               root=UUID=3f5ad593-4546-4a94-a374-bcfb68aa11f7
45               root=PARTUUID=3f5ad593-4546-4a94-a374-bcfb68aa11f7
46
47
48       rootfstype=<filesystem type>
49           "auto" if not specified.
50
51           Example.
52
53               rootfstype=ext3
54
55
56       rootflags=<mount options>
57           specify additional mount options for the root filesystem. If not
58           set, /etc/fstab of the real root will be parsed for special mount
59           options and mounted accordingly.
60
61       ro
62           force mounting / and /usr (if it is a separate device) read-only.
63           If none of ro and rw is present, both are mounted according to
64           /etc/fstab.
65
66       rw
67           force mounting / and /usr (if it is a separate device) read-write.
68           See also ro option.
69
70       rootfallback=<path to blockdevice>
71           specify the block device to use as the root filesystem, if the
72           normal root cannot be found. This can only be a simple block device
73           with a simple file system, for which the filesystem driver is
74           either compiled in, or added manually to the initramfs. This
75           parameter can be specified multiple times.
76
77       rd.auto rd.auto=1
78           enable autoassembly of special devices like cryptoLUKS, dmraid,
79           mdraid or lvm. Default is off as of dracut version >= 024.
80
81       rd.hostonly=0
82           removes all compiled in configuration of the host system the
83           initramfs image was built on. This helps booting, if any disk
84           layout changed, especially in combination with rd.auto or other
85           parameters specifying the layout.
86
87       rd.cmdline=ask
88           prompts the user for additional kernel command line parameters
89
90       rd.fstab=0
91           do not honor special mount options for the root filesystem found in
92           /etc/fstab of the real root.
93
94       resume=<path to resume partition>
95           resume from a swap partition
96
97           Example.
98
99               resume=/dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0-part1
100               resume=/dev/disk/by-uuid/3f5ad593-4546-4a94-a374-bcfb68aa11f7
101               resume=UUID=3f5ad593-4546-4a94-a374-bcfb68aa11f7
102
103
104       rd.skipfsck
105           skip fsck for rootfs and /usr. If you’re mounting /usr read-only
106           and the init system performs fsck before remount, you might want to
107           use this option to avoid duplication.
108
109   iso-scan/filename
110       Mount all mountable devices and search for ISO pointed by the argument.
111       When the ISO is found set it up as a loop device. Device containing
112       this ISO image will stay mounted at /run/initramfs/isoscandev. Using
113       iso-scan/filename with a Fedora/Red Hat/CentOS Live iso should just
114       work by copying the original kernel cmdline parameters.
115
116       Example.
117
118           menuentry 'Live Fedora 20' --class fedora --class gnu-linux --class gnu --class os {
119               set isolabel=Fedora-Live-LXDE-x86_64-20-1
120               set isofile="/boot/iso/Fedora-Live-LXDE-x86_64-20-1.iso"
121               loopback loop $isofile
122               linux (loop)/isolinux/vmlinuz0 boot=isolinux iso-scan/filename=$isofile root=live:LABEL=$isolabel ro rd.live.image quiet rhgb
123               initrd (loop)/isolinux/initrd0.img
124           }
125
126
127   Misc
128       rd.emergency=[reboot|poweroff|halt]
129           specify, what action to execute in case of a critical failure.
130           rd.shell=0 also be specified.
131
132       rd.driver.blacklist=<drivername>[,<drivername>,...]
133           do not load kernel module <drivername>. This parameter can be
134           specified multiple times.
135
136       rd.driver.pre=<drivername>[,<drivername>,...]
137           force loading kernel module <drivername>. This parameter can be
138           specified multiple times.
139
140       rd.driver.post=<drivername>[,<drivername>,...]
141           force loading kernel module <drivername> after all automatic
142           loading modules have been loaded. This parameter can be specified
143           multiple times.
144
145       rd.retry=<seconds>
146           specify how long dracut should retry the initqueue to configure
147           devices. The default is 180 seconds. After 2/3 of the time,
148           degraded raids are force started. If you have hardware, which takes
149           a very long time to announce its drives, you might want to extend
150           this value.
151
152       rd.timeout=<seconds>
153           specify how long dracut should wait for devices to appear. The
154           default is 0, which means forever. Note that this timeout should be
155           longer than rd.retry to allow for proper configuration.
156
157       rd.noverifyssl
158           accept self-signed certificates for ssl downloads.
159
160       rd.ctty=<terminal device>
161           specify the controlling terminal for the console. This is useful,
162           if you have multiple "console=" arguments.
163
164       rd.shutdown.timeout.umount=<seconds>
165           specify how long dracut should wait for an individual umount to
166           finish during shutdown. This avoids the system from blocking when
167           unmounting a file system cannot complete and waits indefinitely.
168           Value 0 means to wait forever. The default is 90 seconds.
169
170   Debug
171       If you are dropped to an emergency shell, the file
172       /run/initramfs/rdsosreport.txt is created, which can be saved to a (to
173       be mounted by hand) partition (usually /boot) or a USB stick.
174       Additional debugging info can be produced by adding rd.debug to the
175       kernel command line. /run/initramfs/rdsosreport.txt contains all logs
176       and the output of some tools. It should be attached to any report about
177       dracut problems.
178
179       rd.info
180           print informational output though "quiet" is set
181
182       rd.shell
183           allow dropping to a shell, if root mounting fails
184
185       rd.debug
186           set -x for the dracut shell. If systemd is active in the initramfs,
187           all output is logged to the systemd journal, which you can inspect
188           with "journalctl -ab". If systemd is not active, the logs are
189           written to dmesg and /run/initramfs/init.log. If "quiet" is set, it
190           also logs to the console.
191
192       rd.memdebug=[0-5]
193           Print memory usage info at various points, set the verbose level
194           from 0 to 5.
195
196               Higher level means more debugging output:
197
198                   0 - no output
199                   1 - partial /proc/meminfo
200                   2 - /proc/meminfo
201                   3 - /proc/meminfo + /proc/slabinfo
202                   4 - /proc/meminfo + /proc/slabinfo + memstrack summary
203                       NOTE: memstrack is a memory tracing tool that tracks the total memory
204                             consumption, and peak memory consumption of each kernel modules
205                             and userspace progress during the whole initramfs runtime, report
206                             is genereted and the end of initramsfs run.
207                   5 - /proc/meminfo + /proc/slabinfo + memstrack (with top memory stacktrace)
208                       NOTE: memstrack (with top memory stacktrace) will print top memory
209                             allocation stack traces during the whole initramfs runtime.
210
211       rd.break
212           drop to a shell at the end
213
214       rd.break={cmdline|pre-udev|pre-trigger|initqueue|pre-mount|mount|pre-pivot|cleanup}
215           drop to a shell on defined breakpoint
216
217       rd.udev.info
218           set udev to loglevel info
219
220       rd.udev.debug
221           set udev to loglevel debug
222
223   I18N
224       rd.vconsole.keymap=<keymap base file name>
225           keyboard translation table loaded by loadkeys; taken from keymaps
226           directory; will be written as KEYMAP to /etc/vconsole.conf in the
227           initramfs.
228
229           Example.
230
231               rd.vconsole.keymap=de-latin1-nodeadkeys
232
233
234       rd.vconsole.keymap.ext=<list of keymap base file names>
235           list of extra keymaps to bo loaded (sep. by space); will be written
236           as EXT_KEYMAP to /etc/vconsole.conf in the initramfs
237
238       rd.vconsole.unicode
239           boolean, indicating UTF-8 mode; will be written as UNICODE to
240           /etc/vconsole.conf in the initramfs
241
242       rd.vconsole.font=<font base file name>
243           console font; taken from consolefonts directory; will be written as
244           FONT to /etc/vconsole.conf in the initramfs.
245
246           Example.
247
248               rd.vconsole.font=eurlatgr
249
250
251       rd.vconsole.font.map=<console map base file name>
252           see description of -m parameter in setfont manual; taken from
253           consoletrans directory; will be written as FONT_MAP to
254           /etc/vconsole.conf in the initramfs
255
256       rd.vconsole.font.unimap=<unicode table base file name>
257           see description of -u parameter in setfont manual; taken from
258           unimaps directory; will be written as FONT_UNIMAP to
259           /etc/vconsole.conf in the initramfs
260
261       rd.locale.LANG=<locale>
262           taken from the environment; if no UNICODE is defined we set its
263           value in basis of LANG value (whether it ends with ".utf8" (or
264           similar) or not); will be written as LANG to /etc/locale.conf in
265           the initramfs.
266
267           Example.
268
269               rd.locale.LANG=pl_PL.utf8
270
271
272       rd.locale.LC_ALL=<locale>
273           taken from the environment; will be written as LC_ALL to
274           /etc/locale.conf in the initramfs
275
276   LVM
277       rd.lvm=0
278           disable LVM detection
279
280       rd.lvm.vg=<volume group name>
281           only activate all logical volumes in the the volume groups with the
282           given name. rd.lvm.vg can be specified multiple times on the kernel
283           command line.
284
285       rd.lvm.lv=<volume group name>/<logical volume name>
286           only activate the logical volumes with the given name. rd.lvm.lv
287           can be specified multiple times on the kernel command line.
288
289       rd.lvm.conf=0
290           remove any /etc/lvm/lvm.conf, which may exist in the initramfs
291
292   crypto LUKS
293       rd.luks=0
294           disable crypto LUKS detection
295
296       rd.luks.uuid=<luks uuid>
297           only activate the LUKS partitions with the given UUID. Any "luks-"
298           of the LUKS UUID is removed before comparing to <luks uuid>. The
299           comparisons also matches, if <luks uuid> is only the beginning of
300           the LUKS UUID, so you don’t have to specify the full UUID. This
301           parameter can be specified multiple times.  <luks uuid> may be
302           prefixed by the keyword keysource:, see rd.luks.key below.
303
304       rd.luks.allow-discards=<luks uuid>
305           Allow using of discards (TRIM) requests for LUKS partitions with
306           the given UUID. Any "luks-" of the LUKS UUID is removed before
307           comparing to <luks uuid>. The comparisons also matches, if <luks
308           uuid> is only the beginning of the LUKS UUID, so you don’t have to
309           specify the full UUID. This parameter can be specified multiple
310           times.
311
312       rd.luks.allow-discards
313           Allow using of discards (TRIM) requests on all LUKS partitions.
314
315       rd.luks.crypttab=0
316           do not check, if LUKS partition is in /etc/crypttab
317
318       rd.luks.timeout=<seconds>
319           specify how long dracut should wait when waiting for the user to
320           enter the password. This avoid blocking the boot if no password is
321           entered. It does not apply to luks key. The default is 0, which
322           means forever.
323
324   crypto LUKS - key on removable device support
325       NB: If systemd is included in the dracut initrd, dracut’s built in
326       removable device keying support won’t work. systemd will prompt for a
327       password from the console even if you’ve supplied rd.luks.key. You may
328       be able to use standard systemd fstab(5) syntax to get the same effect.
329       If you do need rd.luks.key to work, you will have to exclude the
330       "systemd" dracut module and any modules that depend on it. See
331       dracut.conf(5) and https://bugzilla.redhat.com/show_bug.cgi?id=905683
332       for more information.
333
334       rd.luks.key=<keypath>[:<keydev>[:<luksdev>]]
335           <keypath> is the pathname of a key file, relative to the root of
336           the filesystem on some device. It’s REQUIRED. When <keypath> ends
337           with .gpg it’s considered to be key encrypted symmetrically with
338           GPG. You will be prompted for the GPG password on boot. GPG support
339           comes with the crypt-gpg module, which needs to be added
340           explicitly.
341
342           <keydev> identifies the device on which the key file resides. It
343           may be the kernel name of the device (should start with "/dev/"), a
344           UUID (prefixed with "UUID=") or a label (prefix with "LABEL="). You
345           don’t have to specify a full UUID. Just its beginning will suffice,
346           even if its ambiguous. All matching devices will be probed. This
347           parameter is recommended, but not required. If it’s not present,
348           all block devices will be probed, which may significantly increase
349           boot time.
350
351           If <luksdev> is given, the specified key will only be used for the
352           specified LUKS device. Possible values are the same as for
353           <keydev>. Unless you have several LUKS devices, you don’t have to
354           specify this parameter. The simplest usage is:
355
356           Example.
357
358               rd.luks.key=/foo/bar.key
359
360
361           As you see, you can skip colons in such a case.
362
363           Note
364           Your LUKS partition must match your key file.
365
366           dracut provides keys to cryptsetup with -d (an older alias for
367           --key-file). This uses the entire binary content of the key file as
368           part of the secret. If you pipe a password into cryptsetup without
369           -d or --key-file, it will be treated as text user input, and only
370           characters before the first newline will be used. Therefore, when
371           you’re creating an encrypted partition for dracut to mount, and you
372           pipe a key into cryptsetup luksFormat,you must use -d -.
373
374           Here is an example for a key encrypted with GPG (warning:
375           --batch-mode will overwrite the device without asking for
376           confirmation):
377
378               gpg --quiet --decrypt rootkey.gpg | \
379               cryptsetup --batch-mode --key-file - \
380                          luksFormat /dev/sda47
381
382           If you use unencrypted key files, just use the key file pathname
383           instead of the standard input. For a random key with 256 bits of
384           entropy, you might use:
385
386               head -32c /dev/urandom > rootkey.key
387               cryptsetup --batch-mode --key-file rootkey.key \
388                          luksFormat /dev/sda47
389
390           You can also use regular key files on an encrypted keydev.
391
392           Compared to using GPG encrypted keyfiles on an unencrypted device
393           this provides the following advantages:
394
395           •   you can unlock your disk(s) using multiple passphrases
396
397           •   better security by not loosing the key stretching mechanism
398
399           To use an encrypted keydev you must ensure that it becomes
400           available by using the keyword keysource, e.g.
401           rd.luks.uuid=keysource:aaaa aaaa being the uuid of the encrypted
402           keydev.
403
404           Example:
405
406           Lets assume you have three disks A, B and C with the uuids aaaa,
407           bbbb and cccc. You want to unlock A and B using keyfile keyfile.
408           The unlocked volumes be A', B' and C' with the uuids AAAA, BBBB and
409           CCCC. keyfile is saved on C' as /keyfile.
410
411           One luks keyslot of each A, B and C is setup with a passphrase.
412           Another luks keyslot of each A and B is setup with keyfile.
413
414           To boot this configuration you could use:
415
416               rd.luks.uuid=aaaa
417               rd.luks.uuid=bbbb
418               rd.luks.uuid=keysource:cccc
419               rd.luks.key=/keyfile:UUID=CCCC
420
421           Dracut asks for the passphrase for C and uses the keyfile to unlock
422           A and B. If getting the passphrase for C fails it falls back to
423           asking for the passphrases for A and B.
424
425           If you want C' to stay unlocked, specify a luks name for it, e.g.
426           rd.luks.name=cccc=mykeys, otherwise it gets closed when not needed
427           anymore.
428
429   MD RAID
430       rd.md=0
431           disable MD RAID detection
432
433       rd.md.imsm=0
434           disable MD RAID for imsm/isw raids, use DM RAID instead
435
436       rd.md.ddf=0
437           disable MD RAID for SNIA ddf raids, use DM RAID instead
438
439       rd.md.conf=0
440           ignore mdadm.conf included in initramfs
441
442       rd.md.waitclean=1
443           wait for any resync, recovery, or reshape activity to finish before
444           continuing
445
446       rd.md.uuid=<md raid uuid>
447           only activate the raid sets with the given UUID. This parameter can
448           be specified multiple times.
449
450   DM RAID
451       rd.dm=0
452           disable DM RAID detection
453
454       rd.dm.uuid=<dm raid uuid>
455           only activate the raid sets with the given UUID. This parameter can
456           be specified multiple times.
457
458   MULTIPATH
459       rd.multipath=0
460           disable multipath detection
461
462       rd.multipath=default
463           use default multipath settings
464
465   FIPS
466       rd.fips
467           enable FIPS
468
469       boot=<boot device>
470           specify the device, where /boot is located.
471
472           Example.
473
474               boot=/dev/sda1
475               boot=/dev/disk/by-path/pci-0000:00:1f.1-scsi-0:0:1:0-part1
476               boot=UUID=<uuid>
477               boot=LABEL=<label>
478
479
480       rd.fips.skipkernel
481           skip checksum check of the kernel image. Useful, if the kernel
482           image is not in a separate boot partition.
483
484   Network
485           Important
486           It is recommended to either bind an interface to a MAC with the
487           ifname argument, or to use the systemd-udevd predictable network
488           interface names.
489
490           Predictable network interface device names based on:
491
492           •   firmware/bios-provided index numbers for on-board devices
493
494           •   firmware-provided pci-express hotplug slot index number
495
496           •   physical/geographical location of the hardware
497
498           •   the interface’s MAC address
499
500           See:
501           http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
502
503           Two character prefixes based on the type of interface:
504
505           en
506               ethernet
507
508           wl
509               wlan
510
511           ww
512               wwan
513
514           Type of names:
515
516           o<index>
517               on-board device index number
518
519           s<slot>[f<function>][d<dev_id>]
520               hotplug slot index number
521
522           x<MAC>
523               MAC address
524
525           [P<domain>]p<bus>s<slot>[f<function>][d<dev_id>]
526               PCI geographical location
527
528           [P<domain>]p<bus>s<slot>[f<function>][u<port>][..][c<config>][i<interface>]
529               USB port number chain
530
531           All multi-function PCI devices will carry the [f<function>] number
532           in the device name, including the function 0 device.
533
534           When using PCI geography, The PCI domain is only prepended when it
535           is not 0.
536
537           For USB devices the full chain of port numbers of hubs is composed.
538           If the name gets longer than the maximum number of 15 characters,
539           the name is not exported. The usual USB configuration == 1 and
540           interface == 0 values are suppressed.
541
542           PCI ethernet card with firmware index "1"
543
544               •   eno1
545
546           PCI ethernet card in hotplug slot with firmware index number
547
548               •   ens1
549
550           PCI ethernet multi-function card with 2 ports
551
552               •   enp2s0f0
553
554               •   enp2s0f1
555
556           PCI wlan card
557
558               •   wlp3s0
559
560           USB built-in 3G modem
561
562               •   wwp0s29u1u4i6
563
564           USB Android phone
565
566               •   enp0s29u1u2
567
568       The following options are supported by the network-legacy dracut
569       module. Other network modules might support a slightly different set of
570       options; refer to the documentation of the specific network module in
571       use. For NetworkManager, see nm-initrd-generator(8).
572
573       ip={dhcp|on|any|dhcp6|auto6|either6|link6|single-dhcp}
574
575           dhcp|on|any
576               get ip from dhcp server from all interfaces. If netroot=dhcp,
577               loop sequentially through all interfaces (eth0, eth1, ...) and
578               use the first with a valid DHCP root-path.
579
580           single-dhcp
581               Send DHCP on all available interfaces in parallel, as opposed
582               to one after another. After the first DHCP response is
583               received, stop DHCP on all other interfaces. This gives the
584               fastest boot time by using the IP on interface for which DHCP
585               succeeded first during early boot. Caveat: Does not apply to
586               Network Manager and to SUSE using wicked.
587
588           auto6
589               IPv6 autoconfiguration
590
591           dhcp6
592               IPv6 DHCP
593
594           either6
595               if auto6 fails, then dhcp6
596
597           link6
598               bring up interface for IPv6 link-local addressing
599
600       ip=<interface>:{dhcp|on|any|dhcp6|auto6|link6}[:[<mtu>][:<macaddr>]]
601           This parameter can be specified multiple times.
602
603           dhcp|on|any|dhcp6
604               get ip from dhcp server on a specific interface
605
606           auto6
607               do IPv6 autoconfiguration
608
609           link6
610               bring up interface for IPv6 link local address
611
612           <macaddr>
613               optionally set <macaddr> on the <interface>. This cannot be
614               used in conjunction with the ifname argument for the same
615               <interface>.
616
617       ip=<client-IP>:[<peer>]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[<mtu>][:<macaddr>]]
618           explicit network configuration. If you want do define a IPv6
619           address, put it in brackets (e.g. [2001:DB8::1]). This parameter
620           can be specified multiple times.  <peer> is optional and is the
621           address of the remote endpoint for pointopoint interfaces and it
622           may be followed by a slash and a decimal number, encoding the
623           network prefix length.
624
625           <macaddr>
626               optionally set <macaddr> on the <interface>. This cannot be
627               used in conjunction with the ifname argument for the same
628               <interface>.
629
630       ip=<client-IP>:[<peer>]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[<dns1>][:<dns2>]]
631           explicit network configuration. If you want do define a IPv6
632           address, put it in brackets (e.g. [2001:DB8::1]). This parameter
633           can be specified multiple times.  <peer> is optional and is the
634           address of the remote endpoint for pointopoint interfaces and it
635           may be followed by a slash and a decimal number, encoding the
636           network prefix length.
637
638       ifname=<interface>:<MAC>
639           Assign network device name <interface> (i.e. "bootnet") to the NIC
640           with MAC <MAC>.
641
642               Warning
643               Do not use the default kernel naming scheme for the interface
644               name, as it can conflict with the kernel names. So, don’t use
645               "eth[0-9]+" for the interface name. Better name it "bootnet" or
646               "bluesocket".
647
648       rd.route=<net>/<netmask>:<gateway>[:<interface>]
649           Add a static route with route options, which are separated by a
650           colon. IPv6 addresses have to be put in brackets.
651
652           Example.
653
654                   rd.route=192.168.200.0/24:192.168.100.222:ens10
655                   rd.route=192.168.200.0/24:192.168.100.222
656                   rd.route=192.168.200.0/24::ens10
657                   rd.route=[2001:DB8:3::/8]:[2001:DB8:2::1]:ens10
658
659
660       bootdev=<interface>
661           specify network interface to use routing and netroot information
662           from. Required if multiple ip= lines are used.
663
664       BOOTIF=<MAC>
665           specify network interface to use routing and netroot information
666           from.
667
668       rd.bootif=0
669           Disable BOOTIF parsing, which is provided by PXE
670
671       nameserver=<IP> [nameserver=<IP> ...]
672           specify nameserver(s) to use
673
674       rd.peerdns=0
675           Disable DNS setting of DHCP parameters.
676
677       biosdevname=0
678           boolean, turn off biosdevname network interface renaming
679
680       rd.neednet=1
681           boolean, bring up network even without netroot set
682
683       vlan=<vlanname>:<phydevice>
684           Setup vlan device named <vlanname> on <phydevice>. We support the
685           four styles of vlan names: VLAN_PLUS_VID (vlan0005),
686           VLAN_PLUS_VID_NO_PAD (vlan5), DEV_PLUS_VID (eth0.0005),
687           DEV_PLUS_VID_NO_PAD (eth0.5)
688
689       bond=<bondname>[:<bondslaves>:[:<options>[:<mtu>]]]
690           Setup bonding device <bondname> on top of <bondslaves>.
691           <bondslaves> is a comma-separated list of physical (ethernet)
692           interfaces. <options> is a comma-separated list on bonding options
693           (modinfo bonding for details) in format compatible with
694           initscripts. If <options> includes multi-valued arp_ip_target
695           option, then its values should be separated by semicolon. if the
696           mtu is specified, it will be set on the bond master. Bond without
697           parameters assumes bond=bond0:eth0,eth1:mode=balance-rr
698
699       team=<teammaster>:<teamslaves>[:<teamrunner>]
700           Setup team device <teammaster> on top of <teamslaves>. <teamslaves>
701           is a comma-separated list of physical (ethernet) interfaces.
702           <teamrunner> is the runner type to be used (see teamd.conf(5));
703           defaults to activebackup. Team without parameters assumes
704           team=team0:eth0,eth1:activebackup
705
706       bridge=<bridgename>:<ethnames>
707           Setup bridge <bridgename> with <ethnames>. <ethnames> is a
708           comma-separated list of physical (ethernet) interfaces. Bridge
709           without parameters assumes bridge=br0:eth0
710
711   NFS
712       root=[<server-ip>:]<root-dir>[:<nfs-options>]
713           mount nfs share from <server-ip>:/<root-dir>, if no server-ip is
714           given, use dhcp next_server. If server-ip is an IPv6 address it has
715           to be put in brackets, e.g. [2001:DB8::1]. NFS options can be
716           appended with the prefix ":" or "," and are separated by ",".
717
718       root=nfs:[<server-ip>:]<root-dir>[:<nfs-options>],
719       root=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>], root={dhcp|dhcp6}
720           netroot=dhcp alone directs initrd to look at the DHCP root-path
721           where NFS options can be specified.
722
723           Example.
724
725                   root-path=<server-ip>:<root-dir>[,<nfs-options>]
726                   root-path=nfs:<server-ip>:<root-dir>[,<nfs-options>]
727                   root-path=nfs4:<server-ip>:<root-dir>[,<nfs-options>]
728
729
730       root=/dev/nfs nfsroot=[<server-ip>:]<root-dir>[:<nfs-options>]
731           Deprecated!  kernel Documentation_/filesystems/nfsroot.txt_ defines
732           this method. This is supported by dracut, but not recommended.
733
734       rd.nfs.domain=<NFSv4 domain name>
735           Set the NFSv4 domain name. Will override the settings in
736           /etc/idmap.conf.
737
738       rd.net.dhcp.retry=<cnt>
739           If this option is set, dracut will try to connect via dhcp <cnt>
740           times before failing. Default is 1.
741
742       rd.net.timeout.dhcp=<arg>
743           If this option is set, dhclient is called with "-timeout <arg>".
744
745       rd.net.timeout.iflink=<seconds>
746           Wait <seconds> until link shows up. Default is 60 seconds.
747
748       rd.net.timeout.ifup=<seconds>
749           Wait <seconds> until link has state "UP". Default is 20 seconds.
750
751       rd.net.timeout.route=<seconds>
752           Wait <seconds> until route shows up. Default is 20 seconds.
753
754       rd.net.timeout.ipv6dad=<seconds>
755           Wait <seconds> until IPv6 DAD is finished. Default is 50 seconds.
756
757       rd.net.timeout.ipv6auto=<seconds>
758           Wait <seconds> until IPv6 automatic addresses are assigned. Default
759           is 40 seconds.
760
761       rd.net.timeout.carrier=<seconds>
762           Wait <seconds> until carrier is recognized. Default is 10 seconds.
763
764   CIFS
765       root=cifs://[<username>[:<password>]@]<server-ip>:<root-dir>
766           mount cifs share from <server-ip>:/<root-dir>, if no server-ip is
767           given, use dhcp next_server. if server-ip is an IPv6 address it has
768           to be put in brackets, e.g. [2001:DB8::1]. If a username or
769           password are not specified as part of the root, then they must be
770           passed on the command line through cifsuser/cifspass.
771
772               Warning
773               Passwords specified on the kernel command line are visible for
774               all users via the file /proc/cmdline and via dmesg or can be
775               sniffed on the network, when using DHCP with DHCP root-path.
776
777       cifsuser=<username>
778           Set the cifs username, if not specified as part of the root.
779
780       cifspass=<password>
781           Set the cifs password, if not specified as part of the root.
782
783               Warning
784               Passwords specified on the kernel command line are visible for
785               all users via the file /proc/cmdline and via dmesg or can be
786               sniffed on the network, when using DHCP with DHCP root-path.
787
788   iSCSI
789       root=iscsi:[<username>:<password>[:<reverse>:<password>]@][<servername>]:[<protocol>]:[<port>][:[<iscsi_iface_name>]:[<netdev_name>]]:[<LUN>]:<targetname>
790           protocol defaults to "6", LUN defaults to "0". If the "servername"
791           field is provided by BOOTP or DHCP, then that field is used in
792           conjunction with other associated fields to contact the boot server
793           in the Boot stage. However, if the "servername" field is not
794           provided, then the "targetname" field is then used in the Discovery
795           Service stage in conjunction with other associated fields. See
796           rfc4173[1].
797
798               Warning
799               Passwords specified on the kernel command line are visible for
800               all users via the file /proc/cmdline and via dmesg or can be
801               sniffed on the network, when using DHCP with DHCP root-path.
802
803           Example.
804
805               root=iscsi:192.168.50.1::::iqn.2009-06.dracut:target0
806
807
808           If servername is an IPv6 address, it has to be put in brackets:
809
810           Example.
811
812               root=iscsi:[2001:DB8::1]::::iqn.2009-06.dracut:target0
813
814
815       root=???
816       netroot=iscsi:[<username>:<password>[:<reverse>:<password>]@][<servername>]:[<protocol>]:[<port>][:[<iscsi_iface_name>]:[<netdev_name>]]:[<LUN>]:<targetname>
817       ...
818           multiple netroot options allow setting up multiple iscsi disks:
819
820           Example.
821
822               root=UUID=12424547
823               netroot=iscsi:192.168.50.1::::iqn.2009-06.dracut:target0
824               netroot=iscsi:192.168.50.1::::iqn.2009-06.dracut:target1
825
826
827           If servername is an IPv6 address, it has to be put in brackets:
828
829           Example.
830
831               netroot=iscsi:[2001:DB8::1]::::iqn.2009-06.dracut:target0
832
833
834               Warning
835               Passwords specified on the kernel command line are visible for
836               all users via the file /proc/cmdline and via dmesg or can be
837               sniffed on the network, when using DHCP with DHCP root-path.
838               You may want to use rd.iscsi.firmware.
839
840       root=??? rd.iscsi.initiator=<initiator> rd.iscsi.target.name=<target
841       name> rd.iscsi.target.ip=<target ip> rd.iscsi.target.port=<target port>
842       rd.iscsi.target.group=<target group> rd.iscsi.username=<username>
843       rd.iscsi.password=<password> rd.iscsi.in.username=<in username>
844       rd.iscsi.in.password=<in password>
845           manually specify all iscsistart parameter (see iscsistart --help)
846
847               Warning
848               Passwords specified on the kernel command line are visible for
849               all users via the file /proc/cmdline and via dmesg or can be
850               sniffed on the network, when using DHCP with DHCP root-path.
851               You may want to use rd.iscsi.firmware.
852
853       root=??? netroot=iscsi rd.iscsi.firmware=1
854           will read the iscsi parameter from the BIOS firmware
855
856       rd.iscsi.login_retry_max=<num>
857           maximum number of login retries
858
859       rd.iscsi.param=<param>
860           <param> will be passed as "--param <param>" to iscsistart. This
861           parameter can be specified multiple times.
862
863           Example.
864
865               "netroot=iscsi rd.iscsi.firmware=1 rd.iscsi.param=node.session.timeo.replacement_timeout=30"
866
867
868           will result in
869
870               iscsistart -b --param node.session.timeo.replacement_timeout=30
871
872       rd.iscsi.ibft rd.iscsi.ibft=1: Turn on iBFT autoconfiguration for the
873       interfaces
874
875       rd.iscsi.mp rd.iscsi.mp=1: Configure all iBFT interfaces, not only used
876       for booting (multipath)
877
878       rd.iscsi.waitnet=0: Turn off waiting for all interfaces to be up before
879       trying to login to the iSCSI targets.
880
881       rd.iscsi.testroute=0: Turn off checking, if the route to the iSCSI
882       target IP is possible before trying to login.
883
884   FCoE
885       rd.fcoe=0
886           disable FCoE and lldpad
887
888       fcoe=<edd|interface|MAC>:{dcb|nodcb}:{fabric|vn2vn}
889           Try to connect to a FCoE SAN through the NIC specified by
890           <interface> or <MAC> or EDD settings. The second argument specifies
891           if DCB should be used. The optional third argument specifies
892           whether fabric or VN2VN mode should be used. This parameter can be
893           specified multiple times.
894
895               Note
896               letters in the MAC-address must be lowercase!
897
898   NVMf
899       rd.nvmf.hostnqn=<hostNQN>
900           NVMe host NQN to use
901
902       rd.nvmf.hostid=<hostID>
903           NVMe host id to use
904
905       rd.nvmf.discover={rdma|fc|tcp},<traddr>,[<host_traddr>],[<trsvcid>]
906           Discover and connect to a NVMe-over-Fabric controller specified by
907           <traddr> and the optionally <host_traddr> or <trsvcid>. The first
908           argument specifies the transport to use; currently only rdma, fc,
909           or tcp are supported. The <traddr> parameter can be set to auto to
910           select autodiscovery; in that case all other parameters are
911           ignored. This parameter can be specified multiple times.
912
913   NBD
914       root=???
915       netroot=nbd:<server>:<port/exportname>[:<fstype>[:<mountopts>[:<nbdopts>]]]
916           mount nbd share from <server>.
917
918           NOTE: If "exportname" instead of "port" is given the standard port
919           is used. Newer versions of nbd are only supported with
920           "exportname".
921
922       root=/dev/root netroot=dhcp with dhcp
923       root-path=nbd:<server>:<port/exportname>[:<fstype>[:<mountopts>[:<nbdopts>]]]
924           netroot=dhcp alone directs initrd to look at the DHCP root-path
925           where NBD options can be specified. This syntax is only usable in
926           cases where you are directly mounting the volume as the rootfs.
927
928           NOTE: If "exportname" instead of "port" is given the standard port
929           is used. Newer versions of nbd are only supported with
930           "exportname".
931
932   DASD
933       rd.dasd=....
934           same syntax as the kernel module parameter (s390 only)
935
936   ZFCP
937       rd.zfcp=<zfcp adaptor device bus ID>,<WWPN>,<FCPLUN>
938           rd.zfcp can be specified multiple times on the kernel command line.
939
940       rd.zfcp=<zfcp adaptor device bus ID>
941           If NPIV is enabled and the allow_lun_scan parameter to the zfcp
942           module is set to Y then the zfcp adaptor will be initiating a scan
943           internally and the <WWPN> and <FCPLUN> parameters can be omitted.
944
945           Example.
946
947               rd.zfcp=0.0.4000,0x5005076300C213e9,0x5022000000000000
948               rd.zfcp=0.0.4000
949
950
951       rd.zfcp.conf=0
952           ignore zfcp.conf included in the initramfs
953
954   ZNET
955       rd.znet=<nettype>,<subchannels>,<options>
956           The whole parameter is appended to /etc/ccw.conf, which is used on
957           RHEL/Fedora with ccw_init, which is called from udev for certain
958           devices on z-series. rd.znet can be specified multiple times on the
959           kernel command line.
960
961       rd.znet_ifname=<ifname>:<subchannels>
962           Assign network device name <interface> (i.e. "bootnet") to the NIC
963           corresponds to the subchannels. This is useful when dracut’s
964           default "ifname=" doesn’t work due to device having a changing MAC
965           address.
966
967           Example.
968
969               rd.znet=qeth,0.0.0600,0.0.0601,0.0.0602,layer2=1,portname=foo
970               rd.znet=ctc,0.0.0600,0.0.0601,protocol=bar
971
972
973   Booting live images
974       Dracut offers multiple options for live booted images:
975
976       SquashFS with read-only filesystem image
977           The system will boot with a read-only filesystem from the SquashFS
978           and apply a writable Device-mapper snapshot or an OverlayFS overlay
979           mount for the read-only base filesystem. This method ensures a
980           relatively fast boot and lower RAM usage. Users must be careful to
981           avoid writing too many blocks to a snapshot volume. Once the blocks
982           of the snapshot overlay are exhausted, the root filesystem becomes
983           read-only and may cause application failures. The snapshot overlay
984           file is marked Overflow, and a difficult recovery is required to
985           repair and enlarge the overlay offline. Non-persistent overlays are
986           sparse files in RAM that only consume content space as required
987           blocks are allocated. They default to an apparent size of 32 GiB in
988           RAM. The size can be adjusted with the rd.live.overlay.size= kernel
989           command line option.
990
991           The filesystem structure is traditionally expected to be:
992
993               squashfs.img          |  SquashFS from LiveCD .iso
994                  !(mount)
995                  /LiveOS
996                      |- rootfs.img  |  Filesystem image to mount read-only
997                           !(mount)
998                           /bin      |  Live filesystem
999                           /boot     |
1000                           /dev      |
1001                           ...       |
1002
1003           For OverlayFS mount overlays, the filesystem structure may also be
1004           a direct compression of the root filesystem:
1005
1006               squashfs.img          |  SquashFS from LiveCD .iso
1007                  !(mount)
1008                  /bin               |  Live filesystem
1009                  /boot              |
1010                  /dev               |
1011                  ...                |
1012
1013           Dracut uses one of the overlay methods of live booting by default.
1014           No additional command line options are required other than
1015           root=live:<URL> to specify the location of your squashed
1016           filesystem.
1017
1018           •   The compressed SquashFS image can be copied during boot to RAM
1019               at /run/initramfs/squashed.img by using the rd.live.ram=1
1020               option.
1021
1022           •   A device with a persistent overlay can be booted read-only by
1023               using the rd.live.overlay.readonly option on the kernel command
1024               line. This will either cause a temporary, writable overlay to
1025               be stacked over a read-only snapshot of the root filesystem or
1026               the OverlayFS mount will use an additional lower layer with the
1027               root filesystem.
1028
1029       Uncompressed live filesystem image
1030           When the live system was installed with the --skipcompress option
1031           of the livecd-iso-to-disk installation script for Live USB devices,
1032           the root filesystem image, rootfs.img, is expanded on installation
1033           and no SquashFS is involved during boot.
1034
1035           •   If rd.live.ram=1 is used in this situation, the full,
1036               uncompressed root filesystem is copied during boot to
1037               /run/initramfs/rootfs.img in the /run tmpfs.
1038
1039           •   If rd.live.overlay=none is provided as a kernel command line
1040               option, a writable, linear Device-mapper target is created on
1041               boot with no overlay.
1042
1043       Writable filesystem image
1044           The system will retrieve a compressed filesystem image, extract it
1045           to /run/initramfs/fsimg/rootfs.img, connect it to a loop device,
1046           create a writable, linear Device-mapper target at
1047           /dev/mapper/live-rw, and mount that as a writable volume at /. More
1048           RAM is required during boot but the live filesystem is easier to
1049           manage if it becomes full. Users can make a filesystem image of any
1050           size and that size will be maintained when the system boots. There
1051           is no persistence of root filesystem changes between boots with
1052           this option.
1053
1054           The filesystem structure is expected to be:
1055
1056               rootfs.tgz            |  Compressed tarball containing filesystem image
1057                  !(unpack)
1058                  /rootfs.img        |  Filesystem image at /run/initramfs/fsimg/
1059                     !(mount)
1060                     /bin            |  Live filesystem
1061                     /boot           |
1062                     /dev            |
1063                     ...             |
1064
1065           To use this boot option, ensure that rd.writable.fsimg=1 is in your
1066           kernel command line and add the root=live:<URL> to specify the
1067           location of your compressed filesystem image tarball or SquashFS
1068           image.
1069
1070       rd.writable.fsimg=1
1071           Enables writable filesystem support. The system will boot with a
1072           fully writable (but non-persistent) filesystem without snapshots
1073           (see notes above about available live boot options). You can use
1074           the rootflags option to set mount options for the live filesystem
1075           as well (see documentation about rootflags in the Standard section
1076           above). This implies that the whole image is copied to RAM before
1077           the boot continues.
1078
1079               Note
1080               There must be enough free RAM available to hold the complete
1081               image.
1082           This method is very suitable for diskless boots.
1083
1084       root=live:<url>
1085           Boots a live image retrieved from <url>. Requires the dracut
1086           livenet module. Valid handlers: http, https, ftp, torrent, tftp.
1087
1088           Examples.
1089
1090               root=live:http://example.com/liveboot.img
1091               root=live:ftp://ftp.example.com/liveboot.img
1092               root=live:torrent://example.com/liveboot.img.torrent
1093
1094
1095       rd.live.debug=1
1096           Enables debug output from the live boot process.
1097
1098       rd.live.dir=<path>
1099           Specifies the directory within the boot device where the
1100           squashfs.img or rootfs.img can be found. By default, this is
1101           /LiveOS.
1102
1103       rd.live.squashimg=<filename of SquashFS image>
1104           Specifies the filename for a SquashFS image of the root filesystem.
1105           By default, this is squashfs.img.
1106
1107       rd.live.ram=1
1108           Copy the complete image to RAM and use this for booting. This is
1109           useful when the image resides on, e.g., a DVD which needs to be
1110           ejected later on.
1111
1112       rd.live.overlay={<devspec>[:{<pathspec>|auto}]|none}
1113           Manage the usage of a permanent overlay.
1114
1115<devspec> specifies the path to a device with a mountable
1116               filesystem.
1117
1118<pathspec> is the path to a file within that filesystem, which
1119               shall be used to persist the changes made to the device
1120               specified by the root=live:<url> option.
1121
1122               The default pathspec, when auto or no :<pathspec> is given, is
1123               /<rd.live.dir>/overlay-<label>-<uuid>, where <label> is the
1124               device LABEL, and <uuid> is the device UUID. * none (the word
1125               itself) specifies that no overlay will be used, such as when an
1126               uncompressed, writable live root filesystem is available.
1127
1128               If a persistent overlay is detected at the standard LiveOS
1129               path, the overlay & overlay type detected, whether
1130               Device-mapper or OverlayFS, will be used.
1131
1132           Examples.
1133
1134               rd.live.overlay=/dev/sdb1:persistent-overlay.img
1135               rd.live.overlay=UUID=99440c1f-8daa-41bf-b965-b7240a8996f4
1136
1137
1138       rd.live.overlay.size=<size_MiB>
1139           Specifies a non-persistent Device-mapper overlay size in MiB. The
1140           default is 32768.
1141
1142       rd.live.overlay.readonly=1
1143           This is used to boot with a normally read-write persistent overlay
1144           in a read-only mode. With this option, either an additional,
1145           non-persistent, writable snapshot overlay will be stacked over a
1146           read-only snapshot, /dev/mapper/live-ro, of the base filesystem
1147           with the persistent overlay, or a read-only loop device, in the
1148           case of a writable rootfs.img, or an OverlayFS mount will use the
1149           persistent overlay directory linked at /run/overlayfs-r as an
1150           additional lower layer along with the base root filesystem and
1151           apply a transient, writable upper directory overlay, in order to
1152           complete the booted root filesystem.
1153
1154       rd.live.overlay.reset=1
1155           Specifies that a persistent overlay should be reset on boot. All
1156           previous root filesystem changes are vacated by this action.
1157
1158       rd.live.overlay.thin=1
1159           Enables the usage of thin snapshots instead of classic dm
1160           snapshots. The advantage of thin snapshots is that they support
1161           discards, and will free blocks that are not claimed by the
1162           filesystem. In this use case, this means that memory is given back
1163           to the kernel when the filesystem does not claim it anymore.
1164
1165       rd.live.overlay.overlayfs=1
1166           Enables the use of the OverlayFS kernel module, if available, to
1167           provide a copy-on-write union directory for the root filesystem.
1168           OverlayFS overlays are directories of the files that have changed
1169           on the read-only base (lower) filesystem. The root filesystem is
1170           provided through a special overlay type mount that merges the lower
1171           and upper directories. If an OverlayFS upper directory is not
1172           present on the boot device, a tmpfs directory will be created at
1173           /run/overlayfs to provide temporary storage. Persistent storage can
1174           be provided on vfat or msdos formatted devices by supplying the
1175           OverlayFS upper directory within an embedded filesystem that
1176           supports the creation of trusted.* extended attributes and provides
1177           a valid d_type in readdir responses, such as with ext4 and xfs. On
1178           non-vfat-formatted devices, a persistent OverlayFS overlay can
1179           extend the available root filesystem storage up to the capacity of
1180           the LiveOS disk device.
1181
1182           If a persistent overlay is detected at the standard LiveOS path,
1183           the overlay & overlay type detected, whether OverlayFS or
1184           Device-mapper, will be used.
1185
1186           The rd.live.overlay.readonly option, which allows a persistent
1187           overlayfs to be mounted read-only through a higher level transient
1188           overlay directory, has been implemented through the multiple lower
1189           layers feature of OverlayFS.
1190
1191   ZIPL
1192       rd.zipl=<path to blockdevice>
1193           Update the dracut commandline with the values found in the
1194           dracut-cmdline.conf file on the given device. The values are merged
1195           into the existing commandline values and the udev events are
1196           regenerated.
1197
1198           Example.
1199
1200               rd.zipl=UUID=0fb28157-99e3-4395-adef-da3f7d44835a
1201
1202
1203   CIO_IGNORE
1204       rd.cio_accept=<device-ids>
1205           Remove the devices listed in <device-ids> from the default
1206           cio_ignore kernel command-line settings. <device-ids> is a list of
1207           comma-separated CCW device ids. The default for this value is taken
1208           from the /boot/zipl/active_devices.txt file.
1209
1210           Example.
1211
1212               rd.cio_accept=0.0.0180,0.0.0800,0.0.0801,0.0.0802
1213
1214
1215   Plymouth Boot Splash
1216       plymouth.enable=0
1217           disable the plymouth bootsplash completely.
1218
1219       rd.plymouth=0
1220           disable the plymouth bootsplash only for the initramfs.
1221
1222   Kernel keys
1223       masterkey=<kernel master key path name>
1224           Set the path name of the kernel master key.
1225
1226           Example.
1227
1228               masterkey=/etc/keys/kmk-trusted.blob
1229
1230
1231       masterkeytype=<kernel master key type>
1232           Set the type of the kernel master key.
1233
1234           Example.
1235
1236               masterkeytype=trusted
1237
1238
1239       evmkey=<EVM key path name>
1240           Set the path name of the EVM key.
1241
1242           Example.
1243
1244               evmkey=/etc/keys/evm-trusted.blob
1245
1246
1247       ecryptfskey=<eCryptfs key path name>
1248           Set the path name of the eCryptfs key.
1249
1250           Example.
1251
1252               ecryptfskey=/etc/keys/ecryptfs-trusted.blob
1253
1254
1255   Deprecated, renamed Options
1256       Here is a list of options, which were used in dracut prior to version
1257       008, and their new replacement.
1258
1259       rdbreak
1260           rd.break
1261
1262       rd.ccw
1263           rd.znet
1264
1265       rd_CCW
1266           rd.znet
1267
1268       rd_DASD_MOD
1269           rd.dasd
1270
1271       rd_DASD
1272           rd.dasd
1273
1274       rdinitdebug rdnetdebug
1275           rd.debug
1276
1277       rd_NO_DM
1278           rd.dm=0
1279
1280       rd_DM_UUID
1281           rd.dm.uuid
1282
1283       rdblacklist
1284           rd.driver.blacklist
1285
1286       rdinsmodpost
1287           rd.driver.post
1288
1289       rdloaddriver
1290           rd.driver.pre
1291
1292       rd_NO_FSTAB
1293           rd.fstab=0
1294
1295       rdinfo
1296           rd.info
1297
1298       check
1299           rd.live.check
1300
1301       rdlivedebug
1302           rd.live.debug
1303
1304       live_dir
1305           rd.live.dir
1306
1307       liveimg
1308           rd.live.image
1309
1310       overlay
1311           rd.live.overlay
1312
1313       readonly_overlay
1314           rd.live.overlay.readonly
1315
1316       reset_overlay
1317           rd.live.overlay.reset
1318
1319       live_ram
1320           rd.live.ram
1321
1322       rd_NO_CRYPTTAB
1323           rd.luks.crypttab=0
1324
1325       rd_LUKS_KEYDEV_UUID
1326           rd.luks.keydev.uuid
1327
1328       rd_LUKS_KEYPATH
1329           rd.luks.keypath
1330
1331       rd_NO_LUKS
1332           rd.luks=0
1333
1334       rd_LUKS_UUID
1335           rd.luks.uuid
1336
1337       rd_NO_LVMCONF
1338           rd.lvm.conf
1339
1340       rd_LVM_LV
1341           rd.lvm.lv
1342
1343       rd_NO_LVM
1344           rd.lvm=0
1345
1346       rd_LVM_SNAPSHOT
1347           rd.lvm.snapshot
1348
1349       rd_LVM_SNAPSIZE
1350           rd.lvm.snapsize
1351
1352       rd_LVM_VG
1353           rd.lvm.vg
1354
1355       rd_NO_MDADMCONF
1356           rd.md.conf=0
1357
1358       rd_NO_MDIMSM
1359           rd.md.imsm=0
1360
1361       rd_NO_MD
1362           rd.md=0
1363
1364       rd_MD_UUID
1365           rd.md.uuid
1366
1367       rd_NO_MULTIPATH: rd.multipath=0
1368
1369       rd_NFS_DOMAIN
1370           rd.nfs.domain
1371
1372       iscsi_initiator
1373           rd.iscsi.initiator
1374
1375       iscsi_target_name
1376           rd.iscsi.target.name
1377
1378       iscsi_target_ip
1379           rd.iscsi.target.ip
1380
1381       iscsi_target_port
1382           rd.iscsi.target.port
1383
1384       iscsi_target_group
1385           rd.iscsi.target.group
1386
1387       iscsi_username
1388           rd.iscsi.username
1389
1390       iscsi_password
1391           rd.iscsi.password
1392
1393       iscsi_in_username
1394           rd.iscsi.in.username
1395
1396       iscsi_in_password
1397           rd.iscsi.in.password
1398
1399       iscsi_firmware
1400           rd.iscsi.firmware=0
1401
1402       rd_NO_PLYMOUTH
1403           rd.plymouth=0
1404
1405       rd_retry
1406           rd.retry
1407
1408       rdshell
1409           rd.shell
1410
1411       rd_NO_SPLASH
1412           rd.splash
1413
1414       rdudevdebug
1415           rd.udev.debug
1416
1417       rdudevinfo
1418           rd.udev.info
1419
1420       rd_NO_ZFCPCONF
1421           rd.zfcp.conf=0
1422
1423       rd_ZFCP
1424           rd.zfcp
1425
1426       rd_ZNET
1427           rd.znet
1428
1429       KEYMAP
1430           vconsole.keymap
1431
1432       KEYTABLE
1433           vconsole.keymap
1434
1435       SYSFONT
1436           vconsole.font
1437
1438       CONTRANS
1439           vconsole.font.map
1440
1441       UNIMAP
1442           vconsole.font.unimap
1443
1444       UNICODE
1445           vconsole.unicode
1446
1447       EXT_KEYMAP
1448           vconsole.keymap.ext
1449
1450   Configuration in the Initramfs
1451       /etc/conf.d/
1452           Any files found in /etc/conf.d/ will be sourced in the initramfs to
1453           set initial values. Command line options will override these values
1454           set in the configuration files.
1455
1456       /etc/cmdline
1457           Can contain additional command line options. Deprecated, better use
1458           /etc/cmdline.d/*.conf.
1459
1460       /etc/cmdline.d/*.conf
1461           Can contain additional command line options.
1462

AUTHOR

1464       Harald Hoyer
1465

SEE ALSO

1467       dracut(8) dracut.conf(5)
1468

NOTES

1470        1. rfc4173
1471           http://tools.ietf.org/html/rfc4173#section-5
1472
1473
1474
1475dracut 056                        02/18/2022                 DRACUT.CMDLINE(7)
Impressum