RE: [gentoo-hardened] Could not load modules.dep

[Charles Taylor]

Don't mess with your scripts... Never know when it
will break something... As root, simply:

touch /lib/modules/kernel-hardened-2.18-r6/modules.dep

Problem solves, and no config/script file tinkering!

It's been working perfectly for me for months.

Charles

--- Clemente Aguiar
<clemente.aguiar@××××××××××××××××.pt> wrote:

>
> See below some feedback on the suggestions given:
>
> > -----Mensagem original-----
> > De: Igor Novgorodov [mailto:igor@××××.net]
> > Enviada: quinta-feira, 10 de Maio de 2007 14:10
> > Para: Clemente Aguiar
> > Assunto: Re: [gentoo-hardened] Could not load
> modules.dep
> >
> > > Since a while ago I have been getting a series
> of errors at
> > start-up
> > > on my servers, such as:
> >
> > > "FATAL: Could not load
> > >
> /lib/modules/kernel-hardened-2.18-r6/modules.dep:
> > > No such file or directory"
> >
> > > I configured my hardened kernels with "loadable
> module support"
> > > disabled, so I think that modules.dep could
> never exist.
> >
> > > First of all, I can see these messages "fly" by
> the console at
> > > start-up, but it seems that they are not logged
> (I can't find them
> > > anywhere). Shouldn't they get logged somewhere?
> > You can try setting RC_BOOTLOG="yes" in
> /etc/conf.d/rc
> > Messages will be logged to /var/log/boot.msg
>
> I did as suggested and emerged
> "app-admin/showconsole" as well (it is a
> requirement for this to work), and most boot
> messages where logged in
> /varlog/boot.msg, but not all, and the ones I
> mentioned where NOT
> logged.
>
>
>
> > > Second, how can I get rid of the messages
> altogether?
> > Just do "rc-update del modules" to remove module
> init script
> > from startup
> >
>
> I did as you suggested, but when I rebooted, a
> warning was issued and
> "modules" init script was automatically added back
> to "boot".
>
> Any other suggestions?
>
> Clemente
> --
> gentoo-hardened@g.o mailing list
>
>

-- 
gentoo-hardened@g.o mailing list