Hi, Sam schrieb: > Neither - it's an empty directory.
This is not going to work with an emtpy directory. > What's going on? I haven't figured it out yet, but Yast seems to be creating > /var/adm/mount/AP_0x00000001 directories during that 20 mins. But they are > deleted/unmounted when I go back to online update, so those dir(s) have to be > recreated everytime. > > The /var/adm/mount dirs are eerily similar to the ones in > /var/lib/zypp/cache/Source.A2QBo0/repodata. But I haven't figured out the > correlation between the two. I've only had 10.1 installed for a few days. YaST downloads the repository metadata into /var/adm/mount/AP_0x00000001 and copies them to /var/lib/zypp/cache when the download is finished, overwriting the previous copy. > What I was hoping to do was split the updating task: a) keep the metadata > local so I can easily browse updates, etc. and b) when I *decide* to update a > package, then Yast can fetch the RPMs over the network. What you are looking for is a tool like apt or smart where refreshing the repository metadata and performing the actual update are really separate steps that have to be invoked separately. And that is exactly my proposal, have a look at one of these tools or maybe even both. What you are trying to do will be very clumsy with YaST because YaST refreshes the repository metadata automatically when the online_update module is invoked. > BTW, I don't have 'createrepo' on my system. It is not installed by default, but available for installation in the repository. I guess that you will not need it at all. Andreas Hanke
