From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Thu, 22 Jan 2004 17:28:42 +0000 Subject: Re: PATCH: drop symbolink link to kernel headers Message-Id: <20040122172842.GH14310@kroah.com> 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="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Thu, Jan 22, 2004 at 01:40:50AM +0100, Dagfinn Ilmari Manns=E5ker wrote: > Greg KH writes: >=20 > > 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. >=20 > 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}. Ah yes, you are correct. Got that mixed up... > /usr/src/linux can be whatever you like, and third-party, out-of-three > modules tend to look there (after /lib/modules/$(uname -r)/build and > /usr/src/linux-$(uname -r)) for the current kernel headers. But /lib/modules/`uname -r`/build is much better than defaulting to /usr/src/linux thanks, greg k-h ------------------------------------------------------- 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