EMR wrote:manfred wrote:Mac Pro 1.1 and 2.1 unfortunately are not compatible to OS X Yosemite and also incompatible to Little Snitch. Even with Piker-Alpha bootloader or similar approaches.
Whatever the state of the compatibility of early Mac Pros with the Piker-Alpha bootloader is, it was GOOD ENOUGH with Yosemite 10.10.1 AND Little Snitch 3.4.2. Guess what's changed on the very same computer (that's right, an early Mac Pro) with the very same operating system (that's right, Yosemite 10.10.1, thanks to Piker-Alpha's bootloader) and Little Snitch 3.5! That's right, you guessed it! It's Little Snitch 3.5. That's the only thing that's changed. And, as I'm saying, I have it up and running on this unsupported machine (which has been unsupported since Mountain Lion days, which I have run without any trouble, as I have run Mavericks).
So you have to do better than that in your explanation. If an early Mac Pro is "unsupported" (although it works better than many recent "supported" Macs) for Little Snitch 3.5, it was equally "unsupported" for Little Snitch 3.4.2. "Unsupported" as it might be, it worked flawlessly with 3.4.2. How come the 3.5 installer doesn't get to clear the boot and kernel caches on these machines? Since Little Snitch 3.5 can successfully be updated on these machines via Safe Boot, it should be feasible for you to achieve the same result through a more thorough installation procedure. Labelling the problem "unsupported" doesn't cut it.
I have a recent clone so I figured I was safe to try it.
I have just followed the steps outlined by Manfred;
Verify & repair your file system permissions
Start the Disk Utility.app
Select your internal hard drive / ssd in the left column
In the right colum choose »First Aid« > Repair Disk
Reinstall Little Snitch
While still in Safe Boot Mode, start the Little Snitch Installer again and run through the installation process.
Boot your Mac again in Safe Boot mode.
Boot your Mac again normally.
Most likely, the required restart afterwards works as expected and your system is up and running.
……...and LS appears to be working fine.
Jazzguy, nothing against you. Just wanted some feedback from the developer before I went any further.
There was an extra boot. Probably unnecessary but I thought I’d include the info for completeness.
Just had the nightly build update pop up, gave it a miss though.