build: don't rely on the order of dependencies

It is impossible to sanely keep things tracked like that. All common
algorithms work on unordered graphs, and now we match that as well.

README.adoc

@@ -221,7 +221,7 @@ and the new `pr_info` message should now show on the terminal at the end of the
 
 This works because we have a <<9p>> mount there setup by default, which makes a host directory available on the guest.
 
-The fast method is slightly risky because your kernel module might have corrupted the kernel memory, which could affect future runs.
+The fast method is slightly risky because your previously insmodded buggy kernel module attempt might have corrupted the kernel memory, which could affect future runs.
 
 Such failures are however unlikely, and you should be fine if you don't see anything weird happening.
 
@@ -12314,6 +12314,7 @@ Runnable stuff:
 * https://github.com/linux-kernel-labs Yocto based, source inside a kernel fork subdir: https://github.com/linux-kernel-labs/linux/tree/f08b9e4238dfc612a9d019e3705bd906930057fc/tools/labs which the author would like to upstream https://www.reddit.com/r/programming/comments/79w2q9/linux_device_driver_labs_the_linux_kernel/dp6of43/
 * Android AOSP: https://stackoverflow.com/questions/1809774/how-to-compile-the-android-aosp-kernel-and-test-it-with-the-android-emulator/48310014#48310014 AOSP is basically a uber bloated Buildroot (2 hours build vs 30 minutes), Android is Linux based, and QEMU is the emulator backend. These instructions might work for debugging the kernel: https://github.com/Fuzion24/AndroidKernelExploitationPlayground
 * https://github.com/s-matyukevich/raspberry-pi-os Does both an OS from scratch, and annotates the corresponding kernel source code. For RPI3, no QEMU support: https://github.com/s-matyukevich/raspberry-pi-os/issues/8
+* https://github.com/pw4ever/linux-kernel-hacking-helper as of bd9952127e7eda643cbb6cb4c51ad7b5b224f438, Bash, Arch Linux rootfs
 
 Theory: