[gentoo-user] Re: make oldconfig
James wrote: Hello, It seems like I remember that 'make oldconfig' is not needed any more, to pass the current (booted) kernel option to the .config for building a new kernel. Of is 'make oldconfig' still a good idea? It's not needed, but a good idea to see if there are any new options.
[gentoo-user] Re: make oldconfig
Dale bellsouth.net> writes: Well, the reason I asked is for clarity. I found this gentoo doc, which seems a little dated: http://gentoo-wiki.com/ HOWTO_Detailed_Kernel_Configuration So what I gleen is that you run on a kernel, say version linux-2.6.24-gentoo-r8 You down load newer sources, say version linux-2.6.25-gentoo-r7 cd /usr/src rm linux ln -sf /usr/src/linux-2.6.25-gentoo-r7 linux make oldconfig make menuconfig cp System.map /boot/System.map-2.6.25-gentoo-r7 cp arch/x86_64/boot/bzImage /boot/kernel-2.6.25-gentoo-r7 cp .config /boot/config-2.6.25-gentoo-r7 edit grub apppropriately and reboot to the new kernel? This is what I do, but I do not use the oldconfig command. A friend asked me how I build new kernel on gentoo and I was hoping to find a current howto, that does not use genkernel and such. I did not have any luck finding one (although I did not look very hard). Any suggestions are appreciated. The aforementioned howto suggest that make oldconfig, xconfig and menuconfig are alternate ways? Maybe your not suppose to mix oldconfig with menuconfig? The reason I ask is some 2.6.23 to 2.6.24. to 2.6.25 kernel have lost setting (selected options) using menuconfig alone. However, for a while the selected options were always correctly included using the above steps (without using oldconfig command syntax). This is the source of my need for some clarity. Maybe an updated howto is what is really needed? One that skips genkernel and such? James
[gentoo-user] Re: make oldconfig
Daniel Pielmeier googlemail.com> writes: > In the case you run menuconfig oldconfig is not needed. I did so > myself in the past. Now i simply run just oldconfig, because you have > a better control of what has changed between the versions. After > oldconfig menuconfig is not needed one of them will suffer. Thanks for all the input. I do agree that oldconfig and menuconfig are not both needed. That said, I'll stick with menuconfig thanks again, James
[gentoo-user] Re: make oldconfig
On Sat, 9 Aug 2008 20:35:43 + (UTC) james <[EMAIL PROTECTED]> wrote: > Daniel Pielmeier googlemail.com> writes: > > > > In the case you run menuconfig oldconfig is not needed. I did so > > myself in the past. Now i simply run just oldconfig, because you > > have a better control of what has changed between the versions. > > After oldconfig menuconfig is not needed one of them will suffer. > > > Thanks for all the input. > I do agree that oldconfig and menuconfig are not both > needed. > > That said, I'll stick with menuconfig FWIW, I use oldconfig, which usually goes very quickly. Then if there was a prompt I wasn't really clear on, I google a little and make any needed changes with menuconfig. -- »Q« Kleeneness is next to Gödelness.
[gentoo-user] Re: make oldconfig ?
Alexander Kapshuk gmail.com> writes: > > 1) #make silentoldconfig > > 2) #make olddefconfig > > 3) #make oldconfig > > (3) still seems to work. (2) uses defaults so I do not want that, but > > what about (1)? What's the difference between (1) and (3) ? Where do > > I read about them of find the sources? I'd still like to look at the sources for these scripts, if anybody knows where they are located, I have not had any luck locating the sources for oldconfig and the > > I did notice after running (3) and then 'make && make modules install' > > the slilentoldconfig script was ran (it flashed by quickly):: > > scripts/kconfig/conf --silentoldconfig Kconfig > Although not specific to the question asked, but just an observation I > have made, when using 'make oldconfig', copying the current '.config' > to the directory containing the sources for the new kernel is not > required, provided 'make install' was used to install the previous > kernel, which would have put the config file into the boot directory. > 'make oldconfig' uses the config file for the old kernel found in the > '/boot' directory to generate a new '.config' file. All good to know; the more reason I probably need to read those scripts, as I roll out my (ansible) codes for using one bank of hardware to setup and boot a variety of different cluster and container configurations. I thought they might be in /usr/src/linux/scripts/ but no? No hints in the top level Makefile either. One of the Gentoo GSoC projects is to rework kernel building too. Now I'm stoked to read the scripts/makefile for oldconfig and such curiously, James
[gentoo-user] Re: make oldconfig ?
Tom H gmail.com> writes: > Perhaps: > /usr/src/linux/scripts/kconfig/Makefile > /usr/src/linux/scripts/kconfig/conf.c thx, James
[gentoo-user] Re: make oldconfig ?
Tom H gmail.com> writes: > >> /usr/src/linux/scripts/kconfig/Makefile > >> /usr/src/linux/scripts/kconfig/conf.c > I'm not too sure what you're looking for but if you want to compare > config_new and config_old where you generated config_new with > config_old and "make oldconfig", you can use "./scripts/diffconfig > .config config.old". Background:: I have been researching and reading about a plethora of cluster/cloud approaches to running normal linux codes (frameworks if you like) and also Hi Performance Computing (many machines on a single problem). Long story short version, it seems the more the linux system is minimized, in size and complexity, the faster the containers or HPC applications run on top of it and the easier it is to 'secure' the cluster. Many, in the cluster world, particularly the HPC folks, are not using systemd as it adds unnecessary complexity and degrades performance, albeit systemd does bring some ease of management to large numbers of nodes. Gentoo has quite a following of openrc folks, as I am one, and there needs to be a openrc pathway to cluser-paradise, imho. Most folks are keeping their secrets as to how to best tune a linux kernel for cluster or container deployment. Mix that in with Systemd complexities and the result is a very obfuscated environment for kernel tuning and benchmarking of clusters. So I'm going to need tools to rapidly (CI?) rebuild various linux kernels with minor tweaks to the config, as well as deployment consistency. Cluster vendors have basically two strategies:: Commercially offer a version of the cluster that is tuned to a specific performance need, and/or commercially offer the very nice management tools that make clustering easy, pleasant and robust. I have become very interested in developing a small cluster for testing some of the myriad of cluster offerings. IMHO:: a cluster is just a local cloud that is run locally. So for my example 12 systems, mostly amd64, but some intel and arm64 systems, are to be used. The desire is to be able to use these systems, to rapidly throw up a cluster for containers, or HPC, run some codes, trap and retain data for later analysis and comparison with runs against other cluster architectures and codes that constitute a given target cluster. Loosely, cluster benchmarking. There is the myriad of 'frameworks' that are available for the various clusters one can build. It's all quite complex on the surface (vendor hyperbole), but underneath, vetting performance claims is quite simple. Load of the test-cluster with codes, run some jobs/apps/codes on a given cluser+frameworks, collect data for analysis and comparison. Present:: Gentoo's GSoC has at least two projects that are very appealing to me along these lines:: 1) Stateless Minimal Gentoo 2) kernelconfig Item two is the tie-in for oldconfig and associated semantics. PXE boot and other metrics are at play here too. So a comprehensive kernel build and deploy system, for lots of systems and different architectures, is of interest. Most prototype work is done on amd64. Live kernel patching is an active area of development and in some circumstances will not necessitate the reboot of the system/node to update the kernel [A]. Item one is similar to CoreOS. CoreOS has a system for rapidly deploying systems from a cold boot as well as live updates to the running OS with rollback if necessary. Impressive to say the least. But, CoreOS is locked into the systemd pathway. Myself, being of the minimalistic embedded ilk, I tend to lean towards the alpine-docker pathway of minimization and openrc/busybox. Lofty goals. But, extraordinarily useful to linux folks, especially those with small to medium size data-centers. Note, lots of folks drop me email privately with information, concerns and tidbits of wisdom most useful in my journey to cluster-paradise. Public guidance and even scorn, are also most welcome. Reams of inexpensive arm64 machines combined with compiler advances make clustering the most exciting adventure in the linux world, atm. hth, James [A] http://rhelblog.redhat.com/2015/03/23/live-kernel-patching-update/
[gentoo-user] Re: make oldconfig necessary?
On 2011-08-01, Pandu Poluan wrote: > Let's say I have a .config from an older kernel version (for example, > 2.6.38), and now I want to install a newer kernel (let's say, 3.0). > > Is it necessary to first do `make oldconfig`, or is it safe to go > directly to `make menuconfig`? It's always safe to do 'make menuconfig', and always has been (at least since the 0.97 days when I started running Linux). You just have to select all the options correctly. All that 'make oldconfig' does is start you out with something as close to your old kernel configuration as possible. -- Grant Edwards grant.b.edwardsYow! CHUBBY CHECKER just at had a CHICKEN SANDWICH in gmail.comdowntown DULUTH!
[gentoo-user] Re: make oldconfig necessary?
On 2011-08-01, Michael Orlitzky wrote: > Use oldconfig. Running 'oldconfig' will prompt you for any new > sections/drivers that have appeared since your last kernel. Running > 'menuconfig' will silently accept all of the defaults for these new > options. > > Why is it safer if only the new stuff gets defaulted? Because on more > than one occasion, there has been a group of drivers, e.g. wireless > chipsets, that got a new "enable anything" option. So while you may > have had your Atheros chipset enabled in the old kernel, the new > kernel has a "enable wireless networking" option that defaults to > "no" despite the fact that your old kernel had one or more wireless > chipsets enabled. > > This also happened with the entire SATA subsystem, Been there, tripped over that. ;) I didn't pay close enough attention when running "make oldconfig" and suddenly no hard-drives with the new kernel. It took me an embarassingly long time to figure out what had gone wrong... -- Grant Edwards grant.b.edwardsYow! Did an Italian CRANE at OPERATOR just experience gmail.comuninhibited sensations in a MALIBU HOT TUB?
Re: [gentoo-user] Re: make oldconfig
Nikos Chantziaras wrote: James wrote: Hello, It seems like I remember that 'make oldconfig' is not needed any more, to pass the current (booted) kernel option to the .config for building a new kernel. Of is 'make oldconfig' still a good idea? It's not needed, but a good idea to see if there are any new options. Why is it not needed? I could have sworn that we touched on this a week or two ago where somebody said that /proc/config.gz could be read by make config but people nixed that. -- Eric Martin Key fingerprint = D1C4 086E DBB5 C18E 6FDA B215 6A25 7174 A941 3B9F signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Re: make oldconfig
cd /usr/src rm linux ln -sf /usr/src/linux-2.6.25-gentoo-r7 linux cp /usr/src/linux-2.6.24-gentoo-r8/.config /usr/src/linux-2.6.25-gentoo-r7 make oldconfig make menuconfig On 8/6/08, James <[EMAIL PROTECTED]> wrote: > Dale bellsouth.net> writes: > > > > Well, the reason I asked is for clarity. > I found this gentoo doc, which seems a little dated: > > > http://gentoo-wiki.com/ > HOWTO_Detailed_Kernel_Configuration > > > So what I gleen is that you run on > a kernel, say version linux-2.6.24-gentoo-r8 > > You down load newer sources, say version > linux-2.6.25-gentoo-r7 > > cd /usr/src > > rm linux > > ln -sf /usr/src/linux-2.6.25-gentoo-r7 linux > > make oldconfig > make menuconfig > > cp System.map /boot/System.map-2.6.25-gentoo-r7 > cp arch/x86_64/boot/bzImage /boot/kernel-2.6.25-gentoo-r7 > cp .config /boot/config-2.6.25-gentoo-r7 > > > edit grub apppropriately > and reboot to the new kernel? > > > This is what I do, but I do not use the oldconfig command. > > A friend asked me how I build new kernel on gentoo and > I was hoping to find a current howto, that does not > use genkernel and such. I did not have any luck finding one > (although I did not look very hard). > > > Any suggestions are appreciated. The aforementioned howto > suggest that make oldconfig, xconfig and menuconfig are > alternate ways? Maybe your not suppose to mix oldconfig > with menuconfig? > > The reason I ask is some 2.6.23 to 2.6.24. to 2.6.25 > kernel have lost setting (selected options) using > menuconfig alone. However, for a while the selected > options were always correctly included using the above > steps (without using oldconfig command syntax). > > > This is the source of my need for some clarity. > Maybe an updated howto is what is really needed? > One that skips genkernel and such? > > > James > > > > > > > -- Salam, Marc
Re: [gentoo-user] Re: make oldconfig
James wrote: Dale bellsouth.net> writes: Well, the reason I asked is for clarity. I found this gentoo doc, which seems a little dated: http://gentoo-wiki.com/ HOWTO_Detailed_Kernel_Configuration So what I gleen is that you run on a kernel, say version linux-2.6.24-gentoo-r8 You down load newer sources, say version linux-2.6.25-gentoo-r7 cd /usr/src rm linux ln -sf /usr/src/linux-2.6.25-gentoo-r7 linux make oldconfig make menuconfig cp System.map /boot/System.map-2.6.25-gentoo-r7 cp arch/x86_64/boot/bzImage /boot/kernel-2.6.25-gentoo-r7 cp .config /boot/config-2.6.25-gentoo-r7 edit grub apppropriately and reboot to the new kernel? This is what I do, but I do not use the oldconfig command. A friend asked me how I build new kernel on gentoo and I was hoping to find a current howto, that does not use genkernel and such. I did not have any luck finding one (although I did not look very hard). Any suggestions are appreciated. The aforementioned howto suggest that make oldconfig, xconfig and menuconfig are alternate ways? Maybe your not suppose to mix oldconfig with menuconfig? The reason I ask is some 2.6.23 to 2.6.24. to 2.6.25 kernel have lost setting (selected options) using menuconfig alone. However, for a while the selected options were always correctly included using the above steps (without using oldconfig command syntax). This is the source of my need for some clarity. Maybe an updated howto is what is really needed? One that skips genkernel and such? James I think this is going to be a debate sort of like which is better, KDE or Gnome? I have to say, when I run make oldconfig, I don't run make menuconfig unless I have some problems. I'm not saying that is the right way either. A lot of this may depend on the situation and hardware. I'm sort of like this, if you run make oldconfig then what is there to change when running make menuconfig afterwards? My recommendation, run make oldconfig and answer no to most everything if your hardware works currently. Keep in mind, most new stuff is for new hardware. The only exception may be some of the new stuff with regard to managing the CPU and such. Those you may want to research. Also keep in mind that help is available even during the make oldconfig. Hit the question mark for that. After that, make your kernel and give it a run. Save your old working one just in case. Another thing to do before copying your old config, run make mrproper or make mrclean. Those will give you a fresh new kernel source. I'm not aware of a "current" howto. May can try google for Linux? www.google.com/linux Dale :-) :-)
Re: [gentoo-user] Re: make oldconfig
2008/8/6, James <[EMAIL PROTECTED]>: > So what I gleen is that you run on > a kernel, say version linux-2.6.24-gentoo-r8 > > You down load newer sources, say version > linux-2.6.25-gentoo-r7 > > cd /usr/src > > rm linux > > ln -sf /usr/src/linux-2.6.25-gentoo-r7 linux > > make oldconfig > make menuconfig > > cp System.map /boot/System.map-2.6.25-gentoo-r7 > cp arch/x86_64/boot/bzImage /boot/kernel-2.6.25-gentoo-r7 > cp .config /boot/config-2.6.25-gentoo-r7 > > > edit grub apppropriately > and reboot to the new kernel? In the case you run menuconfig oldconfig is not needed. I did so myself in the past. Now i simply run just oldconfig, because you have a better control of what has changed between the versions. After oldconfig menuconfig is not needed one of them will suffer. Regards, Daniel
Re: [gentoo-user] Re: make oldconfig
on 08/06/2008 04:58 AM James wrote the following: Dale bellsouth.net> writes: Well, the reason I asked is for clarity. I found this gentoo doc, which seems a little dated: http://gentoo-wiki.com/ HOWTO_Detailed_Kernel_Configuration So what I gleen is that you run on a kernel, say version linux-2.6.24-gentoo-r8 You down load newer sources, say version linux-2.6.25-gentoo-r7 cd /usr/src rm linux ln -sf /usr/src/linux-2.6.25-gentoo-r7 linux cd linux make oldconfig make menuconfig
[gentoo-user] Re: make oldconfig behaviour
· Galevsky <[EMAIL PROTECTED]>: > Now I have to build my conf again since the whole configuration may > not suit what I was looking for. Take your old .config as a base. > Anyone to tell me what oldconfig target does ? It takes the .config it finds in the source directory and builds the config from there. If there are new "selections" in the new kernel, you'll be asked for the value they should get. In short: Before running "make oldconfig", copy the .config from your old kernel to your new kernel tree and then run make oldconfig. Alexander Skwar -- Linux! Guerrilla UNIX Development Venimus, Vidimus, Dolavimus. -- Mark A. Horton KA4YBR, [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] Re: make oldconfig ?
On Tue, Apr 19, 2016 at 10:42 PM, James wrote: >>> >>> 1) #make silentoldconfig >>> 2) #make olddefconfig >>> 3) #make oldconfig >>> >>> (3) still seems to work. (2) uses defaults so I do not want that, >>> but what about (1)? What's the difference between (1) and (3) ? >>> Where do I read about them of find the sources? > > I'd still like to look at the sources for these scripts, if anybody > knows where they are located, I have not had any luck locating the > sources for oldconfig > > I thought they might be in /usr/src/linux/scripts/ but no? No hints in > the top level Makefile either. One of the Gentoo GSoC projects is to > rework kernel building too. Now I'm stoked to read the > scripts/makefile for oldconfig and such Perhaps: /usr/src/linux/scripts/kconfig/Makefile /usr/src/linux/scripts/kconfig/conf.c
Re: [gentoo-user] Re: make oldconfig ?
On Wed, Apr 20, 2016 at 12:52 AM, James wrote: > Tom H gmail.com> writes: >> >> Perhaps: >> /usr/src/linux/scripts/kconfig/Makefile >> /usr/src/linux/scripts/kconfig/conf.c > > thx, You're welcome. I'm not too sure what you're looking for but if you want to compare config_new and config_old where you generated config_new with config_old and "make oldconfig", you can use "./scripts/diffconfig .config config.old".
Re: [gentoo-user] Re: make oldconfig necessary?
On Mon, Aug 1, 2011 at 21:09, Grant Edwards wrote: > On 2011-08-01, Pandu Poluan wrote: >> Let's say I have a .config from an older kernel version (for example, >> 2.6.38), and now I want to install a newer kernel (let's say, 3.0). >> >> Is it necessary to first do `make oldconfig`, or is it safe to go >> directly to `make menuconfig`? > > It's always safe to do 'make menuconfig', and always has been (at > least since the 0.97 days when I started running Linux). You just > have to select all the options correctly. > > All that 'make oldconfig' does is start you out with something as > close to your old kernel configuration as possible. > Sorry for the misunderstanding, my bad. What I meant was: If I want a kernel config as close as possible to the older kernel, can I just use `make menuconfig`, or do I have to first run `make oldconfig`. Again, sorry for the confusion. Rgds, -- Pandu E Poluan ~ IT Optimizer ~ • Blog : http://pepoluan.tumblr.com • Linked-In : http://id.linkedin.com/in/pepoluan
Re: [gentoo-user] Re: make oldconfig necessary?
On Mon, Aug 1, 2011 at 10:09 AM, Grant Edwards wrote: > On 2011-08-01, Pandu Poluan wrote: >> Let's say I have a .config from an older kernel version (for example, >> 2.6.38), and now I want to install a newer kernel (let's say, 3.0). >> >> Is it necessary to first do `make oldconfig`, or is it safe to go >> directly to `make menuconfig`? > > It's always safe to do 'make menuconfig', and always has been (at > least since the 0.97 days when I started running Linux). You just > have to select all the options correctly. > > All that 'make oldconfig' does is start you out with something as > close to your old kernel configuration as possible. Which is an incredible timesaver...I hope I never forget to keep the "/proc/config.gz" option enabled again. -- :wq
Re: [gentoo-user] Re: make oldconfig necessary?
On Mon, 1 Aug 2011 21:39:29 +0700, Pandu Poluan wrote about Re: [gentoo-user] Re: make oldconfig necessary?: > What I meant was: > > If I want a kernel config as close as possible to the older kernel, > can I just use `make menuconfig`, or do I have to first run `make > oldconfig`. Just copy your old .config file to the new kernel source directory, then run make menuconfig and select what you want. Job done. The make menuconfig will silently do a make oldconfig on the existing .config file before it puts the menu on the screen. This means that the options in the menu hierarchy will reflect the options that were in your old .config file, with newer features [i.e. not in the earlier kernel] set to defaults. -- Regards, Dave [RLU #314465] *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* dwn...@ntlworld.com (David W Noon) *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* signature.asc Description: PGP signature
Re: [gentoo-user] Re: make oldconfig necessary?
On Monday 01 August 2011 17:58:18 David W Noon wrote: > The make menuconfig will silently do a make oldconfig on the > existing .config file before it puts the menu on the screen. This > means that the options in the menu hierarchy will reflect the options > that were in your old .config file, with newer features [i.e. not in the > earlier kernel] set to defaults. ...and flagged with "(NEW)" so you can see them. -- Rgds Peter Linux Counter 5290, 1994-04-23
Re: [gentoo-user] Re: make oldconfig behaviour
Many thanks Alexander, I misunderstood what oldconfig means. just any existing .config file into ... into the src dir. LOL. Thanks again. Gal' 2007/6/16, Alexander Skwar <[EMAIL PROTECTED]>: · Galevsky <[EMAIL PROTECTED]>: > Now I have to build my conf again since the whole configuration may > not suit what I was looking for. Take your old .config as a base. > Anyone to tell me what oldconfig target does ? It takes the .config it finds in the source directory and builds the config from there. If there are new "selections" in the new kernel, you'll be asked for the value they should get. In short: Before running "make oldconfig", copy the .config from your old kernel to your new kernel tree and then run make oldconfig. Alexander Skwar -- Linux! Guerrilla UNIX Development Venimus, Vidimus, Dolavimus. -- Mark A. Horton KA4YBR, [EMAIL PROTECTED] -- [EMAIL PROTECTED] mailing list ��í¢ï¿½z� ��(��&j)b� b�
