Are you saying that you already tried to repair it with package-cleanup, and that didn't work for you?<br><br>I probably can't help you beyond what I've already suggested--again, I'm a lot more familiar with Debian than CentOS.<br>
<br><br clear="all">William Tracy<br>Work: <a href="mailto:wtracy@cisco.com">wtracy@cisco.com</a><br>Play: <a href="mailto:afishionado@gmail.com">afishionado@gmail.com</a><br>Cell phone: (805) 704-0917<br>Internet phone: (707) 206-6441<br>
<br><br><div class="gmail_quote">On Thu, Mar 17, 2011 at 6:44 PM, Todd Cary <span dir="ltr"><<a href="mailto:todd@aristesoftware.com">todd@aristesoftware.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Bill -<br>
<br>
Though I have run the following command with the results in parts of this message . Do you think it would be advantageous to run your suggested rpm command?<br>
<br>
Todd<div class="im"><br>
<br>
<br>
<br>
On 3/17/2011 5:44 PM, William Tracy wrote:<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">
A different possible approach: Supposedly this command will forcibly reinstall a package from an rpm file, replacing any accidentally deleted files:<br>
<br>
rpm -U --force <package.rpm><br>
<br>
I found a forum post that suggests that the "yum-utils" package includes a "package-cleanup" command that will do this without making you manually track down the rpm files.<br>
<br>
YMMV; I'm more of a Debian guy. I happen to have a Red Hat system here at work where I can pull up man pages, but I don't have root access to test anything out (or install yum-utils).<br>
<br>
<br>
William Tracy<br></div>
Work: <a href="mailto:wtracy@cisco.com" target="_blank">wtracy@cisco.com</a> <mailto:<a href="mailto:wtracy@cisco.com" target="_blank">wtracy@cisco.com</a>><br>
Play: <a href="mailto:afishionado@gmail.com" target="_blank">afishionado@gmail.com</a> <mailto:<a href="mailto:afishionado@gmail.com" target="_blank">afishionado@gmail.com</a>><div class="im"><br>
Cell phone: <a href="tel:%28805%29%20704-0917" target="_blank"></a><a href="tel:%28805%29%20704-0917" target="_blank">(805) 704-0917</a><br>
Internet phone: <a href="tel:%28707%29%20206-6441" target="_blank"></a><a href="tel:%28707%29%20206-6441" target="_blank">(707) 206-6441</a><br>
<br>
<br></div><div><div></div><div class="h5">
On Thu, Mar 17, 2011 at 12:57 PM, Todd Cary <<a href="mailto:todd@aristesoftware.com" target="_blank">todd@aristesoftware.com</a> <mailto:<a href="mailto:todd@aristesoftware.com" target="_blank">todd@aristesoftware.com</a>>> wrote:<br>
<br>
Scott -<br>
<br>
Again thank you for the assistance, and my delays in<br>
getting back is due to being "in the field" frequently.<br>
<br>
I can afford to have the server down for a period of time<br>
since it is mainly for FTP, testing PHP and displaying<br>
images for clients.<br>
<br>
Do I include the EL in the symbolic link as in<br>
vmlinuz -> vmlinuz-2.6.9-100.EL<br>
<br>
Todd<br>
<br>
# grub.conf generated by anaconda<br>
#<br>
# Note that you do not have to rerun grub after making<br>
changes to this file<br>
# NOTICE: You have a /boot partition. This means that<br>
# all kernel and initrd paths are relative to<br>
/boot/, eg.<br>
# root (hd0,0)<br>
# kernel /vmlinuz-version ro<br>
root=/dev/VolGroup00/LogVol00<br>
# initrd /initrd-version.img<br>
#boot=/dev/hdc<br>
default=0<br>
timeout=5<br>
splashimage=(hd0,0)/grub/splash.xpm.gz<br>
hiddenmenu<br>
title CentOS (2.6.9-100.EL)<br>
root (hd0,0)<br>
kernel /vmlinuz-2.6.9-100.EL ro<br>
root=/dev/VolGroup00/LogVol00 rhgb quiet<br>
initrd /initrd-2.6.9-100.EL.img<br>
<br>
Todd<br>
<br>
<br>
On 3/17/2011 12:01 AM, Scott Doty wrote:<br>
<br>
On 03/16/2011 04:58 PM, Todd Cary wrote:<br>
<br>
Scott -<br>
<br>
Yup...I was not paying attention to the link syntax<br>
- I do know better :-).<br>
<br>
On the advice of others in the Centos forum, I did<br>
the following:<br>
<br>
rpm -Uvh --replacepkgs --replacefiles<br>
kernel-2.6.9-100.EL.i686.rpm<br>
redhat-logos-1.1.26-1.centos4.4.noarch.rpm<br>
grub-0.95-3.8.i386.rpm<br>
<br>
So now I have the following in the /boot/ directory:<br>
<br>
drwxr-xr-x 5 root root 9216 Mar 9 10:31 .<br>
drwxr-xr-x 24 root root 4096 Jan 24 08:34 ..<br>
-rw-r--r-- 1 root root 51676 Feb 17 22:41<br>
config-2.6.9-100.EL<br>
drwxr-xr-x 2 root root 1024 Mar 9 10:31 grub<br>
-rw-r--r-- 1 root root 444812 May 5 2007<br>
grub-0.95-3.8.i386.rpm<br>
-rw-r--r-- 1 root root 1343054 Mar 9 10:29<br>
initrd-2.6.9-100.EL.img<br>
-rw-r--r-- 1 root root 13409764 Feb 18 06:25<br>
kernel-2.6.9-100.EL.i686.rpm<br>
drwx------ 2 root root 12288 Jan 12 2007<br>
lost+found<br>
-rw-r--r-- 1 root root 9371 Aug 12 2006 message<br>
-rw-r--r-- 1 root root 9371 Aug 12 2006<br>
message.ja<br>
-rw-r--r-- 1 root root 7919724 Aug 13 2006<br>
redhat-logos-1.1.26-1.centos4.4.noarch.rpm<br>
-rw-r--r-- 1 root root 67797 Feb 17 22:41<br>
symvers-2.6.9-100.EL.gz<br>
-rw-r--r-- 1 root root 770652 Feb 17 22:41<br>
System.map-2.6.9-100.EL<br>
drwx------ 2 root root 9216 Mar 9 10:03<br>
.Trash-root<br>
-rw-r--r-- 1 root root 1538264 Feb 17 22:41<br>
vmlinuz-2.6.9-100.EL<br>
<br>
I am not sure of what to have the symbolic link for<br>
vmlinuz point to; vmlinuz-2.6.9-100???<br>
<br>
<br>
That looks correct. but check grub.conf to make sure<br>
the kernel file you're trying to boot is the correct one.<br>
<br>
Also, remember that it will look a little funny, if you<br>
have a separate /boot partition -- the filenames will<br>
be in the "root" directory, like this:<br>
<br>
title Fedora (2.6.35.10-74.fc14.x86_64)<br>
root (hd0,0)<br>
kernel /vmlinuz-2.6.35.10-74.fc14.x86_64 ro<br>
root=UUID=69effc7d-ef6e-4982-9bdc-2f3bea9e056e rhgb<br>
quiet SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8<br>
KEYTABLE=us selinux=0<br>
initrd /initramfs-2.6.35.10-74.fc14.x86_64.img<br>
<br>
It's the kernel line I'm referring to, it will be<br>
"/vmlinuz-..." instead of "/boot/vmlinuz-..." -- but<br>
_only_ if /boot is a separate partition.<br>
<br>
Quick question -- if it _doesn't_ boot, can you afford<br>
for this system to be down until it can be fixed?<br>
<br>
-Scott<br>
<br>
<br>
_______________________________________________<br>
talk mailing list<br></div></div>
<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a> <mailto:<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a>><div class="im"><br>
<a href="http://nblug.org/cgi-bin/mailman/listinfo/talk" target="_blank">http://nblug.org/cgi-bin/mailman/listinfo/talk</a><br>
<br>
<br>
<br>
-- Ariste Software<br>
Petaluma, CA 94952<br>
<br>
<a href="http://www.aristesoftware.com" target="_blank">http://www.aristesoftware.com</a><br>
<br>
<br>
_______________________________________________<br>
talk mailing list<br></div>
<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a> <mailto:<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a>><div class="im"><br>
<a href="http://nblug.org/cgi-bin/mailman/listinfo/talk" target="_blank">http://nblug.org/cgi-bin/mailman/listinfo/talk</a><br>
<br>
<br>
<br>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a><br>
<a href="http://nblug.org/cgi-bin/mailman/listinfo/talk" target="_blank">http://nblug.org/cgi-bin/mailman/listinfo/talk</a><br>
</div></blockquote><div><div></div><div class="h5">
<br>
-- <br>
Ariste Software<br>
Petaluma, CA 94952<br>
<br>
<a href="http://www.aristesoftware.com" target="_blank">http://www.aristesoftware.com</a><br>
<br>
<br>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@nblug.org" target="_blank">talk@nblug.org</a><br>
<a href="http://nblug.org/cgi-bin/mailman/listinfo/talk" target="_blank">http://nblug.org/cgi-bin/mailman/listinfo/talk</a><br>
</div></div></blockquote></div><br>