Ralf Corsepius wrote:
Jesse Keating wrote:
Try doing updates on a netbook,
I own one - Typical "yum update" times are in the order of "very few"
minutes at average.
Looking only at install times...
Asus EEE 900A (SSD): 3m40s
HP xw4400 Workstation (SATA platter): 1m25s
...and the latter did kernel-devel as well as kernel, kernel-headers and
kernel-firmware, plus it also had to remove a kmod-nvidia. (Times are
...so the SSD is about 3x slower or more (especially as I notice
kernel-devel took the desktop the longest).
Yum isn't really the problem here, it's the
rpms themselves, constantly doing ldconfigs, cache updates, tonnes of
From what I experience, SELinux policy updates are by far means the
most resource intense/most time consuming part of updating.
Really? For me, it's always OOo updates... 100 MB in a single package?
(What's worse is that OOo can't be updated while running... it doesn't
crash, but it becomes unable to save; bad news if you forgot to save
first. That and Firefox are the only things I'm aware of with that
problem, but at least with FF it only breaks typing addresses into the
Whereas selinux is a 2.0 MB package :-).
Please do not quote my e-mail address unobfuscated in message bodies.
"It's impossible! But... do-able."
-- Robert MacDougal (Sean Connery, Entrapment)
fedora-devel-list mailing list