Oddball schreef:
zypper mr –keep-packages –remote , does this mean that the repo-'state' itself is cached on the repo?
because this would save a lot of trouble..
What i understand is that pkgs have to get from one place to another first? My speed is high enough, somewhere around 250K/s, installing doesn't take much time either. Total dl + installing 1150+ or so pkgs, 2,5 GB+ done in less than 2 hours. Problem is to recognise when exactly the repo changes.. and how much time that takes.. At few occasions i ran into this, and offcourse many off us have, and when i logged out and in again, refreshed the repos, and than factory update again, the changes were taken into account, and the update could be finished.. This time not yet. If i reboot completely, chance is big, that i have to reinstall, and start over.... I rather would not want this, because it takes much valuable time... everybody knows this... Will there be no way to solve this problem to everybodies satisfactory? Like paralell serving? That means that factory can change, but not for the servers that are occupied, (with uploading the updates to the custumers,) they change as soon as the updates are completed. As soon as the exhanged image is available, all new connections get the new image to update from, while those who are busy updating from the older one, can complete their downloads. Is this construction possible somehow? I can imagine that some script would be able to redirect new connections to the location of the new image, while existing connections remain to download from the earlier image? -- Enjoy your time around, Oddball (M9.) (Now or never...) OS: Linux 2.6.27.4-2-default x86_64 Huidige gebruiker: oddball@AMD64x2-sfn1 Systeem: openSUSE 11.1 Beta 4 (x86_64) KDE: 4.1.2 (KDE 4.1.2) "release 2.6" -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org