On Mon, Oct 19, 2009 at 10:52 PM, Bill Page <[email protected]> wrote: > > On Tue, Oct 20, 2009 at 12:29 AM, William Stein <[email protected]> wrote: >> >> 3. One could probably replace the "expand to 2GB" vmdk by one that >> expands larger. > > Yes, exactly what I meant. > >> >>> Using a Windows file system shared folder does not work because it >>> does not support linux symbolic links. :-( >> >> It depends what you want to use it for, I guess. But yes, Windows >> doesn't have linux symlinks, which is definitely a problem. >> > > I was thinking of using it to install a "writeable" version of Sage by > copying from /sage. This does not work because the Sage distribution > requires symlinks. Otherwise it works fine to access files and save > them in a manner accessible to windows. > >>> >>> In the meantime I created a new .vdi disk as workspace and I am >>> playing with that. After copying /sage over to this disk I tried >>> './sage -upgrade but something here is still read-only it seems... >>> >>> # ./sage -upgrade >> >> Look at SAGE_ROOT in the file "sage" -- you're still running the old >> version from the read only file system. Just edit SAGE_ROOT to your >> new location. >> > > Ah yes I forgot that. Now it works ... up to this point: > > ./install: line 356: make: command not found
Yes, not having any compilers will cause trouble! > > real 0m0.008s > user 0m0.000s > sys 0m0.004s > Error building Sage. > Error installing Sage! > # > > So now I must look for the development tools but these are apparently > packaged differently as sfs files. How much more would these add to > the size of the Sage image? Exactly 90MB. To install them yourself get this file: http://distro.ibiblio.org/pub/linux/distributions/puppylinux/puppy-4.3.1/devx_431.sfs and stick it in /mnt/home/, then restart. Suddenly GCC, make, etc., should magically appear. I think that's all you have to do. By the way, sfs = "squash file system", which in puppy linux is a compressed filesystem that gets layered on top of another filesystem using unionfs. Very cool. > BTW, how do I kill that annoying "sage-ensure_notify" pop-up message? > I deleted the crontab entry but its still live. Look in /etc/rc.d/rc.local and you'll see -- just delete a line. I didn't actually end up using the crontab entry, since cron isn't even running. >> That is correct. I hope somebody creates a completely separate >> virtual machine aimed at what you want. > > I think an upgradable and package installable version of Sage for > Windows+VirtualBox would be desirable. Among other things this > requires that the Sage shell include gcc and other tools required for > installing spkgs. Yep. I think it can be done for 90MB more for compilers plus a unionfs mounted partition, hopefully. Note that upgrading right now might be possible by simply swapping out the virtual disk that contains the data that is mounted as /sage/.... > >> Maybe you just want to run a full Linux under Windows + VirtualBox >> though, for which there are already oodles and oodles of existing options? >> > > No, that's not very interesting unless for some reason you have no > alternative. If you need windows then I think it is better to run > Windows on VirtualBox under Linux. I do that whenever I can these days > but unenlightened corporate IT managers sometimes do not allow it. :-( Thanks a lot for taking interest in this VirtualBox Sage appliance project! It's really been great getting your feedback. And I would obviously be happy to help with making a version of all this that includes fricas... -- William --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
