From: steve roemen <sdroemen@cox.net>
To: jburks@wavicle.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5.47 bk latest pull
Date: Fri, 15 Nov 2002 19:43:51 -0600 [thread overview]
Message-ID: <200211151943.51968.sdroemen@cox.net> (raw)
In-Reply-To: <20021116012156Z267181-32597+23019@vger.kernel.org>
Jeff Garzik replied with this:
Are you using the Rusty's modutils, or the old, no-longer-works-with-2.5
modutils?
i was still using modutils 2.4.19 so that is the problem.
i asked jeff where the new modutils is and he replied:
search for Rusty's module-related patches on lkml, I don't have a URL
handy, sorry :(
They don't work with 2.4.x... currently there is a hack solution where
Rusty's modutils "make install" renames the current modutils to
<program>.old. Then when you run Rusty's modprobe, if it's a 2.4
kernel, the program will do nothing more than exec modprobe.old. (I
don't like it that way, but such as it is with a development kernel...)
anybody have the url for these new modutils?
-steve
On Friday 15 November 2002 11:08 am, Joe Burks wrote:
> I've had this same problem using 2.5.47bk4 from kernel.org.
>
> I also noticed that make modules_install no longer runs depmod, so my
> module dependencies didn't get set up until I ran depmod manually which
> then exposed the QM_MODULES problem.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-11-16 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 17:08 2.5.47 bk latest pull Joe Burks
2002-11-16 1:43 ` steve roemen [this message]
2002-11-16 1:48 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-11-16 0:40 steve roemen
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=200211151943.51968.sdroemen@cox.net \
--to=sdroemen@cox.net \
--cc=jburks@wavicle.org \
--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