RHEL kernel update install problem!

[Sancho Panza]

Herta and all,

Please pardon my copy of the preceeding message text, but it is needed 
here. /etc/grub.conf (1) does not seem to be where it is supposed to be 
or softlinked... I found some hand scribbled notes from 2 years ago 
indicating that the /boot partition had run out of room for additional 
updates, so the additional attempts at kernel update went into /boot 
directory on main partition BUT did not get registered to show in the 
GRUB menu... problem is I don't have the other part of the note... the 
paper was in a pile of admin stuff that I was entering into my 
maintenance database... but no entries are in the database. Must be the 
the digital gremlins stole it (evil grin).

It has been quite a while since I set up "giskard" and it underwent a 
transition to the current OS from a server configured with RH 7.2.... 
since it is getting de-activated in June, I may just let it be for now. 
I am moving the web stuff to another site and will convert the machine 
to a satellite link based netserver at my office.

All that being said- if there are any other considerations, I would love 
to hear about them.

Herta Van den Eynde wrote:

> Sancho,
>
> The grub boot list is constructed from /etc/grub.conf which normally 
> is a softlink to /boot/grub/grub.conf.  Each entry in the grub menu 
> starts with the "title" tag, so you can try to construct a new entry 
> along the same lines, referencing your new kernel and (usually) 
> corresponding initrd.  The "default" tag indicates which entry will be 
> started by default.  First entry is entry 0.
>
> Hope this helps,
>
> Herta
>
>
> Sancho Panza wrote:
>
>> I have tried to perform the last two kernel updates and for 
>> what--ever reason the kernels 37.0.2EL and wound up in the /boot 
>> directory but do not appear in the GRUB boot list.
>>
>> This problem occurred once before but I cannot locate my notes about 
>> the way I solved the problem. I vaguely recall that I had to get into 
>> the *boot partition* (as opposed to /boot as I see it mounted)  to do 
>> something-- but don't have the time to fool around.
>>
>> Would some kind soul send a FAQ ref or give me a clue as to where to 
>> turn to solve the issue.
>>
>> Many thanks in advance....
>> Jack
>>
>