From owner-freebsd-announce Thu May 8 22:26:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA11809 for freebsd-announce-outgoing; Thu, 8 May 1997 22:26:17 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA11804; Thu, 8 May 1997 22:26:14 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id WAA16607; Thu, 8 May 1997 22:26:21 -0700 (PDT) To: current@freebsd.org cc: announce@freebsd.org Subject: 3.0 SNAPshots on ftp.freebsd.org Date: Thu, 08 May 1997 22:26:21 -0700 Message-ID: <16603.863155581@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Well, it looks like someone other than myself got to break sysinstall for this snap (not to name names, but the CVS repository will point up the guilty party :-) - using the (A)ll disk option will now core dump sysinstall in the 970505 sources (and it's still broken in -current but I expect a fix to be committed shortly). Hmph. I'm sorry folks, and I don't really know what to say, but it's effectively the case now that 3.0-970505-SNAP is unusable with a very often-used installation option and so I will now withdraw it from ftp.freebsd.org. Since doing this on a regular basis also sucks, I think that I will call a halt to all further 3.0-SNAPs for the time being until I can evolve a better way of dealing with this. My feeling is that our best solution will be to find some VERY KIND PERSON [hint hint :-)] to allow us to use their PPro-200 box to build and offer for FTP daily 3.0-SNAPs in much the same way that the releng22.freebsd.org (admin1.calweb.com) machine does it for the 2.2 branch. That way people can just grab the snap-o-the-day and see what they think of it. If one looks especially functional, we can also copy it to ftp.freebsd.org in much the same way we do with the RELENG 2.2 stuff but it will *not* be the most definitive version, that will remain on the SNAP-server. Thoughts? Anyone care to donate some CPU time, disk space and network connectivity to host this service? Basically, it's gotta be at least a mid-speed Pentium Pro or a fast Pentium (200Mhz), have at least 800MB of disk storage to spare and be T1 or better connected to the net. Anything less and really, honestly, you don't want to go there. ;-) Thanks! Jordan