Thanks for the various comments. I have definitely used cp to copy sage from one place to another before, with expected behaviour on first startup. This time I used scp for some reason. I just redid it using rsync, following Dave's suggestion, and everything is normal.
John On Mon, Apr 25, 2011 at 10:02 AM, Dr. David Kirkby <[email protected]> wrote: > On 04/25/11 08:46 AM, Dima Pasechnik wrote: >> >> >> On Apr 25, 3:39 am, John Cremona<[email protected]> wrote: > >>> I just moved a fresh build in this way (using scp -pr, though source >>> and destination were local) and the first time I run Sage from the new >>> location is starts up normally. > >>> John >> > > > Using rsync will be a far more reliable way to copy files locally than scp. > It will also be far less computationally intensive. scp can use a lot of CPU > time. I know on one of my older Suns which has Gbit ethernet, copying > between two systems with Gbit ethernet is slowed if scp is used due to the > encryption/decryption. > > rsync seems to preserve more attributes about files than does scp, cp or > tar. > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail? > > Dave > > -- > To post to this group, send an email to [email protected] > To unsubscribe from this group, send an email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
