> -----Original Message----- > From: plug-discuss-admin@lists.plug.phoenix.az.us > [mailto:plug-discuss-admin@lists.plug.phoenix.az.us]On Behalf Of foodog > Sent: Saturday, May 26, 2001 11:13 AM > To: plug-discuss@lists.plug.phoenix.az.us > Subject: Re: More Kernel 2.4 Q's > > > Craig, I'm waiting for your answers too. I tried to build a new RH 7.1 > kernel to include IPX support but that portion's broken. I found some > online discussion of it, including a kernel patch but it's not RH > specific. IIRC, it's a fix for 2.4-3 instead of 2.4-2 (plus I've never > done kernel patch voodoo). > > I think I can help with #4. After I hose everything up, 'make mrproper' > *seems* to reset to the defaults. > > I've got a pretty sad record of getting a new kernel *and* the modules > to work. I've occasionally just built everything I need into the > kernel. I use the same build sequence, FWIW: make menuconfig followed > by dep, clean, bzImage, modules, modules_install, install. Also > experimented a bit with the linuxconf 'install new kernel' thing > followed by lilo instead of 'make install'. > > I hope someday to find kernel docs starting with "If you follow these > instructions it will always work..." :-) > ---- I found some answers on the seawolf mailing list @ redhat - see below - seems to answer most of my questions 2 thru 7 - still looking for takers on 1 & 8. Also apparently ipchains load as a module of iptables which is why other modules previously used by ipchains - namely the ip_masq_ftp, ip_masq_irc etc...won't work - and of course the ipmasqadm doesn't work either. So new question is anyone doing port forwarding with iptables yet? -- Clipped from https://listman.redhat.com/pipermail/seawolf-list/ --- >> > Or edit the top level Makerfile and change the >> > EXTRAVERSION line so the modules will install in >> > different directory, and the old ones remain >> > usable with the old kernel. >> >> No no no ... this can make patches fail to apply. >> >> Run the make command(s) with "EXTRAVERSION=-foo" on the command line >> instead (to give you vmlinuz-2.4.x-foo, say). > >Interesting! Can you give an example? where would this go in: > ># make dep clean bzImage modules modules_install make EXTRAVERSION=-foo menuconfig make EXTRAVERSION=-foo dep bzImage modules modules_install make clean isn't necessary from a fresh untar. Also, if it is on SMP, use make -j2 or make -j4, etc.. Craig