From owner-freebsd-current Tue Jan 26 21:15:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA27890 for freebsd-current-outgoing; Tue, 26 Jan 1999 21:15:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA27882 for ; Tue, 26 Jan 1999 21:15:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.2/8.9.1) with ESMTP id VAA77599; Tue, 26 Jan 1999 21:16:24 -0800 (PST) To: The Hermit Hacker cc: freebsd-current@FreeBSD.ORG Subject: Re: "make upgrade NOCONFIRM=YES" (Was: Re: Hate to ask, but...aout -> elf ... ) In-reply-to: Your message of "Tue, 26 Jan 1999 23:54:25 -0400." Date: Tue, 26 Jan 1999 21:16:23 -0800 Message-ID: <77595.917414183@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Already fixed. :) > > 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}.or g > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message