From owner-freebsd-questions@FreeBSD.ORG Fri Oct 12 10:31:38 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F46C45B for ; Fri, 12 Oct 2012 10:31:38 +0000 (UTC) (envelope-from jamie@kode5.net) Received: from kontrol.kode5.net (kontrol.kode5.net [80.229.5.32]) by mx1.freebsd.org (Postfix) with ESMTP id 9D7148FC1C for ; Fri, 12 Oct 2012 10:31:37 +0000 (UTC) Received: from kontrol.kode5.net (localhost [127.0.0.1]) by kontrol.kode5.net (8.14.5/8.14.5) with ESMTP id q9CAVZpP076920 for ; Fri, 12 Oct 2012 11:31:35 +0100 (BST) (envelope-from jamie@kode5.net) Received: (from jamie@localhost) by kontrol.kode5.net (8.14.5/8.14.5/Submit) id q9CAVZZc076919 for freebsd-questions@freebsd.org; Fri, 12 Oct 2012 11:31:35 +0100 (BST) (envelope-from jamie@kode5.net) X-Authentication-Warning: kontrol.kode5.net: jamie set sender to jamie@kode5.net using -f Date: Fri, 12 Oct 2012 11:31:35 +0100 From: Jamie Paul Griffin To: freebsd-questions@freebsd.org Subject: Re: problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE Message-ID: <20121012103135.GE18344@kontrol.kode5.net> Mail-Followup-To: freebsd-questions@freebsd.org References: <50771338.8040102@islogistics.com> <5077690F.7020703@FreeBSD.org> <20121012085343.GB18344@kontrol.kode5.net> <5077DCB7.60807@ose.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5077DCB7.60807@ose.nl> x-operating-system: FreeBSD 9.1-PRERELEASE amd64 x-pgp-fingerprint: A4B9 E875 A18C 6E11 F46D B788 BEE6 1251 1D31 DC38 x-pgp-key: 1D31DC38 User-Agent: Mutt/1.5.21 (2010-09-15) X-Virus-Scanned: clamav-milter 0.97.6 at kontrol.kode5.net X-Virus-Status: Clean X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Oct 2012 10:31:38 -0000 [ Bas Smeelen wrote on Fri 12.Oct'12 at 11:02:47 +0200 ] > On 10/12/2012 10:53 AM, Jamie Paul Griffin wrote: > > [ Greg Larkin wrote on Thu 11.Oct'12 at 20:49:19 -0400 ] > > > >> Hi Stuart, > >> > >> If you click the link in this mailing list article > >> (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218554.html), > >> then follow the rest of the threaded messages, you should be able fix > >> the problem once you upgrade to 7.4. > >> > >> The issue is that freebsd-update cannot update the ld-elf.so.1 binary > >> on a running system, so after the upgrade to 7.4 (or higher), the > >> system is not completely updated. > >> > >> This message > >> (http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html) > >> has a fix, but it involves booting from a liveCD and replacing the > >> binary manually. > > Would it be easier to do an update by building from source? I've never used freebsd-update myself so not had to troubleshoot these issues before. > > That's probably the best way. > > Bit I am wondering about this. > I upgraded several systems (physical and virtual machines) with > freebsd-update from 7.1 -> 7.3 -> 8.1 -> 8.3 and also one system from 7.1 -> > 7.4 (with custom kernels) and did not encounter this. Did I just get lucky then? I couldn't comment on the freebsd-update(8) procedure as I've never used it. But I'd personally upgrade the system by building from source. You can then easily integrate your custom kernel and I would *imagine* you'd avoid the issues you've encountered so far. Make sure you read /usr/src/UPDATING thoroughly, and also check your customer kernel options. Some changes have been made to more recent versions of FreeBSD, such as the ata(4) driver. I believe in the past certain elements could be (and still can be) added in a modular fasion, explicitly setting each element. Now, you only need to have: device scbus, device ata and options ATA_CAM. Already present in the GENERIC kernel config now. See man 4 ata for details. I hope i've got that right, hopefully others will correct my comments if necessary but in any case, reading the appropriate files will provide all the information needed. For example: /usr/src/sys/conf/NOTES and /usr/src/sys/{i386,amd64}/NOTES have more information about kernel options that might be helpful and of interest to you.