From owner-freebsd-current@FreeBSD.ORG Thu Nov 13 09:11:23 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 DEB1916A4CE for ; Thu, 13 Nov 2003 09:11:23 -0800 (PST) Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95DED43F3F for ; Thu, 13 Nov 2003 09:11:22 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id 0B4AF384EC; Thu, 13 Nov 2003 18:11:21 +0100 (CET) Date: Thu, 13 Nov 2003 18:11:20 +0100 From: Jesper Skriver To: eculp@encontacto.net Message-ID: <20031113171120.GC73775@FreeBSD.org> Mail-Followup-To: Jesper Skriver , eculp@encontacto.net, freebsd-current@freebsd.org References: <20031113064835.qccgccsoowkw0o00@mail.encontacto.net> <20031113145037.GR60410@submonkey.net> <20031113065514.kkcg0ckwsw88okcw@mail.encontacto.net> <20031113073915.yy8s4ooggssk4kw0@mail.encontacto.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031113073915.yy8s4ooggssk4kw0@mail.encontacto.net> User-Agent: Mutt/1.4.1i X-PGP-Fingerprint: 6B88 9CE8 66E9 E631 C9C5 5EB4 22AB F0EC F956 1C31 X-PGP-Public-Key: http://freesbee.wheel.dk/~jesper/gpgkey.pub cc: freebsd-current@freebsd.org Subject: Re: 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 17:11:24 -0000 On Thu, Nov 13, 2003 at 07:39:15AM -0800, eculp@encontacto.net wrote: > 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 :-) I upgraded a ancient -current last night, I did 1) cvsup 2) build and install new kernel 3) reboot 4) build and isntall new world 5) mergemaster 6) reboot /Jesper