To: linux-hotplug@vger.kernel.org
Subject: Re: PATCH: drop symbolink link to kernel headers
Date: Thu, 22 Jan 2004 00:40:50 +0000 [thread overview]
Message-ID: <d8jvfn4lsrx.fsf@wirth.ping.uio.no> (raw)
In-Reply-To: <5701.1074622084@www46.gmx.net>
Greg KH <greg@kroah.com> 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, 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.
--
ilmari
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-01-22 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 18:08 PATCH: drop symbolink link to kernel headers Svetoslav Slavtchev
2004-01-21 23:53 ` Greg KH
2004-01-22 0:40 ` [this message]
2004-01-22 1:51 `
2004-01-22 3:42 ` Dave Dodge
2004-01-22 17:06 ` linas
2004-01-22 17:24 ` Svetoslav Slavtchev
2004-01-22 17:28 ` Greg KH
2004-01-22 17:31 ` Greg KH
2004-02-03 0:52 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d8jvfn4lsrx.fsf@wirth.ping.uio.no \
--to=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.