On Dec 27, 2007 9:37 PM, Adam Getchell <[EMAIL PROTECTED]> wrote: > > On Dec 22, 2007 1:16 PM, William Stein <[EMAIL PROTECTED]> wrote: > > > Did you first run the VMware vmshrink utility, then turn the vmware > > machine off and exit vmware before creating the 7z file? Also, > > how big is your vmware-sage-deluxe when uncompressed? > > vmshrink gives the result "disk compression disabled". I compiled > vmshrink from source and used the pre-built binary to doublecheck, > I'll have to look into my VMware workstation settings to see if I've > got something off.
I remember vaguely seeing that error message once. You definitely want to fix that, as it will make a _huge_ difference. I don't remember the fix, except I found it by googling around for a bit. > vmware-sage-deluxe (nice name) was about 6.8 Gb as of 2.9. It's a bit > bigger now, but I'll check into reducing it. > > > Do you think you could somewhat commit to making new vmware > > sage releases for "the next 2-3 months", say? > > Sure! I'm upgrading Sage to 2.9.1 right now. In order of priority, I'm > working on: > > 1. Upgrade to 2.9.1 (and follow-ons) If you do "sage -upgrade" you'll get 2.9.1.1 > 2. shrink with vmtools > 3. Secure some space for regular uploads (checking with our local > cluster group right now for access) Send me an offlist email, and I can make an account for you on sage.math.washington.edu > 4. Bundle in vmtools for better graphics performance (last time I > tried, required rpm tools, and didn't build) It's *very* important that the "deluxe" sage vmware machine have the vmware tools fully working. This makes a big difference -- e.g., the mouse will move in and out of the virtual machine more easily, etc. > 5. Build version with more generic monitor resolutions Very likely if you had vmware tools working it would automatically resize the display to whatever resolution the user selects (or however they resize their vmware image). Getting vmware tools working well is always the first step... By the way, the vmware "virtual marketplace" has tons pre-made virtual machines. It's possible you could find one, add Sage to it, and be good to go. I've tried that before and been disappointed though. It would also be very good if a Sage virtual machine could be listed in the VMware tools virtual marketplace. I filled out the forms to get SAge listed once, and they were completely ignored (I heard nothing back from vmware). Perhaps you would have better luck? > I also need some time to look over how you're doing a build from > scratch, to see if I'm off or there's other things that could be done. I just do a straight build. Then i replace all the spkg' files in spkg/standard by empty files, using the command /usr/local/bin/shrink that I wrote. > > Optimally we would just included it on the main sagemath.org website > > under downloads, and mirror it out to the mirrors. > > Okay. I'm a little short on space to put the image up for you to look > at right now, but I expect to get a vmware-sage-deluxe image available > for download so you can look it over in the first week of January or > so. > OK. > What a great tool! I was just giving up on Python for scientific > programming, Thanks! > as they'd taken steps away from functional programming in > Python 3000. I'm worried about that too. :-( What's the latest on it? Anyway, it will be at least a year (minimum; probably more) until Sage is using Python 3000. -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~----------~----~----~----~------~----~------~--~---
