From owner-freebsd-announce Thu May 8 04:21:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA21544 for freebsd-announce-outgoing; Thu, 8 May 1997 04:21:47 -0700 (PDT) Received: from time.cdrom.com (jkh@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA21538 for ; Thu, 8 May 1997 04:21:45 -0700 (PDT) Received: (from jkh@localhost) by time.cdrom.com (8.8.5/8.6.9) id EAA13595 for announce@freebsd.org; Thu, 8 May 1997 04:21:49 -0700 (PDT) Date: Thu, 8 May 1997 04:21:49 -0700 (PDT) From: "Jordan K. Hubbard" Message-Id: <199705081121.EAA13595@time.cdrom.com> To: announce@freebsd.org Subject: 3.0-970505-SNAP replaces 3.0-970502-SNAP on ftp.freebsd.org Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk No big problems with the previous 3.0 SNAPshot, but a problem with the package installer (which would hang the install at the very end) was preventing people from testing all the things I wanted tested and so a replacement SNAPshot was merited. I also took the opportunity to clean up some of the new /etc/rc.mechanism stuff in 3.0 and this is reflected in the newer SNAP. Apologies for the inconvenience, but this is also the SNAPshot which I'll be putting on CDROM (since why would I want to use a known-broken package installer and take tech support calls for it? :) and I wanted, as always, the network folks to have the same bits available. Thanks. Jordan 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 From owner-freebsd-announce Thu May 8 22:46:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12352 for freebsd-announce-outgoing; Thu, 8 May 1997 22:46:15 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12343 for ; Thu, 8 May 1997 22:46:12 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.5/8.8.5) with ESMTP id WAA25223 for ; Thu, 8 May 1997 22:46:11 -0700 (PDT) Message-Id: <199705090546.WAA25223@austin.polstra.com> To: freebsd-announce@freebsd.org Subject: Users of CVSup2.FreeBSD.ORG please read! Date: Thu, 08 May 1997 22:46:11 -0700 From: John Polstra Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk CVSup2.FreeBSD.ORG developed RAM problems beginning May 7, 1997. The problems have now been fixed, but while they lasted some file corruption occurred. This took the form of little 1-bit errors scattered through a number of files, including some served by CVSup. I have run MD5 checksums on the entire CVS repository both on freefall and on CVSup2. Here is a list of files which may have been corrupted: CVSROOT/commitlogs/gnu CVSROOT/commitlogs/ports CVSROOT/commitlogs/share CVSROOT/commitlogs/sys CVSROOT/commitlogs/usrsbin src/gnu/usr.bin/gdb/Attic/ChangeLog,v src/sys/i386/i386/math_emulate.c,v src/usr.sbin/ppp/lqr.c,v I have replaced the possibly-corrupted files with fresh copies from freefall, but people who did updates from CVSup2 during the past two days may have gotten bad copies. CVSup checksums all updated files, but it cannot detect errors that occur in RAM between the times when the program writes the data and the kernel flushes it to disk. If you ran a CVSup update from CVSup2 on May 7 or May 8, please delete the files listed above from your local repository, and do another update to replace them with known good versions. There is some chance that the RAM errors caused some files to go out corrupted even though the corruption didn't show up on disk. Unfortunately, there is no way of knowing whether that happened. The RAM has been replaced and CVSup2 is working fine again now. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth From owner-freebsd-announce Fri May 9 21:22:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA16184 for freebsd-announce-outgoing; Fri, 9 May 1997 21:22:02 -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 VAA16178; Fri, 9 May 1997 21:22:00 -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 VAA18080; Fri, 9 May 1997 21:22:09 -0700 (PDT) To: current@freebsd.org cc: announce@freebsd.org Subject: A 3.0-current SNAP building machine has been found! Date: Fri, 09 May 1997 21:22:09 -0700 Message-ID: <18077.863238129@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ACC TelEnterprises & James FitzGibbon have stepped forward and created, how shall I put it, a very *attractively* configured and connected machine for this purpose, complete with administrative support. Therefore, once I have it set up to start building SNAPs, I'll start up the cron job and have David G. point "current.freebsd.org" at this machine so that it people can ftp the latest 3.0-SNAPs from it in the same way they currently have releng22.freebsd.org for the RELENG_2_2 (2.2-stable) branch. Of course, this raises an interesting question: Now that it's truly possible to get daily releases from the 3.0 & 2.2 bits (and, if someone else is still up to volunteer a box, I guess we could also create a releng210.freebsd.org for the 2.1-stable branch?) - what differentiates a "good" one from a bad one? Which ones should we copy over to ftp.freebsd.org, periodically? I suppose that Terry will now suggest some sort of voting system and I can't even say that it's such a bad idea (just so long as I don't have to write the vote collection and tabulation software :-). Comments? Jordan