Hi, I have created a rescue ramdisk system; it's currently living in git branch visible on http://gitweb.dragonflybsd.org/~ftigeot/dragonfly.git/shortlog/refs/heads/dfly_initrd2
All binaries on the ramdisk are static and most of them are crunched together with the crunchgen and crunchide utilities to reduce space overhead. Steps to test it: * Use the git dfly_initrd2 branch from the repository on git://leaf.dragonflybsd.org/~ftigeot/dragonfly.git * Or apply the patches in http://leaf.dragonflybsd.org/~ftigeot/dfly_initrd2/ on top of a DragonFly -master (3.7) repository * Run a full make buildworld / make installworld / make upgrade sequence A ramdisk image will be put into /boot/kernel/initrd.gz * Reboot and select the 'r' choice in the bootloader menu Your machine will boot in a single user ramdisk environment; it's pretty spartan but there are enough utilities to mount filesystems, manage disk slices or disklabel partitions, etc... I would like to know if this new ramdisk can be used as-is to mount encrypted root filesystems and other weird schemes currently requiring a custom initrd. -- Francois Tigeot
