On Thu, Feb 16, 2017 at 9:39 AM, William Stein <wst...@gmail.com> wrote:
> On Thu, Feb 16, 2017 at 12:20 AM, Emmanuel Charpentier
> <emanuel.charpent...@gmail.com> wrote:
>> Huh ? I have "only" 4 GB of RAM, to share (to *dedicate*) to boith systems.
>
> I guess I'm probably a lot older than you.... but 4GB of RAM is plenty
> to run VirtualBox + Linux, etc.   I've spent years using laptops with
> a VM and another OS and that much (maybe less) memory, while working
> on Sage.
>
>> Even if Windows may run on 2 GB RAM, I doubt that VM+Linux+Sage+whatever is
>> needed to serve Jupyter would run on 2 GB RAM. Crawl, maybe..
>>
>> Using the "old" notebook might be better here (the browser could run on the
>> Windows side. But the main problem is the *dedication* (*fixed* allocation)
>> of resources to each system.
>>
>> Hell, I don't even know how many execution threads my CPU has...
>
> It doesn't really matter much for using VirtualBox.
>
> You should see if you have VT-x instructions -- that's critical for
> performance.  The Atom Z530 does:
> http://ark.intel.com/products/35463/Intel-Atom-Processor-Z530-512K-Cache-1_60-GHz-533-MHz-FSB
>
>> Less important, but still a hurdle : configuring network-like communications
>> between the two machines. I know how to do this from Liux, but I'm nit so at
>> ease in Windows (I don't even know if Windows Home will let me create the
>> necessary pseudo-adapter, aka tun device in Linux parlance...).
>
> This isn't very hard.  I've done it a million times on Windows, OS X,
> etc.  It used to be kind of hard with VMware back in 1998, but now
> there is this thing called Google which makes it very easy to find
> information about how to do things...
>
>> Thanks for your advice. I'll consider it.
>
> Well give it a shot.  I'm a little conflicted, since obviously it is
> also very useful to us (the sage community) that you're testing Erik
> Bray's cygwin installer, etc...

To be clear (and I'll respond more on this later) the current version
of my Windows build is aimed toward what I guess you could call
"casual" users and is designed more toward making Sage look like a
real "software product" that one can install and have 'just work'.
There are no optional packages yet just because I haven't tested them
all on Cygwin yet, and if there ever are they'll probably be installed
from binaries, not compiled on the user's local machine.

It's not intended for developers of Sage or "power users" who want to
compile and fine-tune their own packages.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to