From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: installing modules to ($PREFIX)/lib/modules/2.....
Date: Fri, 8 Nov 2002 10:59:14 -0500 [thread overview]
Message-ID: <20021108155914.GE1319@rdlg.net> (raw)
In-Reply-To: <20021108155537.GA1027@mars.ravnborg.org>
Didn't work. Put them in /lib/modules/2.4.18. (Didn't bite me this time
because my server is on a different kernel but will in the near future).
I cut and past exactly as below.
Thus spake Sam Ravnborg (sam@ravnborg.org):
> Date: Fri, 8 Nov 2002 16:55:37 +0100
> From: Sam Ravnborg <sam@ravnborg.org>
> To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>,
> Linux-Kernel <linux-kernel@vger.kernel.org>
> Subject: Re: installing modules to ($PREFIX)/lib/modules/2.....
>
> On Fri, Nov 08, 2002 at 10:41:32AM -0500, Robert L. Harris wrote:
> > I've compiled my kernel and modules but want to install the modules to
> > /tmp/lib/modules/2.4.18 so I can tar that up and move it to the server
> > in question. Is there a system for doing this built into the kernel
> > compile structure I haven't found yet?
>
> make INSTALL_PATH=/tmp modules_install
> IIRC this is true for 2.4 as well.
>
> Sam
:wq!
---------------------------------------------------------------------------
Robert L. Harris | PGP Key ID: FC96D405
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
FYI:
perl -e 'print $i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10);'
next prev parent reply other threads:[~2002-11-08 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-08 15:41 installing modules to ($PREFIX)/lib/modules/2 Robert L. Harris
2002-11-08 15:55 ` Sam Ravnborg
2002-11-08 15:59 ` Robert L. Harris [this message]
2002-11-08 16:21 ` Sam Ravnborg
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=20021108155914.GE1319@rdlg.net \
--to=robert.l.harris@rdlg.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.