RE: 4 -> 5 Problem
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/ 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:[EMAIL PROTECTED]
>> > > 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);
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
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:[EMAIL PROTECTED] > Sent: 02 December 2003 18:32 > To: Lawrence Farr > Cc: 'M. Warner Losh'; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: 4 -> 5 Problem > > On Tue, Dec 02, 2003 at 05:27:12PM -, Lawrence Farr wrote: > > I get this error when trying to install the kernel, > > the same kernel installs fine on the box that made it. > > > > [EMAIL PROTECTED]:/usr/src# make installkernel > > > > > -Original Message- > > > From: M. Warner Losh [mailto:[EMAIL PROTECTED] > > > 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. > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4 -> 5 Problem
On Tue, Dec 02, 2003 at 05:27:12PM -, Lawrence Farr wrote: > I get this error when trying to install the kernel, > the same kernel installs fine on the box that made it. > > [EMAIL PROTECTED]:/usr/src# make installkernel > > > -Original Message- > > From: M. Warner Losh [mailto:[EMAIL PROTECTED] > > 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. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
I get this error when trying to install the kernel, the same kernel installs fine on the box that made it. [EMAIL PROTECTED]:/usr/src# make installkernel Lawrence Farr EPC Direct Limited > -Original Message- > From: M. Warner Losh [mailto:[EMAIL PROTECTED] > Sent: 02 December 2003 17:16 > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: Re: 4 -> 5 Problem > > In message: <[EMAIL PROTECTED]> > Kris Kennaway <[EMAIL PROTECTED]> writes: > : On Tue, Dec 02, 2003 at 04:33:42PM -, Lawrence Farr wrote: > : > > : > I've just tried this again, and noticed an error message that I'd > : > missed: > : > : > 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. > > Warner > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4 -> 5 Problem
In message: <[EMAIL PROTECTED]> Kris Kennaway <[EMAIL PROTECTED]> writes: : On Tue, Dec 02, 2003 at 04:33:42PM -, Lawrence Farr wrote: : > : > I've just tried this again, and noticed an error message that I'd : > missed: : : > 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. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4 -> 5 Problem
On Tue, Dec 02, 2003 at 04:33:42PM -, Lawrence Farr wrote: > > I've just tried this again, and noticed an error message that I'd > missed: > 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. Kris pgp0.pgp Description: PGP signature
RE: 4 -> 5 Problem
I've just tried this again, and noticed an error message that I'd missed: [EMAIL PROTECTED]:/usr/src# make installkernel make: no target to make. "/usr/src/Makefile.inc1", line 157: warning: "make -f /dev/null -m /usr/src/share/mk CPUTYPE=i686 -V CPUTYPE" returned non-zero status cd /usr/obj/usr/src/sys/P6MPFW; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE=i686 GROFF_BIN_PATH=/usr/obj/usr/src/i386/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/i386/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/i386/legacy/usr/share/tmac PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/ bin:/usr/obj/usr/src/i386/legacy/usr/games:/usr/obj/usr/src/i386/usr/sbin:/u sr/obj/usr/src/i386/usr/bin:/usr/obj/usr/src/i386/usr/games:/sbin:/bin:/usr/ sbin:/usr/bin make KERNEL=kernel install thiskernel=`sysctl -n kern.bootfile` ; if [ "`dirname "$thiskernel"`" != /boot/kernel ] ; then chflags -R noschg /boot/kernel ; rm -rf /boot/kernel ; else if [ -d /boot/kernel.old ] ; then chflags -R noschg /boot/kernel.old ; rm -rf /boot/kernel.old ; fi ; mv /boot/kernel /boot/kernel.old ; sysctl kern.bootfile=/boot/kernel.old/"`basename "$thiskernel"`" ; fi mkdir -p /boot/kernel install -p -m 555 -o root -g wheel kernel /boot/kernel *** Signal 12 I also tried un-setting CPUTYPE, but got the same error. This gives you a zero sized kernel in /boot/kernel. Running install -p -m 555 -o root -g wheel kernel /boot/kernel from within the correct /obj directory works though. Lawrence Farr EPC Direct Limited > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Farr > Sent: 26 November 2003 19:32 > To: [EMAIL PROTECTED] > Subject: RE: 4 -> 5 Problem > > I'm still getting this with fresh sources. Has anyone else done 4->5 > in the last few days? Is it worth filing a PR? > > Lawrence Farr > EPC Direct Limited > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf Of > Lawrence Farr > > Sent: 25 November 2003 16:27 > > To: 'Clement Laforet' > > Cc: [EMAIL PROTECTED] > > Subject: RE: 4 -> 5 Problem > > > > Err yes I did. Im trying to install a kernel. > > > > Lawrence Farr > > EPC Direct Limited > > > > > -Original Message- > > > From: Clement Laforet [mailto:[EMAIL PROTECTED] > > > Sent: 25 November 2003 16:26 > > > To: Lawrence Farr > > > Cc: [EMAIL PROTECTED] > > > Subject: Re: 4 -> 5 Problem > > > > > > On Tue, 25 Nov 2003 16:18:26 - > > > "Lawrence Farr" <[EMAIL PROTECTED]> wrote: > > > > > > > > the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, > > > > the stable one from Mon Mar 24 16:30:45 GMT 2003, and the > > > > src and obj are fresh from last night. > > > > > > did you read /usr/src/UPDATING ? > > > > > > 20031112: > > > The statfs structure has been updated with 64-bit > fields to > > > allow accurate reporting of multi-terabyte filesystem > > > sizes. You should build world, then build and boot > > > the new kernel > > > BEFORE doing a `installworld' as the new kernel will > > > know about > > > binaries using the old statfs structure, but an old > > > kernel will > > > not know about the new system calls that support the > > > new statfs > > > structure. > > > > > > clem > > > > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to > > "[EMAIL PROTECTED]" > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
I'm still getting this with fresh sources. Has anyone else done 4->5 in the last few days? Is it worth filing a PR? Lawrence Farr EPC Direct Limited > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Farr > Sent: 25 November 2003 16:27 > To: 'Clement Laforet' > Cc: [EMAIL PROTECTED] > Subject: RE: 4 -> 5 Problem > > Err yes I did. Im trying to install a kernel. > > Lawrence Farr > EPC Direct Limited > > > -Original Message- > > From: Clement Laforet [mailto:[EMAIL PROTECTED] > > Sent: 25 November 2003 16:26 > > To: Lawrence Farr > > Cc: [EMAIL PROTECTED] > > Subject: Re: 4 -> 5 Problem > > > > On Tue, 25 Nov 2003 16:18:26 - > > "Lawrence Farr" <[EMAIL PROTECTED]> wrote: > > > > > > the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, > > > the stable one from Mon Mar 24 16:30:45 GMT 2003, and the > > > src and obj are fresh from last night. > > > > did you read /usr/src/UPDATING ? > > > > 20031112: > > The statfs structure has been updated with 64-bit fields to > > allow accurate reporting of multi-terabyte filesystem > > sizes. You should build world, then build and boot > > the new kernel > > BEFORE doing a `installworld' as the new kernel will > > know about > > binaries using the old statfs structure, but an old > > kernel will > > not know about the new system calls that support the > > new statfs > > structure. > > > > clem > > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: 4 -> 5 Problem
Err yes I did. Im trying to install a kernel. Lawrence Farr EPC Direct Limited > -Original Message- > From: Clement Laforet [mailto:[EMAIL PROTECTED] > Sent: 25 November 2003 16:26 > To: Lawrence Farr > Cc: [EMAIL PROTECTED] > Subject: Re: 4 -> 5 Problem > > On Tue, 25 Nov 2003 16:18:26 - > "Lawrence Farr" <[EMAIL PROTECTED]> wrote: > > > > the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, > > the stable one from Mon Mar 24 16:30:45 GMT 2003, and the > > src and obj are fresh from last night. > > did you read /usr/src/UPDATING ? > > 20031112: > The statfs structure has been updated with 64-bit fields to > allow accurate reporting of multi-terabyte filesystem > sizes. You should build world, then build and boot > the new kernel > BEFORE doing a `installworld' as the new kernel will > know about > binaries using the old statfs structure, but an old > kernel will > not know about the new system calls that support the > new statfs > structure. > > clem > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4 -> 5 Problem
On Tue, 25 Nov 2003 16:18:26 - "Lawrence Farr" <[EMAIL PROTECTED]> wrote: > > the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, > the stable one from Mon Mar 24 16:30:45 GMT 2003, and the > src and obj are fresh from last night. did you read /usr/src/UPDATING ? 20031112: The statfs structure has been updated with 64-bit fields to allow accurate reporting of multi-terabyte filesystem sizes. You should build world, then build and boot the new kernel BEFORE doing a `installworld' as the new kernel will know about binaries using the old statfs structure, but an old kernel will not know about the new system calls that support the new statfs structure. clem ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4 -> 5 Problem
I build 5-CURRENT every night, and NFS export src and obj to my other CURRENT machines to update. I've been doing this quite happily this way for a while. When I try to do an installkernel on a stable machine, I get: [EMAIL PROTECTED]:/usr/src# make installkernel Bad system call (core dumped) *** Error code 140 Stop in /usr/src. I can no longer do this on any of the current boxes either: mkdir -p /boot/kernel install -p -m 555 -o root -g wheel kernel /boot/kernel *** Signal 12 Stop in /usr/obj/usr/src/sys/P6MPFW. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I tried with -DALWAYS_CHECK_MAKE as well. Have I missed something in UPDATING? Anyone else doing this without issue? the Current target machine is from Thu Sep 25 14:32:19 GMT 2003, the stable one from Mon Mar 24 16:30:45 GMT 2003, and the src and obj are fresh from last night. Lawrence Farr EPC Direct Limited ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
