From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] udev-181 and kmod vs module-init-tools
Date: Mon, 19 Mar 2012 14:31:39 -0500 [thread overview]
Message-ID: <CAEH5T2MHSFLHq+Zoax4rsV_bC2cMgV8vTwzTSSV02Lj6rMgRiQ@mail.gmail.com> (raw)
In-Reply-To: <4F6762CD.30407@fu-berlin.de>
On Mon, Mar 19, 2012 at 11:46 AM, Hinnerk van Bruinehsen
<h.v.bruinehsen@fu-berlin.de> wrote:
> it worked flawless for me. Nothing "bad" happened.
> If it's a server you could also build a monolithic Kernel and remove
> the dependency completly since most servers don't need loadable
> modules. It even adds a little security-wise...
Thanks... I tried it, but didn't reboot yet. I was going to upgrade
kernel at the same time, it tells me this during "make install" phase:
DEPMOD 3.2.11-gentoo
Warning: you may need to install module-init-tools
See http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt
But looking in the scripts seems the test is not valid for kmod:
if ! "$DEPMOD" -V 2>/dev/null | grep -q module-init-tools; then
echo "Warning: you may need to install module-init-tools" >&2
echo "See http://www.codemonkey.org.uk/docs/post-halloween-2.6.txt" >&2
sleep 1
fi
so I think it's a false alarm.
Now I just found
http://comments.gmane.org/gmane.linux.kernel.modules/659 this seems to
confirm it. And of course while I was compiling, the new kernel 3.3
has showed up in portage, with this problem fixed. :)
Now I'm rebooting, watching ping replied, fingers crossed... it's
alive! Success. :)
Thanks,
Paul
prev parent reply other threads:[~2012-03-19 19:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 15:47 [gentoo-user] udev-181 and kmod vs module-init-tools Paul Hartman
2012-03-19 16:46 ` Hinnerk van Bruinehsen
2012-03-19 19:31 ` Paul Hartman [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=CAEH5T2MHSFLHq+Zoax4rsV_bC2cMgV8vTwzTSSV02Lj6rMgRiQ@mail.gmail.com \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@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