public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: monolithic kernel warning
Date: Fri, 7 Nov 2008 00:55:15 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.11.07.00.55.14@cox.net> (raw)
In-Reply-To: 49137D33.5090006@nagafix.co.uk

Antoine Martin <antoine@nagafix.co.uk> posted
49137D33.5090006@nagafix.co.uk, excerpted below, on  Thu, 06 Nov 2008
23:26:43 +0000:

> I often use monolithic kernels and I would like to get rid of the
> multiple boot warnings about /lib/modules/whatever directory being
> missing. Somewhere early in the boot could just mkdir && depmod -a, I'm
> just not sure where.

Do you have the modules service in the boot runlevel?  If you're running 
a monolithic kernel, perhaps you should remove it.  (It may also be 
necessary to change your CONFIG_PROTECT and CONFIG_PROTECT_MASK to 
prevent it coming back on upgrades, and maybe even touch an empty file as 
appropriate so the config protection works on it.  I believe I did that 
with some service file at one point, but don't remember which one it was, 
now.)  Of course, you may also need to kill the "needs modules" 
dependencies in various other services.

FWIW I'm running the still far from stable baselayout-2/openrc setup, and 
have been for some time, so I've long forgotten the details on stable 
baselayout and therefore can't easily get too detailed in my answer, but 
the above is what I'd try first in an attempt to deal with it, here.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman	`




      reply	other threads:[~2008-11-07  0:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06 23:26 [gentoo-amd64] monolithic kernel warning Antoine Martin
2008-11-07  0:55 ` Duncan [this message]

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=pan.2008.11.07.00.55.14@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /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