I noticed than when the download of a single package in a Yast Online Update (YOU) fails, the downloading of the remaining packages continues, but it doesn't install anything at the end. Worse, on the next run it will retrieve files that were already downloaded on previous occasions: so that if again there is a network problem or aborted transmission, the session will fail again - I thought this would have been corrected by now :-? This may be just a nuissance for people with permanent or flat rate network connections, but it is maddening for those of us with only a modem connection, and worse if we pay the phone company by the minute, as is my case. For example, now I have about 68 Mbytes of files in the "/var/lib/YaST2/you/i386/update/8.1/rpm/*" directories. The kde update files are incomplete, but if I select to update kde_3.0.4 YOU will happily download again the 24 Mbytes I already have there, ie, about an hour and a half of phone usage :-( Tricks for fooling YOU? Well, I have managed to install the rpms I had complete with YOU setting a local mirror (thanks to Togan (FAQ) and Johnny Ernst (an email posted here) for the info). I copied all those files to /usr/local/update/i386/update/8.1/, where I have the directories: "disks" (empty), "patches", "rpm", and "scripts". The "patches" I downloaded by ftp, but the "rpms" I copied from "/var/lib/YaST2/you/i386/update/8.1/rpm/*", together with a few more files like "*.info". Then I edited "/etc/sysconfig/onlineupdate" and set YAST2_LOADFTPSERVER="no". Then I added the line "dir:///usr/local/update/" to the file "/etc/suseservers", and fired YOU. I finally could update the rpm files I had downloaded over the past month, that YOU neglected to install because some other package failed to download in the same session. But this method means that I have two full copies of those rpms, at least for some time - or I could tell YOU to delete patches after installing them - and that installing new patches requires me to first get the rpms manually to the local "mirror". Not nice... Now, I have another idea. As YOU uses wget for the actual download, wget could manage incomplete downloads perfectly. However, adding the line "continue = on" to the "wgetrc" file (both system wide or root) doesn't work, because YOU calls wget like this: wget --tries=3 --waitretry=2 --passive-ftp \ -O /var/lib/YaST2/you/i386/update/8.1/rpm/i586/\ kdebase3-konqueror-3.0.4-4.i586.patch.rpm.new.yast.65675 \ ftp://ftp.gwdg.de//pub/linux/suse/ftp.suse.com/suse/i386/update/8.1/\ rpm/i586/kdebase3-konqueror-3.0.4-4.i586.patch.rpm The "-O" option is the culprit: `-O FILE' `--output-document=FILE' The documents will not be written to the appropriate files, but all will be concatenated together and written to FILE. If FILE already exists, it will be overwritten. If the FILE is `-', the documents will be written to standard output. Including this option automatically sets the number of tries to 1. Instead, it could use "-c", or "--continue", but it has some other problems: the server might not support it, for example, and we still need to put the file on a certain place, and with a different name than on the server. The best thing would be for YOU to check if the file has been previously completely downloaded (I assume that can be done with the included gpg signature check, but I'm not sure). YOU could use a temporary directory for the downloads, because wget by default downloads to the local directory, and move the file to the correct place on success, for example. Or the options "--no-directories --directory-prefix=PREFIX" could be used instead. But, as we can not change YOU, then we must find some other way. What I'm thinking is substituting the "/usr/bin/wget" with a script, that adds or replace the adequate options and calls the real wget, thus fooling YOU. After the YOU session, the script must be moved out of the way, and the original wget restored. What do you think, could this be done? Dangers? Ideas? -- Cheers, Carlos Robinson