But isn't the whole reason for compiling a new kernel so that you can "reconfigure" the kernel more to your liking and needs rather than having the new kernel configured exactly as the one you're currently running? Why even bother if you're going to have it look the same. It will be doing exactly the same thing. Mark / * Sometimes it becomes necessary to rock the boat * in order to get the rats up from below decks * so they can be kicked over the side and drowned! * * REGISTERED LINUX USER # 182496 */ <<<<<<<<<<<<<<<<<*REPLY SEPERATOR*>>>>>>>>>>>>>>>>>>>>>> On Mon, 20 Nov 2000 Pe�a Arellano Fabian Erasmo had this to say! > This is a multi-part message in MIME format... > > ------------=_974702805-6208-1504 > > Hello everybody: > > I would like to compile a new kernel for the computer I use. Since I really >don�t know much about the configuration options the "make menuconfig" offers, I would >like to keep the configuration of the current kernel. How can I tell the "make >oldconfig" commnad where to look for the configuration parameters of the current >kernel? Is there a standard directory that file is usually placed? > If it is the case that the new kernel has new configuration options, will the >"make oldconfig" commnad ask me automatically for the needed information? > Thanks in advance. > > Fabi�n Pe�a. > > > ------------=_974702805-6208-1504 > Content-Type: text/plain; name="message.footer" > Content-Disposition: inline; filename="message.footer" > Content-Transfer-Encoding: 8bit > > Keep in touch with http://mandrakeforum.com: > Subscribe the "[EMAIL PROTECTED]" mailing list. > > ------------=_974702805-6208-1504-- >
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
