Thank you. I've thought about putting a switch and an old server on the internet side of lmce and caching there - is that how you do it? Do you have a recipe that folks can follow?thanks,joseph

That's exactly what I've done. Keep in mind that this is not supported. It works for me and has significantly reduced bandwidth usage while speeding up installation of lmce or any ubuntu/debian based distro you use regularly.

I have an old pc I use for various purposes that sits on the internet side of the lmce core. It's running Ubuntu 8.10 and I installed apt-cacher-ng on it using aptitude.

Then when I install lmce on my core I follow the instructions on the wiki for installing the Alpha, except that before I execute the pre-install-from-repo.sh script I make a minor modification to the pre-install-common.sh script. The line I change is:

I change the word localhost and put the IP of my outside server instead. I save the modified script and proceed to run the pre-install-from-repo.sh script to begin the lmce installation.

The first time you install after performing these steps will take the same length of time it always has. On subsequent installations any unchanged packages will be grabbed from your cache rather than the lmce repository.

90-95% of the lmce install now uses the cache on my outside server rather than the lmce repository. All repository downloads go through the outside server and only new/changed/updated packages are fetched from the lmce repository whenever aptitude/apt-get are used. All of my mds automatically use my outside server's repository cache as well with this method.

as I was the only dev who posted in this thread, this must imply, that I "browbeat" the initial poster.

I really can't see, what I did, to imply anything like that.

Actually, I don't think I said or implied any dev browbeat anyone in this thread. If so, it was unintended. In fact, I specifically tried to not single out any devs or the devs in general. Just for the record I thought your posts were helpful.

Quote

And, I do like the posted calculation. We will have a beta by that date. Latest. Promise!

1. my understanding is that the apt-catcher server does not have to be a gateway / router. That is, it can just sit off a switch between the internet / external firewall / router and the core / dcerouter and traffic does not have to pass through it. Is that correct?

1. my understanding is that the apt-catcher server does not have to be a gateway / router. That is, it can just sit off a switch between the internet / external firewall / router and the core / dcerouter and traffic does not have to pass through it. Is that correct?

Correct.

Quote

2. do you change your repo lists to point to the apt-catcher server?

No repository changes. The file /etc/apt/apt.conf.d/02proxy (created during the 'pre-install-from-repo.sh' portion of the lmce install) tells aptitude where to find the cache. The cache acts as a proxy. Leave your sources.list file alone.