starting externalized packages, the sane way
When you are running eg. an apache or torrent client (or other "big" app) from a USB harddrive or stick, you just never know when it's going to be mounted.
As of now, freetz simply tries to start such packages during startup and, when you are lucky the startup of such packages fails, but if you are unlucky, you get software that uses the directory below the mountpoint (i.e. /var/media/ftp/uStor01/, the directory, instead of /var/media/ftp/uStor01/, the mounted partition).
To avoid this in an easy (and pretty straight-forward) manner, externalneeds was created.
Configuration is a simple: "pkgname directory-or-file-to-check-for"
Every package that externalneeds is configured to do the starting-up for is automatically set to manual startup to avoid the problems above.
It's already in a later-to-be-daemonized form (mostly), so making a fully blown daemon, maybe with (a harddrive's / stick's) SerialNo detection, maybe more, maybe less, in either case it shouldn't be too hard (just another thing to check for instead of "just" /etc/init.d/rc.$pkgname status) .
The web-interface only allows you to configure the file itself and the maximum runtime of externalneeds_daemon.sh (via sleeptime and sleepcount).
I don't know if this is (a bit) what "dynamic packages" is supposed to be on about (add in an autorun.inf-style startup script, maybe) and I'm not quite sure if this can even help in the "final" creation of "dynamic packages" for Freetz.
For the time being, I add a .tgz and a patch to the trac system until someone decides to pick it up and add it, or finally implement dynamic packages.