Remove a few references to dracut

[thirdparty/systemd.git] / docs / INITRD_INTERFACE.md

diff --git a/docs/INITRD_INTERFACE.md b/docs/INITRD_INTERFACE.md
index de91ba73958fa1959238c1b8c5dbd34f56d8171d..4e856f89177fca568ccd361df5d0a4c8592b73fc 100644 (file)
--- a/docs/INITRD_INTERFACE.md
+++ b/docs/INITRD_INTERFACE.md
@@ -16,8 +16,9 @@ initrd and initrd-less boots. If an initrd is used, it is a good idea to pass a
 few bits of runtime information from the initrd to systemd in order to avoid
 duplicate work and to provide performance data to the administrator. In this
 page we attempt to roughly describe the interfaces that exist between the
-initrd and systemd. These interfaces are currently used by dracut and the
-ArchLinux initrds.
+initrd and systemd. These interfaces are currently used by
+[mkosi](https://github.com/systemd/mkosi)-generated initrds, dracut and the
+Arch Linux initrds.
 
 * The initrd should mount `/run/` as a tmpfs and pass it pre-mounted when
   jumping into the main system when executing systemd. The mount options should
@@ -49,10 +50,6 @@ implemented as an actual ramdisk, ramfs or tmpfs. We recommend using _initrd_
 in this sense as a term that is unrelated to the actual backing technologies
 used.
 
-Oh, and one last question before closing: instead of implementing these
-features in your own distro's initrd, may I suggest just using Dracut instead?
-It's all already implemented there!
-
 ## Using systemd inside an initrd
 
 It is also possible and recommended to implement the initrd itself based on