Re: [gentoo-user] OT ( was : Cannot boot 2.6.21-gentoo-r4)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alle giovedì 19 luglio 2007, Billy McCann ha scritto: [...] 2. Copy old .config and make. In this case you miss any new kernel options. [...] That is no true. If you copy your old .config and give make, the make asks you for all new options (I think that is the right one make oldconfig) Luigi - -- Public key GPG(0xC5CB65CD) on hkp://pgp.mit.edu -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFGoFrg5ZpKrsXLZc0RAmtCAJ9mcJkY7jJ4455T3PJpMbqAgctl5gCgsJyf fHUfjvA1AkHniGwsgHgy0Hc= =56DK -END PGP SIGNATURE- -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] OT ( was : Cannot boot 2.6.21-gentoo-r4)
On Fri, 20 Jul 2007 08:49:04 +0200 Luigi Pinna [EMAIL PROTECTED] wrote: Alle giovedì 19 luglio 2007, Billy McCann ha scritto: [...] 2. Copy old .config and make. In this case you miss any new kernel options. [...] That is no true. If you copy your old .config and give make, the make asks you for all new options (I think that is the right one make oldconfig) You only get asked for new options if you use the make oldconfig command. Just doing a make uses the arch defaults for them. -- Ian. -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] OT ( was : Cannot boot 2.6.21-gentoo-r4)
On Fri, 2007-07-20 at 08:49 +0200, Luigi Pinna wrote: That is no true. If you copy your old .config and give make, the make asks you for all new options (I think that is the right one make oldconfig) Luigi No. What you seeing is a little different. If you read the Makefile: # If .config is newer than include/config/auto.conf, someone tinkered # with it and forgot to run make oldconfig. # if auto.conf.cmd is missing then we are probably in a cleaned tree so # we execute the config step to be sure to catch updated Kconfig files include/config/auto.conf: $(KCONFIG_CONFIG) include/config/auto.conf.cmd $(Q)$(MAKE) -f $(srctree)/Makefile silentoldconfig [...] So you're basically running [silent]oldconfig... But, e.g., if you happen to # mv /path/to/old/.config .config # make (or similar) then oldconfig doesn't get run and you don't get to choose new kernel options. Anyway I still hold that oldconfig is the safe bet. -- Albert W. Hopkins -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] OT ( was : Cannot boot 2.6.21-gentoo-r4)
On 7/17/07, Albert Hopkins [EMAIL PROTECTED] wrote: On Tue, 2007-07-17 at 14:24 -0500, Billy Wayne McCann wrote: My purpose for pasting this into this discussion is three-fold: to show why I said what I did, to hopefully dispel the notion that I merely made this all up, and to discuss the relevance of the pasted text itself. I apologize for being off-topic and hope that Mick finds himself a working kernel config soon. :) I hope he does as well. Completely on a tangent from the OP, but I would like to argue *for* the use of oldconfig when upgrading kernels. I read the relevant part of the document and I'm not going to contest it, it does not seem to indicate that oldconfig when upgrading kernels doesn't work, but that oldconfig might somehow confuse the user into not selecting a kernel option that they need. OTOH if said person is using an old config that worked then most, if not all, of the needed options are already selected. But what are the alternatives? The document does not cite any. I can think of four choices: 1. make menuconfig and create a new .config from scratch. From my own personal experience I know I'm *much* more likely to forget a needed kernel option starting from scratch than from an old config. 2. Copy old .config and make. In this case you miss any new kernel options. 3. copy old .config and make menuconfig. In this case you're much more likely to miss the *new* kernel options because they don't stand out from the old ones. 4. Copy old .config and make oldconfig. Here you get prompted for any new kernel options, plus you keep all your old ones when feasible. Or, if you're lucky enough to be using Gentoo, you could run genkernel. However browsing the genkernel sources it seems to do 2, 3 or 4 depending on what options it is given. 2 seems relevant only if you want to upgrade your kernel but not take advantage of any new features. 3 is prone to overlooking the aforementioned features. So that leaves 1 which is ridiculous and 4 which just about every other document found on the net about upgrading kernels recommends, including the Greg Kroah-Hartman's _Linux Kernel in a Nutshell_ (Greg being both a Kernel and Gentoo developer). I think that in general, and when used correctly, oldconfig is in fact a very useful tool when performing kernel upgrades, but of course YMMV. -- Albert W. Hopkins -- [EMAIL PROTECTED] mailing list Albert, Thanks for taking the time to put these thoughts together. I think I understand better now. Much appreciated. Billy Wayne -- #end_transmission# #earth_creature#
Re: [gentoo-user] OT ( was : Cannot boot 2.6.21-gentoo-r4)
On Tue, 2007-07-17 at 14:24 -0500, Billy Wayne McCann wrote: My purpose for pasting this into this discussion is three-fold: to show why I said what I did, to hopefully dispel the notion that I merely made this all up, and to discuss the relevance of the pasted text itself. I apologize for being off-topic and hope that Mick finds himself a working kernel config soon. :) I hope he does as well. Completely on a tangent from the OP, but I would like to argue *for* the use of oldconfig when upgrading kernels. I read the relevant part of the document and I'm not going to contest it, it does not seem to indicate that oldconfig when upgrading kernels doesn't work, but that oldconfig might somehow confuse the user into not selecting a kernel option that they need. OTOH if said person is using an old config that worked then most, if not all, of the needed options are already selected. But what are the alternatives? The document does not cite any. I can think of four choices: 1. make menuconfig and create a new .config from scratch. From my own personal experience I know I'm *much* more likely to forget a needed kernel option starting from scratch than from an old config. 2. Copy old .config and make. In this case you miss any new kernel options. 3. copy old .config and make menuconfig. In this case you're much more likely to miss the *new* kernel options because they don't stand out from the old ones. 4. Copy old .config and make oldconfig. Here you get prompted for any new kernel options, plus you keep all your old ones when feasible. Or, if you're lucky enough to be using Gentoo, you could run genkernel. However browsing the genkernel sources it seems to do 2, 3 or 4 depending on what options it is given. 2 seems relevant only if you want to upgrade your kernel but not take advantage of any new features. 3 is prone to overlooking the aforementioned features. So that leaves 1 which is ridiculous and 4 which just about every other document found on the net about upgrading kernels recommends, including the Greg Kroah-Hartman's _Linux Kernel in a Nutshell_ (Greg being both a Kernel and Gentoo developer). I think that in general, and when used correctly, oldconfig is in fact a very useful tool when performing kernel upgrades, but of course YMMV. -- Albert W. Hopkins -- [EMAIL PROTECTED] mailing list
