From: Peter Samuelson <peter@cadcamlab.org>
To: ferret@phonewave.net
Cc: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
Petr Vandrovec <VANDROVE@vc.cvut.cz>,
Dana Lacoste <dana.lacoste@peregrine.com>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: Linus's include file strategy redux
Date: Sat, 16 Dec 2000 17:43:51 -0600 [thread overview]
Message-ID: <20001216174351.N3199@cadcamlab.org> (raw)
In-Reply-To: <20001215195611.L829@nightmaster.csn.tu-chemnitz.de> <Pine.LNX.3.96.1001215193529.19208C-100000@tarot.mentasm.org>
In-Reply-To: <Pine.LNX.3.96.1001215193529.19208C-100000@tarot.mentasm.org>; from ferret@phonewave.net on Fri, Dec 15, 2000 at 07:37:49PM -0800
[ferret@phonewave.net]
> Do you have an alternative reccomendation? I've shown where the
> symlink method WILL fail. You disagree that having the configured
> headers copied is a workable idea. What else is there?
4.5 more megabytes, per kernel, on my root filesystem. (That's *after*
pruning the extra include/asm-*/'s.) Thanks but no thanks.
Symlinks fail only if you move or delete your tree. By doing that, you
have proven that you actually know what and where your kernel sources
are, which in turn is strong evidence that you are not in need of those
"External Module Compiling for Dummies" scripts.
Conversely, by actually trusting a random script to compile an external
module unaided, the user is all but declaring himself incapable of
messing around with the /usr/src/linux that came pre-installed.
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-17 0:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-15 16:56 [OT] Re: Linus's include file strategy redux Petr Vandrovec
2000-12-15 16:00 ` Dana Lacoste
2000-12-15 16:16 ` Eli Carter
2000-12-15 17:31 ` ferret
2000-12-15 18:56 ` Ingo Oeser
2000-12-16 3:37 ` ferret
2000-12-16 6:57 ` Keith Owens
2000-12-16 16:40 ` ferret
2000-12-16 23:43 ` Peter Samuelson [this message]
2000-12-17 3:05 ` ferret
2000-12-17 8:08 ` Peter Samuelson
2000-12-17 20:08 ` ferret
2000-12-18 3:58 ` Peter Samuelson
2000-12-18 19:21 ` ferret
-- strict thread matches above, loose matches on Subject: below --
2000-12-15 17:09 Petr Vandrovec
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=20001216174351.N3199@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=VANDROVE@vc.cvut.cz \
--cc=dana.lacoste@peregrine.com \
--cc=ferret@phonewave.net \
--cc=ingo.oeser@informatik.tu-chemnitz.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