[rhn-users] kernel-devel

[David A. Ranch]

The kernel is just another package to up2date so it won't matter.  For
that matter, up2date is configured to IGNORE kernel updates by default.

--David

> Hi, regarding step 1. If for example I build the new kernel 'called
> 2.6.15-prep'. Install it; how does up2date update the various software
> components when the kernel name is non-standard?
>
> Also, could I just Modify the 'Makefile' to have the same name as the
> running kernel, and just do a make modules;make modules_install?
>
> Thx jason
>
>
> -----Original Message-----
> From: rhn-users-bounces at redhat.com [mailto:rhn-users-bounces at redhat.com]
> On Behalf Of David A. Ranch
> Sent: Saturday, March 04, 2006 12:22 PM
> To: Red Hat Network Users List
> Subject: Re: [rhn-users] kernel-devel
>
>
> When you install the kernel-src.rpm, these sources come with a kernel
> .config file that Redhat used to compile that specific kernel up.  With
> that said, you can occasionally compile new kernel components against
> this SRC tree and only install those few modules vs. everything as long
> as all of the code dependencies are met.  I personally don't recommend
> this approach.  For example, you won't be able to compile in new SCSI
> controller into the kernel unless the base kernel already had base SCSI
> support turned on.  Make sense?  For your netfilter example, I'd
> recommend to do the following:
>
>   1. install the kernel src.rpm for your RUNNING kernel version
>   2. make sure that in the top of the kernel's Makefile, the "NAME="
> variable is something unique
>   3. Apply your patches to the kernel
>   4. Make the entire kernel and all modules
>   5. make install everything which will create a NEW kernel for you
>   6. Update your LILO or Grub to boot this new kernel
>   7. Reboot and use the new kernel.  If it works, good! If not, you can
> fall back to the stock RH kernel
>
>
> Why patch the kernel sources at all?  Maybe there is a bug fix available
> for the kernel but Redhat hasn't released an official binary yet.  Or
> maybe you have a new piece of HW that the stock Redhat kernel doesn't
> support but the vendor offers RHEL drivers.  If you patch the Redhat
> sources, you'll then have an official Redhat kernel with the drivers you
> require.
>
>
> --David
>
>
> Jason Sigurdur wrote:
>   
>> Hi, what exactly is a 'configured source'? This is something that is
>> provided by the kernel-devel package. How does it fullfile
>>     
> requirements
>   
>> for building modules without the kernel source package?
>>
>> Why must one 'patch' the kernel "requiring the kernel source tree" for
>> modules? Is it not the porpose of the kernel-devel package to build
>> modules with out the kernel-source?
>>
>> For example; I would like to install a new netfilter module. Why must
>> one patch the kernel then go throught a make modules and make
>> modules_install?
>>
>> Thx confused
>>
>> jason
>>
>> _______________________________________________
>> rhn-users mailing list
>> rhn-users at redhat.com
>> https://www.redhat.com/mailman/listinfo/rhn-users
>>   
>>     
>
> _______________________________________________
> rhn-users mailing list
> rhn-users at redhat.com
> https://www.redhat.com/mailman/listinfo/rhn-users
>
> _______________________________________________
> rhn-users mailing list
> rhn-users at redhat.com
> https://www.redhat.com/mailman/listinfo/rhn-users
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/rhn-users/attachments/20060306/29d16063/attachment.htm>