modprobe.d question.

[F. Heitkamp]

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.

The brute force approach would be to just write a shell script that
executes during the boot process.

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.

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.

I am not using a initial ram disk.

This is on a "linux from scratch" like system, but not LFS.

Any corrections or thoughts?

Fred



--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Kay Sievers]

Post by F. Heitkamp
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.

Post by F. Heitkamp
I am still using SYSV init as well.

Poor choice. :)

Post by F. Heitkamp
The brute force approach would be to just write a shell script that e=

xecutes

Post by F. Heitkamp
during the boot process.

Right, that's the generic SYSV style, and should work.

Post by F. Heitkamp
From what I understand reading docs what adding install fbcon modprob=

e -v

Post by F. Heitkamp
fbcon =C2=A0to =C2=A0a conf file in modprobe.d =C2=A0(say I called it=

fbcon.conf ) would do

Post by F. Heitkamp
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.

Post by F. Heitkamp
I am most familiar with debian and there is a file called /etc/module=

s that

Post by F. Heitkamp
lists modules to be installed during boot, but I think the magic of m=

odprobe

Post by F. Heitkamp
is not used so the dependencies would not get included.

That should work fine on Debian, just add it there.

Post by F. Heitkamp
I am not using a initial ram disk.

That does not matter.

Post by F. Heitkamp
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
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug=
" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html