freebsd-update painfully slow - slower than source code build of world and kernel

[Christopher Arnold]

On Tue, 6 Jan 2009, Daniel Bond wrote:

> reading your answer, you are obviously confusing what I am saying about 
> freebsd-update with the portsnap program. Also, I also wrote in my first post 
>
No i'm not confusing them, just trying to follow two subjects at the same 
time. Sorry if that is confusing.

> that HTTP_PROXY / Caching proxy server does not help me much. This is because 
> I download a lot of "initial tarball snapshots".. I would rarely see "Cache 
> hits" in my proxy log. I guess I could set something up to fetch nightly via 
> proxy, to keep the data in house, for when I need it. I don't want to use a 
> PROXY server, I feel this is attacking the problem at the wrong end.
>
Ok, lets go again. Either you mirror (maybe by having a squid proxy and 
walk the tree) and thats going to me even worse for you. Or you use a squid 
proxy to keep stuff you need close to you and share among different 
installations.

Or you setup one or more national squid proxies and configure your 
machines manually just like you do with cvsup.



> I agree, I am interested to hear the views of the wise ones. Personally I'm 
> going back to CVSup until freebsd-update and portsnap mirrors are in a more 
> distributed or usable state.
>
At least portsnap started to work for me earlier today. Havn't tried 
update yet.

But yes i agree, update and portsnap infrastructure could be done better.
I have some ideas and will try to write them down in a while.

 	/Chris