Why is trouble-maker written in Perl?
Perl was chosen because it was available on all of the initial target systems, and had a minimal amount of module dependencies for the planned development.
Do all of the trouble scripts have to be written in Perl?
No. You may write a trouble script in whatever language you choose. Perl, shell, python, and ruby are the most popular.
Why are the troubles in the kitbag packed with tar but not compressed?
As uncompressing files takes time, and compression does not provide large gains for small files, we felt it was unnecessary to compress the trouble modules.
Additionally, this would require installing more Perl modules.
Why is trouble-maker installed in /usr/local/trouble-maker?
/usr/local/trouble-maker was chosen as an install location because it is a somewhat standard place to put non-system files and because it is unlikely to be in the path.
This protects against accidental execution. If it bothers you, you can add /usr/local/trouble-maker to your path.
Why do I have to type 'yes' every time I run trouble-maker?
This step prevents against accidental execution. You may bypass the check by editing trouble-maker.pl and changing the value of $bypass from 0 to 1
Why do I have to delete /tmp/trouble-maker every time?
This step protects against running trouble-maker twice before solving the first problem. A second run will overwrite the backup and rescue files.