On Thu, Feb 23, 2017 at 12:54 PM, Chris Jones
wrote:
> For those allergic to command-lines, or afraid of terminals,
>>
>
> I figured for those using macports the above probably did not apply ;)
You'd be surprised. It's not 2000 any more.
--
brandon s allbery kf8nh
On 23/02/17 17:51, Michael Parson wrote:
On Fri, 24 Feb 2017, Dave Horsfall wrote:
On Thu, 23 Feb 2017, Chris Jones wrote:
[...]
If not, then go to in terminal
/opt
assuming that is your macports prefix.
Run 'open .' which will start finder in that area, and then activate TM.
Sir, you
On Fri, 24 Feb 2017, Dave Horsfall wrote:
On Thu, 23 Feb 2017, Chris Jones wrote:
[...]
If not, then go to in terminal
/opt
assuming that is your macports prefix.
Run 'open .' which will start finder in that area, and then activate TM.
Sir, you are a genius :-) Gimme your address, and I'
On Thu, 23 Feb 2017, Chris Jones wrote:
[...]
> If not, then go to in terminal
>
> /opt
>
> assuming that is your macports prefix.
>
> Run 'open .' which will start finder in that area, and then activate TM.
Sir, you are a genius :-) Gimme your address, and I'll send you a
lollipop.
Regret
On 23/02/17 14:38, Dave Horsfall wrote:
Let's say that I accidentally lost a critical Macports file (don't ask).
How would I recover it with Time Machine? It seems that my only options
are to recover an arbitrary file within my home directory, or to restore
the entire Mac, thereby making the w
Let's say that I accidentally lost a critical Macports file (don't ask).
How would I recover it with Time Machine? It seems that my only options
are to recover an arbitrary file within my home directory, or to restore
the entire Mac, thereby making the whole Time Machine concept about as
usef
