I guess what you have in mind in running a script to
create inode-entries is to map the devices to user's
static view-point of the device namespace. If that's
the case, consider a mounted-pipe / STREAMS device
and a daemon combination to invoke your script
functionality. This would make your device-interface
non-generic, but cleaner and more effective than a
post-install script ( which will be called only on
module load ).
DevFS would do the job if you provide library based
API for implementing identity-mapping using your
proc data. Somewhat like the ALSA model for sound.
- arvind <arvind@xxxxxxxxxxx>
Do you Yahoo!?
Yahoo! Photos: High-quality 4x6 digital prints for 25Â¢