From owner-freebsd-hubs Mon Apr 27 18:12:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26676 for freebsd-hubs-outgoing; Mon, 27 Apr 1998 18:12:31 -0700 (PDT) (envelope-from owner-freebsd-hubs@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 SAA26648 for ; Mon, 27 Apr 1998 18:12: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 SAA06427 for ; Mon, 27 Apr 1998 18:12:29 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: hubs@FreeBSD.ORG Subject: FreeBSD 2.2.5 release removed from ftp.freebsd.org Date: Mon, 27 Apr 1998 18:12:29 -0700 Message-ID: <6423.893725949@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We're at 93% utilization on that partition and we can free up a fair bit of space by elimintating 2.2.5 and its associated bits, so I'm going for it. With 2.2.6 in place, we still have a major release available for each branch and I think that's all anyone can expect of a perpetually space-crunched site like ftp.cdrom.com. I'll also update the 3.0 snap while I'm at it and eliminate the now-unnecessary 2.2.x-stuff directory (which I never liked). Anyway, heads up! Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Mon Apr 27 18:17:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28018 for freebsd-hubs-outgoing; Mon, 27 Apr 1998 18:17:09 -0700 (PDT) (envelope-from owner-freebsd-hubs@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 SAA27928 for ; Mon, 27 Apr 1998 18:17:01 -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 SAA06464 for ; Mon, 27 Apr 1998 18:17:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: hubs@FreeBSD.ORG Subject: Further note... Date: Mon, 27 Apr 1998 18:17:02 -0700 Message-ID: <6461.893726222@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ftp://ftp.freebsd.org/pub/FreeBSD/2.2.6-RELEASE/commerce has changed from a symlink to a directory and pub/FreeBSD/2.2.x-stuff eliminated. If your mirror script(s) get confused by events like this, please be sure and remove the old symlink by hand. Thanks! Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Tue Apr 28 16:30:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07683 for freebsd-hubs-outgoing; Tue, 28 Apr 1998 16:30:52 -0700 (PDT) (envelope-from owner-freebsd-hubs@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 QAA07667 for ; Tue, 28 Apr 1998 16:30:48 -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 QAA07150 for ; Tue, 28 Apr 1998 16:30:48 -0700 (PDT) (envelope-from jdp) Message-Id: <199804282330.QAA07150@austin.polstra.com> To: hubs@FreeBSD.ORG Subject: CVSup 15.4 is now available Date: Tue, 28 Apr 1998 16:30:48 -0700 From: John Polstra Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This release solves big problems introduced by the latest version of CVS. We are going to switch to the new CVS on freefall eventually, so hubs should upgrade without too much delay. Otherwise your users will start getting zillions of checksum mismatches. See below for more details. John 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 $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Wed Apr 29 06:13:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25102 for freebsd-hubs-outgoing; Wed, 29 Apr 1998 06:13:18 -0700 (PDT) (envelope-from owner-freebsd-hubs@FreeBSD.ORG) Received: from imap.ncsa.es (correo.nexus.es [194.179.50.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25091 for ; Wed, 29 Apr 1998 06:13:15 -0700 (PDT) (envelope-from jesusr@ncsa.es) Received: from jesus.nexus.es (piolin.ncsa.es [194.179.50.134]) by imap.ncsa.es (8.8.8/8.8.8) with SMTP id PAA13594 for ; Wed, 29 Apr 1998 15:33:39 +0200 (CEST) Reply-To: "Jesus Rodriguez" From: "Jesus Rodriguez" To: Subject: www mirroring and cvsup Date: Wed, 29 Apr 1998 15:16:01 +0200 Message-ID: <01bd7370$f47854a0$8632b3c2@jesus.nexus.es> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello... We are starting to mirroring freebsd in Spain (es.freebsd.org). In handbook says we have to "cvsuping" the www release=current... i'm trying this but i can't get any file... but if i get www release=cvs there is no problem and i get all .sgml web files. Do i need some special permission for getting the www release=current collection ? Please, reply directly to me, i'm not (yet) subscribed to this list. Thanks in advance. hostmaster@es.freebsd.org --------------------------------------------------------- Jesus Rodriguez (jesusr@ncsa.es) Dpto. Tecnico Nexus Comunicaciones, S.A. Telf. 902-466664 --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Wed Apr 29 23:14:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14894 for freebsd-hubs-outgoing; Wed, 29 Apr 1998 23:14:18 -0700 (PDT) (envelope-from owner-freebsd-hubs@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14821 for ; Wed, 29 Apr 1998 23:14:07 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id IAA20043; Thu, 30 Apr 1998 08:13:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id IAA00818; Thu, 30 Apr 1998 08:13:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199804300613.IAA00818@greenpeace.grondar.za> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jesus Rodriguez" cc: freebsd-hubs@FreeBSD.ORG Subject: Re: www mirroring and cvsup Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 30 Apr 1998 08:13:57 +0200 From: Mark Murray Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jesus Rodriguez" wrote: > Hello... > > We are starting to mirroring freebsd in Spain (es.freebsd.org). In handbook > says we have to "cvsuping" the www release=current... i'm trying this but i > can't get any file... but if i get www release=cvs there is no problem and i > get all .sgml web files. > Do i need some special permission for getting the www release=current > collection ? Here is the supfile that I use for the web pages. You may need permission from the FreeBSD folk to do this. www release=current host=freefall.freebsd.org hostbase=/home base=/usr/local/www prefix=/usr/local/www delete old use-rel-suffix compress M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Thu Apr 30 01:04:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28901 for freebsd-hubs-outgoing; Thu, 30 Apr 1998 01:04:31 -0700 (PDT) (envelope-from owner-freebsd-hubs@FreeBSD.ORG) Received: from imap.ncsa.es (correo.nexus.es [194.179.50.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28896 for ; Thu, 30 Apr 1998 01:04:28 -0700 (PDT) (envelope-from jesusr@ncsa.es) Received: from jesus.nexus.es (piolin.ncsa.es [194.179.50.134]) by imap.ncsa.es (8.8.8/8.8.8) with SMTP id KAA01040 for ; Thu, 30 Apr 1998 10:25:20 +0200 (CEST) Reply-To: "Jesus Rodriguez" From: "Jesus Rodriguez" To: Subject: Ftp mirror space Date: Thu, 30 Apr 1998 10:07:23 +0200 Message-ID: <01bd740f$0137af80$8632b3c2@jesus.nexus.es> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello... How many disk space do we need for mirroring ftp.freebsd.org ? Thanks in advance. --------------------------------------------------------- Jesus Rodriguez (jesusr@ncsa.es) Dpto. Tecnico Nexus Comunicaciones, S.A. Telf. 902-466664 --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Thu Apr 30 02:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA06934 for freebsd-hubs-outgoing; Thu, 30 Apr 1998 02:10:30 -0700 (PDT) (envelope-from owner-freebsd-hubs@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA06847 for ; Thu, 30 Apr 1998 02:10:13 -0700 (PDT) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.8.8/8.8.8) with ESMTP id LAA25069; Thu, 30 Apr 1998 11:10:09 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.8.8/8.8.8) with ESMTP id LAA01553; Thu, 30 Apr 1998 11:10:08 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199804300910.LAA01553@greenpeace.grondar.za> To: "Jesus Rodriguez" cc: hubs@FreeBSD.ORG Subject: Re: Ftp mirror space Date: Thu, 30 Apr 1998 11:10:07 +0200 From: Mark Murray Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jesus Rodriguez" wrote: > Hello... > > How many disk space do we need for mirroring ftp.freebsd.org ? Lots! Start with 4 gigs if you want it all. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Thu Apr 30 02:17:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08182 for freebsd-hubs-outgoing; Thu, 30 Apr 1998 02:17:37 -0700 (PDT) (envelope-from owner-freebsd-hubs@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 CAA08146 for ; Thu, 30 Apr 1998 02:17:22 -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 CAA14623; Thu, 30 Apr 1998 02:16:43 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Jesus Rodriguez" cc: hubs@FreeBSD.ORG Subject: Re: Ftp mirror space In-reply-to: Your message of "Thu, 30 Apr 1998 10:07:23 +0200." <01bd740f$0137af80$8632b3c2@jesus.nexus.es> Date: Thu, 30 Apr 1998 02:16:43 -0700 Message-ID: <14619.893927803@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello... > > How many disk space do we need for mirroring ftp.freebsd.org ? If you're interested in everything under the FreeBSD area, it's currently just a little over 6.6GB. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Thu Apr 30 08:47:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26838 for freebsd-hubs-outgoing; Thu, 30 Apr 1998 08:47:05 -0700 (PDT) (envelope-from owner-freebsd-hubs@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26822 for ; Thu, 30 Apr 1998 08:47:01 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.8.8/8.8.8) id LAA04422; Thu, 30 Apr 1998 11:46:49 -0400 (EDT) (envelope-from wollman) Date: Thu, 30 Apr 1998 11:46:49 -0400 (EDT) From: Garrett Wollman Message-Id: <199804301546.LAA04422@khavrinen.lcs.mit.edu> To: "Jesus Rodriguez" Cc: Subject: Ftp mirror space In-Reply-To: <01bd740f$0137af80$8632b3c2@jesus.nexus.es> References: <01bd740f$0137af80$8632b3c2@jesus.nexus.es> Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > How many disk space do we need for mirroring ftp.freebsd.org ? /dev/sd1s1c 4114229 2681454 1103637 71% /y /dev/sd2s1d 4309186 2913196 1051256 73% /y/ftp/pub/XFree86 This seems to be about the minimum (extracted sources and ports distfiles excluded). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message From owner-freebsd-hubs Thu Apr 30 08:51:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA27364 for freebsd-hubs-outgoing; Thu, 30 Apr 1998 08:51:36 -0700 (PDT) (envelope-from owner-freebsd-hubs@FreeBSD.ORG) Received: from burka.rdy.com (dima@burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA27358 for ; Thu, 30 Apr 1998 08:51:34 -0700 (PDT) (envelope-from dima@burka.rdy.com) Received: by burka.rdy.com id IAA14162; (8.8.8/RDY) Thu, 30 Apr 1998 08:50:41 -0700 (PDT) Message-Id: <199804301550.IAA14162@burka.rdy.com> Subject: Re: Ftp mirror space In-Reply-To: <199804300910.LAA01553@greenpeace.grondar.za> from Mark Murray at "Apr 30, 98 11:10:07 am" To: mark@grondar.za (Mark Murray) Date: Thu, 30 Apr 1998 08:50:41 -0700 (PDT) Cc: jesusr@ncsa.es, hubs@FreeBSD.ORG X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mark Murray writes: > "Jesus Rodriguez" wrote: > > Hello... > > > > How many disk space do we need for mirroring ftp.freebsd.org ? > > Lots! Start with 4 gigs if you want it all. It's not gonna be enough. /dev/ccd0h 8196347 5931438 1609202 79% /ccd And I'm not mirroring incoming directory and distfiles. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hubs" in the body of the message > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message