Tony Nelson wrote:
On 09-07-31 10:51:46, Justin P. Mattock wrote:
> Tony Nelson wrote:
>
>> On 09-07-31 03:02:20, Justin P. Mattock wrote:
>> ...
>>
>>
>>> opps!!
>>> I guess it helps to have ext4 compiled in the kernel..
>>> (sh^t I'm a neewbie)..
>>>
>>>
>> It only needs to be a module, but then it must be present in your
>> initrd (mkinitrd -f /boot/initrd-`uname -r`.img `uname -r`, or
>> whatever kernel version you're making it for).
>>
>>
>>
> At the moment I see that once you
> make install in the kernel source tree
> fedora will automatically read the script to create
> .img and so forth.
>
OK.
> In your honest opinion what is the best way to handle
> the old stale kernels in /boot i.g.(remove them without
> generating a SIGSEGV).
>
I just leave them there until my /boot gets full. If they're from
RPMs, I do a `yum remove kernel-<version>`, otherwise I just `rm *-
<version>`.
is there a way to tell yum "hey I have a source here, add it to the
list"
instead of creating an rpm and then installing the rpm?
> while following through git I usually have multiple kernels,
> and usually end up just removing them through time. In this case
> as soon as I removed some old vmlinuz's and so forth was when I hit
> this SIGSEGV(my guess is somewhere the system keeps account as to
> what is put into /boot.)
>
Probably. I don't use grubby (if needed, I write my own grub stanza).
You may have to use the source to find out.
Alright, so I can go ahead and remove grubby.
Justin P. Mattock