On 5/16/07, Christopher Faylor
<cgf-use-the-mailinglist-please(spammersareevil)cygwin.com> wrote:
On Wed, May 16, 2007 at 09:32:10PM -0600, Morgan Gangwere wrote:
>one of them (for Intel Mac processors with Dual Cores in some stores)
>there was a driver that would not allow Cygwin to talk to the device
>like UNIX does because it did not have "Hyperviser" mode access -
>special access to let the software kernel run on the CPU directly...
>(listen to "security now - Blue Pill" for more info) - x86 normal
>systems are fine with the system at current because they do not allow
>for Hypervisor.
Cygwin is a standard Windows DLL which uses Windows APIs to emulate
linux. The words "talk to the device like UNIX does" do not make sense
in that context.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
i must be confused then - i can talk to /dev/hda2 like it was a real
UNIX device -- am i wrong is saying that we do attempt to use windows
as a proxy for the real hardware?
--
Morgan gangwere
"Space does not reflect society, it expresses it." -- Castells, M.,
Space of Flows, Space of Places: Materials for a Theory of Urbanism in
the Information Age, in The Cybercities Reader, S. Graham, Editor.
2004, Routledge: London. p. 82-93.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
