Re: [gentoo-user] What creates System.map, config and vmlinuz?
On Wednesday 17 September 2003 07:34, Yuri Enshin wrote:
Just use installkernel script from sys-apps/debianutils (AFAIK, this
package are in 'system', so installed automaticaly while initial
install) after make {bzImage,modules,modules_install}.
And at least on i386 arch this is called by the install target.
--
Jesper
11:24:32 up 16:29, 1 user, load average: 0.08, 0.06, 0.07
--
[EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
You're welcome. On Mon, 15 Sep 2003 19:30:31 -0700 Mark Knecht [EMAIL PROTECTED] wrote: On Mon, 2003-09-15 at 19:06, Brett I.Holcomb wrote: You haven't made a mistake. Brett Collins. You say mistake. Actually, this is one very nice feature of Gentoo vs. Redhat. In Redhat /boot was always mounted, so if I made a mistake and ran 'make install' I could overwrite an existing kernel. I like having to mount /boot by hand when I'm ready to copy it, just like you. Yes, I like it too. It's part of what I like about Gentoo! Got it. Thanks. As Collins pointed out, and I checked it to be true, System.map is created and is in /usr/src/linux after my build, so that is answered. If I would have bothered to edit the config file in /boot I would have figured out that is is the .config file used when I built the kernel. I suppose again that 'make install' copies it over. I could do that by hand also. It must be a copy of .config from /usr/src/linux. It's not recommended to edit this by hand. Use make menuconfig to do this. So, actually, thanks very much for helping clear up a few small mysteries for me today. I've been building kernels off and on for a while, but since moving my home studio main desktop machine, first from Win XP and then from Redhat, to Gentoo I've gotten more attuned to build code much more often. Under Redhat I built very little code. Gentoo is a different experience. Yes, Gentoo is a very nice experience! If you want you can really learn about Linux with it. Thanks much, Mark You're welcome! -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
Mark Knecht wrote:
QUESTION 2: What is the process to create these files if I want them?
Just use installkernel script from sys-apps/debianutils (AFAIK, this
package are in 'system', so installed automaticaly while initial
install) after make {bzImage,modules,modules_install}.
This script:
1) Copy your bzImage, System.map and .config to /boot and name this
files as vmlinuz-version, System.map-version, config-version (ex.
vmlinuz-2.4.20-gentoo-r5 etc.)
2) Make the symlinks to this files (vmlinuz-vmlinuz-2.4.20-gentoo-r5,
System.map-System.map-2.4.20-gentoo-r5, ...)
3) If symlinks already exists, rename old symlinls to name.old
4) Check for lilo presence and, if lilo present, run lilo to reflect
kernel changes
So, if you use this script, symlink 'vmlinuz' in your /boot directory
always point to latest installed kernel, and 'vmlinuz.old' - to previus
kernel version. Also, 'System.map' point to System.map for latest
kernel, and 'System.map.old' - for previous, and some theme for kernel
config files (.config). And then your install new kernel, this simlinks
just 'shifted' for new version. This way, you don't need change anything
in bootloader config file - you once setup two boot menu items for
newest and old kernel and this items always work.
--
[EMAIL PROTECTED] mailing list
[gentoo-user] What creates System.map, config and vmlinuz?
Hi, I've never received an answer for these question in the Redhat reflectors, and never asked here. Please excuse my ignorance on this subject. I just did a kernel build of gentoo-sources-2.4.20-r7 by hand (make dep clean bzImage modules modules_install then copy bzImage to /boot by hand) and I do not get the System.map, config and vmlinuz files in /boot. However, I apparently did a build of 2.4.20-r5 some other way (possibly make install?) and these files, plus their links were created. QUESTION 1: What do these files do, and are they necessary? QUESTION 2: What is the process to create these files if I want them? QUESTION 3: What is the difference between booting from a vmlinuz file and a bzImage file? QUESTION 4: Does having these -r5 files impact running -r7 if the -r7 versions don't exist and the links point to the -r5 versions? Thanks, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
On Mon, 15 Sep 2003 09:57:12 -0700 Mark Knecht [EMAIL PROTECTED] wrote: Hi, I've never received an answer for these question in the Redhat reflectors, and never asked here. Please excuse my ignorance on this subject. I just did a kernel build of gentoo-sources-2.4.20-r7 by hand (make dep clean bzImage modules modules_install then copy bzImage to /boot by hand) and I do not get the System.map, config and vmlinuz files in /boot. However, I apparently did a build of 2.4.20-r5 some other way (possibly make install?) and these files, plus their links were created. QUESTION 1: What do these files do, and are they necessary? The vmlinuz and bzImage (or other names) in /boot are the kernel used for booting. The System.map files (optional) are really only needed to interpret dumps if your kernel craps out. QUESTION 2: What is the process to create these files if I want them? You must build a new kernel to create these files, then copy them from the /usr/src/linux/ location to /boot. Ask again, if you don't know how to build a kernel, or still betterm RTFM (google, gentoo documentation, redhat documentation, etc., etc.). QUESTION 3: What is the difference between booting from a vmlinuz file and a bzImage file? There is no difference; the names are whatever you pick. The kernel build process creates/usr/src/linux.../System.map (symbols map) and /usr/src/linux.../arch/i386/boot/bzImage (bootable kernel). You then copy these files to /boot and name them whatever you like, example /boot/System-map-latest and /boot/bzImage-latest. Then you update your grub or lilo boot loader controls to allow boot from the /boot/bzImage-latest. Many people like to include symlinks ln -s /boot/System.map-latest /boot/System.map and ln -s /boot/bzImage-lastest /boot/vmlinuz QUESTION 4: Does having these -r5 files impact running -r7 if the -r7 versions don't exist and the links point to the -r5 versions? There is absolutely no impact in having mulitple map and kernel files on /boot. You must specify the appropriate kernel name in a stanza in your boot manager (grub or lilo), and you may have multiple choices. The only problem you are likely to encounter is with modules when you are using something like nvidia which installs for a particular kernel release only. Enjoy, -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
Hi Mark, I'm, not an expert with this, but I'll try... Am Montag, 15. September 2003 18:57 schrieb Mark Knecht: Hi, I've never received an answer for these question in the Redhat reflectors, and never asked here. Please excuse my ignorance on this subject. I just did a kernel build of gentoo-sources-2.4.20-r7 by hand (make dep clean bzImage modules modules_install then copy bzImage to /boot by hand) and I do not get the System.map, config and vmlinuz files in /boot. However, I apparently did a build of 2.4.20-r5 some other way (possibly make install?) and these files, plus their links were created. I think, there is a make bzlilo. Maybe you used this one? QUESTION 1: What do these files do, and are they necessary? Afaik system.map is created and needed by your bootmanager (lilo?). vmlinuz is your kernel or a symlink to it. I dont know what config could be. I don't have this file and my machine boots quite good. I use grub now, but I had lilo installed before. QUESTION 2: What is the process to create these files if I want them? vmlinuz is created by you, when you copy your kernel after compiling with cp arch/i386/boot/bzImage /boot/vmlinuz. Maybe make bzlilo does that for you, I never used this. System.map is created by your bootloader, when you install it (call /sbin/lilo, setup in grup?). QUESTION 3: What is the difference between booting from a vmlinuz file and a bzImage file? There is none. It's just the name of your kernelimage. QUESTION 4: Does having these -r5 files impact running -r7 if the -r7 versions don't exist and the links point to the -r5 versions? No, if you have a section in the configfile of your bootloader, that starts the -r7 kernel. Don't forget to call /sbin/lilo, if you use lilo (/boot mounted). After that there should be a System.map. Thanks, Mark Hand Michael -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
They are created during a kernel build (make dep make ). vmlinuz is a linux kernel. Some distros use this while others use bzImage. Wen I move bzImage to /boot I usually rename the Gentoo bzImage to vmlinuz-x.y.z where x.y.z is a version such as 2.4.20. I'm just used to seeing vmlinuz due to past experience. System.Map contains symbols used for debugging as far as I know. You probably can live without it as I've had System.map for kernel x when I'm running kernel y. LILO records the location of the kernel - vmlinuz, or whatever you named it. On Monday 15 September 2003 17:10, you wrote: Hi Mark, I'm, not an expert with this, but I'll try... Am Montag, 15. September 2003 18:57 schrieb Mark Knecht: Hi, I've never received an answer for these question in the Redhat reflectors, and never asked here. Please excuse my ignorance on this subject. I just did a kernel build of gentoo-sources-2.4.20-r7 by hand (make dep clean bzImage modules modules_install then copy bzImage to /boot by hand) and I do not get the System.map, config and vmlinuz files in /boot. However, I apparently did a build of 2.4.20-r5 some other way (possibly make install?) and these files, plus their links were created. I think, there is a make bzlilo. Maybe you used this one? QUESTION 1: What do these files do, and are they necessary? Afaik system.map is created and needed by your bootmanager (lilo?). vmlinuz is your kernel or a symlink to it. I dont know what config could be. I don't have this file and my machine boots quite good. I use grub now, but I had lilo installed before. QUESTION 2: What is the process to create these files if I want them? vmlinuz is created by you, when you copy your kernel after compiling with cp arch/i386/boot/bzImage /boot/vmlinuz. Maybe make bzlilo does that for you, I never used this. System.map is created by your bootloader, when you install it (call /sbin/lilo, setup in grup?). QUESTION 3: What is the difference between booting from a vmlinuz file and a bzImage file? There is none. It's just the name of your kernelimage. QUESTION 4: Does having these -r5 files impact running -r7 if the -r7 versions don't exist and the links point to the -r5 versions? No, if you have a section in the configfile of your bootloader, that starts the -r7 kernel. Don't forget to call /sbin/lilo, if you use lilo (/boot mounted). After that there should be a System.map. Thanks, Mark Hand Michael -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
I'm not too knowledgable in this area but I'm pretty sure the other two answers you've got so far are (in part) wrong. I did my first x86 install and kernel build the other day and found this info myself after trying to figure out why the x86 and ppc kernel procedures were different. (So I can confirm that all this is just a short google away. :-) * Mark Knecht [EMAIL PROTECTED] [2003-09-15 09:57]: I just did a kernel build of gentoo-sources-2.4.20-r7 by hand (make dep clean bzImage modules modules_install then copy bzImage to /boot by hand) and I do not get the System.map, config and vmlinuz files in /boot. However, QUESTION 1: What do these files do, and are they necessary? vmlinux is your kernel. Often necessary. System.map is the symbol map and is necessary. bzImage is a compressed file that contains both. (So you use it instead of the others.) QUESTION 2: What is the process to create these files if I want them? Do `make vmlinux` instead of `make bzImage` - they should be in the source root. (They may actually be there after doing make bzImage - have a look - but that's what you do if you don't want the compressed image.) QUESTION 3: What is the difference between booting from a vmlinuz file and a bzImage file? As far as your system once it's booted - nothing. But (this is an educated guess here, someone correct me if I'm wrong) you're more likely to run out of memory during boot without the compression due to the excellent design of the peecee architecture. :-) QUESTION 4: Does having these -r5 files impact running -r7 if the -r7 versions don't exist and the links point to the -r5 versions? No. Cheers David -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
Thus spake David Friggens on Mon, Sep 15, 2003 at 04:57:22PM CDT * Mark Knecht [EMAIL PROTECTED] [2003-09-15 09:57]: I just did a kernel build of gentoo-sources-2.4.20-r7 by hand (make dep clean bzImage modules modules_install then copy bzImage to /boot by hand) and I do not get the System.map, config and vmlinuz files in /boot. However, QUESTION 1: What do these files do, and are they necessary? vmlinux is your kernel. Often necessary. System.map is the symbol map and is necessary. bzImage is a compressed file that contains both. (So you use it instead of the others.) bzImage doesn't contain the system symbol map, but the symbol map is frequently used to translate numeric locations in bzImage into symbol names for debugging purposes. System.map isn't required. The file /usr/src/linux/arch/xxx/boot/bzImage gets copied, usually, to /boot/vmlinuz when one builds a kernel, so they're the same file, really. /boot/vmlinuz (if it's the working kernel image) is _always_ required. bzImage in the kernel build tree is only generated when one builds a kernel, and can be deleted. QUESTION 2: What is the process to create these files if I want them? Do `make vmlinux` instead of `make bzImage` - they should be in the source root. (They may actually be there after doing make bzImage - have a look - but that's what you do if you don't want the compressed image.) You don't need the uncompressed kernel. The proper sequence of commands (or one of them) to create a new kernel is as follows: cd /usr/src/linux[assuming this is the base of your kernel source tree] make menuconfig [set things the way you want them] make dep make clean make bzImage modules make modules_install cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-whatever You may need to dicker with your lilo or grub config file to reference your new kernel, and if you use lilo, you'll need to run it to update the boot info. -- Lindsay Haisley | Everything works| PGP public key FMP Computer Services | if you let it | available at 512-259-1190 |(The Roadie) | http://www.fmp.com/pubkeys http://www.fmp.com| | -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
* Lindsay Haisley [EMAIL PROTECTED] [2003-09-15 17:40]: Thus spake David Friggens on Mon, Sep 15, 2003 at 04:57:22PM CDT * Mark Knecht [EMAIL PROTECTED] [2003-09-15 09:57]: OK, I've got my wires crossed a bit. Mark - you can pretty much ignore what I said. :-) I started to do a bit more googling, but the firewall I'm currently behind has just died. No more web surfing for a while... and I do not get the System.map, config and vmlinuz files in /boot. However, vmlinux is your kernel. Often necessary. System.map is the symbol map and I hadn't come across vmlinuz, so I just assumed it was a typo for vmlinux. Before the firewall died I came across this: If you find a file name 'vmlinux' in the top directory of the source tree, just ignore it. This is an intermediate file and you can't boot from it. [ http://www.cs.helsinki.fi/linux/linux-kernel/2001-51/0088.html ] But you can on ppc and sparc... :-) bzImage doesn't contain the system symbol map, but the symbol map is I'm sure I read that it does. I'll assume I'm wrong as I wait to track down my source later on. /boot/vmlinuz (if it's the working kernel image) is _always_ required. Sorry, I meant to put a :-) after saying the kernel is often required. Cheers David -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
* David Friggens [EMAIL PROTECTED] [2003-09-16 11:16]: * Lindsay Haisley [EMAIL PROTECTED] [2003-09-15 17:40]: bzImage doesn't contain the system symbol map, but the symbol map is I'm sure I read that it does. I'll assume I'm wrong as I wait to track down my source later on. OK, firewall's back up and after some Googling it appears I that I'm not hallucinating about what I read. But... I couldn't find the original thing I read, but I came across some discussion on the the Linux Kernel Mailing List entitled Re: zImage now holds vmlinux, System.map and config in sections. (fwd). Starting here: http://www.ussg.iu.edu/hypermail/linux/kernel/0302.3/0203.html with threaded replies starting here: http://www.ussg.iu.edu/hypermail/linux/kernel/0302.3/0382.html The discussion wasn't complete, so I'm still a little confused but the following quote indicates that maybe it's not relevant to x86. Well, then it doesn't have sections. As far as I could see the original post only applied to architectures for which zImage is an ELF binary. Similarly, this will not exist on x86/x86-64 where the (b)zImage is mostly a binary blob. David -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
On Mon, 2003-09-15 at 15:40, Lindsay Haisley wrote: bzImage doesn't contain the system symbol map, but the symbol map is frequently used to translate numeric locations in bzImage into symbol names for debugging purposes. System.map isn't required. The file /usr/src/linux/arch/xxx/boot/bzImage gets copied, usually, to /boot/vmlinuz when one builds a kernel, so they're the same file, really. OK, so for a couple of years I've made a consistent 'mistake' because I almost always do this copy by hand, but I never rename it. So the bzImage files in my /boot directory, by convention, should really be named vmlinuz, but I haven't been doing that. My grub.conf file is of course consistent with this copy mistake showing that I boot a bunch of files called bzImage-xxx, and the machine certainly does boot, but I'll follow the convention from now on. Thanks. /boot/vmlinuz (if it's the working kernel image) is _always_ required. bzImage in the kernel build tree is only generated when one builds a kernel, and can be deleted. Sure. Makes sense. QUESTION 2: What is the process to create these files if I want them? Do `make vmlinux` instead of `make bzImage` - they should be in the source root. (They may actually be there after doing make bzImage - have a look - but that's what you do if you don't want the compressed image.) Does 'make vmlinuz' make an uncompressed kernel? You don't need the uncompressed kernel. The proper sequence of commands (or one of them) to create a new kernel is as follows: cd /usr/src/linux[assuming this is the base of your kernel source tree] make menuconfig [set things the way you want them] make dep make clean make bzImage modules make modules_install cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-whatever I'm sorry for not being clearer. The above steps, other than the second name in the last cp command, are what I always do. That was not what drop 2/3's of my question. You've now explained why I had bzImage files and had this one vmlinuz file. That's cool, but that's only 1/3. The other 2/3's are where do the System.map and config files come from? If they are created by the above set of steps, then are they under /usr/src/linux somewhere after I've built the kernel? Or are they only created if you do some other step not listed above? (If so, what's the step? The only other one I know of is to do 'make install' instead of the copy by hand. Maybe there is a 'make System.map' step or something I've never heard of. Thanks much to you, and also to Brett, Collins and Dived for their responses also. Cheers, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
You haven't made a mistake. You can name them anything you want so long as the lilo.conf or grub conf files have the right name. Distros like Caldera used vmlinuz for the kernel name, Gentoo has bzImage. I name mine vmlinuz-2.4.20-XFS for example or vmlinuz-2.4.20-XFS-test - it helps me keep them straight. However, LILO or Grub has to know about them. My /etc/lilo.conf has three enteries Gentoo boots vmlinuz-2.4.20-XFS Test boots vmlinuz-2.2.20-XFS Memtest boots memtest/memtest.bin What happens is a kernel build creates bzImage in the /usr/src/linux directory tree. Then the docs tell you to copy it to /boot. I copy and rename it because I like vmlinuz. The name makes no difference. As far as Gentoo goes - at least the last builds I did - the kernel wasn't copied but if it is feel free to rename it. However, I don't mount /boot until I'm ready to copy to it. When the kernel is built the System.map file is also built. If you want copy it to /boot too. It provides symbols for debuggin. I've run with a System.map that was built several kernel builds ago - however, I don't do debugging G All you need is the bzImage (or whatever you call it) and to tell LILO or Grub about it and you can boot. Many of the rest of the files come from LILO or grub On Monday 15 September 2003 21:31, you wrote: On Mon, 2003-09-15 at 15:40, Lindsay Haisley wrote: OK, so for a couple of years I've made a consistent 'mistake' because I almost always do this copy by hand, but I never rename it. So the bzImage files in my /boot directory, by convention, should really be named vmlinuz, but I haven't been doing that. My grub.conf file is of course consistent with this copy mistake showing that I boot a bunch of files called bzImage-xxx, and the machine certainly does boot, but I'll follow the convention from now on. Thanks. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
On Mon, 15 Sep 2003 18:31:46 -0700 Mark Knecht [EMAIL PROTECTED] wrote: On Mon, 2003-09-15 at 15:40, Lindsay Haisley wrote: bzImage doesn't contain the system symbol map, but the symbol map is frequently used to translate numeric locations in bzImage into symbol names for debugging purposes. System.map isn't required. The file /usr/src/linux/arch/xxx/boot/bzImage gets copied, usually, to /boot/vmlinuz when one builds a kernel, so they're the same file, really. OK, so for a couple of years I've made a consistent 'mistake' because I almost always do this copy by hand, but I never rename it. So the bzImage files in my /boot directory, by convention, should really be named vmlinuz, but I haven't been doing that. No mistake, my friend. What you name the copy of the generated kernel on /boot is totally immaterial (read that statement again). The only thing that matters is that your grub or lilo info matches the name you chose. You may have many kernel images in /boot. Even if you name the kernal junk,, if you call it junk in your lilo/grub references, it's cool. The other 2/3's are where do the System.map and config files come from? If they are created by the above set of steps, then are they under /usr/src/linux somewhere after I've built the kernel? The System.map (always this name) is always generated in the top level directory of the kernel source tree (/usr/src/linux.../). You can optionally copy it to /boot and give it any name. Your system will not run better or worse without a System.map file in /boot. An example, here is a lysting of my files in /boot lrwxrwxrwx1 root root 22 Sep 10 07:35 System.map - System.map-2.6.0-test5 -rw-r--r--1 root root 582820 Jul 4 08:26 System.map-2.4.20-r5 -rw-r--r--1 root root 834050 Aug 6 21:09 System.map-2.6.0-test2 -rw-r--r--1 root root 861825 Aug 29 21:02 System.map-2.6.0-test3-ip -rw-r--r--1 root root 868095 Sep 10 07:34 System.map-2.6.0-test5 ... lrwxr-xr-x1 root root 17 Jul 27 16:47 bzImage - bzImage-2.4.20-r5 -rw-r--r--1 root root 1209213 Jul 4 08:26 bzImage-2.4.20-r5 -rw-r--r--1 root root 2127731 Aug 6 21:09 bzImage-2.6.0-test2 -rw-r--r--1 root root 2302783 Aug 29 21:02 bzImage-2.6.0-test3-ip -rw-r--r--1 root root 2315221 Sep 10 07:34 bzImage-2.6.0-test5 Currently, I'm only using bzImage-2.6.0-test5; the other names are just leftover baggage. You can see a steady progression from my last 2.4 kernel through current. the ...test3-ip kernel was the first to contain all the necessary additions to run the shorewall firewall. A side note: I've never had any reason to use the System.map files in five years running linux, but I keep them just in case I ever have a kernel crash. Enjoy, -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
* Mark Knecht [EMAIL PROTECTED] [2003-09-15 18:31]: Does 'make vmlinuz' make an uncompressed kernel? No, 'make vmlinux' does, but you don't want that on x86. 'make vmlinuz' produces an error. The other 2/3's are where do the System.map and config files come from? I've just been reading Section 10 of the Kernel HOWTO, which explains in detail about System.map: http://www.tldp.org/HOWTO/Kernel-HOWTO/kernel_files_info.html Cheers David -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
Thus spake Mark Knecht on Mon, Sep 15, 2003 at 08:31:46PM CDT On Mon, 2003-09-15 at 15:40, Lindsay Haisley wrote: bzImage doesn't contain the system symbol map, but the symbol map is frequently used to translate numeric locations in bzImage into symbol names for debugging purposes. System.map isn't required. The file /usr/src/linux/arch/xxx/boot/bzImage gets copied, usually, to /boot/vmlinuz when one builds a kernel, so they're the same file, really. OK, so for a couple of years I've made a consistent 'mistake' because I almost always do this copy by hand, but I never rename it. So the bzImage files in my /boot directory, by convention, should really be named vmlinuz, but I haven't been doing that. It's really a no-nevermind. You can call the file in the /boot directory whatever you want to, as long as it agrees with the grub or lilo reference to it in their config files. Do `make vmlinux` instead of `make bzImage` - they should be in the source root. (They may actually be there after doing make bzImage - have a look - but that's what you do if you don't want the compressed image.) Does 'make vmlinuz' make an uncompressed kernel? # make vmlinuz make: *** No rule to make target `vmlinuz'. Stop. It don't compute ;-) The other 2/3's are where do the System.map and config files come from? System.map is created by the kernel build (make bzImage). Generally you can copy it to your /boot, along with your kernel image and if it's needed to put human-readable names on numeric kernel addresses, it'll be found there. Several programs use it, ps being one, I believe, but it's not mission critical. It may now be included in the bzImage created by a build, but I don't know if every program that might use it knows to look for it there. The config file, actually .config, is created by the kernel configuration process (rather than the kernel build) and contains all your kernel settings. If you have a configuration you want to save off so that you can build an identical kernel somewhere else, with all the same options, just copy it to a fresh kernel tree somewhere and do a 'make oldconfig', or run 'make menuconfig' and and save your changes if you want to modify anything. Gentoo kernels create /proc/config which is the contents of the config file used to generate the kernel. Even if you wipe out your kernel tree you can just copy /proc/config to .config in a new kernel tree and you can reproduce the running kernel. If they are created by the above set of steps, then are they under /usr/src/linux somewhere after I've built the kernel? Yes, in the root of the source tree. -- Lindsay Haisley | Everything works| PGP public key FMP Computer Services | if you let it | available at 512-259-1190 |(The Roadie) | http://www.fmp.com/pubkeys http://www.fmp.com| | -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
On Mon, 2003-09-15 at 19:06, Brett I.Holcomb wrote: You haven't made a mistake. Brett Collins. You say mistake. I say 'mistake'. I did understand, especially after Lindsay's explanation about the 'convention' being to change the name, that it's just a 'mistake' and not a mistake. ;-) But thanks for the extra What happens is a kernel build creates bzImage in the /usr/src/linux directory tree. Then the docs tell you to copy it to /boot. I copy and rename it because I like vmlinuz. The name makes no difference. As far as Gentoo goes - at least the last builds I did - the kernel wasn't copied but if it is feel free to rename it. However, I don't mount /boot until I'm ready to copy to it. Actually, this is one very nice feature of Gentoo vs. Redhat. In Redhat /boot was always mounted, so if I made a mistake and ran 'make install' I could overwrite an existing kernel. I like having to mount /boot by hand when I'm ready to copy it, just like you. When the kernel is built the System.map file is also built. If you want copy it to /boot too. It provides symbols for debuggin. I've run with a System.map that was built several kernel builds ago - however, I don't do debugging G Got it. Thanks. As Collins pointed out, and I checked it to be true, System.map is created and is in /usr/src/linux after my build, so that is answered. If I would have bothered to edit the config file in /boot I would have figured out that is is the .config file used when I built the kernel. I suppose again that 'make install' copies it over. I could do that by hand also. So, actually, thanks very much for helping clear up a few small mysteries for me today. I've been building kernels off and on for a while, but since moving my home studio main desktop machine, first from Win XP and then from Redhat, to Gentoo I've gotten more attuned to build code much more often. Under Redhat I built very little code. Gentoo is a different experience. Thanks much, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
On Mon, 2003-09-15 at 19:26, Lindsay Haisley wrote: Gentoo kernels create /proc/config which is the contents of the config file used to generate the kernel. Even if you wipe out your kernel tree you can just copy /proc/config to .config in a new kernel tree and you can reproduce the running kernel. Lindsay, Thanks for everything, but especially for this tip. Great info and I had no idea it was there. Cheers, Mark -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
Keep asking questions. That's the best way to learn. In a year or two, you'll be fielding these questions for a new crop of newbies. It's best, of course, to do a little bit of research on your own. Otherwise, some people on the list get a little bit cranky. -- Collins Richey - Denver Area if you fill your heart with regrets of yesterday and the worries of tomorrow, you have no today to be thankful for. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] What creates System.map, config and vmlinuz?
On Tuesday 16 September 2003 05:26, Lindsay Haisley wrote: Gentoo kernels create /proc/config which is the contents of the config file used to generate the kernel. Even if you wipe out your kernel tree you can just copy /proc/config to .config in a new kernel tree and you can reproduce the running kernel. Not always. One have to select support for /proc/ and that one wants the used config support to be compiled in the kernel. The first is met by almost anybody's kernel, but the second might be missing, because it takes quite a bit unnecessary space (at least quite many people thinks in this way). I though have always used that, because through that I don't need to look up the options that I didn't turn on. ;) -- [EMAIL PROTECTED] mailing list
