From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Dodge Date: Thu, 22 Jan 2004 03:42:05 +0000 Subject: Re: PATCH: drop symbolink link to kernel headers Message-Id: <20040121224205.D16000@mail.puug.net> List-Id: References: <5701.1074622084@www46.gmx.net> In-Reply-To: <5701.1074622084@www46.gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, Jan 22, 2004 at 01:40:50AM +0100, Dagfinn Ilmari Manns?ker wrote: > Greg KH writes: > > No one should be putting their kernel code in /usr/src/linux, so that's > > just a bad thing to start with. /usr/src/linux points to the version of > > linux that your glibc was built against, that is all. > > No, that's /usr/include/{linux,asm} you're thinking of. They should be > _copies_ of the kernel headers glibc was built against, and not symlinks > to /usr/src/linux/{include,asm}. /usr/src/linux can be whatever you like, True. But because of past misbehavior by distributions and glibc, leading to the sort of confusion above about what might be found in /usr/src/linux, you should really avoid using /usr/src/linux for anything at all. Since at least early 2.4 the kernel README has explictly stated that kernels should not be placed in /usr/src/linux. > and third-party, out-of-tree modules tend to look there I'm sure they do. But that doesn't mean they should :-) -Dave Dodge ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel