Re: Adding custom module to modules.conf
Jens.Toerring_at_physik.fu-berlin.de
Date: 10/04/04
- Next message: Grant Edwards: "Re: processes vs threads advantages?"
- Previous message: Måns Rullgård: "Re: processes vs threads advantages?"
- In reply to: John: "Re: Adding custom module to modules.conf"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 4 Oct 2004 13:32:07 GMT
John <red0356@yahoo.com> wrote:
> First and foremost, thanks to both of you for your quick replies - I
> hope I will gain enough knowledge to help others.
> Modifying the modules.conf file to both of your suggestions worked:
> alias char-major-253 <driver name>
> My attempt was not to rely on the major number being 253, because my
> kernel module dynamically obtains this major number during init. I
> thought specifying the device node name instead of char-major-# would
> provide this capability. What is the preferred method for dealing
> with modules that have dynamic major numbers?
Have a script that loads it on e.g. boot and then creates the device
file(s) with the correct major device number you get from scanning the
file /proc/devices for the module name. Have another script (or the
same script when invoked with a different argument) that removes the
device files on shutdown. Rather easy to realize with a small script
in /etc/init.d.
Regards, Jens
-- \ Jens Thoms Toerring ___ Jens.Toerring@physik.fu-berlin.de \__________________________ http://www.toerring.de
- Next message: Grant Edwards: "Re: processes vs threads advantages?"
- Previous message: Måns Rullgård: "Re: processes vs threads advantages?"
- In reply to: John: "Re: Adding custom module to modules.conf"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
