All of lore.kernel.org
 help / color / mirror / Atom feed
From: "PORTER,CHRISTOPHER B" <console@ufl.edu>
To: Thomas Bleher <bleher@informatik.uni-muenchen.de>
Cc: SELinux@tycho.nsa.gov
Subject: Re: Module problems after 2.4 upgrade
Date: Sun, 11 Jan 2004 23:35:02 -0500 (EST)	[thread overview]
Message-ID: <655108679.1073882102217.JavaMail.osg@spnode33> (raw)

I'm not familiar with the process of or need to relabel that 
directory. After compiling the kernel to a floppy disk I did "make 
modules" and "make modules_install", which both seemed to work. 
I'm a bit boggled as to why the system then can't find the modules 
when it can if I simply remove the floppy and boot from the non-SE 
kernel. In other words, the configuration files haven't changed.


Thanks for the suggestion though,


Christopher Porter
console@ufl.edu

On Sun Jan 11 17:04:24 EST 2004, Thomas Bleher 
<bleher@informatik.uni-muenchen.de> wrote:

> * "PORTER,CHRISTOPHER B" <console@ufl.edu> [2004-01-11 22:46]:
>> KERNEL: 2.4.20-8
>> OS: Redhat 9 (Shrike)
>> 
>> I've installed the SE kernel, done make bzdisk, and done make 
>> modules and make modules_install. Everything exited 
>> successfully, and the floppy boots fine. However, when the 
>> system goes to start various services and load modules, I get a 
>> range of problems such as those that follow:
>> 
>> "modprobe: Can't locate module ..."
>> 
>> "Do you need to install insmod?"
>> 
>> I double-checked and made sure that loadable module support WAS 
>> compiled in. I tried once before to grab new modutils but it 
>> didn't pan out. Any suggestions or known problems?
>  Have you relabeled your /lib/modules? Only matters if you boot 
> up in
> enforcing mode, which is not clear from your message.
> 
> Just a random thought, because I stumbled over this two times 
> today.
> 
> Friendly,
> Thomas
> 
> --
> This message was distributed to subscribers of the selinux 
> mailing list.
> If you no longer wish to subscribe, send mail to 
> majordomo@tycho.nsa.gov with
> the words "unsubscribe selinux" without quotes as the message.
> 
> 



--
PORTER,CHRISTOPHER B


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

             reply	other threads:[~2004-01-12  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-12  4:35 PORTER,CHRISTOPHER B [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11 21:01 Module problems after 2.4 upgrade PORTER,CHRISTOPHER B
2004-01-11 22:04 ` Thomas Bleher

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=655108679.1073882102217.JavaMail.osg@spnode33 \
    --to=console@ufl.edu \
    --cc=SELinux@tycho.nsa.gov \
    --cc=bleher@informatik.uni-muenchen.de \
    /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.