I always do a fresh install.
*** I JUST FOUND THE INSTALLER BUG ***
Just comparing install logs (on Alt-F1 screen):
DFly 2.0.1-REL:
-<<< Executing `cd /dev && /bin/test -c ad0s3a || /bin/sh MAKEDEV ad0s3a'
->>> Exit status: 0
-<<< Executing `/sbin/newfs ...etc
DFly 2.2.0-REL:
-<<< Executing `cd /dev && /bin/echo ad0s3a || /bin/sh MAKEDEV ad0s3a'
| ad0s3a
->>> Exit status: 0
-<<< Executing `/sbin/newfs ...etc
There is the problem, "echo ad0s3a" always returns 0, so MAKEDEV never
happens.
Cheers, MK
Bill Hacker (via DragonFly issue tracker) wrote:
Bill Hacker <[email protected]> added the comment:
First reaction is 'NFW that should have happened' - at least not as a
result of disklabel mismatch, device ID, etc.
Second thought is:
Did you do an upgrade with the DFLY toolset, OR a newfs and from-scratch
new install, or...
.just install over top of the old system, with neither an 'upgrade' nor
newfs - in which case, might there have been 'debris' - old files left
in place?
HTH,
Bill Hacker
_____________________________________________________
DragonFly issue tracker <[email protected]>
<http://bugs.dragonflybsd.org/issue1292>
_____________________________________________________
