mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mikael Pettersson <mikpe@user.it.uu.se>
Cc: davidsen@tmr.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Module loading on demand
Date: 22 Feb 2003 17:41:15 +0000	[thread overview]
Message-ID: <1045935675.4721.1.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <200302221545.h1MFjmkW006417@harpo.it.uu.se>

On Sat, 2003-02-22 at 15:45, Mikael Pettersson wrote:
> If this is the RedHat system you mentioned in your post on sym53c8xx
> loading oddity, then you need apply the fix below which I posted to
> LKML on Jan 19th.
> 
> ===snip===
> If you're running a RedHat system, you'll also need the following
> patch to /etc/rc.d/rc.sysinit. Without it the kernel's modprobe and
> hotplug functionalities will be disabled by rc.sysinit.
> 
> --- /etc/rc.d/rc.sysinit.~1~	2002-08-22 23:10:52.000000000 +0200
> +++ /etc/rc.d/rc.sysinit	2003-01-14 03:04:57.000000000 +0100
> @@ -334,7 +334,7 @@
>      IN_INITLOG=
>  fi
>  
> -if ! grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/ksyms ]; then
> +if ! grep -iq nomodules /proc/cmdline 2>/dev/null && [ -f /proc/modules ]; then
>      USEMODULES=y
>  fi

The other nasty is that if you install Rusty's rpms for the better module tools, and
then install a Red Hat kernel errata your errata kernel will not boot because the
Rusty tools replace insmod.static with a tool which only works standalone on 2.5. Its
not a big deal since most people who build 2.5 kernels build their own 2.4 ones too,
and you can fix the initrd by hand, but it is one to know about.


  reply	other threads:[~2003-02-22 16:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-22 15:45 Mikael Pettersson
2003-02-22 17:41 ` Alan Cox [this message]
2003-02-22 16:57   ` Magnus Danielson
  -- strict thread matches above, loose matches on Subject: below --
2003-02-22 13:43 Bill Davidsen
2003-02-22 16:48 ` Bart De Schuymer

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=1045935675.4721.1.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@user.it.uu.se \
    /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

all inboxes | Powered by JetHome®