From owner-freebsd-announce Mon Nov 4 01:08:46 1996 Return-Path: owner-freebsd-announce Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA14333 for freebsd-announce-outgoing; Mon, 4 Nov 1996 01:08:46 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA14320 for ; Mon, 4 Nov 1996 01:08:42 -0800 (PST) Received: (from jkh@localhost) by time.cdrom.com (8.7.6/8.6.9) id BAA00352 for announce@freebsd.org; Mon, 4 Nov 1996 01:08:41 -0800 (PST) Date: Mon, 4 Nov 1996 01:08:41 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <199611040908.BAA00352@time.cdrom.com> To: announce@freebsd.org Subject: FreeBSD branch changes. Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Lieber FreeBSD user, This is a public-service announcement for those who keep an eye on our development process but do not subscribe to the hackers@FreeBSD.ORG mailing list (a very high-volume list, so this is understandable). FreeBSD's development stream has, as of November 3rd, branched into the 2.2-RELEASE and 3.0-CURRENT development streams. The 2.1-STABLE branch is also still alive, soon to terminate (for real, this time) with the impending release of FreeBSD 2.1.6. This branch has occurred so that 2.2 may be readied for release without impacting significant new developments, like SMP support, in the mainstream -current branch. As this implies, the release of 2.2 is also imminent. Here, modulo any of the usual two-week slips here and there, is our release schedule for 96/97: December 1996: FreeBSD 2.1.6 RELEASE. End of 2.1-STABLE branch. January 1997: FreeBSD 2.2 RELEASE. Beginning of 2.2-STABLE. Spring 1997: FreeBSD 2.2.x RELEASE. Bugfix release for 2.2R This is also probably as good a time as any to announce that new XFree86 3.2 binaries, with early Matrox support, are available at ftp://ftp.freebsd.org/pub/FreeBSD/XFree86/2.2-CURRENT/XF8632/ Thanks to the XFree86 project for the timely binaries, which will be distributed with 2.2-RELEASE (2.1.6 binaries are still pending but should be available before that release). Lest there be any confusion about the 2.1.6 and 2.2 releases coming so close together, let me also just explain that the two branches of development had really very little to do with one another, and the fact that both branches came to release status around the same time was simply how the scheduling worked out. When engineering is allowed to do the scheduling, it rarely employs traditional marketing strategems. :) In summary: 2.1.6-RELEASE is aimed squarely at commercial users who don't need to be on the leading edge of development but favor things like stability and a long test-cycle instead. 2.1-STABLE has had only incremental refinements made to it since 2.1.5 was released, and 2.1.6 will end what we feel to have been a very successful branch. 2.2-RELEASE will begin introducing the more leading edge technologies we've been developing over the year that -stable has run in parallel, and will also be entering bug-fix mode after its release. Existing -stable customers will be encouraged to make the jump to 2.2-STABLE some time after 2.2's release, once the first round of customer PRs have come back and been acted on. 3.0-CURRENT is now the bleeding edge of development, and where all new development takes place. Until code freeze on the 10th of November, changes may also be marked "For 2.2-RELEASE" and they will be brought into that branch as necessary. After code freeze, it will have to be a clearly important bug fix to make it in before the release date. Many significant changes are planned for 3.0, and those interested in its development should subscribe to the freebsd-current mailing list (send mail to majordomo@freebsd.org). As always, *all* branches of FreeBSD development are available from a single CVS repository which may be freely replicated to your own machine (see http://www.freebsd.org/handbook) or browsed via the web at http://www.freebsd.org/cgi-bin/cvsweb Please don't hesitate to use this valuable resource! As always, Jordan for The FreeBSD Core Team. From owner-freebsd-announce Tue Nov 5 03:27:37 1996 Return-Path: owner-freebsd-announce Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA26219 for freebsd-announce-outgoing; Tue, 5 Nov 1996 03:27:37 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id DAA26213 for freebsd-announce@FreeBSD.ORG; Tue, 5 Nov 1996 03:27:34 -0800 (PST) Date: Tue, 5 Nov 1996 03:27:34 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199611051127.DAA26213@freefall.freebsd.org> To: freebsd-announce@FreeBSD.ORG Subject: CVSup users PLEASE READ Sender: owner-freebsd-announce@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk A few people have been experiencing hangs and/or premature EOFs from the server with CVSup 13.5. The problem is caused by an incompatible mix of Modula-3 shared libraries and header files. I inadvertently made it possible for this to happen during a brief window when I split the shared libraries into a separate "modula-3-lib" port. This problem does not affect people who installed the "cvsup-13.5" (binary) package. Here is the scenario under which you might encounter the problems: * You already had Modula-3 installed on your system. * You built CVSup 13.5 from the port (i.e., from source). * Building the CVSup port caused the new "modula-3-lib" port to get built and installed, but it did not cause the latest version of the "modula-3" port to get built and installed. Under this scenario, your CVSup port got built with a new set of shared libraries, but an old set of header files. Here is another indication that you are probably affected by this problem: * The file "/usr/local/lib/m3/FreeBSD/libm3.so.4.0" exists on your system. * The file "/usr/local/bin/m3build-4" does _not_ exist on your system. If you think you've been hit by this problem, you can fix it like this: * pkg_delete your "cvsup", "modula-3", and "modula-3-lib" packages (use "pkg_info -ac" to see which versions are installed). * Make sure these three ports are up to date in your ports tree. * Rebuild and install the "cvsup" port. (It will cause the other two ports to be rebuilt and installed too.) I apologize for causing this problem. I have fixed the ports so that it shouldn't happen any more. The time window during which the ports were wrong was from 10/29/96 23:14 GMT until 11/1/96 20:27 GMT. Thanks to Satoshi Asami for first noticing the problem, and to James FitzGibbon for helping me confirm the cause of it. -- 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 Tue Nov 5 20:26:11 1996 Return-Path: owner-freebsd-announce Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA14638 for freebsd-announce-outgoing; Tue, 5 Nov 1996 20:26:11 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA14631 for ; Tue, 5 Nov 1996 20:26:06 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.2/8.6.9) with ESMTP id UAA16586; Tue, 5 Nov 1996 20:26:01 -0800 (PST) To: "Paul T. Root" Cc: announce@freebsd.org Subject: Re: FreeBSD branch changes. In-reply-to: Your message of "Tue, 05 Nov 1996 21:18:10 CST." <199611060318.VAA04170@horton.iaces.com> Date: Tue, 05 Nov 1996 20:26:01 -0800 Message-ID: <16583.847254361@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > [Paul T. Root writes] > > Any word on what Walnut Creek is going to do? Just 2.2 or both. And if > both, what about subscriptions. I don't think I need both sets of > CD's. Do I? That was a question we wrestled with, my wanting to make both CD releases full 2-CD sets. The alternative would have been to do one as a release and one as a SNAP, but then 2.2R would have been shipped on only one CD and been somewhat less functional as a result, and I didn't like that. Our final compromise was that we would do both as release CDs, with those customers who feel they got one or the other in error being encouraged to contact us for a credit towards a free copy of the release to follow, no questions asked. Either way, it should work out. Jordan From owner-freebsd-announce Wed Nov 6 00:22:11 1996 Return-Path: owner-freebsd-announce Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA29432 for freebsd-announce-outgoing; Wed, 6 Nov 1996 00:22:11 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA29427 for ; Wed, 6 Nov 1996 00:22:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id AAA00374 for ; Wed, 6 Nov 1996 00:20:41 -0800 (PST) Message-Id: <199611060820.AAA00374@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: announce@freebsd.org Subject: SUP on sup.freebsd.org From: David Greenman Date: Wed, 06 Nov 1996 00:20:41 -0800 Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello everyone. If you're still doing SUP from sup.freebsd.org, please be aware that it was necessary to significantly cut back the number of simultaneous SUPers yesterday due to the extremely high load that it was putting on Walnut Creek's T1 (coupled with some other stuff was making it almost unusable). In fact it's been shut off completely until just a few minutes ago. We've been telling people for months to convert to CVSup, and now we really mean it! We'll continue to provide limited SUP service on sup.freebsd.org (freefall) for at least another week or two, but at some point the service will be discontinued completely. So please switch to using CVSup. It has much lighter network load and is quite a bit faster as well. Thanks, and sorry for the short notice, but the load problem had reached critical and something had to be done immediately. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-announce Wed Nov 6 23:41:10 1996 Return-Path: owner-freebsd-announce Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA09024 for freebsd-announce-outgoing; Wed, 6 Nov 1996 23:41:10 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA09018 for ; Wed, 6 Nov 1996 23:41:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id XAA02856 for ; Wed, 6 Nov 1996 23:39:34 -0800 (PST) Message-Id: <199611070739.XAA02856@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: announce@freebsd.org Subject: addendum on SUP and sup.freebsd.org From: David Greenman Date: Wed, 06 Nov 1996 23:39:34 -0800 Sender: owner-freebsd-announce@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It's clear from the amount of hate mail sitting in my mailbox this morning that I inadvertantly forgot to mention/clarify one important thing in my announcement about SUP service from sup.freebsd.org being discontinued: THIS ONLY AFFECTS SUP.FREEBSD.ORG (FREEFALL)!!! It does *not* affect the other sup.freebsd.org providers of the SUP service. It *only* pertains to the service being provided from freefall. I fully expect (and always intended) for the SUP service to be continued on the SUP "mirrors". I should have made that clear (it was obvious to me, however :-)) in my announcement. Sorry about that. It's been rumored that some of the sup.freebsd.org sites don't have complete collections or are way out of date. If you find this to be the case, please complain so that the site maintainer(s) know about it and can fix it. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project