Hi all,
I downloaded latest CentOS 5.5 DVD i386 image from one of FTP's in a list.
I've burned that image to DVD and created new DVD to use for fresh installations. Now when I install fresh CentOS 5.5 (in VM) I am getting info that there are 50 packages updates.
This is ok when I have good internet speed (@work) but when I am home, this update takes a lot of time.
I guess I can skip updates but I wasn't experiencing such annoyance with CentOS 5.4. My gues is that when CentOS 5.4 was finalized there is no updates to that DVD.
Is there any suggestions ?
On Wed, Aug 25, 2010 at 02:14:02PM +0200, Aleksandar Stoisavljevic wrote:
This is ok when I have good internet speed (@work) but when I am home, this update takes a lot of time.
Welcome to life on the internet.
I guess I can skip updates but I wasn't experiencing such annoyance with CentOS 5.4. My gues is that when CentOS 5.4 was finalized there is no updates to that DVD.
Why in the world would you opt to skip updates? How is updating your system an annoyance?
5.X are just point-in-time snapshots of CentOS 5 and all patches leading up to the time that 5.X was released. Updates are a continuing process that will occur for the lifetime of the release.
Is there any suggestions ?
Yes, bite the bullet and update.
John
At Wed, 25 Aug 2010 07:19:25 -0500 CentOS mailing list centos@centos.org wrote:
On Wed, Aug 25, 2010 at 02:14:02PM +0200, Aleksandar Stoisavljevic wrote:
This is ok when I have good internet speed (@work) but when I am home, this update takes a lot of time.
Welcome to life on the internet.
I guess I can skip updates but I wasn't experiencing such annoyance with CentOS 5.4. My gues is that when CentOS 5.4 was finalized there is no updates to that DVD.
Why in the world would you opt to skip updates? How is updating your system an annoyance?
5.X are just point-in-time snapshots of CentOS 5 and all patches leading up to the time that 5.X was released. Updates are a continuing process that will occur for the lifetime of the release.
Is there any suggestions ?
Yes, bite the bullet and update.
The main problem is that yum is NOT well written to deal with a slow and *unreliable* dial-up interface -- it in fact behaves extremly poorly when used with dial-up (and no, it is just not possible for me to get a better internet connection at home -- dialup is *all* that is available where I live). It assumes that ANY network problems are due to a busy server and it switches to another server (and in the case of metadata, starts the download from the beginning!). *I* often find it better to use wget to snarf the repo metadata. I *also* use my laptop to *manually* download (using wget) the packages for my desktop machine (the two machines are different archs: the desktop is x86_64 and the laptop is a i686).
Oh, and I remove up-to-date and yum's update deamon. Both are a waste of time. (I also removed Open Office, since it is too big to maintain on a dial-up system, esp. since *I* don't ever do 'word processing'.) I manually run 'yum check-update' from time to time (when is the centos updates digest going to resume on this list?).
John
Robert,
On 25 August 2010 14:24, Robert Heller heller@deepsoft.com wrote:
The main problem is that yum is NOT well written to deal with a slow and *unreliable* dial-up interface -- it in fact behaves extremly
Grab a copy of a repository at work, copy it home and set up a local repository. Yum will be perfectly happy with the setup. Sample to rsync to mirrorservice.org:
export RSYNCCMD="rsync -avP --delete" $RSYNCCMD rsync://rsync.mirrorservice.org/sites/mirror.centos.org/5.5/updates/x86_64/ /storage/centos/5.5/updates/x86_64/ $RSYNCCMD rsync://rsync.mirrorservice.org/sites/mirror.centos.org/5.5/updates/i386/ /storage/centos/5.5/updates/i386/
At Wed, 25 Aug 2010 14:41:11 +0100 CentOS mailing list centos@centos.org wrote:
Robert,
On 25 August 2010 14:24, Robert Heller heller@deepsoft.com wrote:
The main problem is that yum is NOT well written to deal with a slow and *unreliable* dial-up interface -- it in fact behaves extremly
Grab a copy of a repository at work, copy it home and set up a local repository. Yum will be perfectly happy with the setup. Sample to rsync to mirrorservice.org:
My 'work' is at home (dialup). The local library is only good for about 1.5mbits/sec (about 150kbytes/sec). I don't have enough free disk space for a full repo on either my laptop or my desktop.
export RSYNCCMD="rsync -avP --delete" $RSYNCCMD rsync://rsync.mirrorservice.org/sites/mirror.centos.org/5.5/updates/x86_64/ /storage/centos/5.5/updates/x86_64/ $RSYNCCMD rsync://rsync.mirrorservice.org/sites/mirror.centos.org/5.5/updates/i386/ /storage/centos/5.5/updates/i386/
On Wed, August 25, 2010 16:19, Robert Heller wrote:
At Wed, 25 Aug 2010 14:41:11 +0100 CentOS mailing list centos@centos.org wrote:
Robert,
On 25 August 2010 14:24, Robert Heller heller@deepsoft.com wrote:
The main problem is that yum is NOT well written to deal with a slow and *unreliable* dial-up interface -- it in fact behaves extremly
Grab a copy of a repository at work, copy it home and set up a local repository. Yum will be perfectly happy with the setup. Sample to rsync to mirrorservice.org:
My 'work' is at home (dialup). The local library is only good for about 1.5mbits/sec (about 150kbytes/sec). I don't have enough free disk space for a full repo on either my laptop or my desktop.
You've received plenty of good advice here and people have made an effort to find viable solutions to your problem, it would be perfectly possible for you to get a cheap USB drive to act as a repository for both your systems. Unfortunately, you will find that all modern operating systems and many applications are increasingly reliant on Online Updates (Windows included).
You seem dismissive of any offline solutions that have been put forward to you, yet you have discounted the feasibility of working with an online solution as well.
To be honest, then, I therefore cannot think of any solution to your problem.
At Wed, 25 Aug 2010 16:28:04 +0200 CentOS mailing list centos@centos.org wrote:
On Wed, August 25, 2010 16:19, Robert Heller wrote:
At Wed, 25 Aug 2010 14:41:11 +0100 CentOS mailing list centos@centos.org wrote:
Robert,
On 25 August 2010 14:24, Robert Heller heller@deepsoft.com wrote:
The main problem is that yum is NOT well written to deal with a slow and *unreliable* dial-up interface -- it in fact behaves extremly
Grab a copy of a repository at work, copy it home and set up a local repository. Yum will be perfectly happy with the setup. Sample to rsync to mirrorservice.org:
My 'work' is at home (dialup). The local library is only good for about 1.5mbits/sec (about 150kbytes/sec). I don't have enough free disk space for a full repo on either my laptop or my desktop.
You've received plenty of good advice here and people have made an effort to find viable solutions to your problem, it would be perfectly possible for you to get a cheap USB drive to act as a repository for both your systems. Unfortunately, you will find that all modern operating systems and many applications are increasingly reliant on Online Updates (Windows included).
You seem dismissive of any offline solutions that have been put forward to you, yet you have discounted the feasibility of working with an online solution as well.
To be honest, then, I therefore cannot think of any solution to your problem.
*I* don't have a problem. I just download the packages I need (I have enough space for that) -- I update the laptop directly and then download just the packages I need for my desktop system. I just don't need a full repo. It can be a struggle, but I am managing to keep both systems up-to-date.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Greetings,
On Wed, Aug 25, 2010 at 7:49 PM, Robert Heller heller@deepsoft.com wrote:
My 'work' is at home (dialup). The local library is only good for about 1.5mbits/sec (about 150kbytes/sec). I don't have enough free disk space for a full repo on either my laptop or my desktop.
Perhaps it's time for you to get an USB external HDD.
Saying that one can't maintain a 30+GB repo in an ext3 filesystem based pocket/toolbox is not exactly the style nowadays.
regards,
Rajagopal
On 8/25/10 7:14 AM, Aleksandar Stoisavljevic wrote:
Hi all,
I downloaded latest CentOS 5.5 DVD i386 image from one of FTP's in a list.
I've burned that image to DVD and created new DVD to use for fresh installations. Now when I install fresh CentOS 5.5 (in VM) I am getting info that there are 50 packages updates.
This is ok when I have good internet speed (@work) but when I am home, this update takes a lot of time.
I guess I can skip updates but I wasn't experiencing such annoyance with CentOS 5.4. My gues is that when CentOS 5.4 was finalized there is no updates to that DVD.
Is there any suggestions ?
Updates are a good thing - they mean bugs and security issues are being fixed. If you like to baby-sit the update process, try it this way: yum install yum-downloadonly then you can: yum -y --downloadonly update and go away (or sleep) while the update rpms download. If this step doesn't complete you can restart it as many times as necessary and it won't actually install anything. After the downloads have completed, you can do yum -y update to install them and it will run quickly.
Les Mikesell wrote, On 08/25/2010 08:29 AM:
On 8/25/10 7:14 AM, Aleksandar Stoisavljevic wrote:
Hi all,
I downloaded latest CentOS 5.5 DVD i386 image from one of FTP's in a list.
I've burned that image to DVD and created new DVD to use for fresh installations. Now when I install fresh CentOS 5.5 (in VM) I am getting info that there are 50 packages updates.
This is ok when I have good internet speed (@work) but when I am home, this update takes a lot of time.
I guess I can skip updates but I wasn't experiencing such annoyance with CentOS 5.4. My gues is that when CentOS 5.4 was finalized there is no updates to that DVD.
Is there any suggestions ?
Updates are a good thing - they mean bugs and security issues are being fixed. If you like to baby-sit the update process, try it this way: yum install yum-downloadonly then you can: yum -y --downloadonly update and go away (or sleep) while the update rpms download. If this step doesn't complete you can restart it as many times as necessary and it won't actually install anything. After the downloads have completed, you can do yum -y update to install them and it will run quickly.
And if you are maintaining more than one machine at home, you need to realize that you don't need to waste the time twice to update the same thing on two machines. Assuming your home machines are networked together.
change /etc/yum.conf from keepcache=0 to keepcache=1
and then after updating the first machine, you can update the second by scp -pr root@machine1:/var/cache/yum/ \ root@machine2:/var/cache/yum/ or rsync --relative root@machine1:/var/cache/yum/./ \ root@machine2:/var/cache/yum/ (I do suggest reading the man pages on both commands and see if there are other things you want to add, such as -hvaK --delete-after --hard-links --sparse on rsync.)
Then do the yum update on the second, and it will only pull in updates that are unique to the second system. Of course if the second system pulls in new updates and you have 3, 4 ... N machines to update, you'll want to pull from the systems with more stuff to do the updates on later systems.
Another option would be to see if your employer would be OK with you occasionally making DVD or USB copies of the CentOS & EPEL mirrors maintained at work to take home, assuming your employer maintains a mirror set locally.
current Centos updates 2.0G updates/i386 2.1G updates/x86_64 (of course this is without trimming the 450MB that repomanage --nocheck -k1 -o i386/ might tell you about if the mirror is maintained with out rsync) current epel 3.7G i386 4.2G x86_64
On 26/08/10 00:03, Todd Denniston wrote:
And if you are maintaining more than one machine at home, you need to realize that you don't need to waste the time twice to update the same thing on two machines. Assuming your home machines are networked together.
Good Point. I run a 'fat' squid proxy on my network so updates only get downloaded once. Disk space is cheap. Just need to increase the cache size (mine set at 50G) and max file size limit (have mine set at ~400M) and configure yum to use the proxy (or use a transparent proxy).
This also makes it easy to stage and test updates.
Kal
-
Aleksandar Stoisavljevic -
Giles Coochey -
Hakan Koseoglu -
John R. Dennison -
Kahlil Hodgson -
Les Mikesell -
Rajagopal Swaminathan -
Robert Heller -
Todd Denniston