Agreeing with Corey... You would just need to have a dev/test system where you can build the module for the specific kernel you are targeting, then can either just copy the module around as required, or bundle it in a custom RPM... Marco On Thu, Jul 12, 2012 at 10:38 AM, Corey Kovacs <corey.kovacs@xxxxxxxxx> wrote: > It certainly is. As long as you package the module for a specific kernel > and enforce adherence you should be fine. If an upgraded kernel is > required, then you'll need to rebuild the module rpm and upgrade that as > well. You'd simply need to have the module rpm require the specific kernel, > and place the binary module in the /lib/modules/<uname -r> dir structure. > > There isn't much you can't package using rpm. I've seen a demo of creating > an rpm for an installed baseline oracle instance. You have to know what > oracle is doing and why, but if you have that, it's tedious but not too > hard to package third party stuff. > > -C > > > > On Thu, Jul 12, 2012 at 7:23 AM, Parvez Shaikh <parvez.h.shaikh@xxxxxxxxx>wrote: > >> Hi all, >> >> We're using RHEL 5.5. Uname -a gives following output - >> >> Linux xxxxx 2.6.18-194.3.1.el5 #1 SMP Fri May 7 01:43:09 EDT 2010 x86_64 >> x86_64 x86_64 GNU/Linux >> >> We want to use TIPC on this and for this we need to build TIPC kernel >> module, insert module whenever needed. >> >> The question I have is, is it possible to ship kernel modules as rpms? >> >> How to ship pre-built kernel modules without having to build them on target >> machines? >> >> Thanks, >> Parvez >> -- >> redhat-list mailing list >> unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe >> https://www.redhat.com/mailman/listinfo/redhat-list >> > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe > https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
