I'm maintaining both a full Time Machine backup and a clone of my primary volume using SuperDuper! to update the clone volume incrementally, nightly. I may be a little paranoid, but hey, better safe than sorry. If anything nasty happens to the primary volume, I can immediately restart from the clone (it did happen once to me about nine or ten years ago).
Here is my issue with LS. It is really annoying that the first time I boot up from the cloned volume after an incremental update, Little Snitch asks if I want to use the new rules or the old factory ones. Every time after each clone update. What's worse is that when the LS dialog box pops up during the booting sequence, the dreaded rosetta also pops up and the dialog box becomes unresponsive to any click on the option buttons. It seems however that it does actually register the click because the boot up completes with the new updated rules enabled.
Why does LS do this? If I make a clone I expect it to behave the same as the original volume. Can LS be set to understand this, so that I can reboot there unattended?
I have a 2009 iMac with OS X 10.8.2 and LS 3.0.1, however, the issue goes back years.
Here is my issue with LS. It is really annoying that the first time I boot up from the cloned volume after an incremental update, Little Snitch asks if I want to use the new rules or the old factory ones. Every time after each clone update. What's worse is that when the LS dialog box pops up during the booting sequence, the dreaded rosetta also pops up and the dialog box becomes unresponsive to any click on the option buttons. It seems however that it does actually register the click because the boot up completes with the new updated rules enabled.
Why does LS do this? If I make a clone I expect it to behave the same as the original volume. Can LS be set to understand this, so that I can reboot there unattended?
I have a 2009 iMac with OS X 10.8.2 and LS 3.0.1, however, the issue goes back years.