Bill Jonas on Tue, 13 Feb 2001 12:42:43 -0500 |
On Tue, Feb 13, 2001 at 12:17:43PM -0500, Rupert Heesom wrote: > Thanks for this tip....I looked in my /usr/src/linux directory, and did > find both a ".config" and ".config.old". The .config saves your most recent options, .config.old is a backup of the .config you have previously, before you ran 'make config', 'make menuconfig', or 'make xconfig' the most recent time. > Do I understand correctly that when I do a "make xconfig", then I can > use the .config file to load into the xconfig prog the kernel previous > settings rather than resetting all the options? If there is a .config in that directory, it is used by default. I'm not sure how you would tell the configuration programs not to use it. I just move it or remove it if I want to start from scratch. Do note that when you upgrade your kernel, you don't want to use the old .config file directly, as some things may have changed; instead, you put the .config from the previous version in your source directory and run a 'make oldconfig' to pick up just the things that have been added or changed. (This is for when you're using the .config from a previous kernel.) > If so, is the file name ".config" std convention? I've previously saved > settings when playing around with the config program into a file called > "rupert". Yes, .config is a standard Linux convention. -- Bill Jonas | "In contrast to the What You See Is What You bill@billjonas.com | Get (WYSIWYG) philosophy, UNIX is the You http://www.billjonas.com/ | Asked For It, You Got It operating system." http://www.debian.org/ | --Scott Lee, as quoted by Lamb and Robbins ______________________________________________________________________ Philadelphia Linux Users Group - http://www.phillylinux.org Announcements-http://lists.phillylinux.org/mail/listinfo/plug-announce General Discussion - http://lists.phillylinux.org/mail/listinfo/plug
|
|