From owner-freebsd-questions@FreeBSD.ORG Thu Jun 12 19:30:35 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D841C37B401 for ; Thu, 12 Jun 2003 19:30:35 -0700 (PDT) Received: from pa-plum1b-166.pit.adelphia.net (pa-plum1b-217.pit.adelphia.net [24.53.161.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id C854643F93 for ; Thu, 12 Jun 2003 19:30:34 -0700 (PDT) (envelope-from wmoran@potentialtech.com) Received: from potentialtech.com (working [172.16.0.95]) h5D2UYOg002513; Thu, 12 Jun 2003 22:30:34 -0400 (EDT) (envelope-from wmoran@potentialtech.com) Message-ID: <3EE9374A.9030501@potentialtech.com> Date: Thu, 12 Jun 2003 22:30:34 -0400 From: Bill Moran User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030429 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cp References: <200306120805.45148.andrewr@uidaho.edu><011101c330fa$8a4cebc0$d037630a@dh.com> <20030612183418.GB7415@webserver.get-linux.org> <000e01c33149$78996bc0$e1210343@compaq7058> In-Reply-To: <000e01c33149$78996bc0$e1210343@compaq7058> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@FreeBSD.ORG Subject: Re: Upgrading 5.0 -> 5.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 02:30:36 -0000 cp wrote: >>You should *really* use 'make buildkernel' in the toplevel if you're >>combining it with a world update. Recommended procedure: >>~# cvsup /my/5.1.supfile >>~# cd /usr/src >>/usr/src# make buildworld >>/usr/src# make buildkernel KERNCONF= >>/usr/src# make installkernel KERNCONF= >>/usr/src# reboot >>OK boot -s >># fsck -p && mount -a >># ( cd /usr/src && make installworld ) >># reboot >>OK boot >> >>Also read chapter 21 of the Handbook. > > > I have a related question on this if you would permit. > I just did the same thing (5.0->5.1), I started to follow > the handbook but became concerned in reading posts > on the subject that suggested to installworld prior to > building the kernel and booting. I also do not have > access to the console in any convenient manner so I > knew that it would never come back from > the boot (it would be a week before I could then > get it up). So I did this: > > cvsup (src=all) RELENG_5_1 > buildworld > installworld > make buildkernel KERNCONF=MINE Wow. Don't do this. Here's the reason: Running kernel and world out of sync can potentially cause all sorts of problems (and usually does). The buildworld, buildkernel, installkernel, reboot, installworld sequence is designed to specifically reduce the chances of getting you into a corner you can't back out of. For example: make buildworld make buildkernel < anywhere before this point, if you have problems or change your mind, you just delete /usr/obj and everything is back to normal make installkernel < After this point, reverting consists of copying kernel.old back to kernel and /modules.old back to /modules reboot into single user mode < if the new kernel doesn't boot, you can boot kernel.old and follow the steps above to get things back to where they were make installworld < If you got this far ... chances are everything went well and you'll have no reason to revert. > At this point, it won't complete the kernel build and is > showing signs of being unusable (e.g. "ipfw show" just > dumps core). Is it too late to correct this or is a > reinstall and reconfigure next week the only option left? I would suggest recvsupping to RELENG_5_0 and try the buildworld, buildkernel again ... if they both succeed, continue with the installkernel, reboot, installworld process and you should be back to a fully functioning 5.0 system I actually had to do this once, and it worked. From there, you should be able to do the 5.0 -> 5.1 upgrade process again. Even better, if you know the exact date of the sources used to build the kernel that's currently running, you can use the date keyword to cvsup sources to exactly that date. That would be even safer: *default release=cvs date=2003.03.23.10.00.00 -- Bill Moran Potential Technologies http://www.potentialtech.com