freebsd stable - Oct 2003 - Help saving my system

Hi Guys, here's the scenario:
 
1. Had FreeBSD 5.1 system running.
2. Did a cvsup get of stable (that's right, stable, so 4.9)
3. Compiled make buildworld, then did a make build world, and re-compiled
with generic kernel
4. Booted into a system which could not mount the file system (expected
since its 4.9)
 
So now I am trying to save the system and here's where I've gotten to:
 
1. Booted disc 2 of 5.1 cd into "fixme" mode.
2. Mounted live cdrom filesystem and then mounted my root drive to /mnt
3. Did a chroot to /mnt so that I would emulate my live system environment
4. Re-did a cvsup of the branch current.
5. Ran make buildworld from /usr/src
 
Here is what happens when I do that:
 
"/dev/null", line 1: Need an operator 
"/dev/null", line 1: Need an operator 
"/dev/null", line 1: Need an operator 
"/dev/null", line 1: Need an operator 
"/dev/null", line 1: Need an operator 
"/dev/null", line 1: Need an operator 
"/dev/null", line 1: Need an operator
make: fatal errors encountered -- cannot continue
"/usr/src/Makefile.inc1", line 156: warning:
"/usr/obj/usr/src/make.i386/make -f /dev/null -m /usr/src/share/mk
CPUTYPE=dummy -V CPUTYPE" returned non-zero status
"/usr/src/Makefile.inc1", line 158: CPUTYPE global should be set with
?=.
*** Error code 1
 
Help!
 
-Jason
 


________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________From
lekanteto at gmx.net  Sat Oct 18 02:31:02 2003
From: lekanteto at gmx.net (Stefan Koesling)
Date: Sat Oct 18 02:32:00 2003
Subject: FreeBSD 4.9 RC3 (i386) now available
In-Reply-To: <20031018070433.GE1434@freebsdmall.com>
References: <20031018070433.GE1434@freebsdmall.com>
Message-ID: <3F9107D2.1050900@gmx.net>

I use IPFW2. What has been fixed, what should be tested?

-Stefan


Murray Stokely wrote:
>A number of the issues brought up with RC2 have been resolved, and the
>latest release candidate (RC3) is now available for i386 (alpha coming
>soon) :
>
>ftp.FreeBSD.org/pub/FreeBSD/releases/i386/4.9-RC3
>ftp.FreeBSD.org/pub/FreeBSD/releases/i386/ISO-IMAGES/4.9-RC3-i386-disc1.iso
>
>MD5 (4.9-RC3-i386-disc1.iso) = a8fc7f9b86865004a02ab7a805cddbf0
>
>We are especially interested in hearing reports from users using IPFW2
>after Kirk's recent fix.  Please send us a note if you are able to
>test IPFW2 in any substantial way.  The firewire module loading issue
>has been resolved, but the SATA issue has not.  John Baldwin has a
>patch posted at http://people.freebsd.org/~jhb/patches/sata.patch
>(thanks to everyone on this list who helped debug this)
>
>     Thanks,
>
>     Release Engineering Team
>  
>

On Sat, 18 Oct 2003 00:21:26 -0700
Jason Dictos <jason.dictos@tapeware.com> wrote:

JD> environment 4. Re-did a cvsup of the branch current.
JD> 5. Ran make buildworld from /usr/src

JD> Help!

I kinda don't understand what are you trying to ACHIEVE. I'd try to
"Upgrade" from Disk 1 of 5.1-RELEASE.

-- 
Alex.

I was able to mount devfs to the new chroot area and perform a
rebuild of the newly gotten current branch. Then I compiled the kernel and
rebooted into a working system again. The fact that the new chroot area
didn't have devfs mounted to its local /dev directory caused make buildworld
to fail.

Hope that made sense,
-Jason 


-----Original Message-----
From: Alex Povolotsky [mailto:tarkhil@webmail.sub.ru] 
Sent: Sunday, October 19, 2003 1:00 AM
To: freebsd-stable@freebsd.org; Jason Dictos

On Sat, 18 Oct 2003 00:21:26 -0700
Jason Dictos <jason.dictos@tapeware.com> wrote:

JD> environment 4. Re-did a cvsup of the branch current.
JD> 5. Ran make buildworld from /usr/src

JD> Help!

I kinda don't understand what are you trying to ACHIEVE. I'd try to
"Upgrade" from Disk 1 of 5.1-RELEASE.

--
Alex.

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security service
working around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________

________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs Email
Security System. For more information on a proactive email security
service working around the clock, around the globe, visit
http://www.messagelabs.com
________________________________________________________________________