I’ve finished repackaging piaware 1.19-3 with my own policy changes.
If you’re happy with FlightAware’s 1.19-3 release then there’s no real reason to use this.
It is mostly aimed at those who want to make different policy decisions about how piaware behaves.
$ wget https://github.com/mutability/mutability-repo/releases/download/v0.1.0/mutability-repo_0.1.0_armhf.deb $ sudo dpkg -i mutability-repo_0.1.0_armhf.deb $ sudo apt-get update $ sudo apt-get remove piaware # sorry, it's awkward to make the two versions coexist $ sudo apt-get install piaware-mutability $ sudo apt-get install dump1090-flightaware # or dump1090-mutability, or faup1090 $ sudo dpkg-reconfigure piaware-mutability
There were a couple of bugfixes and some code rearrangement needed along the way, but this version has fundamentally the same features as FlightAware’s version, just configured differently.
In summary this is what is done differently:
piaware runs as an unprivileged user, not as root
piaware can be configured via debconf / dpkg-reconfigure
config files live in /etc, not in /root
log files live in /var/log, not in /tmp
log rotation is done by logrotate, not by piaware itself
external commands that piaware wants to run, e.g. “restart dump1090” or “start faup1090” or “upgrade system packages”, are delegated to user-editable shellscripts in /etc/piaware.hooks
the default hooks will gain root access via sudo, if permitted, for the specific commands they need to run
there’s a sudo configuration provided that has the necessary commands (all commented out by default)
sending of system health information (CPU temperature etc) to FlightAware can be disabled
echoing of log messages to FlightAware can be disabled
Based on FlightAware piaware v1.19-3
They’re on github. Look here.
what are you talking about my code is PERFECT!
Create github issues, email, or post here on the forum please