From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Brad Tilley <bradtilley@usa.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Directory where modules are loacted in 2.6.7 build
Date: Wed, 07 Jul 2004 12:09:00 -0400 [thread overview]
Message-ID: <40EC201C.2060906@nortelnetworks.com> (raw)
In-Reply-To: <922iggP8L3328S17.1089215951@uwdvg017.cms.usa.net>
Brad Tilley wrote:
> This is probably a stupid question, but here goes:
>
> When a normal user on a x86 PC builds a 2.6.x kernel in his home
> directory by
> issuing the 'make' command where are the modules placed?
They're left where they are compiled.
To actually put them anywhere, you must do "make modules_install" as root.
Chris
next prev parent reply other threads:[~2004-07-07 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 15:59 Directory where modules are loacted in 2.6.7 build Brad Tilley
2004-07-07 16:07 ` Erik Mouw
2004-07-07 16:09 ` Chris Friesen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-07 17:01 Brad Tilley
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=40EC201C.2060906@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=bradtilley@usa.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.