From owner-freebsd-current Tue Jan 26 19:54:38 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18866 for freebsd-current-outgoing; Tue, 26 Jan 1999 19:54:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat0690.mpoweredpc.net [142.177.190.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18856 for ; Tue, 26 Jan 1999 19:54:33 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id XAA02137; Tue, 26 Jan 1999 23:54:26 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 26 Jan 1999 23:54:25 -0400 (AST) From: The Hermit Hacker To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: "make upgrade NOCONFIRM=YES" (Was: Re: Hate to ask, but...aout -> elf ... ) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make upgrade NOCONFIRM=YES Your source tree must not be fully populated; unable to find upgrade script in /usr/src/release/scripts/doupgrade.sh. *** Error code 1 Stop. *** Error code 1 Stop. Just connected to freefall and did a 'cvs checkout' of release, and the file doesn't appear to exist there either, so it isn't an out of sync cvsup or anything...*raised eyebrow* On Tue, 26 Jan 1999, The Hermit Hacker wrote: > On Tue, 26 Jan 1999, Jordan K. Hubbard wrote: > > > > Is it a simple matter of 'make aout-to-elf', or...? > > > > As of today, just type "make upgrade NOCONFIRM=YES" and wait for the > > server to reboot some n hours later (where n is governed by the speed > > of your machine :). > > Oh, now, *that* makes me nervous :) 2500 kilometers away from my baby, > and "waiting for the server to reboot" is what I'm trying to avoid :) > > What exactly does this do? I'm going to read through the Makefile as soon > as I get it upgraded but...I think my more immediate concern is the kernel > and boot blocks...any summary somewhere of what to expect? :) Binaries > breaking? config files in /etc going poof? > > thanks... > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message