is present in this particular CD image (2004-06-23 (it’s bitten me too)). The issue seems to have since been resolved, but this particular image is still not really usable.
Heh. And the bootloader is now defaulting to waiting for user input before continuing to boot the system. Matt made two commits here in the last day, and it’s not something that I can fix properly myself. Keeping a copy of the old bootloader around is a fair temporary solution.
Yikes, this is not a good week for DragonFly users. :-/
It turns out that the bootloader issue was due to a different commit than I thought. It was due to the new “Dual-console default” feature. My UPS was sending something that was being interpreted as keyboard input, which of course, dumped my to a boot prompt.
A problem described in the following email (and at least one prior):
http://leaf.dragonflybsd.org/mailarchive/bugs/2004-06/msg00179.html
is present in this particular CD image (2004-06-23 (it’s bitten me too)). The issue seems to have since been resolved, but this particular image is still not really usable.
Heh. And the bootloader is now defaulting to waiting for user input before continuing to boot the system. Matt made two commits here in the last day, and it’s not something that I can fix properly myself. Keeping a copy of the old bootloader around is a fair temporary solution.
Yikes, this is not a good week for DragonFly users. :-/
It turns out that the bootloader issue was due to a different commit than I thought. It was due to the new “Dual-console default” feature. My UPS was sending something that was being interpreted as keyboard input, which of course, dumped my to a boot prompt.