public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <ALESSANDRO.SUARDI@oracle.com>
To: mikpe@csd.uu.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why kernel 2.5.58 only mounts / (not home etc)
Date: Mon, 20 Jan 2003 02:49:07 -0800 (GMT-08:00)	[thread overview]
Message-ID: <5352464.1043059747431.JavaMail.nobody@web11.us.oracle.com> (raw)

Mikael Pettersson wrote:

> On Sat, 18 Jan 2003 16:48:44 -0800 (GMT-08:00), Alessandro Suardi wrote:
> >As I reported in the same thread as the breakage of modules in 2.5.59,
> > module autoloading doesn't work for me since 2.5.58. Using Rusty's
> > module-init-tools 0.9.8 or 0.9.9-pre. Same utils work flawlessly under
> > 2.4.21-pre3.

[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

Indeed, I'm running a RedHat 8.0 and this change to rc.sysinit brought me
 up and running again. Thanks !

--alessandro

             reply	other threads:[~2003-01-20 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-20 10:49 Alessandro Suardi [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-19  9:01 Why kernel 2.5.58 only mounts / (not home etc) Mikael Pettersson
2003-01-19  0:48 Alessandro Suardi
2003-01-18 23:21 Max Valdez
2003-01-18 23:44 ` Andrew Morton
2003-01-18 23:53   ` Max Valdez
2003-01-19  0:48     ` Andrew Morton
2003-01-19  1:34   ` Leopold Gouverneur

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=5352464.1043059747431.JavaMail.nobody@web11.us.oracle.com \
    --to=alessandro.suardi@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.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