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] Official RH kernel documents, and load balancing
Date: Tue, 23 Sep 2003 01:00:38 +0000	[thread overview]
Message-ID: <marc-lartc-106427892610799@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106426463629736@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 3861 bytes --]

My kernel rebuilds:

1. Redhat Kernel Sources
# rpm -i  kernel-source-<version>src.rpm
# cd /usr/src/linux-<version>
# cp /boot/config-<oldversion> ./.config
# <edit> Makefile
Change extra version to the kernel version of your choice. If building 
on the existing kernel, sue the extra version defined for the 
distribution. I highly discourage doing this unless you are only 
compiling new modules into an existing kernel.
# make menuconfig
<selectr your options>
# make dep; make bzImage; make modules; make modules_install
# cp arch/<your arch>/boot/bzImage /boot/vmlinuz-<version>
Modify your boot loader include the new kernel. For EXT3 kernels, you 
need an extra step described below. RH8/9 {/boot/grub/grub.conf}

2. Kernel.org Sources
Same as above, but the first two steps are replaced with getting the 
kernel.org sources into that directory (pretty simple)

Making EXT3 support:

cd /boot/
mkdir tmp
cp init-<olderversion>.img init-<version>.gz
gunzip init-<version>.gz
mount -o loop init-<version> tmp
cd tmp/lib/
cp -f /lib/modules/<version>/kernel/fs/ext3/ext3.o .
cp -f /lib/modules/<version>/kernel/fs/jbd/jbd.o .
cd /boot
umount tmp
gzip init-<version>
mv init-<version>.gz init-<version>.img (you can leave this as .gz as 
long as you change /boot/grub/grub.conf to look for the .gz instead of 
the .img)

Alex wrote:

>I'm not sure what the document says, but after make bzImage && make modules
>&& make modules_install you can do a "make bzlilo" if you are using lilo as
>your boot loader and it will copy vmlinuz in /boot or just copy
>/usr/src/linux/arch/i386/boot/bzImage to /boot and then configure lilo or
>grub, whatever you have.
>
>btw, if you do "make bzlilo" it will work even if you have grub installed
>instead of lilo ( it will copy the thing to /boot but you will also see a
>error about lilo.conf, but nothing to worry about )
>
>Alex
>
>----- Original Message ----- 
>From: <carlosh@echos.co.nz>
>To: <lartc@mailman.ds9a.nl>
>Sent: Tuesday, September 23, 2003 12:09 AM
>Subject: [LARTC] Official RH kernel documents, and load balancing
>
>
>  
>
>>Hi:
>>
>>
>>I have an 'advanced-networking' problem. I want to have two interfaces to
>>the internet, apart from the internal one to the LAN.
>>
>>I came across this page:
>>
>>    
>>
>http://www.redhat.com/mirrors/LDP/HOWTO/Adv-Routing-HOWTO/lartc.rpdb.multipl
>  
>
>>e-links.html
>>
>>
>>and Julian's patches for the kernel published here:
>>http://www.ssi.bg/~ja/
>>and the How-to: http://www.ssi.bg/~ja/nano.txt
>>
>>
>>So, I downloaded the patch:
>>
>>routes-2.4.22-9.diff (December 14, 2001), and applied it to my 2.4
>>    
>>
>kernel...
>  
>
>>The kernel re-compile part was fine, following the instructions in :
>>
>>http://tldp.org/HOWTO/Kernel-HOWTO/
>>
>>
>>The issue is when I have to create a new initrd file.. it appears to
>>    
>>
>create
>  
>
>>a vmlinuz, not a bzImage as the kernel-howto document says.
>>
>>
>>So the new kernel does not boot...
>>
>>
>>Questions:
>>
>>Have anyone done this?
>>
>>I mean, having two connections to the Internet, using RH8.0 or RH 9.0, and
>>having them selecting (balancing) which interface to use to send packets
>>out, and receiving in either seamlessly and with NAT ?
>>
>>I think this functionality should be built in and available, instead of
>>having to patch the kernel?
>>
>>What would you guys recommend?
>>
>>
>>As for the initrd part, any suggestions? Is there an official RedHat
>>"re-build kernel" document?
>>
>>
>>
>>Thanks before-hand,
>>
>>Carlos
>>_______________________________________________
>>LARTC mailing list / LARTC@mailman.ds9a.nl
>>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>>    
>>
>
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>  
>

[-- Attachment #2: Type: text/html, Size: 5568 bytes --]

      parent reply	other threads:[~2003-09-23  1:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-22 21:09 [LARTC] Official RH kernel documents, and load balancing carlosh
2003-09-23  0:36 ` Alex
2003-09-23  1:00 ` Daniel Chemko [this message]

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-106427892610799@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