On the subject of how much the SuSE FTP site sucks, I thought I'd throw in my $0.02 US. The update structure on the FTP site is nice, but YaST1 doesn't know how to properly deal with it. Why would this be soo hard to implement? The /pub/mirrors/suse/suse_update/6.4/ structure looks something like: drwxr-xr-x 2 root root 118 Apr 6 05:03 a1/ drwxr-xr-x 2 root root 188 Apr 6 05:03 ap1/ drwxr-xr-x 2 root root 180 Mar 31 11:03 gra1/ drwxr-xr-x 2 root root 126 Apr 4 16:03 kpa1/ drwxr-xr-x 2 root root 646 Apr 5 13:50 n1/ drwxr-xr-x 2 root root 165 Apr 1 16:03 n2/ drwxr-xr-x 2 root root 124 Apr 4 05:03 pay2/ drwxr-xr-x 2 root root 125 Apr 5 05:03 sec1/ drwxr-xr-x 2 root root 122 Mar 31 16:03 xwm1/ drwxr-xr-x 2 root root 862 Apr 6 05:03 zq1/ With a1/ looking something like: -rw-r--r-- 1 root root 86 Apr 6 05:03 INDEX -r--r--r-- 1 root root 2900856 Apr 6 05:03 yast-1.05.2-2.i386.rpm lrwxrwxrwx 1 root root 22 Apr 4 19:01 yast.rpm -> yast-1.05.2-2.i386.rpm How are we as users and local administrators supposed to deal with this? You could simply use a tool like mirror (thanks, Argentium :) to get the entire structure locally, but it's still cumbersome. Why doesn't YaST have a mechanism to actually read the RPM filenames and assess which ones you need? Better yet, why not have the setup/ structure in this FTP directory so that YaST could use the update/ structure as a valid installation medium? I'd write a PERL script to do it myself, but that wouldn't work, since I don't have any knowlege of PERL and have no desire to learn it... -- -=|JP|=- Jon Pennington | Atipa Linux Solutions jpennington@atipa.com | http://www.atipa.com Kansas City, MO, USA | 816-241-2641 x121 -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/