From owner-freebsd-current Sun Oct 19 16:35:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA08836 for current-outgoing; Sun, 19 Oct 1997 16:35:28 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA08825 for ; Sun, 19 Oct 1997 16:35:19 -0700 (PDT) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.8.5/8.8.5) id BAA00469; Mon, 20 Oct 1997 01:41:01 +0200 (CEST) From: Mikael Karpberg Message-Id: <199710192341.BAA00469@ocean.campus.luth.se> Subject: Re: usable current SNAP In-Reply-To: <19971019114225.54861@lemis.com> from Greg Lehey at "Oct 19, 97 11:42:25 am" To: grog@lemis.com (Greg Lehey) Date: Mon, 20 Oct 1997 01:41:01 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Greg Lehey: > On Sat, Oct 18, 1997 at 08:02:08PM -0600, Steve Passe wrote: > > Hi, > > > >>> I need to bring up a web server this week using current. This needs to > >>> be a "works first time" installation (to impress a client). > >> > >> I don't understand this. This is *not* the purpose of -current. To > >> quote: > >> ... > > > > Yes, I know all this, I'm one of the people doing development work > > with 3.0-current, I won't be back complaining that xxx doesn't work! > > And your customers? > > > I have various assorted reasons, I just would like to here "I installed > > SNAP-9710xx and all went well" from someone b4 grabbing > > the tarballs... > > Oh well. The last two weeks I built -current, and it seems to be > working fine. More specifically, I supped on the 9th and the 16th. I just installed 3.0-971012-SNAP and it went very nice and smooth, except for dying in the post-installation menu when I tried to get packages. If you just install, reboot, and fix packages later, if shouldn't be a problem. :-) I had no problem with it dying either, actually, since it just meant I had to remove the disk, wait for the system to boot, and install packages later. The bug is fixed in later SNAPs, Jordan reports. But MFS is broken there. :-( /Mikael