On Monday 03 December 2001 03:01 am, Ben wrote: > I've compiled several kernels recently and had to do it > more than once (the first time, I forgot and left PPP > support out :). Looking at the README, I think you might > need to run 'make mrproper' _before_ running xconfig.
Thanks; I was reading everything I could find, but I completely missed anything about "mrproper"... > Also, I don't know if this really matters, but everything > I've read says to run 'make bzImage' before 'make > modules'. In the command line I'm using, "bzImage" is the last item specified, and I presume the last MAKE to be performed, I would guess: "make dep clean modules modules_install bzImage" ONE THING that is bugging me, however: Red Hat's "Red Hat Package Manager"! Whenever RPM's are involved, (and that is ALWAYS), I never understand what is really happening: I've been using Linux for over a year now, and I still feel like a newcomer! What RPM's are you supposed to download and use, when compiling a kernel? are you SUPPOSED to use the RPM that says "src" in it? And what are all those OTHERS for? kernel-2.4.9-12.i386.rpm kernel-2.4.9-12.i686.rpm kernel-headers-2.4.9-12.i386.rpm kernel-doc-2.4.9-12.i386.rpm kernel-source-2.4.9-12.i386.rpm kernel-BOOT-2.4.2-2.i386.rpm kernel-pcmcia-cs-3.1.24-2.i386.rpm kernel-smp-2.4.2-2.i586.rpm kernel-enterprise-2.4.2-2.i686.rpm kernel-smp-2.4.2-2.i686.rpm Now, I can see that I do not need to have anything to do with the last four; I don't have any pcmcia stuff, no extra processors, and I don't live on a starsip ;-) But the first two: what do I do about those? I was reading that the Intel PII MMX processor (mine's 400 MHz) should properly be considered a 686 (as opposed to a 586); this was being said for the first section of the make xconfig, where you specify which processor you have. Anyway, when you "rpm" these packages, how do you know what is going where? In the /usr/src/linux-2.4/README, under the part about "INSTALLING the kernel": "Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be." How does this apply to the RPM's, which seem to have CREATED this area in the first place? Is there a way to "force" the RPM to unpack in another place, or should this be ignored? I am reading, and trying to learn more & more about this as I go, but I sometimes get bogged down in all the details (I'm sure you've noticed! ;-) How about just doing it the way they say in the README, all the way? Forget the RPM's? TIA, mVIIs [EMAIL PROTECTED] _______________________________________________ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
