Actually that line is in the file just commented out and replaced with "chmod 755 /usr/local/bin/xastir"
Thus for Dave VK4BDJ's benefit a simple edit of the update-xastir script would fix the problem as long as update-xastir does not get changed with each update. Which would be the equal of a dog chasing its own tail endlessly. 73 Dave KB3EFS On 06/17/2014 08:41 PM, David A Aitcheson wrote: > Curt/Tom, > > This occurrence leads me to wonder if we should consider adding "chmod > 4755 /usr/local/bin/xastir" as the last line (or near to the last line) > to the script ./update-xastir for the next release? > > 73 > Dave > KB3EFS > > > On 06/17/2014 05:58 PM, David wrote: >> Hi All......A couple of days ago i used ./update-xastir on my Linux >> Mint 17 >> box ....update was ok but i found i couldnt access my AX25 tncport >> "socket: Operation" not permitted message came up in terminal that i >> started >> it in......went round and round trying to find the answer..not too >> much white hair to pull out >> >> I had a thought about the chmod of xastir that was in the HowTo:AX25 >> from the Xastir web site... >> went and did the "chmod 4755 /usr/local/bin/xastir" >> and bingo i was back in business >> >> obviously when i did the update it replaced the xastir bin file so >> needed the chmod again.. >> >> them's the breaks .....ive added this one in my notebook so i wont get >> caught again >> >> 73 David VK4BDJ >> _______________________________________________ >> Xastir mailing list >> [email protected] >> http://xastir.org/mailman/listinfo/xastir >> -- David A Aitcheson [email protected] Go Green! Print this email only when necessary. _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
