Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Make it work for 10.3 & 10.2 also' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Make it work for 10.3 & 10.2 also
Authored by: aaronfreimark on Oct 24, '07 01:56:24PM

The hint above is fantastic. Unfortunately, it breaks Software Update for 10.2 and 10.3. This is because the Software Update Server 10.4 only caches local copies of 10.4 software updates.

To keep the above functionality, but to pass 10.2 and 10.3 requests to Apple, add the following lines to your httpd config file, which probably lives at /etc/httpd/sites/0000_any_80_.conf.


        <IfModule mod_proxy.c>
                ProxyRequests Off
                ProxyPass /scanningpoints/scanningpointX.xml http://swscan.apple.com/scanningpoints/scanningpointX.xml
        </IfModule>


[ Reply to This | # ]
...and something for 10.5
Authored by: chrisfriend on Oct 27, '07 09:15:01PM
Since there are no software updates (yet) for 10.5, and it's possible to serve updates to clients on other OSes, here's a tip for those on an older server with users running Leopard. (I used the below hint to serve application updates to a Leopard client from a Tiger Server.)

Similar to the original hint from zpjet, adding an additional Redirect entry will cover the new URL for Leopard updates:

Pattern: /catalogs/others/index-leopard.merged-1.sucatalog
Path: http://yoursus.yourdomain.com:8088/index.sucatalog

Please note that this simply points Leopard to the same catalog as everyone else. I'm sure there are likely to be implications beyond missing OS updates that I can't forsee, but it's working great for the time being, where no such updates are around to be missed.

I'd like to thank everyone else who provided the hints and tweaks above -- you've allowed the transition of my home LAN to Leopard to go much, much, much faster and more simply than I would have imagined.

[ Reply to This | # ]