Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Dec 2003 13:16:17 -0800
From:      othermark <atkin901@yahoo.com>
To:        freebsd-current@freebsd.org
Subject:   RE: 4 -> 5 Problem
Message-ID:  <bqivf3$3pp$1@sea.gmane.org>
References:  <20031202183149.GA1084@pit.databus.com> <20031202190050.0B11E154AF@gunfright.epcdirect.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
I've just completed my 3rd 5.0 -> 5-current upgrade over nfs, and it always
sig 12's on me.  however, if I cd /usr/obj/usr/src/sys/<KERNEL> and 'make
install' from there it works fine.  Good workaround for this particular
problem.

I have also gotten an error regarding this line in Makefile.inc1 for early
versions of 5.x

743 .if (!defined(NO_RESCUE) || \
744     defined(RELEASEDIR)) && \
745     (${TARGET_ARCH} != ${MACHINE_ARCH} || ${BOOTSTRAPPING} < 501101)
746 _crunchide= usr.sbin/crunch/crunchide
747 .endif

where make complains that ${BOOTSTRAPPING} < 501101 is invalid, because it
thinks it's a string comparison..

Changing it to != for a quick hack works for upgrading 5.0.

Lawrence Farr wrote:
> Does this need a note in UPDATING then? 4-> 5 over NFS, and Older
> 5-> Newer 5 over NFS no longer work as previous?
> 
> Lawrence Farr
> EPC Direct Limited

>> > > -----Original Message-----
>> > > From: M. Warner Losh [mailto:imp@bsdimp.com]
>> > > Sent: 02 December 2003 17:16
>> > > : 
>> > > : > install -p -m 555 -o root -g wheel kernel /boot/kernel
>> > > : > *** Signal 12
>> > > : 
>> > > : This usually means you've tried to update something out of
>> > > the correct
>> > > : order.
>> > > 
>> > > Signal 12 means thaqt you didn't upgrade your kernel first.

this cracked me up.

-- 
othermark
atkin901 at nospam dot yahoo dot com
(!wired)?(coffee++):(wired);



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bqivf3$3pp$1>