On Oct 21, 4:32 pm, kcrisman <kcris...@gmail.com> wrote: > On Oct 21, 2:53 am, Ferren <ferren.macint...@gmail.com> wrote: > > > Good point. However, I copied the version number from the README file, > > which says 10.4, because copying from the DMG is messier. The DMG > > claims to be 10.6. > > Then I'm REALLY glad we are changing the README in the next release! > That file just gives a hypothetical name for the release so we didn't > have to change it every time, incidentally. > > So you are saying you have the 10.6 DMG and it's throwing this error > on a Snow Leopard machine? Assuming you didn't do anything weird to > your Xcode (and don't have Macports/Fink), you could really just > download the source and build it, of course. > > The .sage/ directory should be in your top level home directory. If > you open Terminal, and do > > ls -a .sage/ > > you'll either get an error if it doesn't exist, or it will list things > for you. You are correct that the error looks like you need to allow > Sage to change the permissions. It sounds like you already know how > to do this, so I would at least try chmod on that directory, which > should be small if you haven't used Sage much yet. Do you have > unusually strict permissions set up? > > - kcrisman
Strict permissions? Not intentionally! The problem thatd sent my Mac to the guru was that Terminal used my full name on every command line, using up too much space where a simple 'fm' would have been fine. One needed to set up a new user to change this behavior; when I got the new user set up, he didn't have access to anything. I got tired of changing permissions and made the whole disk accessible to myself under any user name. Then I neglected to repair permissions, which evidently protects some essential files from something, because things went to pieces in a hurry. Now, in addition to any Unix-related problems, I may have an idiosyncratic Mac problem. When my Mac guru put Snow Leopard on it (while he was repairing the permissions problem), he set me up with no password for my user account. This appears to be the password that sudo expects--but as of OS X 10.5 (I have 10.6.4), a carriage return is no longer recognized as indicating 'no password', and gets the standard error message. There is a way of changing the root password, described by Apple at http://support.apple.com/kb/ht1528 but so far no version of this has had any effect. Nor has chmod had any effect. There is considerable confusion in my mind about passwords, and I haven't experimented with changing my user account password. Half the time I get the impression that this is the same as the root password-- but then why are there different ways of changing the 2? Experience suggests that the most probable result of messing about with passwords is that I will end up trying to get my machine back into the hands of the local guru--who is 50 km away and 500 m higher up the mountain, not on a bus line, and me with a bicycle. So I experiment somewhat reluctantly. Got any expert Snow Leopards around there? -- To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to sage-support+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-support URL: http://www.sagemath.org
