Re: [expert] compiling new kernel, keeping old kernel, how?
Hi, Thanks, but as I said in my original posting, I have no problem with LILO, or adding OSs to LILO. What I AM having a problem with is figuring out how to compile/install a kernel so that I can keep all the mods/deps from my current kernel, AND those from the new kernel, in 2 SEPERATE places (if it is possible). Thanks, David Charles On Thu, 20 Sep 2001 [EMAIL PROTECTED] wrote: Hi David, All you simply need to do is add another stanza in your /etc/lilo.conf. For example, here's part of my laptop's lilo.conf: image=/boot/vmlinuz-2.4.5-3mdksmp label=245-3smp root=/dev/sda3 read-only optional append= quiet initrd=/boot/initrd-2.4.5-3mdksmp.img image=/boot/vmlinuz-2.4.6 label=246 root=/dev/sda3 read-only optional append= quiet So let's say this one is yours. Near the top of the file, you'll see your 'default' line to reflect which kernel image will boot by default (by what label it has). So if you wanted to boot to the latter kernel image, just have '246' in your default line. Like: default=246 Don't delete your old kosher kernel, just add the new one. Know what I'm saying? And don't forget to run lilo when you're done modifying your lilo.conf! Hope that helps, -Charlie On Thu 20 Sep at 22:13:57 -0400 [EMAIL PROTECTED] done said: Hello everybody, I want to start off by thanking everyone who uses this list, especially those who answered any of my previously posted questions. I would like to compile another kernel, and be able to boot from it. I have pretty much no problem on the how of compiling the kernel. My question concerns the fact that I have a system that is currently in VERY good shape, with very few bugs/problems. I would like to keep my current kernel, as well as all of its dependencies/etc., seperate (and left where they are) from the new kernel. I would like to be able to choose from lilo to boot either kernel A or kernel B (I know how to add to LILO no prob); I would like it that, in the event that the new kernel seems to be incompatible/cause problems with/break some of my software, that I can just delete the kernel, map file, the deps, LILO entry etc. (for this, perhaps a log of which files were installed would be helpful... where would I find it/how would I make such a file during the compile/install process?) from my system, and then, because I kept all the files needed by my current kernel in their own seperate directory, I would be back in business with my current, stable kernel running my system again. Can someone please either point me to a decent doc that details the instructions of such an install, or post a response that includes a nice detailed description of how to do it? Thanks in advance, David Charles Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- GPG Key fingerprint = 4F36 EC4F 2F2C 5F59 9690 09E5 4C0F 9DB0 8623 53CE We're all in this alone. -- Lily Tomlin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] compiling new kernel, keeping old kernel, how?
You can modify these steps however you like, but if you do make sure you understand the consequences. 1) edit /usr/src/linux/Makefile and change EXTRAVERSION to be what ever you want like 'EXTRAVERSION = 24mdk-myversion' 2) 'cd /usr/src/linux' 3) 'cp .config my-configuration' 4) 'make mrproper' 5) 'cp my-configuration .config' 6) 'make menuconfig' then exit and save changes or use your favorite make config. 7) 'make dep bzImage modules' 8) 'cp arch/i386/boot/bzImage /boot/vmlinuz-2.4.9-24mdk-myversion' 9) 'make moudles_install' and they will get copied to /lib/modules/2.4.9-24mdk-myversion 10) 'cp System.map /boot/System.map-2.4.9-24mdk-myversion' 11) point an entry in /etc/lilo.conf to the new kernel in /boot 12) 'lilo' 13) reboot and have fun. Note: all the real work done is by setting the EXTRAVERSION in the Makefile. On Fri, 2001-09-21 at 12:14, [EMAIL PROTECTED] wrote: Hi, Thanks, but as I said in my original posting, I have no problem with LILO, or adding OSs to LILO. What I AM having a problem with is figuring out how to compile/install a kernel so that I can keep all the mods/deps from my current kernel, AND those from the new kernel, in 2 SEPERATE places (if it is possible). Thanks, David Charles On Thu, 20 Sep 2001 [EMAIL PROTECTED] wrote: Hi David, All you simply need to do is add another stanza in your /etc/lilo.conf. For example, here's part of my laptop's lilo.conf: image=/boot/vmlinuz-2.4.5-3mdksmp label=245-3smp root=/dev/sda3 read-only optional append= quiet initrd=/boot/initrd-2.4.5-3mdksmp.img image=/boot/vmlinuz-2.4.6 label=246 root=/dev/sda3 read-only optional append= quiet So let's say this one is yours. Near the top of the file, you'll see your 'default' line to reflect which kernel image will boot by default (by what label it has). So if you wanted to boot to the latter kernel image, just have '246' in your default line. Like: default=246 Don't delete your old kosher kernel, just add the new one. Know what I'm saying? And don't forget to run lilo when you're done modifying your lilo.conf! Hope that helps, -Charlie On Thu 20 Sep at 22:13:57 -0400 [EMAIL PROTECTED] done said: Hello everybody, I want to start off by thanking everyone who uses this list, especially those who answered any of my previously posted questions. I would like to compile another kernel, and be able to boot from it. I have pretty much no problem on the how of compiling the kernel. My question concerns the fact that I have a system that is currently in VERY good shape, with very few bugs/problems. I would like to keep my current kernel, as well as all of its dependencies/etc., seperate (and left where they are) from the new kernel. I would like to be able to choose from lilo to boot either kernel A or kernel B (I know how to add to LILO no prob); I would like it that, in the event that the new kernel seems to be incompatible/cause problems with/break some of my software, that I can just delete the kernel, map file, the deps, LILO entry etc. (for this, perhaps a log of which files were installed would be helpful... where would I find it/how would I make such a file during the compile/install process?) from my system, and then, because I kept all the files needed by my current kernel in their own seperate directory, I would be back in business with my current, stable kernel running my system again. Can someone please either point me to a decent doc that details the instructions of such an install, or post a response that includes a nice detailed description of how to do it? Thanks in advance, David Charles Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- GPG Key fingerprint = 4F36 EC4F 2F2C 5F59 9690 09E5 4C0F 9DB0 8623 53CE We're all in this alone. -- Lily Tomlin =_1001099712-779-752 Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] compiling new kernel, keeping old kernel, how?
On Friday 21 September 2001 21:14, you wrote: Hi, Thanks, but as I said in my original posting, I have no problem with LILO, or adding OSs to LILO. What I AM having a problem with is figuring out how to compile/install a kernel so that I can keep all the mods/deps from my current kernel, AND those from the new kernel, in 2 SEPERATE places (if it is possible). Thanks, David Charles Hmmm, well let's think about this a minute. All booting is done from /boot. Kernels that boot must be stored in /boot kernels are numbered by version and build like vmlinuz-2.2.19-10mdk or vmlinuz-2.4.8-24mdk or vmlinuz-2.4.3-20mdk I have all three in my /boot. One boots RC1 on /dev/hda9, the others boot 8.0 on /dev/hda1. Now modules They exist in /lib/modules/2.2.19-10mdk, /lib/modules/2.4.3-20mdk on /dev/hda1, and /lib/modules/2.4.8-24mdk on /dev/hda9 Now lilo has boot sections for each of these. Moreover there is a boot that aims at vmlinuz and initrd.imd which are merely links and I can link it to either one of the kernels booting with /dev/hda1 as / (I would have to change the root= stanza to make that one boot from /dev/hda9) OK I also have initrd.img-2.4.8-24mdk initrd.img-2.4.3-20mdk initrd.img-2.2.19-10mdk I made these or the installer made them. It is rather simple to do, but required if for example one system uses ext2 and the other uses XFS. These are the modules loaded without accessing / partition, which may not be available. So your problem reduces to moving the stuff you have compiled (as BzImage) to the right named files, making up your own build numbers to guarantee uniqueness. And of course to making the rightly named directories for /lib/modules. This is _please note this, you folks who upgraded the kernel_ the case. Many kernels can coexist on your system, with different names, and the bootloader or the symbolic links, give you access to _all_ of them. The moral is, _never_ upgrade a kernel, always install it. It will _not_ replace the old kernel on an install, and it _will_ on an update. Or worse, only part of it will install and you have the interesting educational experience of booting one kernel with the modules of another; I guarantee this will be an eye-opener. Civileme Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
Re: [expert] compiling new kernel, keeping old kernel, how?
Hi David, All you simply need to do is add another stanza in your /etc/lilo.conf. For example, here's part of my laptop's lilo.conf: image=/boot/vmlinuz-2.4.5-3mdksmp label=245-3smp root=/dev/sda3 read-only optional append= quiet initrd=/boot/initrd-2.4.5-3mdksmp.img image=/boot/vmlinuz-2.4.6 label=246 root=/dev/sda3 read-only optional append= quiet So let's say this one is yours. Near the top of the file, you'll see your 'default' line to reflect which kernel image will boot by default (by what label it has). So if you wanted to boot to the latter kernel image, just have '246' in your default line. Like: default=246 Don't delete your old kosher kernel, just add the new one. Know what I'm saying? And don't forget to run lilo when you're done modifying your lilo.conf! Hope that helps, -Charlie On Thu 20 Sep at 22:13:57 -0400 [EMAIL PROTECTED] done said: Hello everybody, I want to start off by thanking everyone who uses this list, especially those who answered any of my previously posted questions. I would like to compile another kernel, and be able to boot from it. I have pretty much no problem on the how of compiling the kernel. My question concerns the fact that I have a system that is currently in VERY good shape, with very few bugs/problems. I would like to keep my current kernel, as well as all of its dependencies/etc., seperate (and left where they are) from the new kernel. I would like to be able to choose from lilo to boot either kernel A or kernel B (I know how to add to LILO no prob); I would like it that, in the event that the new kernel seems to be incompatible/cause problems with/break some of my software, that I can just delete the kernel, map file, the deps, LILO entry etc. (for this, perhaps a log of which files were installed would be helpful... where would I find it/how would I make such a file during the compile/install process?) from my system, and then, because I kept all the files needed by my current kernel in their own seperate directory, I would be back in business with my current, stable kernel running my system again. Can someone please either point me to a decent doc that details the instructions of such an install, or post a response that includes a nice detailed description of how to do it? Thanks in advance, David Charles Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com -- GPG Key fingerprint = 4F36 EC4F 2F2C 5F59 9690 09E5 4C0F 9DB0 8623 53CE We're all in this alone. -- Lily Tomlin Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
