Would like to propose Flightgear's terrasync should included as an init script. Maps should be downloaded to a global file location such as /usr/local or other defined global file location utilizing /etc/conf.d/terrasync. Reproducible: Always Expected Results: Just a thought. Having a normal user run flightgear without having any maps seems like of lame from what I've seen within the past day or so! A normal user won't know or have time to run the terrasync binary in addition to figuring out how to even run flightgear. Another option, is to include a terrasync option within fgrun. (Not to mention, fixing fgrun bugs.)
Details on the terrasync command can be found here: http://wiki.flightgear.org/flightgear_wiki/index.php?title=Installing_Scenery#TerraSync One question occurs, "What folder should be used to download maps to?" Once answered, the init script can be easily included. <shrugs> If no votes, we should probably close this bug.
i feel this requires for the init script to be capable of handling multiple users, which it is not. terrasync is something you run alongside your actual flightgear instance, not some daemon multiple flightgear instances can access.
terrasync should not be added as a init script, it should be started ether by FGRun in the GUI ( KDE/GNOME ) or by the user at runtime ( if they are running from the command line they should understand how to do this ). Having terrasync would be a waste of resources to run all the time. The same would be true for Atlas and FGCom. If FGRun isn't available that should be the priority, as it would be needed by your "average user".
Vote to close my bug then. Especially since I've never had any more free time for the past years. I see your point concerning terrasync requiring to be run as user during multiplay. This is likely an upstream issue -- likely resolved by now, but will mark as wontfix.
