From owner-freebsd-current@FreeBSD.ORG Tue Dec 2 11:00:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB02616A4CE for ; Tue, 2 Dec 2003 11:00:57 -0800 (PST) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 638BA4400B for ; Tue, 2 Dec 2003 11:00:52 -0800 (PST) (envelope-from bsd-current@epcdirect.co.uk) Received: from localhost (localhost [127.0.0.1]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 4838C154BB; Tue, 2 Dec 2003 19:00:51 +0000 (GMT) Received: from gunfright.epcdirect.co.uk ([127.0.0.1])port 10024) with ESMTP id 85484-06; Tue, 2 Dec 2003 19:00:50 +0000 (GMT) Received: from lfarr (l-farr.int.epcdirect.co.uk [192.168.6.200]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id 0B11E154AF; Tue, 2 Dec 2003 19:00:50 +0000 (GMT) From: "Lawrence Farr" To: "'Barney Wolff'" Date: Tue, 2 Dec 2003 19:00:51 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 In-Reply-To: <20031202183149.GA1084@pit.databus.com> Thread-Index: AcO5ApXAF6bo+aaJTa+jwExg+2GFQgAA95fg Message-Id: <20031202190050.0B11E154AF@gunfright.epcdirect.co.uk> X-Virus-Scanned: by Gunfright.epcdirect.co.uk cc: freebsd-current@freebsd.org cc: "'M. Warner Losh'" cc: kris@obsecurity.org Subject: RE: 4 -> 5 Problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Dec 2003 19:00:57 -0000 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: Barney Wolff [mailto:barney@databus.com] > Sent: 02 December 2003 18:32 > To: Lawrence Farr > Cc: 'M. Warner Losh'; kris@obsecurity.org; freebsd-current@freebsd.org > Subject: Re: 4 -> 5 Problem > > On Tue, Dec 02, 2003 at 05:27:12PM -0000, Lawrence Farr wrote: > > I get this error when trying to install the kernel, > > the same kernel installs fine on the box that made it. > > > > root@galaga:/usr/src# make installkernel > > > > > -----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. > > I've observed this when installing on a different system than the > build system. I got it after building/installing several times > on the build system before trying to installkernel on another system > with /usr/src and /usr/obj nfs-mounted. The problem appeared to be > that the stuff in the legacy directory under /usr/obj is built > assuming that what's on the build system will work under the prior > kernel - which is true on the build system but not necessarily on > the target system. > > My solution was to edit (temporarily) /usr/src/Makefile.inc1 to > put /usr/bin first in the PATH set up for the reinstallkernel > target. That allowed make installkernel to succeed on the target > system. Then I rebooted the target and backed out the change to > /usr/src/Makefile.inc1, and after that make installworld and > mergemaster went fine as usual. > > I didn't delve deeply enough to figure out what a cleaner fix would > be, but this should probably be a PR as otherwise the 5.2 upgrade > may be "difficult" for people who build and install on separate boxes. > > -- > Barney Wolff http://www.databus.com/bwresume.pdf > I'm available by contract or FT, in the NYC metro area or via > the 'Net. >