I'm guessing most of you out there have multiple Linux's running. What I did was I had a central box run wget and download all the patches. Then with some tweaking of Online Update I run all my updates from an internal patch server. Here's what I did:
Verify the yas2-online-update rpm is installed first Run the following to edit the file /etc/suseservers and replace it's contents: echo "http://internalupdateserver.domain.com/download"; > /etc/suseservers Edit the file /etc/sysconfig/onlineupdate and change the following line: YAST2_LOADFTPSERVER="no" Now start the online update program by typing: online_update -n I use the command line version because it doesn't prompt you with all the annoying messages about running zipl when you are done. This procedure is for SLES8 only. I have it worked out for SLES7 if anyone is interested. On the internalupdateserver side just re-create the directory structure as it is on the suse site. Hope this helps someone out there, this list has been a great source of information for me that's for sure. Josh Konkol GuideOne Insurance [EMAIL PROTECTED] -----Original Message----- From: Nick Laflamme [mailto:[EMAIL PROTECTED] Sent: Thursday, April 15, 2004 12:21 PM To: [EMAIL PROTECTED] Subject: Re: SLES on-line updates? Post, Mark K wrote: >Nick, > >YaST Online Update uses wget under the covers to do the retrievals. > Good to know; this lets me to some testing without YaST sanitizing the world for me. :-) >If you have proxies that require authorization, you'll need to create a ~/.wgetrc file with the necessary information to make that happen automagically. >Something like this: ># You can set the default proxies for Wget to use for http and ftp. ># They will override the value in the environment. >http_proxy = http://proxyuser:[EMAIL PROTECTED]:portnumber/ > It's not at all clear that there's a proxy involved. It wouldn't surprise me if there are (allegedly) transparent caches in place, but their whole point is, they shouldn't matter. At any point, "wget" does seem to see any response so far yet on this system, not even some kind of challenge from a proxy server. Why do I get the feeling that I'll have an Apache server up on a test Intel Linux image before long? >Mark Post > Thanks, Nick ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 This message and accompanying documents are covered by the Electronic Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains information intended for the specified individual(s) only. This information is confidential. If you are not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, copying, or the taking of any action based on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
