On Wed, May 7, 2008 at 12:32 AM, Ralph Angenendt <ra+centos at br-online.de> wrote: > > Erm. "man find" is one of the most hideous manual pages on a linux > system (man tar comes close) - so a bit help from your side would have > been nice. > Beauty is in the eye of the beholder. I have never found this particular man page to be bad enough not to consult when needed, even for the first time (like I did, lo these many eons ago, when it was even harder to read than now) and the effort pays off big time in future uses. I could have just said RTFM in so many letters, but I /was/ trying to be nice(r). > a) use locate whereever you can That should work, too, if you know how to use it (I'm not too fond of the man page for this one, either). > b) find / -type f-name "kernel*.rpm" -- this recursively (from / > downwards) finds file which begin with "kernel" and end with "rpm" Actually, the "-type f" is not needed, unless a system has enitities on it that are not files but masquerade as them with names like kernel-headers-2.6.18-53.1.14.el5.i686.rpm. > c) This is not needed anyway, as those packages are ALREADY installed. The problem Lanny cited was that the packages were installed but the kernel did not appear in /boot, and the suggested solution was to remove them and then reinstall them. Yes, if they are properly installed, you don't need to know where they are. Yes, you do not need to know where they are to remove them (your previous email this subject). But you're going to have a real problem reinstalling them if you don't know where they are. Hence, the "find" suggestion. 'Find' is your friend. mhr