[sage-support] Re: win 10, virtualbox 5.1.4, sage 7.3

2016-09-22 Thread Temperus Tempus
Hello, Thanks for your hints. But now it works also with ova on win 10: - Newest VirtualBox 5.1.6 - Sage.ova 7.3 - Instructions according to -- https://ask.sagemath.org/question/32344/vm-virtualbox-sage-70ova-how-to-start/ That works well. DonĀ“t know if it matters: I increased ram of the vi

[sage-support] Re: win 10, virtualbox 5.1.4, sage 7.3

2016-09-12 Thread multiscalar
I should correct that, the size of the .vdi file is in fact ~20GBytes not 8. On Monday, September 12, 2016 at 2:00:06 PM UTC-7, multiscalar wrote: > > I let VirtualBox do dynamic allocation for the disk. I installed Centos7 > development/creative station and built sage7.3 from source. > The size

[sage-support] Re: win 10, virtualbox 5.1.4, sage 7.3

2016-09-12 Thread multiscalar
I let VirtualBox do dynamic allocation for the disk. I installed Centos7 development/creative station and built sage7.3 from source. The size of the .vdi file is ~8GBytes. That shouldn't be too surprising; if you compare that to the .ova file (~3GBytes) the vdi is bigger but still comparable...t

[sage-support] Re: win 10, virtualbox 5.1.4, sage 7.3

2016-09-12 Thread Dima Pasechnik
On Sunday, September 11, 2016 at 7:38:13 PM UTC, multiscalar wrote: > > You might want to consider just installing a linux virtual machine and > building sage from source there. > It's a little bit more work than importing an ova, but longterm it's more > usable. The linux OS + built sage > sh

[sage-support] Re: win 10, virtualbox 5.1.4, sage 7.3

2016-09-11 Thread multiscalar
You might want to consider just installing a linux virtual machine and building sage from source there. It's a little bit more work than importing an ova, but longterm it's more usable. The linux OS + built sage should fit in 10GBytes, so you can in principle have several versions On Thurs