[CentOS] Hosed by 4.2

Joe Landman landman at scalableinformatics.com
Mon Oct 17 03:20:36 UTC 2005


   A yum upgrade on my main server (no pre-loading kernel, yum, etc), 
caused a hiccup.  I didn't see the x86_64 release notes until too late. 
  I did see the useradd chomping down CPU time.  I ignored it as long as 
possible, but then the install wound up hanging the machine.  Rebooted, 
and had to do some fancy tweaking using yum to restore the system to a 
stable state.  Not difficult, just a minor annoyance.

   I am not sure if others are having issues with the 4.2 upgrade, but 
it might be a good idea to avoid upgrading the package (I think it was 
mysql) to avoid hitting that.

   That said, apart from a missing firewire driver, I am quite happy 
with Centos (and that is an upstream provider issue, addressed for the 
most part in centosplus).  The minor pain I went through with this is 
nothing compared to the days of sheer abject terror I went through using 
other distributions "upgrade" system.

   Good work folks!


Robert wrote:
> Karanbir Singh wrote:
>> Robert wrote:
>>> I did a yum upgrade AFTER first manually installing the new kernel. 
>> why did you manually need to install the kernel ? 
> Because a "yum update kernel" offered to install the -SMP kernel.  This 
> is, no doubt, an artifact of anaconda & associates deciding at the time 
> CentOS4 was first installed that an SMP kernel was appropriate for an 
> Athlon XP in an ASUS A7NX8 ver.2 deluxe m/b, compounded by my packrat 
> reluctance to throw it away at the outset.
>> you can / should use yum to do that for you. perhaps go with a 'yum 
>> update yum' before you kick everything off with a 'yum update'. 
> THAT is what I would definitely do different.
>> if you really want the kernel in and running before you do the yum 
>> update, then do a yum update yum; yum update kernel; reboot; yum update
> No.  I didn't want -- or have -- the new kernel running before the 
> update.  I simply wanted it to be available.
> I'm reasonably sure everything is gonna be O.K. Yum is one of the 
> packages that gets reported twice:
> [root at mavis yum.repos.d]# rpm -q yum
> yum-2.2.1-1.centos4
> yum-2.4.0-1.centos4
> The correct version gets executed:
> [root at mavis yum.repos.d]# yum --version
> 2.4.0
> ...but the list of files installed is screwy.  So, it looks like my work 
> is cut out for me:
> [root at mavis yum]# rpm -qa | gawk -F-[0123456789] '{ print $1 }' | sort | 
> uniq | wc -l
> 1433
> [root at mavis yum]# rpm -qa | gawk -F-[0123456789] '{ print $1 }' | sort | 
> wc -l
> 1655
> I'm not overwhelmed by brilliant ideas for scripting the obvious. :-(
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> http://lists.centos.org/mailman/listinfo/centos

Joseph Landman, Ph.D
Founder and CEO
Scalable Informatics LLC,
email: landman at scalableinformatics.com
web  : http://www.scalableinformatics.com
phone: +1 734 786 8423
fax  : +1 734 786 8452
cell : +1 734 612 4615

More information about the CentOS mailing list