Skip to content

Commit 304990b

Browse files
ahesfordericonr
authored andcommitted
kernel.md: clarify dracut kernel command-line capabilities
1 parent d203181 commit 304990b

File tree

1 file changed

+13
-5
lines changed

1 file changed

+13
-5
lines changed

src/config/kernel.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -73,11 +73,19 @@ and then running `update-grub`.
7373

7474
### dracut
7575

76-
Dracut can be configured to add additional command line arguments to the kernel
77-
through a configuration file. The documentation for dracut's configuration files
78-
can be found in [dracut.conf(5)](https://man.voidlinux.org/dracut.conf.5). To
79-
apply these changes, it is necessary to [regenerate](#kernel-hooks) the
80-
initramfs.
76+
Dracut offers a [`kernel_cmdline` configuration
77+
option](https://man.voidlinux.org/dracut.conf.5) and [`--kernel-cmdline`
78+
command-line option](https://man.voidlinux.org/dracut.8) that will encode
79+
command-line arguments directly in the initramfs image. When dracut is used to
80+
create a UEFI executable, arguments set with these options will be passed to the
81+
kernel. However, when an ordinary initramfs is produced, these options will
82+
*not* be passed to the kernel at boot. Instead, they will be written to a
83+
configuration file in `/etc/cmdline.d` within the image. While dracut parses
84+
this configuration to control its own boot-time behavior, the kernel itself will
85+
not be aware of anything set via this mechanism.
86+
87+
After modifying a dracut configuration, [regenerate](#kernel-hooks) the
88+
initramfs to ensure that it includes the changes.
8189

8290
## Kernel hardening
8391

0 commit comments

Comments
 (0)