From: "Diego Calleja García" <diegocg@teleline.es>
To: Piet Delaney <piet@www.piet.net>
Cc: rddunlap@osdl.org, fsanchez@mail.usfq.edu.ec,
linux-kernel@vger.kernel.org
Subject: Re: modules problems with 2.6.0 (module-init-tools-0.9.12)
Date: Wed, 16 Jul 2003 02:12:10 +0200 [thread overview]
Message-ID: <20030716021210.56ea8360.diegocg@teleline.es> (raw)
In-Reply-To: <1058313192.21300.988.camel@www.piet.net>
El 15 Jul 2003 16:53:12 -0700 Piet Delaney <piet@www.piet.net> escribió:
> On Tue, 2003-07-15 at 15:22, Randy.Dunlap wrote:
>
> I heard that if you install the new module-init-tools package in
> /sbin that you would be able to boot old kernels. Is that true?
It works here.
i've a debian distro, i apt-get'ed module-init-tools. Man modprobe says:
BACKWARDS COMPATIBILITY
This version of insmod is for kernels 2.5.48 and above. If it
detects a kernel with support for old-style modules (for which much of
the work was done in userspace), it will attempt to run insmod.modu-
tils in its place, so it is completely transparent to the user.
diego@estel:~$ ls -l /sbin/insmod*
-rwxr-xr-x 1 root root 5072 2003-06-15 12:27 /sbin/insmod
-rwxr-xr-x 1 root root 359 2003-03-06 15:50 /sbin/insmod_ksymoops_clean
-rwxr-xr-x 1 root root 95372 2003-03-06 15:50 /sbin/insmod.modutils
Looking at the size, insmod.modutils seems the 2.4 insmod loader.
next prev parent reply other threads:[~2003-07-15 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 22:09 modules problems with 2.6.0 Fernando Sanchez
2003-07-15 22:22 ` Randy.Dunlap
2003-07-15 23:53 ` modules problems with 2.6.0 (module-init-tools-0.9.12) Piet Delaney
2003-07-16 0:12 ` Diego Calleja García [this message]
2003-07-15 20:13 ` Max Valdez
2003-07-16 3:11 ` Piet Delaney
2003-07-16 3:34 ` Randy.Dunlap
2003-07-16 6:34 ` Martin Schlemmer
2003-07-15 22:30 ` modules problems with 2.6.0 Greg KH
2003-07-16 8:43 ` Marc Schiffbauer
2003-07-16 9:10 ` Eugene Teo
2003-07-16 14:49 ` Fernando Sanchez
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=20030716021210.56ea8360.diegocg@teleline.es \
--to=diegocg@teleline.es \
--cc=fsanchez@mail.usfq.edu.ec \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@www.piet.net \
--cc=rddunlap@osdl.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.