Hi,
I've been using Debian for a few years, and there was one nifty little app that made installing and updating so much easier: apt-proxy.
Most of the time, I'm taking care of small LANs with an average of five client PCs. But this is a very remote place in South France, so most villages only have 512 kbps DSL. One major update for openoffice.org-*, and I have to wait the whole day for updating each machine (unless I scp -r /var/cache/yum from machine to machine, but that's another story).
I'm currently testing an "intermediate" solution: creating a local Yum repository. I have [base], which consists of all the 5.1 RPMS copied over from the DVD. Then [updates], which I'm currently rsyncing from a remote mirror. And I think I'll do something similar with [extra], which only leaves [rpmforge] (but I won't cache that :oD). Not a very satisfying solution, since for example I'm currently installing XFCE as only desktop environment, and I have nevertheless to download every GNOME- and KDE-related update.
A message to the developers: yum-proxy would be a much-needed addition to Yum, in my humble opinion. I don't have the technical skills to develop such a thing, but maybe one of you has (Daniel, do you read this? :oD)
I'm curious about your comments on this.
Cheers,
Niki
Niki Kovacs ha scritto:
Hi,
I've been using Debian for a few years, and there was one nifty little app that made installing and updating so much easier: apt-proxy.
Most of the time, I'm taking care of small LANs with an average of five client PCs. But this is a very remote place in South France, so most villages only have 512 kbps DSL. One major update for openoffice.org-*, and I have to wait the whole day for updating each machine (unless I scp -r /var/cache/yum from machine to machine, but that's another story).
I'm currently testing an "intermediate" solution: creating a local Yum repository. I have [base], which consists of all the 5.1 RPMS copied over from the DVD. Then [updates], which I'm currently rsyncing from a remote mirror. And I think I'll do something similar with [extra], which only leaves [rpmforge] (but I won't cache that :oD). Not a very satisfying solution, since for example I'm currently installing XFCE as only desktop environment, and I have nevertheless to download every GNOME- and KDE-related update.
A message to the developers: yum-proxy would be a much-needed addition to Yum, in my humble opinion. I don't have the technical skills to develop such a thing, but maybe one of you has (Daniel, do you read this? :oD)
I'm curious about your comments on this.
Cheers,
Niki
I also need such a thing... I'm on the process to have a friend of mine write a patch to http-replicator so that it can work as a proxy for rpm files.
Stay tuned, shortly, I hope, I'll have some news.
Regards
Lorenzo Quatrini
Lorenzo Quatrini wrote:
I've been using Debian for a few years, and there was one nifty little app that made installing and updating so much easier: apt-proxy.
Most of the time, I'm taking care of small LANs with an average of five client PCs. But this is a very remote place in South France, so most villages only have 512 kbps DSL. One major update for openoffice.org-*, and I have to wait the whole day for updating each machine (unless I scp -r /var/cache/yum from machine to machine, but that's another story).
I'm currently testing an "intermediate" solution: creating a local Yum repository. I have [base], which consists of all the 5.1 RPMS copied over from the DVD. Then [updates], which I'm currently rsyncing from a remote mirror. And I think I'll do something similar with [extra], which only leaves [rpmforge] (but I won't cache that :oD). Not a very satisfying solution, since for example I'm currently installing XFCE as only desktop environment, and I have nevertheless to download every GNOME- and KDE-related update.
A message to the developers: yum-proxy would be a much-needed addition to Yum, in my humble opinion. I don't have the technical skills to develop such a thing, but maybe one of you has (Daniel, do you read this? :oD)
I'm curious about your comments on this.
Cheers,
Niki
I also need such a thing... I'm on the process to have a friend of mine write a patch to http-replicator so that it can work as a proxy for rpm files.
Stay tuned, shortly, I hope, I'll have some news.
If you are in a location where a caching proxy is useful, wouldn't it be nicer to configure a squid to cache large files and teach yum to behave better in the presence of proxies (i.e. not use a mirrorlist or at least always pick the same server as the first choice from the same location) instead of having ad-hoc per-distribution per-version solutions that won't be of any other use?
Les Mikesell wrote:
Lorenzo Quatrini wrote:
I've been using Debian for a few years, and there was one nifty little app that made installing and updating so much easier: apt-proxy.
Most of the time, I'm taking care of small LANs with an average of five client PCs. But this is a very remote place in South France, so most villages only have 512 kbps DSL. One major update for openoffice.org-*, and I have to wait the whole day for updating each machine (unless I scp -r /var/cache/yum from machine to machine, but that's another story).
I'm currently testing an "intermediate" solution: creating a local Yum repository. I have [base], which consists of all the 5.1 RPMS copied over from the DVD. Then [updates], which I'm currently rsyncing from a remote mirror. And I think I'll do something similar with [extra], which only leaves [rpmforge] (but I won't cache that :oD). Not a very satisfying solution, since for example I'm currently installing XFCE as only desktop environment, and I have nevertheless to download every GNOME- and KDE-related update.
A message to the developers: yum-proxy would be a much-needed addition to Yum, in my humble opinion. I don't have the technical skills to develop such a thing, but maybe one of you has (Daniel, do you read this? :oD)
I'm curious about your comments on this.
Cheers,
Niki
I also need such a thing... I'm on the process to have a friend of mine write a patch to http-replicator so that it can work as a proxy for rpm files.
Stay tuned, shortly, I hope, I'll have some news.
If you are in a location where a caching proxy is useful, wouldn't it be nicer to configure a squid to cache large files and teach yum to behave better in the presence of proxies (i.e. not use a mirrorlist or at least always pick the same server as the first choice from the same location) instead of having ad-hoc per-distribution per-version solutions that won't be of any other use?
Personally, if I was at such a location (where more that 1 or 2 machines needed updates), instead of trying to change anything, I would just rsync the branches of the centos tree I needed down to a web server and have a local mirror.
It takes 5 minutes to setup, and you can do new installs, updates, etc. going forward from the local mirror.
Hi All, I know there are very good reason not to use yet another "non standard" package, and configuring squid to do the work or making a local mirror. My feeling is that none of the "standard" solution is optimal for me, so I'm triyn another way. Http-replicator is small, and easy to setup. The patched version permits, through regular expressions to choose what kind of files to keep in a "flat" cache (where all the files with the same name are considered equal regardless of the source site or mirror). So I can select "RPM$" and/or "DEB$" and so on, and just tell yum/apt to use a proxy. I did some tests unpacking the attached version and it looks working without problems. I'll attach the patch as well as the full patched package, because my friend used a version which is no longer available on rpmforge.
Regards
Lorenzo
-
Johnny Hughes -
Les Mikesell -
Lorenzo Quatrini -
Niki Kovacs