From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from fed1rmmtao08.cox.net ([68.230.241.31]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1Cnft2-0000H1-00 for ; Sun, 09 Jan 2005 11:25:52 -0500 Received: from lnx2.holmesgrown.com ([68.98.98.68]) by fed1rmmtao08.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20050109162522.FJUN27771.fed1rmmtao08.cox.net@lnx2.holmesgrown.com> for ; Sun, 9 Jan 2005 11:25:22 -0500 Received: from lnx3.holmesgrown.com ([192.168.1.5] ident=mail) by lnx2.holmesgrown.com with esmtp (Exim 4.10) id 1CnfsV-000256-00 for speakup@braille.uwo.ca; Sun, 09 Jan 2005 09:25:19 -0700 Received: from steve by lnx3.holmesgrown.com with local (Exim 4.20) id 1CnfsX-00039p-KM for speakup@braille.uwo.ca; Sun, 09 Jan 2005 09:25:21 -0700 Date: Sun, 9 Jan 2005 09:25:21 -0700 From: Steve Holmes To: speakup@braille.uwo.ca Message-ID: <20050109162521.GB11765@lnx3.holmesgrown.com> Mail-Followup-To: speakup@braille.uwo.ca References: <6.2.0.14.0.20050108015134.01f2b0c8@pop.voyager.net> <20050108154209.GA5846@bruzos.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <20050108154209.GA5846@bruzos.org> User-Agent: Mutt/1.5.6i Sender: "Steve Holmes,,," Subject: Re: Kernel Compilation X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jan 2005 16:25:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would like to add some additional comments about kernel recompilation if possible. I am currently using a 2.6.9 kernel on my Slackware 10.0 settup here. When untarring the kernel source from ftp.kernel.org, let it go ahead and dump into linux-2.6.10 (or whatever version) into /usr/src. in Slackware /usr/src/linux is symbolicly linked to the current version anyway. The current configuration generated by a 'make menuconfig' is .config built at the top of the linux source tree. As suggested earlier, I would copy this .config file into a safe place like your personal home directory so it can be brought back in the next time you do a kernel compile. From what I've read in the README in linux-2.6 kernels, you only have to type 'make' to build kernel static source and modules. I just then do a separate 'make modules_install' when I'm ready to install the modules for prime time use. I also have a couple simple shell scripts that copy the compiled kernel from the ../../../boot directory of the kernel source tree over to the /boot directory. I also use lilo to maintain a separate boot label with this kernel image and preserve one older one incase I break it. Hope this helps. - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFB4VrwWSjv55S0LfERAmIhAJ4r6TLDKPAwcs2o/yc3lU+dyEbFRwCePf6t f7kVrPBs1UriBqv3BrQ40Ng= =+UQV -----END PGP SIGNATURE-----