From owner-freebsd-current Sat Jan 22 11:12: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from smarkacz.agsmedia.pl (smarkacz.agsmedia.pl [195.205.87.210]) by hub.freebsd.org (Postfix) with ESMTP id 723F014C16 for ; Sat, 22 Jan 2000 11:09:36 -0800 (PST) (envelope-from jps@smarkacz.agsmedia.pl) Received: (from jps@localhost) by smarkacz.agsmedia.pl (8.9.3/8.9.3) id UAA14792; Sat, 22 Jan 2000 20:09:02 +0100 (CET) (envelope-from jps) To: Scott Burns Cc: "Matt M." , current@FreeBSD.ORG Subject: Re: cvsup 3.4-release to -current References: <3887ECC9.7A2625F5@boda.virtualave.net> <388915EF.90D99DC6@wpsystems.net> X-Editor: Formerly /usr/bin/vi From: smarkacz@anathema.eu.org (smarkacz) In-Reply-To: Scott Burns's message of "Fri, 21 Jan 2000 21:29:03 -0500" Date: 22 Jan 2000 20:09:01 +0100 Message-ID: <86g0vply9e.fsf@smarkacz.agsmedia.pl> Lines: 12 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Burns wrote: > I tried upgrading to 4.0-CURRENT from 3.4-RELEASE, and the buildworld > worked fine, but the installworld was interrupted part of the way > through the install by a signal 12 to sh. I tried doing it from > 3.4-RELEASE a few times, as well as from 3.4-STABLE on the same box, and > I got the same error every time. I ended up booting to the 3.4 install > disk and reinstalling 3.4 with sysinstall to fix it, because sh and csh > would crash with a signal 12 every time. Build 4.0-CURRENT kernel, boot it, THEN do `make installworld'. -- smarkacz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message