Hi Jason,
I wasn't aware of the "ditto" command, thanks for that!
The -upgrade was a lot faster, indeed. It was done over lunch.
Cheers,
Stan
Jason Grout wrote:
> Stan Schymanski wrote:
>
>> Thanks for your help!
>>
>> cp does not have the -a option on my mac and cp -pR leads to the
>> fol
Stan Schymanski wrote:
> Thanks for your help!
>
> cp does not have the -a option on my mac and cp -pR leads to the
> following error message after startup:
Oh, that's right. On a mac, the "ditto" command is nice.
>
> "Warning: something went wrong updating the easy-install.pth file."
>
>
Thanks for your help!
cp does not have the -a option on my mac and cp -pR leads to the
following error message after startup:
"Warning: something went wrong updating the easy-install.pth file."
However, this time no other problems occurred and I was able to run the
notebook server from the ne
John H Palmieri wrote:
> On Mar 12, 11:38 am, mabshoff dortmund.de> wrote:
>> Never us cp to copy Sage unless you know what you are doing, but use
>> tar.
>
> Hm. I've never had any problems using cp; in fact I routinely do it
> before running 'sage -upgrade'. Does 'cp -pR' count as "knowing wh
On Mar 12, 11:38 am, mabshoff wrote:
>
> Never us cp to copy Sage unless you know what you are doing, but use
> tar.
Hm. I've never had any problems using cp; in fact I routinely do it
before running 'sage -upgrade'. Does 'cp -pR' count as "knowing what
I'm doing"?
John
--~--~-~--~-
On Mar 12, 7:17 am, Stan Schymanski wrote:
> Dear all,
Hi,
> I had a great idea (so I thought) about upgrading in the background
> while the sage server is still running. Here is what I did, but it
> didn't work for some reason: In OS X 10.4, I shut down the server
> briefly, changed into the
