>
> Guillaume Rousse wrote on Sat, Mar 09, 2002 at 02:30:01PM +0100 :
>
> > /etc/module.conf only maps modules to a given major/minor number, it
> doesn't
> > triggers module loading.
It does assuming proper modules.conf. When you try access device via
special file and now driver for the requested major number has been
registered and autoloading is enabled in kernel (default in Mandrake)
kernel tries to modprobe {char,block}-major-N. Because modprobe has many
standard majors built in you usually do not need explicit entrie for
common devices.
> > If you want some modules to be loaded automatically at start-up, use
> > /etc/modules instead.
>
> General question. Suppose I have an LT winmodem (say it's pcmcia).
Is
> it better to have an rpm postinstall script add to /etc/modules:
> lt_serial
> or add to /etc/conf.modules:
> alias /dev/modem
>
alias /dev/modem will not work at all.
If it a system without devfs you may either add to /etc/modules or add
alias char-major-N lt_serial
where N is major number (if it has any specific).
If it a system with devfs and lt_serial is devfs-aware and registers
specific device names you can just add
alias /dev/name-for-lt_modem lt_modem
and (once) create link /dev/modem -> name-for-lt_modem
> The modules.conf entry will seemingly work better for pcmcia events,
but
> the modules entry seems to be adequate for pci. Comments?
>
Yes, /etc/modules generally works only if device is available at boot
time.
-andrej
