We need to refactor the init.d code as such:

1. separate start/stop environment independent code from actual init.d code (separate script)
2. create two separate init.d scripts: one for production and another for development

This could probably solve the problem of #2

Within the fishrdb:install task:

• generate the proper init file
• create the appropriate link to the application
• add it to the autostarters
• test

Also: create a fishrdb account with the app

Tape parsing mechanism is functional but seriously difficult to handle

• lexing should be subdivided in three different lexers, possibly using rex
• thorough syntax testing should be performed (not only testing with single note.txt texts)
• line numbering should be tested (it's bugged as it is)
• a fifo queue for better error management should be implemented (so that context is handled in a better way)
• parse errors should be handled inside the parsing code (with the yyerror mechanism)

Feel free to open separate issues for each of these items :-)