apt-mirror vs debmirror and mirror size
I've recently inherited the admin of a group of Ubuntu servers (12.04 LTS), including a local mirror server. This is using a script to update itself with debmirror. What are the relative pros and cons of debmirror over apt-mirror? My previous Linux experience is limited: we are a mainly Windows site and I got assigned this because I've looked after one or two Solaris boxes in the past!
Also, I'm wanting to add 14.04 LTS to the mirror. Is there any way to work out what volume of storage I'll need for the two releases?
Thanks.
1 Answer
I don't think there is much difference. But instead take a look at apt-cacher-ng for an alternative way of doing mostly the same thing, with less work for you and less bandwidth waste.
deb/apt-mirror blindly copies all files (even if some are never used) from the distro/architecture/version you specify, periodically according to cron, etc.
But apt-cacher-ng is passive. When some user pulls a package, that package remains in your server for the next person. Similar to squid, unless there is a newer version online which then gets pulled and also kept.
And it happens to work with all apt distros just fine without you doing any extra work or adding anything else, third party repositories and ppas they all get stored (cached) in your server.
For your users to use apt-cacher-ng they only need to add a proxy to their apt configuration, instead of using a local mirror.
3
