From owner-freebsd-current Mon Sep 9 05:56:30 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA19064 for current-outgoing; Mon, 9 Sep 1996 05:56:30 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA19057; Mon, 9 Sep 1996 05:56:27 -0700 (PDT) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id FAA08637; Mon, 9 Sep 1996 05:56:07 -0700 (PDT) To: Poul-Henning Kamp cc: rkw@dataplex.net (Richard Wackerbarth), current@FreeBSD.org, jhs@FreeBSD.org Subject: Re: Latest Current build failure In-reply-to: Your message of "Mon, 09 Sep 1996 14:40:51 +0200." <10061.842272851@critter.tfs.com> Date: Mon, 09 Sep 1996 05:56:06 -0700 Message-ID: <8624.842273766@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > In message , Richard Wackerbarth writes: > > >I starts out OK, but the list of required things in "minimal" is getting > >rediculously long. The problem is in "proving" that I am using code > >"bootstrapped" from the -current sources. I'm ready to throw in the towel > >on that one and change the "definition" to be: > > if you can complete a "make release" in /usr/src/release you're safe. Slightly off-topic, but speaking of which... I have a 2.2-current box which is talking to a 2.1.5 NFS server here, and doing a make release with CHROOTDIR set to point at an NFS mounted partition is a sure way to kill the 2.2. box stone dead. Unfortunately, a memory upgrade now has me in the embarassing position of having more main memory than swap configured and it's going to be backup and reinstall time for me shortly, just so I can take a panic dump again! :-( Anyone else seeing this problem? Jordan