mkosi: Drop building custom kernel logic

Now that mkosi-kernel is a thing, this logic in systemd is just mostly
bitrotting since I just use mkosi-kernel these days. If I ever need to
hack on systemd and the kernel in tandem, I'll just add support for
building systemd to mkosi-kernel instead, so let's drop the support for
building a custom kernel in systemd's mkosi configuration.

1 files changed, 0 insertions, 20 deletions

diff --git a/docs/HACKING.md b/docs/HACKING.md
index c0892169a9..feec6b4537 100644
--- a/docs/HACKING.md
+++ b/docs/HACKING.md
@@ -337,23 +337,3 @@ To debug systemd-boot in an IDE such as VSCode we can use a launch configuration
     ]
 }
 ```
-
-## Hacking on the kernel + systemd
-
-If you're hacking on the kernel in tandem with systemd, you can clone a kernel repository in mkosi.kernel/ in
-the systemd repository, and mkosi will automatically build that kernel and install it into the final image.
-To prevent the distribution's kernel from being installed (which isn't necessary since we're building our
-own kernel), you can add the following snippets to `mkosi.local.conf`:
-
-(This snippet is for Fedora, the list of packages will need to be changed for other distributions)
-
-```
-[Distribution]
-CacheInitrd=no
-
-[Content]
-BasePackages=conditional
-Packages=systemd
-         util-linux
-         dracut
-```