Date: Mon, 29 Nov 1999 07:35:10 -0500 From: Carl Harris <ceharris@cns.vt.edu> To: freebsd-stable@freebsd.org Subject: Re: Bug-fixing previous -RELEASE, was Re: speaking of 3.4... Message-ID: <19991129073510.A23669@thumper.cns.vt.edu> In-Reply-To: <19991128103420.A95893@phoenix.welearn.com.au>; from jon@welearn.com.au on Sun, Nov 28, 1999 at 10:34:22AM %2B1100 References: <Pine.BSF.3.96.991126130751.29031A-100000@workhorse.iMach.com> <Pine.BSF.4.21.9911261234460.66714-100000@hub.freebsd.org> <19991128103420.A95893@phoenix.welearn.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 28, 1999 at 10:34:22AM +1100, Jonathan Michaels wrote: > things. to go on .. the impression i got from the original > question is that this person (me and others i dare with rather > limited resources as well) might find the traffic some what > financially trying, given most f the rest of the world still > charges internet access by the byte as well as by the minute. > tracking the whole tree could run up a tidy bill, not a real > probelm for those in the trade so to speak but us "hangers on". I have quite limited resources, and pay per-minute charges to my ISP, yet I find that tracking -STABLE with cvsup is not especially burdensome, financially or otherwise. I use a 56K modem to connect to my ISP. cvsup seems involve quite a bit of data flowing from my machine to the cvsup server. Since the back channel of a 56K modem tops out at 33.6 Kbps, this will increase the time it takes to complete the update. I track all of the src-* collections plus ports-all. Typically, I run an update every day, and it takes five to seven minutes to complete the run. Even on days when there are many deltas applied to my copy of the tree, the time required doesn't change significantly (i.e. much of the time is spent in overhead activities that don't vary with the number of deltas). Curiously, I notice that it doesn't run significantly faster on our systems in the office, which have several orders of magnitude greater bandwidth at their disposal. This suggests that network bandwidth isn't really a significant issue WRT the time required to complete the update, which sorta makes sense if the cvsup server has a lot of work on its hands. FWIW, I started tracking -STABLE with the same trepidation about applying all of those changes willy-nilly, without regard for whether I need them or not. The reality is that there really aren't all that many deltas in the src-* collections on a day-to-day basis (relative to the number of changes to ports-all!). After many, many iterations of 'make world' and 'make depend kernel install', I've never had a serious problem as a result of a change committed to -STABLE. --c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991129073510.A23669>