In the future, when planning scheduled updates, grab the packagesGood point. I might have thought of this, just didn't anticipate the usually zippy (500Kb/s and up)
without installing them. up2date -p will do this - it throws the rpms
into /var/spool/up2date and then a subsequent update will get them from
there. If you can't get to the network at all, you could at least
manually update them from the rpms and then do an up2date -u later.
There will undoubtably be times when the network is done, either because
your own network is undergoing maintenance or because your ISP is
busted.
connections I get to go so slooooooow.
I did call my sales rep, and he told me that they had been getting heat from their
larger RHN customers. He said that they were adding bandwidth and would in the future
either segregate the traffic or QOS it somehow... It is still relatively slow, but is much better
now then it was yesterday.
I was speaking up here because I'm sure that many of the RedHat engineers
(the guys who really make things happen) read the lists and share amongst themselves
the interesting posts. I didn't really know who my sales rep would have spoken to, or
whether he was just blowing smoke...
It's one thing when it is "Free" and it is different when it is
labelled "Enterprise, Advanced Server" and you pay $800/year for it.
I'm not a happy customer.
They realized that yesterday. Blocking up2date patch updates for paying customers was not in their plans.
