Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

2017-02-07 Thread GK
be determined and were set to 0 ([Errno 2] No such file or directory: '/proc/vmstat') Also, I found this <https://github.com/Microsoft/BashOnWindows/issues/1071>, so maybe the problem is with that WSL does not properly support virtual memory? On Thursday, January 19, 2017 at 2:26:21 PM UTC+3, GK

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

2017-01-19 Thread GK
On Thursday, January 12, 2017 at 2:00:37 PM UTC+3, David Joyner wrote: > > On Thu, Jan 12, 2017 at 3:43 AM, GK <gnk...@gmail.com > > wrote: > > > >> > >> I am not having any problem starting the notebook. You might genuinely > be > >> out o

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

2017-01-12 Thread GK
> > I am not having any problem starting the notebook. You might genuinely be > out of memory, or hard drive space. > > I am not having trouble starting the notebook either, but I can not do anything with it, also, no, I am not running out of memory nor hard disk space. I have increased the

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

2016-12-26 Thread GK
at some previous post, I increased the amount of virtual memory, but nothing changed. On Friday, December 16, 2016 at 2:09:55 AM UTC+3, Bill Hart wrote: > > It works for me too! > > On Thursday, 15 December 2016 07:40:11 UTC+1, GK wrote: >> >> Hi again, thanks t

Re: [sage-devel] Sage runs in Window's 10's new Unix subsystem

2016-12-14 Thread GK
only". >>> >>> >>>> >>>> You can probably fix the memory allocation issues though. You likely >>>> need to increase the Pagefile system size. Windows allocates a >>>> ridiculously >>>> small amount of memory for this.