Post by omega on Jan 10, 2007 6:58:44 GMT 7
Hi together,
I know, maybe I've opened too many threads in the near past, but this time I really would like to create another one.
I've bumped the version of all my modules to version 1.0 as I think I've finished the design stage for a while and the code for all of them changed substantially. You're advised to install only 1.0 and above versions even though they should be 100% backward compatible.
I've created a new module framework which should allow creating other modules more easily and be more open for further enhancements.
First of all: the new modules will be available at the Unofficial Thecus Wiki: onbeat.dk/thecus/index.php/N5200_Module_List (if they are not there yet, please give the admin some time to upload them).
I was very busy the last couple of days so I was not able yet to document all the changes. The functionality of the packages really wasn't changed. I fixed a bunch of bugs (no serious but nasty ones) and enhanced some of the modules.
The biggest step is the new module structure and the advanced installation process. All modules now are installed into /raid/data/module (yes, this location could also be exported by NFS, RSYNC or SAMBA ) and every installation is logged detailed to a module specific log file (/raid/data/module/logs/...).
The installation log file gets mailed after each installation to everybody who is configured in the Thecus E-Mail notification settings. I've done my own E-Mail notification script which should work with most SMTP MTAs (at least the envelope from address is valid ;D).
Please remember that the autostart module is almost mandatory: almost every module requires this module in order to get started after bootup and stopped on shutdown or reboot.
The autostart module minimizes the changes I needed to do for the original Thecus files (in this case /app/cfg/rc.local) and it will be much more easier to adopt the modules to new firmware versions.
One more note in advance: with the imgdup module which clones the read-only filesystems /img/bin and /img/www we are now able to modify the HTTP server (apache) and especially the web pages too. Without this module this wouldn't be possible.
One module already uses the imgdup module: NOTIFYMAIL. This module fixes the buggy e-mail notification script and with this module everybody should be able to get informed by e-mail for Thecus systems events.
Everything I was writing here is already documented at the Unofficial Thecus Wiki. Please take a look there for further information.
I tried to test all of the modules intensively and I'm quite sure they won't harm your system even something is going wrong. But as always, it is your decision and your risk to use them.
Anyway, I've installed all modules on my own device (I have only one... ) and they are running all the time.
Please share your experiences and keep us informed.
Good night
Andreas
I know, maybe I've opened too many threads in the near past, but this time I really would like to create another one.
I've bumped the version of all my modules to version 1.0 as I think I've finished the design stage for a while and the code for all of them changed substantially. You're advised to install only 1.0 and above versions even though they should be 100% backward compatible.
I've created a new module framework which should allow creating other modules more easily and be more open for further enhancements.
First of all: the new modules will be available at the Unofficial Thecus Wiki: onbeat.dk/thecus/index.php/N5200_Module_List (if they are not there yet, please give the admin some time to upload them).
I was very busy the last couple of days so I was not able yet to document all the changes. The functionality of the packages really wasn't changed. I fixed a bunch of bugs (no serious but nasty ones) and enhanced some of the modules.
The biggest step is the new module structure and the advanced installation process. All modules now are installed into /raid/data/module (yes, this location could also be exported by NFS, RSYNC or SAMBA ) and every installation is logged detailed to a module specific log file (/raid/data/module/logs/...).
The installation log file gets mailed after each installation to everybody who is configured in the Thecus E-Mail notification settings. I've done my own E-Mail notification script which should work with most SMTP MTAs (at least the envelope from address is valid ;D).
Please remember that the autostart module is almost mandatory: almost every module requires this module in order to get started after bootup and stopped on shutdown or reboot.
The autostart module minimizes the changes I needed to do for the original Thecus files (in this case /app/cfg/rc.local) and it will be much more easier to adopt the modules to new firmware versions.
One more note in advance: with the imgdup module which clones the read-only filesystems /img/bin and /img/www we are now able to modify the HTTP server (apache) and especially the web pages too. Without this module this wouldn't be possible.
One module already uses the imgdup module: NOTIFYMAIL. This module fixes the buggy e-mail notification script and with this module everybody should be able to get informed by e-mail for Thecus systems events.
Everything I was writing here is already documented at the Unofficial Thecus Wiki. Please take a look there for further information.
I tried to test all of the modules intensively and I'm quite sure they won't harm your system even something is going wrong. But as always, it is your decision and your risk to use them.
Anyway, I've installed all modules on my own device (I have only one... ) and they are running all the time.
Please share your experiences and keep us informed.
Good night
Andreas