LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Reply
 
Search this Thread
Old 06-02-2005, 02:27 AM   #1
Godsmacker777
Member
 
Registered: Oct 2004
Posts: 52

Rep: Reputation: 15
proper kernel config - using an oldconfig


I know this topic has been covered many times..but that's my problem. I'm a bit confused as to the proper way to use an old kernel config for a new kernel. So what is the best way to go about this?

Currently I make menuconfig for my new kernel..then I "load an alternate config" and go on with my day. Am I correct in that I would be missing new options available to my newer kernel??

So what should I do?

thanks
 
Old 06-02-2005, 06:51 AM   #2
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,372

Rep: Reputation: 163Reputation: 163
After you load the old config, simply open up all the options. If you find another you want to use, include it or build as a module. Then you will have a new old config in the build tree. If I include new options, I rename .config to something that I hope to remember why I did it, and put in in my /home/michael.
 
Old 06-02-2005, 11:27 AM   #3
Godsmacker777
Member
 
Registered: Oct 2004
Posts: 52

Original Poster
Rep: Reputation: 15
I'm sorry but I am just as confused.

Can someone explain what happens when you make menuconfig for a new kernel, then load an alternate config? What happens when an "oldconfig" is loaded?

What is the "proper" way to use an old config for a new kernel?
 
Old 06-03-2005, 02:26 AM   #4
Godsmacker777
Member
 
Registered: Oct 2004
Posts: 52

Original Poster
Rep: Reputation: 15
bump..

can anyone help me understand the process?
 
Old 06-03-2005, 07:16 AM   #5
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,372

Rep: Reputation: 163Reputation: 163
Quote:
Originally posted by Godsmacker777
I'm sorry but I am just as confused.

Can someone explain what happens when you make menuconfig for a new kernel, then load an alternate config? What happens when an "oldconfig" is loaded?

What is the "proper" way to use an old config for a new kernel?
When you load an alternate config file, all the options for that config are loaded and nothing else. So, if you built a previous kernel and you are satisfied with the results, saving the .config file for use later is a good idea.

When you obtain a newer kernel source, using the old config file is a good idea as well - assuming that nothing has changed in your hardware. Maybe the newer kernel source has support for something you did not have previously. There are always newer options in new kernel source releases. Reading the changelog will give you what is new. If it is something you need or want, after loading the old config, just browse through menuconfig until you get to the new options. Decide if you want them after reading the help section and include the option(s). Save your now new config and build.
 
Old 06-03-2005, 02:18 PM   #6
Godsmacker777
Member
 
Registered: Oct 2004
Posts: 52

Original Poster
Rep: Reputation: 15
If I load an old config for a newer version of the kernel, I will still have access to the newer features correct?

When I set up a system I always make a base kernel, in which I have gone through every option of the kernel one at a time. Later kernels might add features, but either way, I have organized my boot partition and I always save my configs :O)

What do these two commands do, and (more importantly) what would be the reason to use them?

Code:
make oldconfig

make mrproper

Thanks for the clarification!
 
Old 06-03-2005, 10:13 PM   #7
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,372

Rep: Reputation: 163Reputation: 163
make mrproper returns the kernel source to its base state. It will delete the .config file - so if you have built from this source before, make sure you back up the config file. If it is a fresh tarball, make mrproper is the first thing to do.

make oldconfig uses the last .config file in the build tree. Again, a fresh tarball would probably have a .config file that may be totally unusable for your system.
 
Old 06-05-2005, 12:11 AM   #8
Godsmacker777
Member
 
Registered: Oct 2004
Posts: 52

Original Poster
Rep: Reputation: 15
thanks~

I just realized how easy gentoo makes my life sometimes..

to all of you who think gentoo is a waste of time..
you're wasting your time avoiding it.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
change kernel configurations when use "make oldconfig" Gijet Red Hat 4 10-09-2006 07:23 PM
the kernel proper slinky2004 Linux - Newbie 4 10-30-2005 09:53 PM
can't load proper keybord config on slackware 10.1 salviadud Linux - Newbie 4 03-14-2005 11:21 AM
How do I make a change to a current kernel? Would 'make oldconfig' work... jtp51 Slackware 11 11-01-2004 11:02 PM
How do i find the proper linux config file? justinfl General 2 10-08-2003 11:01 PM


All times are GMT -5. The time now is 03:23 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration