-On [20040907 23:52], Matthew Dillon (dillon@apollo.backplane.com) wrote:
> I can't make heads or tails of it. All I can think of is that maybe
> you are running a mix of different types of boot code? The 5.x
> boot1/boot2/loader code is not compatible with the DFly boot1/boot2/loader
> code because our partition table is larger. 'boot0' (the master boot
> record) should always be compatible.
OK, I'll try a 4.10 install, see how that fares.
> It is unclear to me *which* CD you tried installing DFly from. It might
> be best to try installing the boot code from an official CD. I recommend
> using a GCC-2.95 daily snapshot CD or the latest reasonably-stable CD
> that I just rolled (dfly-20040907.iso.gz).
I used an aug 27 gcc 2 snapshot from corecode/Simon.
> You can also experiment with just overriding the boot blocks and loader
> binary from a DFly CD. Boot the DFly CD and use disklabel and cp to
> install new boot blocks over an existing configuration, like this:
>
> [boot cd, login as root]
> disklabel -B ad0s2
I have done this before and it didn't work.
Reason I did this was because disklabel complained about old style
bootblocks.
> mount ad0s2a /mnt
> cp /boot/loader /mnt/boot/loader
I haven't tried that by hand yet.
> dd if=/dev/zero of=/dev/ad0s2 bs=32k count=16
> disklabel -r -w ad0s2 auto
> disklabel -B ad0s2
> ... reinstall dragonfly from scratch on that slice ...
I'll try that, see if it makes a difference.
--
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
Free Tibet! http://www.savetibet.org/ | http://www.tibet.nu/
http://www.tendra.org/ | http://www.in-nomine.org/
To the dull mind nature is leaden. To the illumined mind the whole world
burns and sparkles with light...