pcd, modprobe, and kerneld
I recently acquired an HP-7100 CD-R/W drive. I re-built my kernel for modular
support, specifically:
paride
epat
pcd/pg
Everything works like a charm if I load paride, then epat, then pcd, and then
access the drive. Now, I'd like to start automating these steps. In my
modules.dep, I see that pcd depends on paride, and epat depends on paride.
I know that epat must also be installed before pcd will work, but modules.dep
does not show a dependency there. So, can I:
1. Explicitly add dependency information to /etc/conf.modules? Something
like "pcd depends epat", or similar?
2. Use the "pre-install" directive in /etc/conf.modules to effect the behavior
I want, such as: "pre-install pcd modprobe epat"?
3. In some other way convince depmod that pcd depends on epat?
I would also like to convince kerneld that when I access the device /dev/pcd0,
the pcd module should be loaded. By "access the device", I mean something
like:
$ mount -t iso9660 /dev/pcd0 /cdrom
When I enter this command, I want kerneld to load the pcd module, if necessary.
Is this the behavior I should expect from kerneld? Come to think of it, maybe
kerneld is trying to load the module but failing for the reasons outlined above.
I'll have to look into this more when I get home.
Marc
----------
Marc Mongeon <mongeon@bankoe.com>
Unix Specialist
Ban-Koe Systems
9100 W Bloomington Fwy
Bloomington, MN 55431-2200
(612)888-0123, x417 | FAX: (612)888-3344
----------
"It's such a fine line between clever and stupid."
-- David St. Hubbins and Nigel Tufnel of "Spinal Tap"
Reply to: