All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Estabrooks <eric@urbanrage.com>
To: SELINUX <SELinux@tycho.nsa.gov>
Subject: Re: question about 2.6 modules
Date: Tue, 28 Oct 2003 18:26:04 -0600	[thread overview]
Message-ID: <3F9F091C.5090505@urbanrage.com> (raw)
In-Reply-To: <003b01c39d8d$5ead9690$5d38a8c0@lky>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

lky wrote:

> Hi:
> I reinstalled my linux system today. I installed the Redhat9.0 first.
> Then I installed 2.6-based SELinux. In fact I installed two 2.6
> kernels. One is the maintenance kernel with SELinux disabled and the
> other with SELinux enabled.Before the installation I installed the new
> modutils (downloaded from
> http://www.kernel.org/pub/linux/kernel/people/rusty/modules) for the
> 2.6 kernel first. And then I modified the /etc/rc.sysinit, just let
> '/proc/sys/kernel/modprobe' replaced by '/sbin/modprobe'.After that I
> installed the maintenance kernel first. Everything is ok but when I
> rebooted the new kernel I found modules such as my network card and
> loopback device can't be automatically loaded to work yet. Why? The
> modules should work after installed the new modutils for 2.6 kernel.
> Have I forgot something?
> Thanks!
> lky


do the modules have .ko instead of .o? the 2.6 kernel modules now need
to end in .ko to be automatically loaded, and it is just a name
difference. I had this problem with some modules that I had compiled for
2.6 and I just renamed them and depmod'd and they worked fine.

Eric


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3419 bytes --]

  reply	other threads:[~2003-10-29  0:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-28 19:54 question about 2.6 modules lky
2003-10-29  0:26 ` Eric Estabrooks [this message]
2003-10-29  5:33   ` lky

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=3F9F091C.5090505@urbanrage.com \
    --to=eric@urbanrage.com \
    --cc=SELinux@tycho.nsa.gov \
    /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.