These aren't *necessarily* clearly practical possibilities.  Instead, it's intended to keep me from
thinking "too inside the box", to try to eliminate as many "unknown unknowns" as possible.


- TODO: is it possible to kexec directly into MEMDISK?  You can load MEMDISK from GRUB using the
  same kernel+initrd syntax that kexec uses...  so you should be able to MEMDISK directly, no?
        No?  It says "Cannot determine the file type of memdisk", no matter what I try to do?
        Do I need to reformat it somehow?


-----> NOTE: kexec has a problem in that it doesn't reset hardware very well.
                http://www.xmission.com/~ebiederm/files/kexec/README
                "So far failures have broken into three categories"


- TODO: Is there a way to do a soft reset, yet still retain RAM across the reboot, and moreover,
  retain control acros


=== Ultimate DOS disk ====

    There have been several DOS compilations like "every network driver you could possibly need for
    DOS".  However, they all do the hardware-detection code from within DOS.  What if we 1) used
    Linux's existing code to autodetect the hardware, and then 2) built a CUSTOM DOS boot floppy
    image with the SPECIFIC drivers for the hardware we found, and 3) kexec that DOS
    floppy?