Quote:
Originally Posted by slcklnx
I'm sorry, but I want to understand. when I just installed Slackware, I did nothing, I didn’t run anything.
Will it be contained in .config? Is it in the newly installed system? how and by whom is this config created?
|
Good question and yes /usr/src/linux/.config is copied to /boot/config-version and usually symlinked to either /config or /boot/config. It is created by the process of building a working kernel, whether you or someone else built it. This can be accomplished with "make config" (don't do this one) or "make menuconfig" (from command line with ncurses menu display) or "make xconfig" (a 3 part display of heading, options, and help info) or even with make oldconfig a very important tool of a family of tools that uses the running kernel for clues.
Please note that when you installed Slackware you did run a number of commands but they were represented by menu choices. The last one was "Attempt to install lilo now" which was essentially to run "/sbin/lilo" and the skeleton for "/etc/lilo.conf" was created by your choices to questions like "Where do you want lilo installed? 1) MBR, 2) Root, or 3) Don't install LILO now.
The single most important thing you need to remember if you are going to attempt to build a custom kernel is to keep your running kernel and it's entry stanza in your bootloader config ie: /etc/lilo.conf. That way you have a safety net so you can always boot without having to resort to the first stop on the Slackware Install media, which BTW is a huge benefit that I don't know why every other distro hasn't copied, but that's another story. Just protect yourself. Don't Delete when Renaming can take a file out of play while still retaining it to name back if you need it.
