Folks, I've found a problem with YaST2 as shipped with SuSE Linux 9.2 and would appreciate if someone could check to see if the 10.0 beta (or even 9.3 if anyone has it installed) still has the same problem. Essentially, YOU (YaST Online Update) doesn't honour the NO_PROXY variable in /etc/sysconfig/proxy; if you try to access a user-defined update site such as "updates.my.dom" and have either "my.dom" or ".my.dom" (I tried both just in case - neither worked) in the NO_PROXY variable, YOU will still go via the defined proxy server. I even removed all http_proxy and ftp_proxy variables from my environment before running YOU, just in case - made no difference. This may not be much of a problem for a single client running YOU, but as the number of clients increases the behaviour becomes intolerable (the Internet proxy server ends up having to serve requests that would be better serviced by the clients talking directly to the update server - that's why NO_PROXY exists in the first place). Reports either way would be appreciated, thanks... -- "I want my mum!" "Yes, it'd be good to see her. I should imagine a maternally-outraged gorilla could be a useful ally when it comes to the final scrap." - Private Baldrick and Captain Blackadder (Blackadder Goes Forth)