From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 07:39:17 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EC6516A4CE for ; Thu, 13 Nov 2003 07:39:17 -0800 (PST) Received: from insourcery.net (ns1.insourcery.net [198.93.171.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F14843FAF for ; Thu, 13 Nov 2003 07:39:16 -0800 (PST) (envelope-from eculp@encontacto.net) Received: from localhost (localhost [127.0.0.1]) (uid 80) by insourcery.net with local; Thu, 13 Nov 2003 07:39:16 -0800 Received: from customer-200-79-7-2.uninet.net.mxmail.encontacto.net (Horde) with HTTP for ; Thu, 13 Nov 2003 07:39:15 -0800 Message-ID: <20031113073915.yy8s4ooggssk4kw0@mail.encontacto.net> X-Priority: 3 (Normal) Date: Thu, 13 Nov 2003 07:39:15 -0800 From: eculp@encontacto.net To: freebsd-current@freebsd.org References: <20031113064835.qccgccsoowkw0o00@mail.encontacto.net> <20031113145037.GR60410@submonkey.net> <20031113065514.kkcg0ckwsw88okcw@mail.encontacto.net> In-Reply-To: <20031113065514.kkcg0ckwsw88okcw@mail.encontacto.net> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 200.79.7.2 Subject: Unattended reboot was Re: signal 12's everywhere on Current with update this morning. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2003 15:39:17 -0000 Mensaje citado por eculp@encontacto.net: | Mensaje citado por Ceri Davies : | | | On Thu, Nov 13, 2003 at 06:48:35AM -0800, eculp@encontacto.net wrote: | | > I installed an older current snap, Oct 26, on a brandnew dell power edge | | > with a single Xeon 2.4 GHz cpu and 1G in memory. It was running great. | | > I installed everything except the kitchen sink. Then I decided it was | | > time to update, I've got serveral other machines weathering the storms. | | > Bad idea. It doesn't hang or anything that I can get my teeth into but | | > it just give signal 12 core dumps on many if not most applications. I | | > caught this before finishing an install on another box, yesterday | morning. | | > One of the apps that generates signal 12 is ls so I tried pulling ls | | > from the other box and it no longer has a problem. I am at a lost. | | > Any suggestions for where to start would be appreciated. | | | | Read /usr/src/UPDATING. | | | Thanks, I missed that. :( Sorry for the noise. | | ed I'm building new kernels as I write this. My next question is: One of the machines I'm building on is remote and was last rebuilt just before the change. What would be be better sequence for making the change after a fresh cvsup ? 1. Build and Install a new kernel 2. build a new world 3. Run mergemaster 4. ReBoot (I'm not sure it will come up multiuser with a new kernel and a 4 day old userland.) 5. Installworld and assess possible problems :-) or 1. Build and Install a new kernel 2. make buildworld 3. Run mergemaster 4. make installworld; shutdown -r now # and pray :-) Or is there a better option? Has anyone else already done this? Thanks, ed -------------------------------------------------