From owner-freebsd-announce Tue Apr 28 16:27:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07190 for freebsd-announce-outgoing; Tue, 28 Apr 1998 16:27:04 -0700 (PDT) (envelope-from owner-freebsd-announce@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07174 for ; Tue, 28 Apr 1998 16:27:00 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id QAA07120 for ; Tue, 28 Apr 1998 16:27:00 -0700 (PDT) (envelope-from jdp) Message-Id: <199804282327.QAA07120@austin.polstra.com> To: freebsd-announce@FreeBSD.ORG Subject: CVSup 15.4 is now available Date: Tue, 28 Apr 1998 16:27:00 -0700 From: John Polstra Sender: owner-freebsd-announce@FreeBSD.ORG Precedence: bulk Reply-To: postmaster@FreeBSD.ORG X-Loop: FreeBSD.org Announcing CVSup 15.4 --------------------- Release 15.4 of CVSup, the CVS-aware network distribution system, is now available. Where to Get CVSup ------------------ CVSup is free software. It is available from: ftp://ftp.FreeBSD.org/pub/FreeBSD/CVSup/ and from all of the many FreeBSD FTP mirrors. You can find a complete list of them in the FreeBSD Handbook at: http://www.freebsd.org/handbook/mirrors.html CVSup is also available from the author's FTP server: ftp://ftp.polstra.com/pub/FreeBSD/CVSup/ Please avoid this server if possible. It has a rather slow link to the Internet. Full sources as well as FreeBSD binaries are available: cvsup-bin-15.4.tar.gz FreeBSD static binaries for the client + GUI cvsup.nogui-bin-15.4.tar.gz FreeBSD static binaries for the client (no GUI) cvsupd-bin-15.4.tar.gz FreeBSD static binaries for the server cvsup-15.4.tar.gz Sources ** The MD5 file signatures for these files are: MD5 (cvsup-bin-15.4.tar.gz) = aa4159387da988097ab5e7b5a164a93a MD5 (cvsup.nogui-bin-15.4.tar.gz) = 03b9f5013097437a34070b0abe8f3ba9 MD5 (cvsupd-bin-15.4.tar.gz) = 5643802465ec683c3929d006bc95b5e9 MD5 (cvsup-15.4.tar.gz) = 195b4b1cfb7db6d1fefbb4a9c9c27991 An updated port will appear in the FreeBSD ports and packages collections soon: Ports: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports-current/net/cvsup/ ftp://ftp.FreeBSD.org/pub/FreeBSD/ports-current/net/cvsup-bin/ Packages: For FreeBSD-current: ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-current/net/cvsup-15.4.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-current/net/cvsup-bin-15.4.tgz For FreeBSD-2.2: ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-stable/net/cvsup-15.4.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-stable/net/cvsup-bin-15.4.tgz If you want SOCKS support, you must also install the "modula-3-socks" port or package: Port: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports-current/lang/modula-3-socks/ Packages: ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-current/lang/modula-3-socks-1.0.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/packages-stable/lang/modula-3-socks-1.0.tgz SOCKS is supported only under FreeBSD, and only with dynamically linked executables. The static binary distributions do not support SOCKS. ** If you wish to build CVSup from the sources, be sure to read the discussion further on in this announcement. Why a New Release So Soon?? --------------------------- You may have noticed that this release comes rather soon after the release of CVSup 15.3. Unfortunately, around the same time that I released 15.3, the maintainers of CVS released a new version of their own software. The new version of CVS introduced some unfortunate changes in the whitespace conventions for the RCS files that it generates. CVSup updates RCS files by disassembling them on the server, and putting the pieces back together again on the client. The whitespace changes caused by the new version of CVS meant that CVSup's reconstructed RCS files no longer matched the originals exactly. Logically, they were identical in every way; but differences in the whitespace caused their MD5 checksums to disagree. This led to "fixups," which slowed down updates considerably. To solve this problem once and for all, I have introduced a new "loose" checksum in the current version. It is used only for RCS files. It is essentially still an MD5 checksum of the file. But it carefully canonicalizes the white space, such that harmless white space differences (an only the harmless ones) do not affect the checksum. Thus it checksums the meaning of the RCS file, rather than the particular rendition of it. For those who truly want their RCS files to be byte-for-byte identical to those on the server, I have also added a couple of new supfile keywords to help accomplish that, at some cost in update times. See the list of changes below and the man pages for details. Compatibility with Previous Releases ------------------------------------ This version is believed to interoperate properly with all earlier public releases of CVSup. What Has Changed Since the Previous Release? -------------------------------------------- Implemented a "loose" checksumming algorithm for verifying updated RCS files. The algorithm is still basically MD5, but it carefully ignores harmless differences (and only harmless differences) in white space. Thus two RCS files which are logically the same will have identical checksums, even if they have meaningless differences in white space. This change was made necessary by recent new versions of CVS, which introduced some gratuitous changes in the white space conventions for RCS files. Since CVSup updates RCS files by disassembling them on the server and putting them together again on the client, the changes in the conventions for white space led to spurious checksum mismatches under the old, strict checksum. Note: Loose checksums require both the client and server to be at version 15.4 or later. If either is older, then strict checksums are still used. Added a "strictrcs" supfile keyword, for those who don't trust the loose checksums. It causes strict byte-by-byte checksums to be used for RCS files, as was the default in older versions of CVSup. Implemented a "nocheckrcs" keyword for client supfiles and server "releases" files, to suppress the comparison of MD5 checksums for updated RCS files entirely. Given the new loose checksumming algorithm, this option is probably not very useful. Implemented a "norcs" keyword for client supfiles and server "releases" files, to disable the usual algorithm for updating RCS files. If this keyword is specified, RCS files are treated the same as other kinds of files. You can use this to force RCS files to be updated using the rsync algorithm, for instance. Fixed things up so that file names containing white space or other obnoxious characters no longer cause problems. Also, when a release 15.4 or later server or client is connected to an older peer, it is careful not to mention any files whose names contain white space. What Is CVSup? -------------- CVSup is a software package for distributing and updating collections of files across a network. CVSup is specifically tailored to distributing CVS repositories. By taking advantage of the special properties of the files contained in CVS repositories, CVSup is able to perform updates much faster than traditional systems. It is especially valuable for people with slow Internet connections. CVSup parses and understands the RCS files making up a CVS repository. When updates occur, CVSup extracts new deltas directly from the RCS files on the server and edits them into the client's RCS files. Likewise, CVSup notes the addition of new symbolic tags to the files on the server and sends only the new tags to the client. CVSup is able to merge new deltas and tags from the server with deltas and tags added locally on the client machine. This makes it possible for the client to check local modifications into his repository without their being obliterated by subsequent updates from the server. Note: Although this feature is fully implemented in CVSup, it will probably not be practical to use it until some small changes have been made to CVS. In addition to distributing the RCS files themselves, CVSup is able to distribute specific checked-out versions. The client can specify a symbolic tag, a date, or both and CVSup will extract the appropriate versions from the server's CVS repository. Checked-out versions do not need to be stored on the server since CVSup can extract any version directly from the CVS repository. If the client has an existing checked-out tree, CVSup will apply the appropriate edits to update the tree or transform it into the requested version. Only the differences between the existing version and the desired version are sent across the network. To update non-RCS files, CVSup uses the highly efficient rsync algorithm, developed by Andrew Tridgell and Paul Mackerras. CVSup uses lightweight processes (threads) to implement a streaming protocol across the network. This completely eliminates the delays associated with the lock-step, request-reply form of communication used by many existing protocols, such as sup and NNTP. Information is transferred at the full available speed of the network in both directions at once. Network latency and server response delays are rendered practically irrelevant. CVSup uses the "zlib" compression package to optionally compress all communications. This provides an additional 65-75% compression, on top of the diff-based compression already built into CVSup. For efficiency, all processing is built into the CVSup package itself. Neither the client nor the server executes any other programs. For further information about how CVSup works, see the (somewhat out of date) "Blurb" document in the CVSup distribution. Using CVSup to Maintain FreeBSD Sources --------------------------------------- CVSup servers are currently running at about 20 mirror sites around the world. For an up-to-date list of them, see: http://www.freebsd.org/handbook/mirrors-cvsup.html Using CVSup, you can easily receive or update any of the standard FreeBSD source releases, namely, "cvs", "current", and "stable". The manual page for cvsup(1) describes how to do that. For more detailed instructions, see the section on CVSup in the FreeBSD Handbook: http://www.FreeBSD.org/handbook/cvsup.html Building CVSup from the Sources ------------------------------- CVSup is written in Modula-3, a modern, compiled, object-oriented language. Modula-3 integrates threads, exceptions, and garbage collection, providing an ideal vehicle for this sort of application. Without Modula-3, CVSup would almost certainly not exist today. If you wish to build CVSup from the sources, you will first need to install the free Modula-3 compiler and runtime libraries from DEC SRC. A port is available in the FreeBSD ports collection, in "lang/modula-3". The corresponding package is, of course, available in the packages collection. You will also need version 1.0.4 or later of the "zlib" library. In FreeBSD-2.1.6 and later releases, this library has been incorporated into the system sources, in "src/lib/libz". Prior to that, a FreeBSD port was available in "devel/libz" of the FreeBSD ports collection. For other sources of this library, see the "Install" file. Do not try to use versions earlier than 1.0.4. To build the entire system from source under FreeBSD, simply type "make" in the top-level directory. (That's the directory that has sub-directories named "client" and "server", among others.) To force the executables to be statically linked, set the environment variable "M3FLAGS" to "-DSTATIC". To build the client without the GUI (e.g., if you don't have the X Window System installed on your machine), set it to "-DNOGUI". To do both of these things, set the environment variable to "-DSTATIC -DNOGUI". The Makefiles should work on any reasonable Unix system. If you have trouble with them, it is easy to build the components manually. Simply chdir into each of the following subdirectories in the given order and type "m3build": suptcp suplib client server To build statically linked executables, add "-DSTATIC" to each "m3build" command. To build the client without the GUI (e.g., if you don't have the X Window System installed on your machine) add "-DNOGUI". Portability Issues ------------------ I intend for CVSup to be portable to most POSIX systems. Earlier releases have been run on a number of different platforms, including FreeBSD, Linux, HP-UX, SunOS, Solaris, and DEC OSF/1 ALPHA. In the current release I have attempted to increase rather than decrease portability. Anybody who succeeds in porting CVSup to other systems is encouraged to send his changes to . As long as the changes are reasonably palatable, they will be incorporated into future CVSup releases. CVSup uses several POSIX-specific functions which may make it more of an effort to port the package to non-POSIX systems such as Win32. These functions include mmap, fork, syslog, stat, and chmod, among others. Status of this Release ---------------------- CVSup was first released publicly in August of 1996. Since then it has seen heavy use, and it has been quite stable. Like all software, though, it is not perfect. Please be prepared to find bugs -- without a doubt, there are some. Please report bugs to . John Polstra, Copyright 1996-1998 John D. Polstra $Id: Announce,v 1.37 1998/04/28 21:33:14 jdp Exp $ This is the moderated mailing list freebsd-announce. The list contains announcements of new FreeBSD capabilities, important events and project milestones. See also the FreeBSD Web pages at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-announce" in the body of the message From owner-freebsd-announce Thu Apr 30 06:40:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11084 for freebsd-announce-outgoing; Thu, 30 Apr 1998 06:40:34 -0700 (PDT) (envelope-from owner-freebsd-announce@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11076 for ; Thu, 30 Apr 1998 06:40:28 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id GAA21455 for ; Thu, 30 Apr 1998 06:40:05 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: announce@FreeBSD.ORG Subject: Anonymous CVS access now available from anoncvs.freebsd.org Date: Thu, 30 Apr 1998 06:40:03 -0700 Message-ID: <21450.893943603@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-announce@FreeBSD.ORG Precedence: bulk Reply-To: postmaster@FreeBSD.ORG X-Loop: FreeBSD.org Please see: http://www.freebsd.org/handbook/anoncvs.html For full information on using ``anoncvs'' to fetch FreeBSD CVS repository (or buildable source) bits. If you're also interested in setting up your own regional AnonCVS server, please see: ftp://ftp.freebsd.org/pub/FreeBSD/FreeBSD-CVS/anoncvs.shar For some setup instructions on doing this (essentially the list of steps I followed in creating this first server along with the special bits you'll need). That is all! Jordan This is the moderated mailing list freebsd-announce. The list contains announcements of new FreeBSD capabilities, important events and project milestones. See also the FreeBSD Web pages at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-announce" in the body of the message From owner-freebsd-announce Fri May 1 10:54:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20920 for freebsd-announce-outgoing; Fri, 1 May 1998 10:54:12 -0700 (PDT) (envelope-from owner-freebsd-announce@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20848 for announce; Fri, 1 May 1998 10:54:09 -0700 (PDT) (envelope-from jmb) From: "Jonathan M. Bresler" Message-Id: <199805011754.KAA20848@hub.freebsd.org> Subject: FreeBSD-Net: new technical mailing list To: announce Date: Fri, 1 May 1998 10:54:08 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-announce@FreeBSD.ORG Precedence: bulk Reply-To: postmaster@FreeBSD.ORG X-Loop: FreeBSD.org FreeBSD-Net is a new mailing list dedicated to networking and TCP/IP source code discussions. questions should be directed to FreeBSD-questions...as usual. this list is for technical discussions only. to subscribe to a FreeBSD mailing list, send mail to majordomo@FreeBSD.org containing the single line "subscribe ". replace by the name of the list you want to subscribe to. to subscribe use: echo "subscribe freebsd-net" | mail majordomo@FreeBSD.org to unsubscribe use: echo "unsubscribe freebsd-net" | mail majordomo@FreeBSD.org you will be asked, via email, to confirm your subscription request via email. after confirming your subscription request, you will receive notification, via email, that your subscription has been accepted. jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB This is the moderated mailing list freebsd-announce. The list contains announcements of new FreeBSD capabilities, important events and project milestones. See also the FreeBSD Web pages at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-announce" in the body of the message From owner-freebsd-announce Sat May 2 04:21:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08423 for freebsd-announce-outgoing; Sat, 2 May 1998 04:21:06 -0700 (PDT) (envelope-from owner-freebsd-announce@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08417 for ; Sat, 2 May 1998 04:21:05 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id EAA10929; Sat, 2 May 1998 04:20:44 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: Josef Karthauser cc: announce@FreeBSD.ORG Subject: Re: Anonymous CVS access now available from anoncvs.freebsd.org In-reply-to: Your message of "Sat, 02 May 1998 11:39:20 BST." <19980502113920.35240@pavilion.net> Date: Sat, 02 May 1998 04:20:44 -0700 Message-ID: <10925.894108044@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-announce@FreeBSD.ORG Precedence: bulk Reply-To: postmaster@FreeBSD.ORG X-Loop: FreeBSD.org > Hi Jordan, > > I'd like to set one of these up on the UK. A few questions for you then. > > > extract----> > > core# echo $CVSROOT > anoncvs@anoncvs.freebsd.org:/cvs > core# rm -r CVS > core# ls > COPYRIGHT eBones/ kerberosIV/ sbin/ usr.bin/ > Makefile etc/ lib/ secure/ usr.sbin/ > README games/ libexec/ share/ > bin/ gnu/ lkm/ sys/ > contrib/ include/ release/ tools/ > core# cvs log README > select: protocol failure in circuit setup > cvs [log aborted]: end of file from server (consult above messages if any) Hmmm. root@orange-> setenv CVSROOT anoncvs@anoncvs.freebsd.org:/cvs root@orange-> cvs co ls cvs server: Updating ls U ls/Makefile U ls/cmp.c U ls/extern.h U ls/ls.1 U ls/ls.c U ls/ls.h U ls/print.c U ls/stat_flags.c U ls/util.c root@orange-> cd ls root@orange-> cvs log Makefile RCS file: /cvs/src/bin/ls/Makefile,v Working file: Makefile head: 1.4 branch: locks: strict access list: symbolic names: RELENG_2_2_6_RELEASE: 1.2 RELENG_2_2_5_RELEASE: 1.2 bsd_44_lite_2: 1.1.1.1 ... Works for me? > Have you really exported a rsh service from your server? That doesn't sound Yes. > good. The README file in the anoncvssh.shar file hints about a 'pserver' > way of doing it, which I'd prefer. Hints, yes, but the original didn't say how to actually set up the pserver stuff. If you know how to do this, I'm all ears. :) > Also, can I can slave anoncvs off the same cvs tree that > cvs.uk.freebsd.org uses? (I'm intending to run anoncvs off the same machine. Yep. - Jordan This is the moderated mailing list freebsd-announce. The list contains announcements of new FreeBSD capabilities, important events and project milestones. See also the FreeBSD Web pages at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-announce" in the body of the message From owner-freebsd-announce Sat May 2 09:27:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15113 for freebsd-announce-outgoing; Sat, 2 May 1998 09:27:49 -0700 (PDT) (envelope-from owner-freebsd-announce@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15104; Sat, 2 May 1998 09:27:46 -0700 (PDT) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA17526; Sat, 2 May 1998 10:27:40 -0600 (MDT) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA17956; Sat, 2 May 1998 10:27:37 -0600 Date: Sat, 2 May 1998 10:27:37 -0600 Message-Id: <199805021627.KAA17956@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: jkh@FreeBSD.ORG Cc: Josef Karthauser , announce@FreeBSD.ORG Subject: Re: Anonymous CVS access now available from anoncvs.freebsd.org In-Reply-To: <10925.894108044@time.cdrom.com> References: <19980502113920.35240@pavilion.net> <10925.894108044@time.cdrom.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-announce@FreeBSD.ORG Precedence: bulk Reply-To: postmaster@FreeBSD.ORG X-Loop: FreeBSD.org > > good. The README file in the anoncvssh.shar file hints about a 'pserver' > > way of doing it, which I'd prefer. > > Hints, yes, but the original didn't say how to actually set up the > pserver stuff. If you know how to do this, I'm all ears. :) If you're serious, all my CVS boxes use PSERVER mode up here. Nate This is the moderated mailing list freebsd-announce. The list contains announcements of new FreeBSD capabilities, important events and project milestones. See also the FreeBSD Web pages at http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-announce" in the body of the message