From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1N4KBE-0003D9-IP for garchives@archives.gentoo.org; Sat, 31 Oct 2009 20:04:10 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 96C83E0905; Sat, 31 Oct 2009 20:04:06 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 734F0E0905 for ; Sat, 31 Oct 2009 20:04:06 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 040DC67467 for ; Sat, 31 Oct 2009 20:04:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -3.152 X-Spam-Level: X-Spam-Status: No, score=-3.152 required=5.5 tests=[AWL=-0.553, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wq-v91R41PF0 for ; Sat, 31 Oct 2009 20:03:59 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 21D4267447 for ; Sat, 31 Oct 2009 20:03:57 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1N4KAr-0000Sg-D8 for gentoo-user@gentoo.org; Sat, 31 Oct 2009 21:03:45 +0100 Received: from athedsl-374302.home.otenet.gr ([79.131.14.28]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 Oct 2009 21:03:45 +0100 Received: from realnc by athedsl-374302.home.otenet.gr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 31 Oct 2009 21:03:45 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Nikos Chantziaras Subject: [gentoo-user] Re: Kernel upgrading and linux symlink Date: Sat, 31 Oct 2009 22:03:04 +0200 Organization: Lucas Barks Message-ID: References: <87hbtfo68r.fsf@newsguy.com> <877hubcu5a.fsf@newsguy.com> <200910312118.22975.alan.mckinnon@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: athedsl-374302.home.otenet.gr User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091019 Thunderbird/3.0b4 In-Reply-To: <200910312118.22975.alan.mckinnon@gmail.com> Sender: news X-Archives-Salt: 94351a8f-39b2-475e-ade1-8b471eab56d1 X-Archives-Hash: b3af17e20fcf43d4fe34860b343310db On 10/31/2009 09:18 PM, Alan McKinnon wrote: > On Saturday 31 October 2009 20:09:37 Harry Putnam wrote: >> Nikos Chantziaras writes: >>> The link is created only if you have the "symlink" USE flag enabled. >>> >>> Also, "Gentoo requires that the [...] symbolic link points to the >>> sources of the kernel you are running" is not entirely correct. It is >>> required only when you want to build something against that >>> kernel. >>> >>> . . . . Obviously, you need to create the symlink if you want to build >>> the newly installed kernel, even though the system is still running an >>> older one. >> >> Why is that obvious? That's what seemed confusing to me. >> >> Nothing about creating it with USE=symlin, eselect, or by hand is a >> problem. Or hard to follow, and I've always just done it by hand. >> > > Nikos is being kind to the document writers :-) > > In fact, the documentation is flat out wrong - there is no requirement for the > symlink to point to the currently running kernel. It must point to the kernel > sources you want to *configure* or use for an emerge that installs a kernel > driver. > > For instance, you might be running 2.6.31-r4 and also have 2.6.31-r3 > installed. To install nvidia-drivers, you must build it *twice* - against each > kernel you want to use it with (nvidia-drivers builds and installs a kernel > driver into /lib/modules/) It's a bit more obfuscated than that. Maybe nvidia-drivers work different, but ati-drivers will build against /usr/src/linux but install the actual modules in /lib/modules/running_kernel. If /usr/src/linux doesn't point to the running kernel, the modules will be installed in the wrong place.