public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marc Mutz <Marc@Mutz.com>
To: Peter Samuelson <peter@cadcamlab.org>
Cc: Android <android@turbosport.com>, linux-kernel@vger.kernel.org
Subject: Re: Questions about Kernel 2.4.0.*
Date: Fri, 01 Dec 2000 16:01:12 +0000	[thread overview]
Message-ID: <3A27CB48.38A1907C@Mutz.com> (raw)
In-Reply-To: <001c01c05a86$45bb6380$19211518@vnnys1.ca.home.com> <20001130060732.A14250@wire.cadcamlab.org>

Peter Samuelson wrote:
> 
<snip>
> Many people limit their e-mail messages to 80 columns.  What for?
> 
CF'mon, linebreaks are bloat! Those extra characters all around :-)

> The 'build' symlink is to make it easier for external module
> installation scripts to find the build directory for a given kernel.
> This build directory, in turn, will yield the correct header files,
> correct .config, correct compiler flags, etc., all of which can be
> important for building a working module.
> 

I hope 2.4.0 then does that better than 2.2.17:

$ ls /lib/modules/2.2.17*/build -l
/lib/modules/2.2.17/build -> /usr/src/linux
/lib/modules/2.2.17i10-0001/build -> /usr/src/linux
/lib/modules/2.2.17i8-0001/build -> /usr/src/linux
/lib/modules/2.2.17i8-0002/build -> /usr/src/linux
/lib/modules/2.2.17i8p2/build -> /usr/src/linux

though in all cases /usr/src/linux was only a symlink to the
corresponding tree in /usr/src/Linux/2/2/17/...
Should that not be first converted to paths that contain no symlinks?

Marc

-- 
Marc Mutz <Marc@Mutz.com>     http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics

PGP-keyID's:   0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)


-
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-01 17:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-30  4:30 Questions about Kernel 2.4.0.* Android
2000-11-30 12:07 ` Peter Samuelson
2000-12-01 16:01   ` Marc Mutz [this message]
2000-12-01 18:27     ` [uPATCH] " Peter Samuelson
2000-12-01 18:38       ` Marc Mutz
2000-12-01 20:26         ` Peter Samuelson
  -- strict thread matches above, loose matches on Subject: below --
2000-11-30  4:38 Android
2000-11-25 22:20 Questions about Kernel 2.4.0.? Android
2000-11-25 23:45 ` Keith Owens
2000-11-28  4:31 ` Android

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=3A27CB48.38A1907C@Mutz.com \
    --to=marc@mutz.com \
    --cc=android@turbosport.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter@cadcamlab.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