Re: How do you re- re- compile the kernel?
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
Re: How do you re- re- compile the kernel?
ONE MORE QUESTION! After considering what people have been telling me; in the directory /usr/src/linux-2.4/configs, which *.CONFIG file should I choose for default settings? I have an Intel PII MMX 400 MHz: kernel-2.4.9-i386.config kernel-2.4.9-i686.config ? Also, is the kernel-2.4.9-i386-BOOT.config just for making a floppy? --Humbly awaiting your collective *wisdom*... :) On Tuesday 04 December 2001 12:11 pm, I wrote: 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 ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
RE: How do you re- re- compile the kernel?
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
The i386 is the generic kernel that will work with a 386 and above.
kernel-2.4.9-12.i686.rpm
The i686 is for Pentium pro and above (PII, PIII, etc.)
kernel-headers-2.4.9-12.i386.rpm
Header files used for glibc. I believe that this package is going to be
renamed under the glibc-* packages
kernel-doc-2.4.9-12.i386.rpm
Obvious
kernel-source-2.4.9-12.i386.rpm
The kernel source (not to be confused with the source rpm {src.rpm}). This
installs the /usr/src/linux.2.4*
kernel-BOOT-2.4.2-2.i386.rpm
This is the kernel that they used to make the boot images on the CD/floppy.
Only valuable if you want to change those images.
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.
I believe that the original Pentium MMX processors (not PII) fit into the
i586 kernel.
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:
If you rpm -qpl *.rpm, it will show you all of the files that it will be
installing. E.g.
rpm -qpl kernel-headers-2.4.9-12.i386.rpm
/boot/kernel.h-2.4.9
/usr/include/asm
et cetera
If it is installed, just use rpm -ql (no p).
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.
When you install the kernel from kernel.org, it installs a linux directory.
If you are in /usr/src, this may overwrite the current kernel source,
including the libraries in that directory. If you did that, things may not
work very well. Red Hat got around that by making the symlink
/usr/src/linux-2.4. If you are careful, you can avoid problems. When there
was a /usr/src/linux symlink, I would remove the symlink, open the kernel
there, and rename the linux directory to linux-version, and recreate the
symlink.
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! ;-)
You can make the kernel-source install to a different directory, but I don't
think that you have to.
How about just doing it the way they say in the README, all
the way? Forget the RPM's?
Either way; you get to choose. If you don't need anything special compiled
into the kernel, you can safely use the Red Hat kernel rpms. If you want
special support, or you want to make a monolithic kernel, or you want to
only compile the modules/devices that you have, you can compile from the
tarball. Technically, you could get the kernel src.rpm, and change the
.config files to meet those needs, then rebuild the rpms, and install those,
but I think that it would be more that you want to do.
Forrest
TIA,
mVIIs
[EMAIL PROTECTED]
You are still using you @home.com e-mail address?
___
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: How do you re- re- compile the kernel?
If you are going to do a make mrproper you might want to save the /usr/src/linux-2.4/.config file first or you will lose whatever config you were trying to use. It doesn't make a difference what order you run make modules or make bzImage. Gerry On Mon, 3 Dec 2001, Ben Logan wrote: Hi, 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. Also, I don't know if this really matters, but everything I've read says to run 'make bzImage' before 'make modules'. Regards, Ben On Sun, Dec 02, 2001 at 10:17:23PM -0800, Mark Seven Smith wrote: I need USB support, so I was told to download the new RPM's for the kernel (linux-2.4.9-12 is what I found and used), and I used xconfig to set up the USB stuff (which was indeed off, if the default settings are what were being used normally). Anyway, that went fine--I also found that support for the parallel-port Iomega ZIP drive needed to be turn on... I went through and set a few things how I thought they should be set, according to what I understood from the HELP buttons in xconfig. Anyway, I did the rest of the stuff (make dep clean modules modules_install bzImage), and I got a bzImage file, and put it in /boot, calling it /boot/vmlinuz-2.4.9-13custom, and then did mkinitrd initrd-2.4.9-13custom.img 2.4.9-13custom. Then I fixed up LILO to boot the new kernel, and everything was fine! Except, it wasn't. Not only did my USB printer STILLNOT WORK, but my ZIP drive (which at least would be recognized!) wouldn't mount, because you have to specify the filesystem. OK, fine...but when I do, it says that the filesystem isn't supported! Now, in xconfig, there is a section I found where I could specify support for vfat filesystem (all my ZIP disks are formatted for this; so in order to mount them, even to convert them to ext2, I still need vfat ability). In the USB section too, I think I know what is wrong... Anyway, I went back in to xconfig (make xconfig), and re-did things how I figure they should be; and then did all the rest, just as I said above; but now I get errors (this is the last xth lines of output from the line of MAKEs, above, done the second time around): make[6]: Leaving directory `/usr/src/linux-2.4.9-12/drivers/mtd/nand' make[5]: Leaving directory `/usr/src/linux-2.4.9-12/drivers/mtd' make[4]: Leaving directory `/usr/src/linux-2.4.9-12/drivers/mtd' make -C net fastdep make[4]: Entering directory `/usr/src/linux-2.4.9-12/drivers/net' .loopback.o.flags:1: *** missing separator. Stop. make[4]: Leaving directory `/usr/src/linux-2.4.9-12/drivers/net' make[3]: *** [_sfdep_net] Error 2 make[3]: Leaving directory `/usr/src/linux-2.4.9-12/drivers' make[2]: *** [fastdep] Error 2 make[2]: Leaving directory `/usr/src/linux-2.4.9-12/drivers' make[1]: *** [_sfdep_drivers] Error 2 make[1]: Leaving directory `/usr/src/linux-2.4.9-12' make: *** [dep-files] Error 2 That [dep-files] Error 2 is the last line I get, no matter how I try to do this. AND, there is no /usr/src/linux-2.4/arch/i386/boot/bzImage file to be found! (not even the OLD one!) Any ideas? TIA, Mark VII [EMAIL PROTECTED] -- The lyfe so short, the craft so long to learne Chaucer ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
