On Tue, Jul 26, 2011 at 10:17 AM, Dag Wieers <d...@wieers.com> wrote: > On Tue, 26 Jul 2011, Ljubomir Ljubojevic wrote: > >> huyfuo wrote: >>> 2011/7/25 Ljubomir Ljubojevic <off...@plnet.rs>: >>> >>>> But WHY do you use apt on OS that by default uses yum? >>>> >>> There is no speacial reason. But yum is slow. >> >> How have you reached that conclusion? Please read this mail: >> http://osdir.com/ml/centos-devel/2011-07/msg00200.html >> It shows that yum with 18.300 packages will complete dependency check in >> max 1m 9sec (without cache). Have you performed quality test apt vs yum? > > Ljubomir, > > The discussion is quite moot nowadays, but as a long-time user of both apt > and yum, apt still beats the crap out of yum (both in memory usage, speed > and cpu usage), however it is no longer maintained and therefor a dead-end. > > One of the other reasons to be using apt, was that yum only started to be > shipped with RHEL5, and most have (had) RHEL2, RHEL3 and RHEL4 systems > around. up2date is something to be avoided, where possible...
[ This is especially for new RHEL users, not for you, Dag. ] Good point. For some RHEL users, the yum packages available from CentOS and now Scientific Linux can easily be turned to use with a local RHEL mirror repository. I've been doing this stunt for years, setting up a registered RHEL host to mirror Red Hat updates to a local repository and using yum to that local repository to provide updates. The relatively slow connection to Red Hat's central repositories, and yum's somewhat overfrequent updates of its metadata, seem to be the big problem, are resolved by this and yum becomes much more usable. This allows me to put a stake through the heart of up2date and yum-rhn-plugin, except on the licensed machine or machines that are doing the mirroring. (I use one i386 and one x86_64 host to keep both sets of channels updated locally.) One has to be careful of licensing: the local repository should only be accessible to internal, licensed machines, with the relevant channels available only to appropriately licensed hosts. Do *NOT* make this repository available to the Internet at large! I've caught someone doing that, and Red Hat didn't have to yell at them, I got to them first. _______________________________________________ users mailing list users@lists.repoforge.org http://lists.repoforge.org/mailman/listinfo/users
