mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olaf Titz <olaf@bigred.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: ANN: LKMB (Linux Kernel Module Builder) version 0.1.16
Date: Tue, 21 Jan 2003 22:16:06 +0100	[thread overview]
Message-ID: <E18b5kc-0003BB-00@bigred.inka.de> (raw)
In-Reply-To: <1043098758.27074.2.camel@laptop.fenrus.com>

> 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

and because of that (among other reasons) my other report about
compiling outside of the source directory...

> 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

Only while installing a new kernel. And you install the kernel on the
box it needs to run on, which is not necessarily the box it's compiled
on.

> 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

Only for stand-alone machines which only ever compile and run one
kernel. You don't need a data center to violate that, you just need
the fairly usual three-boxes home network (one of which is mainly a
router/firewall which has no development environment if only for
security reasons, or because it's a scavenged '486).

> 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.

Frankly, I think the main reason is that Linus doesn't care at all
about the kernel build process. We've had a _much_ better solution
already in the 2.5 cycle which was rejected for completely bogus
formal reasons coupled with an explicit "why do we need this at all",
even though it was pointed out over and over again what is broken
currently (or was back then, granted it has improved but not as much
as is desirable and possible).

This blatantly erroneous decision[1] just smells of a blind spot or
carelessness more than careful consideration.

Olaf

[1] it's about of the same category as the original Unix' designers
putting utmp and wtmp in /etc. Linus would never have approved _that_.


  reply	other threads:[~2003-01-21 21:08 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
2003-01-21 21:16             ` Olaf Titz [this message]
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=E18b5kc-0003BB-00@bigred.inka.de \
    --to=olaf@bigred.inka.de \
    --cc=linux-kernel@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 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®