Messages in this thread |  | | Date | Wed, 8 May 1996 22:59:17 -0400 (EDT) | From | Kevin M Bealer <> | Subject | Re: An idea: a database of modules settings |
| |
On Tue, 7 May 1996, Eyal Lebedinsky wrote:
> My original suggestion was to have a kernel API, but the persistent data should not be stored > inside the kernel but on a file. > > I guess insmod/rmmod can do it too, to a point, if a format way is established > by which insmod knowd where the parameters are stored (and makes it available > to the module init) and the module lets rmmod know where the outgoing data > is. Maybe just another well-known symbol like the init/cleanup. > > It is importanat that not only detection info is saved but also user settable > modes (from ioctl). >
Wouldn't it be sufficient to create a directory where the modules can stuff this info and allow the module writers to change their code as they will? (Or patch the modules yourself, if you like.)
__kmb203@psu.edu_________________________Debian__1.1___Linux__1.3.97___ THE LESSER-KNOWN PROGRAMMING LANGUAGES #12: LITHP This otherwise unremarkable language is distinguished by the absence of an "S" in its character set; users must substitute "TH". LITHP is said to be useful in protheththing lithtth.
|  |