On 16/10/2004 20:55 Jean Everson Martina said the following:
> Yes I can write a patch to create a new framework for modules, but what 
> I  want is the directions to have it commited in the project. This 
> should be a very large effort, even larger than the internationalization 

then why don't you start on this. as i mentioned there is a current 
framework, though it is very basic. this needs to be enhanced so third 
party module developers could release their modules and users could use 
this framework to drop in the modules into the CF card without having to 
build new images.

i'd think that something like this which works would be very welcomed into 
the m0n0wall project.

> this. A way to do so is having every modules as a new MFS, that can be 
> mounted in /modules directory (just an example), so people developing 
> things that need binaries should have them there. The problem is about 

i was thinking of something like this:

1. uploaded modules thru the webGUI are stored on the CF card (under /conf 
for eg) as tar gzipped images
2. these images are untarred/uncompressed on the fly during bootup and 
install themselves into the memory filesystem
3. the hooks in /etc/rc.bootup and the existing module framework could be 
used to call the modules config parameters and the execute startup options.
4. a simple webGUI page for module management would be needed (add, delete, 
view)

-- 
Regards,                           /\_/\   "All dogs go to heaven."
dinesh at alphaque dot com                (0 0)    http://www.alphaque.com/
+==========================----oOO--(_)--OOo----==========================+
| for a in past present future; do                                        |
|   for b in clients employers associates relatives neighbours pets; do   |
|   echo "The opinions here in no way reflect the opinions of my $a $b."  |
| done; done                                                              |
+=========================================================================+