From: Kay Sievers <kay@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: modprobe.d question.
Date: Thu, 03 May 2012 14:58:37 +0000 [thread overview]
Message-ID: <CAPXgP10x4mvf5_o79TzeD9eb3pwOzq7zXjJkR8oDL+XW+nMqOg@mail.gmail.com> (raw)
In-Reply-To: <4FA27897.6020409@ameritech.net>
On Thu, May 3, 2012 at 2:22 PM, F. Heitkamp <heitkamp@ameritech.net> wrote:
> I have a module that I want to have installed during the boot process
> (fbcon) but I can't figure out what the standard practice would be to do it.
>
> I am still using SYSV init as well.
Poor choice. :)
> The brute force approach would be to just write a shell script that executes
> during the boot process.
Right, that's the generic SYSV style, and should work.
> From what I understand reading docs what adding install fbcon modprobe -v
> fbcon to a conf file in modprobe.d (say I called it fbcon.conf ) would do
> is if the hot-plugging needed fbcon it would use fbcon.conf instead.
No, that makes no sense. modprobe config is only read if modprobe is
called, but nothing will call it. And 'install' instructions are a
very broken concept, and should not be used. Besides the fact that the
above would not work anyway, because it would never be triggered.
> I am most familiar with debian and there is a file called /etc/modules that
> lists modules to be installed during boot, but I think the magic of modprobe
> is not used so the dependencies would not get included.
That should work fine on Debian, just add it there.
> I am not using a initial ram disk.
That does not matter.
> This is on a "linux from scratch" like system, but not LFS.
It needs to support /etc/modules, which is a Debian-specific file.
Kay
prev parent reply other threads:[~2012-05-03 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 12:22 modprobe.d question F. Heitkamp
2012-05-03 14:58 ` Kay Sievers [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=CAPXgP10x4mvf5_o79TzeD9eb3pwOzq7zXjJkR8oDL+XW+nMqOg@mail.gmail.com \
--to=kay@vrfy.org \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).