> Go to ftp://ftp.kernel.org, and download and install the newest kernel > (2.4.18 I think). Supposing you download it to > /usr/src/linux-2.4.18.tar.gz. Create a directory called > /usr/src/linux-2.4.18. cd to it, then type 'gzip -dc > ../linux-2.4.18.tar.gz | tar -xf -' to unpack it. > > It creates a folder called linux, in which the source lies. So the source > for your new kernel should be in /usr/src/linux-2.4.18/linux/. Cd to that > directory. Type 'make menuconfig' and you'll go through all of the MANY > choices to make a new kernel. Then you'll do a 'make dep' then a 'make > bzImage' then a 'make modules' then a 'make modules_install'. Well, a better way, even though no biggie, would be to enter '/etc/src', delete the 'linux' link (rm linux), untar the kernel ('tar zxvf /tmp/linux-2.4.18.tar.gz' (if you downloaded it to /tmp that is), and when the kernel is untared, you move the new linux folder (which at this point isn't a link) with 'mv linux linux-2.4.18' and then make a new 'linux' link to the new kernel folder, like this: 'ln -s linux-2.4.18 linux'.
then the usual commands to build a new kernel is: make menuconfig make dep make bzImage make modules make modules_install or the way I like to do it: make dep && make bzImage && make modules && make modules_install This way it all gets done and I don't have to do anything until it's done. Then it's just to move the '/usr/src/linux/arch/i386/boot/bzImage' to '/boot/kernel-2.4.18' and edit '/etc/lilo.conf' If you don't make it the first time (eg. doesn't get the kernel right), you should remember to run 'make mrproper' before 'make menuconfig' so you are sure you remove all "bad" files, including the helper files and such (which make clean doesn't remove). /Christopher Thorjussen > > When you get through all that, it'll create a file named > /usr/src/linux-2.4.18/linux/arch/i386/boot/bzImage. This is your new > kernel, and why it hides it away in that subdirectory is beyond me, > considering creating it was the goal of all this! Copy this file to /boot, > and integrate as a new OPTION in your boot loader (probably LILO or GRUB). > The important thing is that you don't just replace your current kernel with > this one, but just give yourself the option of booting to either. That's > what will make this easy to back out of. There are existing, very good > docs on all of this at www.linuxdoc.org. > > You'll likely not quite get the kernel right the first time, but it's not a > big deal because when you go back to 'make menuconfig' it will have > remembered all of your previous choices, so you'll only have to make your > revisions. The on-line help during make menuconfig is also pretty good. > > Once you've done this a few time, you'll be able to fly through the menus > in a couple of menus. > > Good luck! > Ted > > --On Monday, March 11, 2002 5:26 PM -0800 Ralph Wiggums > <[EMAIL PROTECTED]> wrote: > > > > > > > I have been 'roughly' following this link, but i do have questions that > > hopefully someone can help me out with. (the Oskar Andreasson Tutorial) > > http://www.linuxsecurity.com/resource_files/firewalls/IPTables-Tutorial/i > > ptables-tutorial/iptables-tutorial.html#INSTALL_RH71 > > > > > > ok, these are the sequential steps i followed and i'm not having any > > sucess. > > > > -I downloaded iptables-1.2.5 from netfilter. (to my internet downloads > > partition) -I unpacked with bzip2 -cd iptables-1.2.5.tar.bz2 | tar -xvf - > > > > -I made the package: make KERNEL_DIR=/boot/vmlinux > > and make install KERNEL_DIR=/boot/vmlinux > > > > > > -i made sure ipchains was off. > > chkconfig --level 0123456 ipchains off > > > > > > -i made sure the service was stopped. (which doesn't really matter > > because 'ipchains' is not compitible with my kernel so it won't work > > anyway.) service ipchains stop > > > > > > -i ran 'modprobe ip_tables' and 'modprobe iptable_nat' to test the > > initial iptables-1.2.5 installation > > > > and 'lsmod' to see the modules were loaded, they seem to be there. > > > > Now to make iptables run i tried: > > chkconfig --level 235 iptables on > > -which produced 'iptables not found'? > > > > -so of course i could not start it as well: > > service iptables start > > :'iptables not found' > > > > > > -Now, does this just mean that iptables is not in my 'path'. I though > > when i 'make' a package is it automatically made in /sbin or where is > > 'should' be made, is this true? i don't really want it (ipchains) to > > reside where it currently is, where i 'unpacked it', on my 'internet > > downloads' partition. > > > > > > > >> From what i understand my kernel is already compiled to run 'iptables', > >> i run Yellow dog Linux 2.1 kernel 2.4.10-12a - but if not i have never > >> compilied a kernel and i would rather save some fun for later ;-) (i've > >> only been running linux a short time but i have a cable provider and > >> really need a decent firewall - hence iptables) > > > > thanks in advance for all your help. > > > > -ralph > > > > _____________________________________________________________ > > Get your spam-free, Linux email now --> http://www.LinuxWaves.com > > Join Linux discussions --> http://Community.LinuxWaves.com > > > > _____________________________________________________________ > > Run a small business? Then you need professional email like > > [EMAIL PROTECTED] from Everyone.net http://www.everyone.net?tag > > > > > > > > >
