From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 26 18:01:26 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2BA2916A401; Mon, 26 Feb 2007 18:01:26 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from netmusician.org (netmusician.org [216.9.132.179]) by mx1.freebsd.org (Postfix) with ESMTP id ECC0313C4A3; Mon, 26 Feb 2007 18:01:25 +0000 (UTC) (envelope-from joe@netmusician.org) Received: from localhost (localhost [127.0.0.1]) by netmusician.org (Postfix) with ESMTP id A9E2F7E8C3; Mon, 26 Feb 2007 13:01:27 -0500 (EST) X-Virus-Scanned: by amavisd-new at netmusician.org Received: from netmusician.org ([127.0.0.1]) by localhost (netmusician.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bW6148KqnG7Q; Mon, 26 Feb 2007 13:01:26 -0500 (EST) Received: from [192.168.0.2] (74-130-30-11.dhcp.insightbb.com [74.130.30.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by netmusician.org (Postfix) with ESMTP id 60C347E8BF; Mon, 26 Feb 2007 13:01:26 -0500 (EST) In-Reply-To: <001001c759a6$438d5ed0$3c01a8c0@coolf89ea26645> References: <6B2A41DC-79FA-42A1-B1BC-BB9F0A74B765@netmusician.org><200702251146.08150.Danovitsch@vitsch.net><228AFDCF-D9C1-43F1-ACBE-719595B10FEE@netmusician.org><003b01c75940$fbc095f0$3c01a8c0@coolf89ea26645> <39E24107-964D-414C-95D1-5B1C376291E4@netmusician.org> <001001c759a6$438d5ed0$3c01a8c0@coolf89ea26645> Mime-Version: 1.0 (Apple Message framework v752.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6F5A88A9-55D6-4D05-88DD-FF39D079A99B@netmusician.org> Content-Transfer-Encoding: 7bit From: Joe Auty Date: Mon, 26 Feb 2007 13:01:19 -0500 To: Ted Mittelstaedt X-Mailer: Apple Mail (2.752.2) Cc: "Daan Vreeken \[PA4DAN\]" , Kip Macy , freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: kernel panic at boot on any 6.x OS X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Feb 2007 18:01:26 -0000 On Feb 26, 2007, at 8:01 AM, Ted Mittelstaedt wrote: > > ----- Original Message ----- > From: "Joe Auty" > To: "Ted Mittelstaedt" > Cc: "Daan Vreeken [PA4DAN]" ; "Kip Macy" > ; ; > > Sent: Sunday, February 25, 2007 10:39 PM > Subject: Re: kernel panic at boot on any 6.x OS > > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> >> On Feb 25, 2007, at 7:56 PM, Ted Mittelstaedt wrote: >> >>> >>> ----- Original Message ----- >>> From: "Joe Auty" >>> To: "Daan Vreeken [PA4DAN]" >>> Cc: "Kip Macy" ; >> questions@freebsd.org>; >>> >>> Sent: Sunday, February 25, 2007 8:14 AM >>> Subject: Re: kernel panic at boot on any 6.x OS >>> >>> >>>> >>>> Any idea how this could have happened after disabling everything in >>>> my /etc/loader.conf, and simply running a: >>>> >>>> make buildworld >>>> make buildkernel KERNCONF=myconfig >>>> make installkernel KERNCONF=myconfig >>>> >>> >>> well your supposed to do this single-user, run mergemaster and a >>> few other >>> things. >>> I also don't see a make installworld. >>> >> >> I usually perform those steps after I've rebooted to ensure that my >> system will boot off the new kernel, as per the instructions in the >> FreeBSD handbook. >> >>> Joe, please try booting from a 6.2-release install ISO. If it >>> works without >>> panicing, >>> then you did something wrong during the upgrade. >>> >> >> Downloading the image now, I'll let you know if I'm able to boot from >> it... >> >>> Since by your own admission your not an expert, you would be well >>> advised >>> to simply back up your files the old fashioned way, reformat your >>> hard disk, >>> install from a 6.2 boot ISO, then restore your files. Leave the >>> fancy >>> in-place >>> updating to someone else. It's a big PIA and doesen't work half >>> the time >>> anyway. >>> >> >> >> How well does simply upgrading with the CD work (as opposed to wiping >> clean)? I've upgraded several times to new releases simply by >> rebuilding world, it has never failed me in the past. I don't doubt >> what you are saying here, but since I will have to change how I work, >> assuming that I can boot off of the 6.2 CD, I'd appreciate any >> general upgrade tips that don't involve wiping the disk clean (which >> is not really an option). >> > > If wiping the disk really isn't an option then you have one or more > of the > following > problems: > > 1) Production system with a lack of hardware spares > > 2) inadequate backup plan and execution. > > People who state that wiping the disk isn't an option are screaming > at the top of their lungs for the hardware gremlins to explain what > MTBF is > all about. > > The gremlins will visit you, I guarentee. And they always pick the > very > best > times for it too. I just hope (if this is your workplace) that > your job > survives. > My production system is backed up daily to two different sites, that's not an issue. The system I'm thinking of upgrading to 6.2 is my test server I run out of my house that stores movie files and other non-essential files. Technically, wiping it clean *would* be an option if it came down to it, just an inconvenience. Perhaps I should invest in another HD to use for instances such as this. >> For instance, is rebuilding world between point releases (e.g. 5.4 to >> 5.5) an okay idea, compared to across major releases (e.g. 5.5 to >> 6.2)? >> >> >> I'll do my own homework regarding this too, but I appreciate any >> nuggets of wisdom you might have! As far as me being an expert, I >> guess I'd categorize me somewhere in between complete newb and >> FreeBSD developer =) >> > > The problem is that all of the ports and packages that you put on a > server > change from release to release. The developers of openssl, for > example, > don't give a tinkers damn about how FreeBSD's upgrade process works, > when they are making changes in their code. > > I run a number of FreeBSD servers and what I do is simply keep them > patched > with security updates. Every once in a while a security hole will be > discovered in a non-core program and if it's serious enough I'll go > into the > port > and do a "make deinstall" followed by downloading and compiling the > program > the "old fashioned way" I shoot for a min of 3 years on the OS > before even > thinking about updating, and when it's time to update the hardware has > generally reached the old rag stage anyway. > Do you run any non-production machines where you test running newer OSes and test software updates and such? ----------- Joe Auty NetMusician: web publishing software for musicians http://www.netmusician.org joe@netmusician.org