Re: DragonFly and FBSD 5.1

[Jeroen Ruigrok/asmodai <asmodai@xxxxxx>]

-On [20031027 17:12], Matthew Dillon (dillon@xxxxxxxxxxxxxxxxxxxx) wrote:
>   I dunno.  I haven't run 5.x in several months.  I'm a little surprised
>   that 5.x wouldn't be able to access a 4.x UFS filesystem, though... that
>   can't be correct.

Actually my memory failed me, when I tried this I forgot that I chose to
reformat /, /var, and /tmp.

After trying to work around the numerous bugs in the installation
routine, page faults after configuring a network, or setting root's
password to fail due to a sig12, I managed to install CURRENT as of the
25th.  (So network configuration broke between the 25th and the 26th.)

I then had to boot from floppy since my root slice lies above the 1024
cylinder limit and the bootmanager is not configurable in that aspect
(for all I know), I managed to boot the installed kernel on
/boot/kernel/kernel.  Trying to log in as my normal user name resulted
in 'login' sig 11'ing but thankfully root, without password, was allowed
to log in.  All well, used boot0cfg to set the boot options to 'packet'
and then booted from the hard disk as it should.  And after setting the
root device to ufs:ad0s2a it tried to load /sbin/init and utterly fails.
This has been tested on reformatting / as UFS and UFS2.

Really got to love this (note obligatory sarcasm).  Got to admit the
bootscreen is a nice touch.  I should try safe and single, see how far
that'll get me.

I just truly wish I'd knew if this was CURRENT being lame or the nForce
2 chip acting up (I doubt the latter, because I can fsck my /usr on
install, which resides on that disk).

I'm telling you, as soon as I am able I'll make DF boot normally with
the nForce 2.

-- 
Jeroen Ruigrok van der Werven <asmodai(at)wxs.nl> / asmodai / kita no mono
PGP fingerprint: 2D92 980E 45FE 2C28 9DB7  9D88 97E6 839B 2EAC 625B
http://www.tendra.org/   | http://www.in-nomine.org/~asmodai/diary/
The earth laughs in flowers...