Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Daniel Chemko" <dchemko@smgtec.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] IMQ Install Without Recompiling Kernel?
Date: Thu, 25 Sep 2003 20:42:25 +0000	[thread overview]
Message-ID: <marc-lartc-106452263703188@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106425949122992@msgid-missing>

>> 2) Why the sarcasm about not wanting to recompile the kernel? I love 
>> using Linux, and I have recompiled kernels before. However, in this 
>> application it may not be my best choice. You do not know my 
>> situation. I tried recompiling the kernel on this machine and had
much 
>> trouble with the particular SCSI card in that machine. However, I
felt 
>> this list was limited to routing issues and NOT kernel recompilation 
>> issues with a SCSI card.
>If this is a closed binary, you still can recomile the kernel with the
RH 
>kernel sources.  I did this before.  I wanted to use a closed source
binary 
>to access tape drives on my debian server.  I used the RH kernel
sources >and the module loaded without any problem.

I had problems with the DPT_I2O if that is what you are talking about.
You just have to remember to add the card's drivers to
initrd-<kernelver>.img (gzipped ext2 file system).

>> 3) My boss prefers that we stay with the stock RH kernel. If that is 
>> not possible then I will recompile, but only if absolutely necessary.
>I'm afraid a recompile is needed.

If the QOS stuff was compiled as a module, you don't even need to
reinstall the entire system, just the QOS sub-system (not tested with
QOS though). For example, with the kernel sources handy, you can patch
PPP - MPPE into a stock Redhat kernel by just running one of their
scripts. Two files from your existing system are changed, but everything
else is untouched.

My best bet without trying it is:
- Download and install the kernel-source RPM (not SRPM)
- # cp /boot/config-<currentkernel> /usr/src/linux-<version>/.config
This gives you the environment setup more or less how RedHat builds them
with, but without the RPM complexity.
- Edit /usr/src/linux-<version>/Makefile and remove the 'custom' tag
from the end of extraversion.
- # make menuconfig
Add the module that you need inside here
- # make dep; make modules
If all goes well, you should get to the end of modules without errors.
- Copy the module file that you added to the installation into the
module directory in /lib/modules.
- # depmod
If there are no errors here, you are home free.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-09-25 20:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 19:35 [LARTC] IMQ Install Without Recompiling Kernel? Walter D. Wyndroski
2003-09-23 19:29 ` Stef Coene
2003-09-23 19:36 ` David Boreham
2003-09-23 19:47 ` Stef Coene
2003-09-23 20:08 ` David Boreham
2003-09-23 23:35 ` Walter D. Wyndroski
2003-09-24 16:29 ` Stef Coene
2003-09-24 16:40 ` David Boreham
2003-09-24 23:30 ` Damjan
2003-09-25 19:39 ` Walter D. Wyndroski
2003-09-25 19:51 ` Walter D. Wyndroski
2003-09-25 20:14 ` Stef Coene
2003-09-25 20:26 ` David Boreham
2003-09-25 20:42 ` Daniel Chemko [this message]
2003-09-28 22:51 ` Walter D. Wyndroski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-106452263703188@msgid-missing \
    --to=dchemko@smgtec.com \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox