On Thu, Aug 31, 2017 at 1:15 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> In the long section "Rationale for Cygwin and possible alternatives", I
> would add subsections for each alternative.

Will do.

>> [hardware-assisted virtualization] typically does not come enabled by
>> default (as a security measure)
>
>
> Is that really true? What is non-secure about hardware-assisted
> virtualization?

That's actually a good question.  I don't have a specific citation for
the claim that the default setting is for "security", so maybe I'll
just remove the parenthetical.  That said, there have been
hypervisor-related exploits (see
https://en.wikipedia.org/wiki/Blue_Pill_(software)) and so ISTM safer
to disable by default for the average user, and assume that if they
know what they're doing enough to explicitly want to run a hypervisor
then they're sophisticated enough to twiddle a BIOS setting.

>> the main problem is that 32-bit Windows applications have a user address
>> space limited to just 2 GB (or 3 GB with a special boot flag). This is in
>> fact not enough to fit all of Sage into memory at once.
>
>
> Do you know how this compares to 32-bit Linux? I would expect a similar
> limit there.

This is less of a problem on Linux.  I was light on the technical
details here but the point is that on Cygwin *every* DLL needs to be
given its own pre-assigned, non-overlapping address space so that they
don't have to be relocated at load time (this breaks Cygwin's fork).
So while it's true that you could run out of memory on Linux as well,
the problem here is that on Cygwin you'll run into problems even
before running out of memory.

-- 
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