1DRACUT.CMDLINE(7) dracut DRACUT.CMDLINE(7)
2
6 dracut.cmdline - dracut kernel command line options
7
9 The root device used by the kernel is specified in the boot
10 configuration file on the kernel command line, as always.
11 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 In the following all kernel command line parameters, which are
21 processed by dracut, are described.
22 "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 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 root=<path to blockdevice>
35 specify the block device to use as the root filesystem.
36 Example.
38 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 rootfstype=<filesystem type>
49 "auto" if not specified.
50 Example.
52 rootfstype=ext3
54 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 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 rw
67 force mounting / and /usr (if it is a separate device) read-write.
68 See also ro option.
69 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 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 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 rd.cmdline=ask
88 prompts the user for additional kernel command line parameters
89 rd.fstab=0
91 do not honor special mount options for the root filesystem found in
92 /etc/fstab of the real root.
93 resume=<path to resume partition>
95 resume from a swap partition
96 Example.
98 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 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 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 Example.
117 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 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 rd.driver.blacklist=<drivername>[,<drivername>,...]
133 do not load kernel module <drivername>. This parameter can be
134 specified multiple times.
135 rd.driver.pre=<drivername>[,<drivername>,...]
137 force loading kernel module <drivername>. This parameter can be
138 specified multiple times.
139 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 rd.retry=<seconds>
146 specify how long dracut should retry the initqueue to configure
147 devices. The default is 30 seconds. After 2/3 of the time, degraded
148 raids are force started. If you have hardware, which takes a very
149 long time to announce its drives, you might want to extend this
150 value.
151 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 rd.noverifyssl
158 accept self-signed certificates for ssl downloads.
159 rd.ctty=<terminal device>
161 specify the controlling terminal for the console. This is useful,
162 if you have multiple "console=" arguments.
163 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 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 rd.info
180 print informational output though "quiet" is set
181 rd.shell
183 allow dropping to a shell, if root mounting fails
184 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 rd.memdebug=[0-5]
193 Print memory usage info at various points, set the verbose level
194 from 0 to 5.
195 Higher level means more debugging output:
197 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 rd.break
212 drop to a shell at the end
213 rd.break={cmdline|pre-udev|pre-trigger|initqueue|pre-mount|mount|pre-pivot|cleanup}
215 drop to a shell on defined breakpoint
216 rd.udev.info
218 set udev to loglevel info
219 rd.udev.debug
221 set udev to loglevel debug
222 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 Example.
230 rd.vconsole.keymap=de-latin1-nodeadkeys
232 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 rd.vconsole.unicode
239 boolean, indicating UTF-8 mode; will be written as UNICODE to
240 /etc/vconsole.conf in the initramfs
241 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 Example.
247 rd.vconsole.font=eurlatgr
249 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 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 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 Example.
268 rd.locale.LANG=pl_PL.utf8
270 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 LVM
277 rd.lvm=0
278 disable LVM detection
279 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 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 rd.lvm.conf=0
290 remove any /etc/lvm/lvm.conf, which may exist in the initramfs
291 crypto LUKS
293 rd.luks=0
294 disable crypto LUKS detection
295 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 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 rd.luks.allow-discards
313 Allow using of discards (TRIM) requests on all LUKS partitions.
314 rd.luks.crypttab=0
316 do not check, if LUKS partition is in /etc/crypttab
317 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 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 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 <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 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 Example.
357 rd.luks.key=/foo/bar.key
359 As you see, you can skip colons in such a case.
362 Note
364 Your LUKS partition must match your key file.
365 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 Here is an example for a key encrypted with GPG (warning:
375 --batch-mode will overwrite the device without asking for
376 confirmation):
377 gpg --quiet --decrypt rootkey.gpg | \
379 cryptsetup --batch-mode --key-file - \
380 luksFormat /dev/sda47
381 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 head -32c /dev/urandom > rootkey.key
387 cryptsetup --batch-mode --key-file rootkey.key \
388 luksFormat /dev/sda47
389 You can also use regular key files on an encrypted keydev.
391 Compared to using GPG encrypted keyfiles on an unencrypted device
393 this provides the following advantages:
394 • you can unlock your disk(s) using multiple passphrases
396 • better security by not loosing the key stretching mechanism
398 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 Example:
405 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 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 To boot this configuration you could use:
415 rd.luks.uuid=aaaa
417 rd.luks.uuid=bbbb
418 rd.luks.uuid=keysource:cccc
419 rd.luks.key=/keyfile:UUID=CCCC
420 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 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 MD RAID
430 rd.md=0
431 disable MD RAID detection
432 rd.md.imsm=0
434 disable MD RAID for imsm/isw raids, use DM RAID instead
435 rd.md.ddf=0
437 disable MD RAID for SNIA ddf raids, use DM RAID instead
438 rd.md.conf=0
440 ignore mdadm.conf included in initramfs
441 rd.md.waitclean=1
443 wait for any resync, recovery, or reshape activity to finish before
444 continuing
445 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 DM RAID
451 rd.dm=0
452 disable DM RAID detection
453 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 MULTIPATH
459 rd.multipath=0
460 disable multipath detection
461 rd.multipath=default
463 use default multipath settings
464 FIPS
466 rd.fips
467 enable FIPS
468 boot=<boot device>
470 specify the device, where /boot is located.
471 Example.
473 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 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 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 Predictable network interface device names based on:
491 • firmware/bios-provided index numbers for on-board devices
493 • firmware-provided pci-express hotplug slot index number
495 • physical/geographical location of the hardware
497 • the interface’s MAC address
499 See:
501 http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames
502 Two character prefixes based on the type of interface:
504 en
506 ethernet
507 wl
509 wlan
510 ww
512 wwan
513 Type of names:
515 o<index>
517 on-board device index number
518 s<slot>[f<function>][d<dev_id>]
520 hotplug slot index number
521 x<MAC>
523 MAC address
524 [P<domain>]p<bus>s<slot>[f<function>][d<dev_id>]
526 PCI geographical location
527 [P<domain>]p<bus>s<slot>[f<function>][u<port>][..][c<config>][i<interface>]
529 USB port number chain
530 All multi-function PCI devices will carry the [f<function>] number
532 in the device name, including the function 0 device.
533 When using PCI geography, The PCI domain is only prepended when it
535 is not 0.
536 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 PCI ethernet card with firmware index "1"
543 • eno1
545 PCI ethernet card in hotplug slot with firmware index number
547 • ens1
549 PCI ethernet multi-function card with 2 ports
551 • enp2s0f0
553 • enp2s0f1
555 PCI wlan card
557 • wlp3s0
559 USB built-in 3G modem
561 • wwp0s29u1u4i6
563 USB Android phone
565 • enp0s29u1u2
567 ip={dhcp|on|any|dhcp6|auto6|either6|link6|single-dhcp}
569 dhcp|on|any
571 get ip from dhcp server from all interfaces. If netroot=dhcp,
572 loop sequentially through all interfaces (eth0, eth1, ...) and
573 use the first with a valid DHCP root-path.
574 single-dhcp
576 Send DHCP on all available interfaces in parallel, as opposed
577 to one after another. After the first DHCP response is
578 received, stop DHCP on all other interfaces. This gives the
579 fastest boot time by using the IP on interface for which DHCP
580 succeeded first during early boot. Caveat: Does not apply to
581 Network Manager and to SUSE using wicked.
582 auto6
584 IPv6 autoconfiguration
585 dhcp6
587 IPv6 DHCP
588 either6
590 if auto6 fails, then dhcp6
591 link6
593 bring up interface for IPv6 link-local addressing
594 ip=<interface>:{dhcp|on|any|dhcp6|auto6|link6}[:[<mtu>][:<macaddr>]]
596 This parameter can be specified multiple times.
597 dhcp|on|any|dhcp6
599 get ip from dhcp server on a specific interface
600 auto6
602 do IPv6 autoconfiguration
603 link6
605 bring up interface for IPv6 link local address
606 <macaddr>
608 optionally set <macaddr> on the <interface>. This cannot be
609 used in conjunction with the ifname argument for the same
610 <interface>.
611 ip=<client-IP>:[<peer>]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[<mtu>][:<macaddr>]]
613 explicit network configuration. If you want do define a IPv6
614 address, put it in brackets (e.g. [2001:DB8::1]). This parameter
615 can be specified multiple times. <peer> is optional and is the
616 address of the remote endpoint for pointopoint interfaces and it
617 may be followed by a slash and a decimal number, encoding the
618 network prefix length.
619 <macaddr>
621 optionally set <macaddr> on the <interface>. This cannot be
622 used in conjunction with the ifname argument for the same
623 <interface>.
624 ip=<client-IP>:[<peer>]:<gateway-IP>:<netmask>:<client_hostname>:<interface>:{none|off|dhcp|on|any|dhcp6|auto6|ibft}[:[<dns1>][:<dns2>]]
626 explicit network configuration. If you want do define a IPv6
627 address, put it in brackets (e.g. [2001:DB8::1]). This parameter
628 can be specified multiple times. <peer> is optional and is the
629 address of the remote endpoint for pointopoint interfaces and it
630 may be followed by a slash and a decimal number, encoding the
631 network prefix length.
632 ifname=<interface>:<MAC>
634 Assign network device name <interface> (i.e. "bootnet") to the NIC
635 with MAC <MAC>.
636 Warning
638 Do not use the default kernel naming scheme for the interface
639 name, as it can conflict with the kernel names. So, don’t use
640 "eth[0-9]+" for the interface name. Better name it "bootnet" or
641 "bluesocket".
642 rd.route=<net>/<netmask>:<gateway>[:<interface>]
644 Add a static route with route options, which are separated by a
645 colon. IPv6 addresses have to be put in brackets.
646 Example.
648 rd.route=192.168.200.0/24:192.168.100.222:ens10
650 rd.route=192.168.200.0/24:192.168.100.222
651 rd.route=192.168.200.0/24::ens10
652 rd.route=[2001:DB8:3::/8]:[2001:DB8:2::1]:ens10
653 bootdev=<interface>
656 specify network interface to use routing and netroot information
657 from. Required if multiple ip= lines are used.
658 BOOTIF=<MAC>
660 specify network interface to use routing and netroot information
661 from.
662 rd.bootif=0
664 Disable BOOTIF parsing, which is provided by PXE
665 nameserver=<IP> [nameserver=<IP> ...]
667 specify nameserver(s) to use
668 rd.peerdns=0
670 Disable DNS setting of DHCP parameters.
671 biosdevname=0
673 boolean, turn off biosdevname network interface renaming
674 rd.neednet=1
676 boolean, bring up network even without netroot set
677 vlan=<vlanname>:<phydevice>
679 Setup vlan device named <vlanname> on <phydevice>. We support the
680 four styles of vlan names: VLAN_PLUS_VID (vlan0005),
681 VLAN_PLUS_VID_NO_PAD (vlan5), DEV_PLUS_VID (eth0.0005),
682 DEV_PLUS_VID_NO_PAD (eth0.5)
683 bond=<bondname>[:<bondslaves>:[:<options>[:<mtu>]]]
685 Setup bonding device <bondname> on top of <bondslaves>.
686 <bondslaves> is a comma-separated list of physical (ethernet)
687 interfaces. <options> is a comma-separated list on bonding options
688 (modinfo bonding for details) in format compatible with
689 initscripts. If <options> includes multi-valued arp_ip_target
690 option, then its values should be separated by semicolon. if the
691 mtu is specified, it will be set on the bond master. Bond without
692 parameters assumes bond=bond0:eth0,eth1:mode=balance-rr
693 team=<teammaster>:<teamslaves>[:<teamrunner>]
695 Setup team device <teammaster> on top of <teamslaves>. <teamslaves>
696 is a comma-separated list of physical (ethernet) interfaces.
697 <teamrunner> is the runner type to be used (see teamd.conf(5));
698 defaults to activebackup. Team without parameters assumes
699 team=team0:eth0,eth1:activebackup
700 bridge=<bridgename>:<ethnames>
702 Setup bridge <bridgename> with <ethnames>. <ethnames> is a
703 comma-separated list of physical (ethernet) interfaces. Bridge
704 without parameters assumes bridge=br0:eth0
705 NFS
707 root=[<server-ip>:]<root-dir>[:<nfs-options>]
708 mount nfs share from <server-ip>:/<root-dir>, if no server-ip is
709 given, use dhcp next_server. If server-ip is an IPv6 address it has
710 to be put in brackets, e.g. [2001:DB8::1]. NFS options can be
711 appended with the prefix ":" or "," and are separated by ",".
712 root=nfs:[<server-ip>:]<root-dir>[:<nfs-options>],
714 root=nfs4:[<server-ip>:]<root-dir>[:<nfs-options>], root={dhcp|dhcp6}
715 netroot=dhcp alone directs initrd to look at the DHCP root-path
716 where NFS options can be specified.
717 Example.
719 root-path=<server-ip>:<root-dir>[,<nfs-options>]
721 root-path=nfs:<server-ip>:<root-dir>[,<nfs-options>]
722 root-path=nfs4:<server-ip>:<root-dir>[,<nfs-options>]
723 root=/dev/nfs nfsroot=[<server-ip>:]<root-dir>[:<nfs-options>]
726 Deprecated! kernel Documentation_/filesystems/nfsroot.txt_ defines
727 this method. This is supported by dracut, but not recommended.
728 rd.nfs.domain=<NFSv4 domain name>
730 Set the NFSv4 domain name. Will override the settings in
731 /etc/idmap.conf.
732 rd.net.dhcp.retry=<cnt>
734 If this option is set, dracut will try to connect via dhcp <cnt>
735 times before failing. Default is 1.
736 rd.net.timeout.dhcp=<arg>
738 If this option is set, dhclient is called with "-timeout <arg>".
739 rd.net.timeout.iflink=<seconds>
741 Wait <seconds> until link shows up. Default is 60 seconds.
742 rd.net.timeout.ifup=<seconds>
744 Wait <seconds> until link has state "UP". Default is 20 seconds.
745 rd.net.timeout.route=<seconds>
747 Wait <seconds> until route shows up. Default is 20 seconds.
748 rd.net.timeout.ipv6dad=<seconds>
750 Wait <seconds> until IPv6 DAD is finished. Default is 50 seconds.
751 rd.net.timeout.ipv6auto=<seconds>
753 Wait <seconds> until IPv6 automatic addresses are assigned. Default
754 is 40 seconds.
755 rd.net.timeout.carrier=<seconds>
757 Wait <seconds> until carrier is recognized. Default is 10 seconds.
758 CIFS
760 root=cifs://[<username>[:<password>]@]<server-ip>:<root-dir>
761 mount cifs share from <server-ip>:/<root-dir>, if no server-ip is
762 given, use dhcp next_server. if server-ip is an IPv6 address it has
763 to be put in brackets, e.g. [2001:DB8::1]. If a username or
764 password are not specified as part of the root, then they must be
765 passed on the command line through cifsuser/cifspass.
766 Warning
768 Passwords specified on the kernel command line are visible for
769 all users via the file /proc/cmdline and via dmesg or can be
770 sniffed on the network, when using DHCP with DHCP root-path.
771 cifsuser=<username>
773 Set the cifs username, if not specified as part of the root.
774 cifspass=<password>
776 Set the cifs password, if not specified as part of the root.
777 Warning
779 Passwords specified on the kernel command line are visible for
780 all users via the file /proc/cmdline and via dmesg or can be
781 sniffed on the network, when using DHCP with DHCP root-path.
782 iSCSI
784 root=iscsi:[<username>:<password>[:<reverse>:<password>]@][<servername>]:[<protocol>]:[<port>][:[<iscsi_iface_name>]:[<netdev_name>]]:[<LUN>]:<targetname>
785 protocol defaults to "6", LUN defaults to "0". If the "servername"
786 field is provided by BOOTP or DHCP, then that field is used in
787 conjunction with other associated fields to contact the boot server
788 in the Boot stage. However, if the "servername" field is not
789 provided, then the "targetname" field is then used in the Discovery
790 Service stage in conjunction with other associated fields. See
791 rfc4173[1].
792 Warning
794 Passwords specified on the kernel command line are visible for
795 all users via the file /proc/cmdline and via dmesg or can be
796 sniffed on the network, when using DHCP with DHCP root-path.
797 Example.
799 root=iscsi:192.168.50.1::::iqn.2009-06.dracut:target0
801 If servername is an IPv6 address, it has to be put in brackets:
804 Example.
806 root=iscsi:[2001:DB8::1]::::iqn.2009-06.dracut:target0
808 root=???
811 netroot=iscsi:[<username>:<password>[:<reverse>:<password>]@][<servername>]:[<protocol>]:[<port>][:[<iscsi_iface_name>]:[<netdev_name>]]:[<LUN>]:<targetname>
812 ...
813 multiple netroot options allow setting up multiple iscsi disks:
814 Example.
816 root=UUID=12424547
818 netroot=iscsi:192.168.50.1::::iqn.2009-06.dracut:target0
819 netroot=iscsi:192.168.50.1::::iqn.2009-06.dracut:target1
820 If servername is an IPv6 address, it has to be put in brackets:
823 Example.
825 netroot=iscsi:[2001:DB8::1]::::iqn.2009-06.dracut:target0
827 Warning
830 Passwords specified on the kernel command line are visible for
831 all users via the file /proc/cmdline and via dmesg or can be
832 sniffed on the network, when using DHCP with DHCP root-path.
833 You may want to use rd.iscsi.firmware.
834 root=??? rd.iscsi.initiator=<initiator> rd.iscsi.target.name=<target
836 name> rd.iscsi.target.ip=<target ip> rd.iscsi.target.port=<target port>
837 rd.iscsi.target.group=<target group> rd.iscsi.username=<username>
838 rd.iscsi.password=<password> rd.iscsi.in.username=<in username>
839 rd.iscsi.in.password=<in password>
840 manually specify all iscsistart parameter (see iscsistart --help)
841 Warning
843 Passwords specified on the kernel command line are visible for
844 all users via the file /proc/cmdline and via dmesg or can be
845 sniffed on the network, when using DHCP with DHCP root-path.
846 You may want to use rd.iscsi.firmware.
847 root=??? netroot=iscsi rd.iscsi.firmware=1
849 will read the iscsi parameter from the BIOS firmware
850 rd.iscsi.login_retry_max=<num>
852 maximum number of login retries
853 rd.iscsi.param=<param>
855 <param> will be passed as "--param <param>" to iscsistart. This
856 parameter can be specified multiple times.
857 Example.
859 "netroot=iscsi rd.iscsi.firmware=1 rd.iscsi.param=node.session.timeo.replacement_timeout=30"
861 will result in
864 iscsistart -b --param node.session.timeo.replacement_timeout=30
866 rd.iscsi.ibft rd.iscsi.ibft=1: Turn on iBFT autoconfiguration for the
868 interfaces
869 rd.iscsi.mp rd.iscsi.mp=1: Configure all iBFT interfaces, not only used
871 for booting (multipath)
872 rd.iscsi.waitnet=0: Turn off waiting for all interfaces to be up before
874 trying to login to the iSCSI targets.
875 rd.iscsi.testroute=0: Turn off checking, if the route to the iSCSI
877 target IP is possible before trying to login.
878 FCoE
880 rd.fcoe=0
881 disable FCoE and lldpad
882 fcoe=<edd|interface|MAC>:{dcb|nodcb}:{fabric|vn2vn}
884 Try to connect to a FCoE SAN through the NIC specified by
885 <interface> or <MAC> or EDD settings. The second argument specifies
886 if DCB should be used. The optional third argument specifies
887 whether fabric or VN2VN mode should be used. This parameter can be
888 specified multiple times.
889 Note
891 letters in the MAC-address must be lowercase!
892 NVMf
894 rd.nvmf.hostnqn=<hostNQN>
895 NVMe host NQN to use
896 rd.nvmf.hostid=<hostID>
898 NVMe host id to use
899 rd.nvmf.discover={rdma|fc|tcp},<traddr>,[<host_traddr>],[<trsvcid>]
901 Discover and connect to a NVMe-over-Fabric controller specified by
902 <traddr> and the optionally <host_traddr> or <trsvcid>. The first
903 argument specifies the transport to use; currently only rdma, fc,
904 or tcp are supported. The <traddr> parameter can be set to auto to
905 select autodiscovery; in that case all other parameters are
906 ignored. This parameter can be specified multiple times.
907 NBD
909 root=???
910 netroot=nbd:<server>:<port/exportname>[:<fstype>[:<mountopts>[:<nbdopts>]]]
911 mount nbd share from <server>.
912 NOTE: If "exportname" instead of "port" is given the standard port
914 is used. Newer versions of nbd are only supported with
915 "exportname".
916 root=/dev/root netroot=dhcp with dhcp
918 root-path=nbd:<server>:<port/exportname>[:<fstype>[:<mountopts>[:<nbdopts>]]]
919 netroot=dhcp alone directs initrd to look at the DHCP root-path
920 where NBD options can be specified. This syntax is only usable in
921 cases where you are directly mounting the volume as the rootfs.
922 NOTE: If "exportname" instead of "port" is given the standard port
924 is used. Newer versions of nbd are only supported with
925 "exportname".
926 DASD
928 rd.dasd=....
929 same syntax as the kernel module parameter (s390 only)
930 ZFCP
932 rd.zfcp=<zfcp adaptor device bus ID>,<WWPN>,<FCPLUN>
933 rd.zfcp can be specified multiple times on the kernel command line.
934 rd.zfcp=<zfcp adaptor device bus ID>
936 If NPIV is enabled and the allow_lun_scan parameter to the zfcp
937 module is set to Y then the zfcp adaptor will be initiating a scan
938 internally and the <WWPN> and <FCPLUN> parameters can be omitted.
939 Example.
941 rd.zfcp=0.0.4000,0x5005076300C213e9,0x5022000000000000
943 rd.zfcp=0.0.4000
944 rd.zfcp.conf=0
947 ignore zfcp.conf included in the initramfs
948 ZNET
950 rd.znet=<nettype>,<subchannels>,<options>
951 The whole parameter is appended to /etc/ccw.conf, which is used on
952 RHEL/Fedora with ccw_init, which is called from udev for certain
953 devices on z-series. rd.znet can be specified multiple times on the
954 kernel command line.
955 rd.znet_ifname=<ifname>:<subchannels>
957 Assign network device name <interface> (i.e. "bootnet") to the NIC
958 corresponds to the subchannels. This is useful when dracut’s
959 default "ifname=" doesn’t work due to device having a changing MAC
960 address.
961 Example.
963 rd.znet=qeth,0.0.0600,0.0.0601,0.0.0602,layer2=1,portname=foo
965 rd.znet=ctc,0.0.0600,0.0.0601,protocol=bar
966 Booting live images
969 Dracut offers multiple options for live booted images:
970 SquashFS with read-only filesystem image
972 The system will boot with a read-only filesystem from the SquashFS
973 and apply a writable Device-mapper snapshot or an OverlayFS overlay
974 mount for the read-only base filesystem. This method ensures a
975 relatively fast boot and lower RAM usage. Users must be careful to
976 avoid writing too many blocks to a snapshot volume. Once the blocks
977 of the snapshot overlay are exhausted, the root filesystem becomes
978 read-only and may cause application failures. The snapshot overlay
979 file is marked Overflow, and a difficult recovery is required to
980 repair and enlarge the overlay offline. Non-persistent overlays are
981 sparse files in RAM that only consume content space as required
982 blocks are allocated. They default to an apparent size of 32 GiB in
983 RAM. The size can be adjusted with the rd.live.overlay.size= kernel
984 command line option.
985 The filesystem structure is traditionally expected to be:
987 squashfs.img | SquashFS from LiveCD .iso
989 !(mount)
990 /LiveOS
991 |- rootfs.img | Filesystem image to mount read-only
992 !(mount)
993 /bin | Live filesystem
994 /boot |
995 /dev |
996 ... |
997 For OverlayFS mount overlays, the filesystem structure may also be
999 a direct compression of the root filesystem:
1000 squashfs.img | SquashFS from LiveCD .iso
1002 !(mount)
1003 /bin | Live filesystem
1004 /boot |
1005 /dev |
1006 ... |
1007 Dracut uses one of the overlay methods of live booting by default.
1009 No additional command line options are required other than
1010 root=live:<URL> to specify the location of your squashed
1011 filesystem.
1012 • The compressed SquashFS image can be copied during boot to RAM
1014 at /run/initramfs/squashed.img by using the rd.live.ram=1
1015 option.
1016 • A device with a persistent overlay can be booted read-only by
1018 using the rd.live.overlay.readonly option on the kernel command
1019 line. This will either cause a temporary, writable overlay to
1020 be stacked over a read-only snapshot of the root filesystem or
1021 the OverlayFS mount will use an additional lower layer with the
1022 root filesystem.
1023 Uncompressed live filesystem image
1025 When the live system was installed with the --skipcompress option
1026 of the livecd-iso-to-disk installation script for Live USB devices,
1027 the root filesystem image, rootfs.img, is expanded on installation
1028 and no SquashFS is involved during boot.
1029 • If rd.live.ram=1 is used in this situation, the full,
1031 uncompressed root filesystem is copied during boot to
1032 /run/initramfs/rootfs.img in the /run tmpfs.
1033 • If rd.live.overlay=none is provided as a kernel command line
1035 option, a writable, linear Device-mapper target is created on
1036 boot with no overlay.
1037 Writable filesystem image
1039 The system will retrieve a compressed filesystem image, extract it
1040 to /run/initramfs/fsimg/rootfs.img, connect it to a loop device,
1041 create a writable, linear Device-mapper target at
1042 /dev/mapper/live-rw, and mount that as a writable volume at /. More
1043 RAM is required during boot but the live filesystem is easier to
1044 manage if it becomes full. Users can make a filesystem image of any
1045 size and that size will be maintained when the system boots. There
1046 is no persistence of root filesystem changes between boots with
1047 this option.
1048 The filesystem structure is expected to be:
1050 rootfs.tgz | Compressed tarball containing filesystem image
1052 !(unpack)
1053 /rootfs.img | Filesystem image at /run/initramfs/fsimg/
1054 !(mount)
1055 /bin | Live filesystem
1056 /boot |
1057 /dev |
1058 ... |
1059 To use this boot option, ensure that rd.writable.fsimg=1 is in your
1061 kernel command line and add the root=live:<URL> to specify the
1062 location of your compressed filesystem image tarball or SquashFS
1063 image.
1064 rd.writable.fsimg=1
1066 Enables writable filesystem support. The system will boot with a
1067 fully writable (but non-persistent) filesystem without snapshots
1068 (see notes above about available live boot options). You can use
1069 the rootflags option to set mount options for the live filesystem
1070 as well (see documentation about rootflags in the Standard section
1071 above). This implies that the whole image is copied to RAM before
1072 the boot continues.
1073 Note
1075 There must be enough free RAM available to hold the complete
1076 image.
1077 This method is very suitable for diskless boots.
1078 root=live:<url>
1080 Boots a live image retrieved from <url>. Requires the dracut
1081 livenet module. Valid handlers: http, https, ftp, torrent, tftp.
1082 Examples.
1084 root=live:http://example.com/liveboot.img
1086 root=live:ftp://ftp.example.com/liveboot.img
1087 root=live:torrent://example.com/liveboot.img.torrent
1088 rd.live.debug=1
1091 Enables debug output from the live boot process.
1092 rd.live.dir=<path>
1094 Specifies the directory within the boot device where the
1095 squashfs.img or rootfs.img can be found. By default, this is
1096 /LiveOS.
1097 rd.live.squashimg=<filename of SquashFS image>
1099 Specifies the filename for a SquashFS image of the root filesystem.
1100 By default, this is squashfs.img.
1101 rd.live.ram=1
1103 Copy the complete image to RAM and use this for booting. This is
1104 useful when the image resides on, e.g., a DVD which needs to be
1105 ejected later on.
1106 rd.live.overlay={<devspec>[:{<pathspec>|auto}]|none}
1108 Manage the usage of a permanent overlay.
1109 • <devspec> specifies the path to a device with a mountable
1111 filesystem.
1112 • <pathspec> is the path to a file within that filesystem, which
1114 shall be used to persist the changes made to the device
1115 specified by the root=live:<url> option.
1116 The default pathspec, when auto or no :<pathspec> is given, is
1118 /<rd.live.dir>/overlay-<label>-<uuid>, where <label> is the
1119 device LABEL, and <uuid> is the device UUID. * none (the word
1120 itself) specifies that no overlay will be used, such as when an
1121 uncompressed, writable live root filesystem is available.
1122 If a persistent overlay is detected at the standard LiveOS
1124 path, the overlay & overlay type detected, whether
1125 Device-mapper or OverlayFS, will be used.
1126 Examples.
1128 rd.live.overlay=/dev/sdb1:persistent-overlay.img
1130 rd.live.overlay=UUID=99440c1f-8daa-41bf-b965-b7240a8996f4
1131 rd.live.overlay.size=<size_MiB>
1134 Specifies a non-persistent Device-mapper overlay size in MiB. The
1135 default is 32768.
1136 rd.live.overlay.readonly=1
1138 This is used to boot with a normally read-write persistent overlay
1139 in a read-only mode. With this option, either an additional,
1140 non-persistent, writable snapshot overlay will be stacked over a
1141 read-only snapshot, /dev/mapper/live-ro, of the base filesystem
1142 with the persistent overlay, or a read-only loop device, in the
1143 case of a writable rootfs.img, or an OverlayFS mount will use the
1144 persistent overlay directory linked at /run/overlayfs-r as an
1145 additional lower layer along with the base root filesystem and
1146 apply a transient, writable upper directory overlay, in order to
1147 complete the booted root filesystem.
1148 rd.live.overlay.reset=1
1150 Specifies that a persistent overlay should be reset on boot. All
1151 previous root filesystem changes are vacated by this action.
1152 rd.live.overlay.thin=1
1154 Enables the usage of thin snapshots instead of classic dm
1155 snapshots. The advantage of thin snapshots is that they support
1156 discards, and will free blocks that are not claimed by the
1157 filesystem. In this use case, this means that memory is given back
1158 to the kernel when the filesystem does not claim it anymore.
1159 rd.live.overlay.overlayfs=1
1161 Enables the use of the OverlayFS kernel module, if available, to
1162 provide a copy-on-write union directory for the root filesystem.
1163 OverlayFS overlays are directories of the files that have changed
1164 on the read-only base (lower) filesystem. The root filesystem is
1165 provided through a special overlay type mount that merges the lower
1166 and upper directories. If an OverlayFS upper directory is not
1167 present on the boot device, a tmpfs directory will be created at
1168 /run/overlayfs to provide temporary storage. Persistent storage can
1169 be provided on vfat or msdos formatted devices by supplying the
1170 OverlayFS upper directory within an embedded filesystem that
1171 supports the creation of trusted.* extended attributes and provides
1172 a valid d_type in readdir responses, such as with ext4 and xfs. On
1173 non-vfat-formatted devices, a persistent OverlayFS overlay can
1174 extend the available root filesystem storage up to the capacity of
1175 the LiveOS disk device.
1176 If a persistent overlay is detected at the standard LiveOS path,
1178 the overlay & overlay type detected, whether OverlayFS or
1179 Device-mapper, will be used.
1180 The rd.live.overlay.readonly option, which allows a persistent
1182 overlayfs to be mounted read-only through a higher level transient
1183 overlay directory, has been implemented through the multiple lower
1184 layers feature of OverlayFS.
1185 ZIPL
1187 rd.zipl=<path to blockdevice>
1188 Update the dracut commandline with the values found in the
1189 dracut-cmdline.conf file on the given device. The values are merged
1190 into the existing commandline values and the udev events are
1191 regenerated.
1192 Example.
1194 rd.zipl=UUID=0fb28157-99e3-4395-adef-da3f7d44835a
1196 CIO_IGNORE
1199 rd.cio_accept=<device-ids>
1200 Remove the devices listed in <device-ids> from the default
1201 cio_ignore kernel command-line settings. <device-ids> is a list of
1202 comma-separated CCW device ids. The default for this value is taken
1203 from the /boot/zipl/active_devices.txt file.
1204 Example.
1206 rd.cio_accept=0.0.0180,0.0.0800,0.0.0801,0.0.0802
1208 Plymouth Boot Splash
1211 plymouth.enable=0
1212 disable the plymouth bootsplash completely.
1213 rd.plymouth=0
1215 disable the plymouth bootsplash only for the initramfs.
1216 Kernel keys
1218 masterkey=<kernel master key path name>
1219 Set the path name of the kernel master key.
1220 Example.
1222 masterkey=/etc/keys/kmk-trusted.blob
1224 masterkeytype=<kernel master key type>
1227 Set the type of the kernel master key.
1228 Example.
1230 masterkeytype=trusted
1232 evmkey=<EVM key path name>
1235 Set the path name of the EVM key.
1236 Example.
1238 evmkey=/etc/keys/evm-trusted.blob
1240 ecryptfskey=<eCryptfs key path name>
1243 Set the path name of the eCryptfs key.
1244 Example.
1246 ecryptfskey=/etc/keys/ecryptfs-trusted.blob
1248 Deprecated, renamed Options
1251 Here is a list of options, which were used in dracut prior to version
1252 008, and their new replacement.
1253 rdbreak
1255 rd.break
1256 rd.ccw
1258 rd.znet
1259 rd_CCW
1261 rd.znet
1262 rd_DASD_MOD
1264 rd.dasd
1265 rd_DASD
1267 rd.dasd
1268 rdinitdebug rdnetdebug
1270 rd.debug
1271 rd_NO_DM
1273 rd.dm=0
1274 rd_DM_UUID
1276 rd.dm.uuid
1277 rdblacklist
1279 rd.driver.blacklist
1280 rdinsmodpost
1282 rd.driver.post
1283 rdloaddriver
1285 rd.driver.pre
1286 rd_NO_FSTAB
1288 rd.fstab=0
1289 rdinfo
1291 rd.info
1292 check
1294 rd.live.check
1295 rdlivedebug
1297 rd.live.debug
1298 live_dir
1300 rd.live.dir
1301 liveimg
1303 rd.live.image
1304 overlay
1306 rd.live.overlay
1307 readonly_overlay
1309 rd.live.overlay.readonly
1310 reset_overlay
1312 rd.live.overlay.reset
1313 live_ram
1315 rd.live.ram
1316 rd_NO_CRYPTTAB
1318 rd.luks.crypttab=0
1319 rd_LUKS_KEYDEV_UUID
1321 rd.luks.keydev.uuid
1322 rd_LUKS_KEYPATH
1324 rd.luks.keypath
1325 rd_NO_LUKS
1327 rd.luks=0
1328 rd_LUKS_UUID
1330 rd.luks.uuid
1331 rd_NO_LVMCONF
1333 rd.lvm.conf
1334 rd_LVM_LV
1336 rd.lvm.lv
1337 rd_NO_LVM
1339 rd.lvm=0
1340 rd_LVM_SNAPSHOT
1342 rd.lvm.snapshot
1343 rd_LVM_SNAPSIZE
1345 rd.lvm.snapsize
1346 rd_LVM_VG
1348 rd.lvm.vg
1349 rd_NO_MDADMCONF
1351 rd.md.conf=0
1352 rd_NO_MDIMSM
1354 rd.md.imsm=0
1355 rd_NO_MD
1357 rd.md=0
1358 rd_MD_UUID
1360 rd.md.uuid
1361 rd_NO_MULTIPATH: rd.multipath=0
1363 rd_NFS_DOMAIN
1365 rd.nfs.domain
1366 iscsi_initiator
1368 rd.iscsi.initiator
1369 iscsi_target_name
1371 rd.iscsi.target.name
1372 iscsi_target_ip
1374 rd.iscsi.target.ip
1375 iscsi_target_port
1377 rd.iscsi.target.port
1378 iscsi_target_group
1380 rd.iscsi.target.group
1381 iscsi_username
1383 rd.iscsi.username
1384 iscsi_password
1386 rd.iscsi.password
1387 iscsi_in_username
1389 rd.iscsi.in.username
1390 iscsi_in_password
1392 rd.iscsi.in.password
1393 iscsi_firmware
1395 rd.iscsi.firmware=0
1396 rd_NO_PLYMOUTH
1398 rd.plymouth=0
1399 rd_retry
1401 rd.retry
1402 rdshell
1404 rd.shell
1405 rd_NO_SPLASH
1407 rd.splash
1408 rdudevdebug
1410 rd.udev.debug
1411 rdudevinfo
1413 rd.udev.info
1414 rd_NO_ZFCPCONF
1416 rd.zfcp.conf=0
1417 rd_ZFCP
1419 rd.zfcp
1420 rd_ZNET
1422 rd.znet
1423 KEYMAP
1425 vconsole.keymap
1426 KEYTABLE
1428 vconsole.keymap
1429 SYSFONT
1431 vconsole.font
1432 CONTRANS
1434 vconsole.font.map
1435 UNIMAP
1437 vconsole.font.unimap
1438 UNICODE
1440 vconsole.unicode
1441 EXT_KEYMAP
1443 vconsole.keymap.ext
1444 Configuration in the Initramfs
1446 /etc/conf.d/
1447 Any files found in /etc/conf.d/ will be sourced in the initramfs to
1448 set initial values. Command line options will override these values
1449 set in the configuration files.
1450 /etc/cmdline
1452 Can contain additional command line options. Deprecated, better use
1453 /etc/cmdline.d/*.conf.
1454 /etc/cmdline.d/*.conf
1456 Can contain additional command line options.
1457
1459 Harald Hoyer
1460
1462 dracut(8) dracut.conf(5)
1463
1465 1. rfc4173
1466 http://tools.ietf.org/html/rfc4173#section-5
1467dracut 054 05/14/2021 DRACUT.CMDLINE(7)