From: Arjan van de Ven <arjanv@redhat.com>
To: Olaf Titz <olaf@bigred.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ANN: LKMB (Linux Kernel Module Builder) version 0.1.16
Date: 20 Jan 2003 22:39:19 +0100 [thread overview]
Message-ID: <1043098758.27074.2.camel@laptop.fenrus.com> (raw)
In-Reply-To: <E18ai8O-00032u-00@bigred.inka.de>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
> And what's exactly wrong with the other 99% solution of putting it in
> /usr/src/linux-`uname -r` ? This has exactly the same advantages but
> doesn't mix up between development and runtime environment; /usr/src
> is clearly where source belongs and /lib/modules is an install target.
back then the argument (not mine btw) was that /usr on a lot of machines
is RO (I think debian has an option for that) so that sysadmins there
compile stuff in /root. /lib/modules however IS standardized and needs
to be writable to install a new kernel so making a symlink to the real
place there isn't too bad. In addition it already is the only directory
with per kernel files.. adding a second one was judged not needed. It
has to be somewhere. /lib/modules/ or /usr/src.. who cares. Linus made
the final call and everybody complies with it since then, just because
it doesn't matter THAT much. It just needs to be SOMEWHERE standard and
/lib/modules suffices so far it seems.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-20 21:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 12:31 Shlomi Fish
2003-01-17 12:37 ` Shlomi Fish
2003-01-17 13:12 ` David Woodhouse
2003-01-17 17:00 ` Shlomi Fish
2003-01-17 18:00 ` Sam Ravnborg
2003-01-17 18:28 ` Shlomi Fish
2003-01-18 22:37 ` Olaf Titz
2003-01-18 22:55 ` Arjan van de Ven
2003-01-20 20:03 ` Olaf Titz
2003-01-20 21:39 ` Arjan van de Ven [this message]
2003-01-21 21:16 ` Olaf Titz
2003-01-21 21:30 ` David Lang
2003-01-21 21:46 ` Sam Ravnborg
2003-01-22 11:21 ` David Woodhouse
2003-01-22 11:18 ` David Woodhouse
2003-01-22 19:16 ` Bill Davidsen
2003-01-22 22:17 ` David Woodhouse
2003-01-19 0:12 ` John Levon
2003-01-19 12:55 ` Olaf Titz
2003-01-19 13:06 ` Arjan van de Ven
2003-01-20 20:16 ` Olaf Titz
2003-01-19 18:22 ` Sam Ravnborg
2003-01-20 20:14 ` Olaf Titz
2003-01-20 20:46 ` Sam Ravnborg
2003-01-19 21:17 Paul Zimmerman
2003-01-19 21:24 Paul Zimmerman
2003-01-23 0:20 Hal Duston
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=1043098758.27074.2.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@bigred.inka.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®