mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: ferret@phonewave.net
Cc: 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: Fri, 15 Dec 2000 19:56:11 +0100	[thread overview]
Message-ID: <20001215195611.L829@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <FBF96516CD5@vcnet.vc.cvut.cz> <Pine.LNX.3.96.1001215093002.16439B-100000@tarot.mentasm.org>
In-Reply-To: <Pine.LNX.3.96.1001215093002.16439B-100000@tarot.mentasm.org>; from ferret@phonewave.net on Fri, Dec 15, 2000 at 09:31:57AM -0800

On Fri, Dec 15, 2000 at 09:31:57AM -0800, ferret@phonewave.net wrote:
> > Maybe you did not notice, but for months we have
> > /lib/modules/`uname -r`/build/include, which points to kernel headers,
> > and which should be used for compiling out-of-tree kernel modules
> > (i.e. latest vmware uses this).
> 
> This symlink really should be a copy instead, because the finished kernel
> may be installed on a machine that does not have kernel source installed
> on it. Dangling symlinks are BAD.

But if you compile for another machine, this copy is bad. It also
takes to much time and space to create this copy.

I really disagree here.

Regards

Ingo Oeser
-- 
10.+11.03.2001 - 3. Chemnitzer LinuxTag <http://www.tu-chemnitz.de/linux/tag>
         <<<<<<<<<<<<       come and join the fun       >>>>>>>>>>>>
-
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/

  reply	other threads:[~2000-12-15 18:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-15 16:56 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 [this message]
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
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
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=20001215195611.L829@nightmaster.csn.tu-chemnitz.de \
    --to=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=VANDROVE@vc.cvut.cz \
    --cc=dana.lacoste@peregrine.com \
    --cc=ferret@phonewave.net \
    --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®