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
