On Thu, 29 Apr 2004 11:59:46 -0500, Steve Pyatt wrote: > I had this same issue. On top of about a dozen others just getting > started. I ran it several times before it seemed to get everything > correctly. The nice thing is once it is downloaded, it did not download > again. You might try running just a few of the packages instead of all of > them. It didn't seem to really matter though. > > Steve > > -----Original Message----- > From: fedora-list-bounces@xxxxxxxxxx > [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Gary Stainburn Sent: > Thursday, April 29, 2004 11:54 AM To: fedora-list@xxxxxxxxxx > Subject: up2date hanging > > Hi folks, > > having got the network working I decided to run up2date. > > Having taken most of yesterday downloading (102 updates) I left it > overnight. > This afternoon when I returned to it, the download had finished and it > needed me to click a button before proceeding (?). > > I clicked about 4 hours ago and then sat watching the hourglass. The > hourglass is still spinning and it's time to go home again. > > Two questions > > 1) should it take this long? (Celeron 700 with 120MB (8MB stolen by > graphics > card) > > 2) if I kill it and start again, will it a) do better next time, and b) > need to re-download everything. > You should edit your /etc/sysconfig/rhn/sources file to use a mirror, rather than the redhat server set as a default. You can get a list of mirrors on the fedora.redhat.com site. Also, run up2date-config and remove "kernel*" from the ignored packages, and set the program to retain the binary packages after installation (in case you need them again later). You might find that up2date works a little better overall with the mirrors, even if you don't make the configuration changes. Finally, I usually run it as "up2date --nox -u -v" from a terminal, which eliminates all interactivity and the gui, so it will complete unattended. Good luck, Chuck
