On Mon, Oct 16, 2000 at 02:09:16PM +0200, Joerg Reuter wrote:
- a couple of front ends that just read and write a central configuration file such as /etc/ax25/ax25-config.conf :-) Yes XML would be nice, Tom does use it for its new soundmodem. But it is hard to do in bash ;), should be easy using python/expat however.
- probably a couple of helper applications that can generate the files in /etc/ax25/ (Similar to the things SuSEconfig or debconf does, but independent of it) You can easily split the function which does generate the configuration-files from the UI. They are completely independent. I will do that after my maths examination (beginning of november).
- a single start/stop script that parses this config file Must search my hard-disk. The problem is that the configuration of the ax25-drivers is very different for each driver. You need _lots_ of logic in this script. As I said, I had such a thing already but then Mirko and me merged our projects. My script supported multiple interfaces, but it got very complex.
- the start/stop script should be able to source additional user-defined scripts Easy one, just use run-parts /etc/ax25/init/ (or is this debian-specific, I hope not...)
Result: maximum flexibility, user friendly, maintainable, upgradeable, ...
Sounds nice, but is a lot of work. This is why I am currently pushing ax25-config a little. Sure, it isn't very nice implementation-wise and a little bit annoying to maintain and extend but it works right now and does support a rather wide range of devices. (actually extending isn't that hard because config-file-templates, configuration and CUI are rather seperate). As i mentioned, I am rather busy with uni at the moment and we are preparing the next LinKT-release (mainly documentation) which has higher priority for me. -hp -- Hans-Peter Zorn, Karlsruhe, Germany http://www.stud.uni-karlsruhe.de/~uhsm/ hpz@gmx.net (preferred) http://1409.org/people/hp/ hp@1409.org (hamradio stuff)