Re: [SLE] A dynamic updates/supplementary server?

On Saturday 03 June 2006 03:16, Stephen Boddy wrote:
I would appreciate a pointer if this is possible and the document exists
already.

I have three systems (Desktop on 10.0, HTPC on 9.3, and Laptop on 10.1)
Once some of the wrinkles are out of 10.1, I intend updating all systems to
10.1. As I understand things, this means that I'll either download each
patch 3 times, or I have to make a local sync of a very large portion of
the updates and supplementary trees.

You're confusing update and upgrade:

- You want to upgrade 9.3 and 10.0 to 10.1
- You want to update the 10.1 laptop

2 different procedures using 2 different repositories.

What'd be very useful is a setup where one machine acts as a server for all
my machines, but it only retrieves the packages as and when they are
required, and then dishes them out to the requesting machine. This way I
don't waste bandwidth (mirrors and mine) downloading KDE 3.5.3 three times,
and I don't waste bandwidth dowloading updates for a whole load of software
I'll never even install.

You mean some kind of caching proxy? (I'm making the name up, I don't know if
it's called that way...)

A kind of system that caches all packages, and serves the cached package
instead of retrieving them again.

Googling... "gg:caching proxy" yields http://www.squid-cache.org/. Is that
what you mean? It is part of SL-10.1. ;)

I suppose this works only if the URL's in the request are the same, e.g.
http://a.org/p.rpm and http://b.org/p.rpm point both to the same package, but
I guess the proxy server would see them as different, because the URL's
differ.

I know that YOU could leave updates in a folder, but it was never
especially clear to me how other machines could use this. Was the folder to
be exported, and mounted on the clients? Would there be conflicts with
multiple machines using a single dir for managing patches? Or do I have to
have SLES for this kind of functionality?

Of course, this is now all up in the air due to the 10.1 changes. Any
guidance out there?

This might also be of interest to you:

http://en.opensuse.org/Installation_Sources
http://en.opensuse.org/Making_a_DVD_from_CDs
http://en.opensuse.org/1_CD_Install

Perhaps it's possible to set up your own installation source with only those
packages you need.

Cheers,

Leen

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: [SLE] A dynamic updates/supplementary server?
    ... portion of the updates and supplementary trees. ... all my machines, but it only retrieves the packages as and when they are ... A kind of system that caches all packages, ... mirror (full updates folder) ...
    (SuSE)
  • [Feisty & Gutsy as well] Re: Latest Updates Break Samba on Dapper / Edgy
    ... the package was disabled on the security server so should not come down ... Updated packages without this patch will be provided for all releases. ... turning on my Gutsy machines as of a few minutes ago shows the ... updates as being available. ...
    (Ubuntu)
  • Re: ITMU Hotfixes
    ... I know that there are updates to install for the server as ... When we send out packages thru SMS we usually ... the deployment in case we run into problems, so test machines first, then ...
    (microsoft.public.sms.admin)
  • Re: Software Update Strategies
    ... When you package the updates by month do you include all updates for win 2k ... ansd xp machines in 1 package or do you have to have seperate packages for ... >I also group packages by month when pushing out. ... >> go through the process as if I was sending it out for the fist time. ...
    (microsoft.public.sms.swdist)
  • Re: Group Policy - Pushing out Software
    ... going to VNC into the computer, log on as the local Admin and do my thing". ... I would suspect that you are familiar with 'updates' via GPO. ... I know the way we access users machines using Remote Desktop ... > life easy for 2 administrators keeping 80 users machines updated. ...
    (microsoft.public.windows.server.active_directory)