Date: Fri, 13 Jul 2012 05:14:57 +0400
From: Andrey Repin <anrdaemon@freemail.ru>
Reply-To: Andrey Repin <cygwin@cygwin.com>
Message-ID: <571052876.20120713051457@mtu-net.ru>
To: LMH <lmh_users-groups@molconn.com>, cygwin@cygwin.com
Subject: Re: pthread help
In-Reply-To: <4FFF556D.9080201@molconn.com>
References: <34152902.post@talk.nabble.com> <4FFF4704.2030005@molconn.com> <4FFF4FB6.4010402@cygwin.com> <4FFF556D.9080201@molconn.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

Greetings, LMH!

> Sorry for the confusion. It is probably better classified as a Linux 
> emulator.

It's not more an emulator, than WINE. Which is NOT an emulator.

> I think of it more or less as a virtualized OS,

Which is totally wrong thought.
It's not virtualized, it's exactly opposite. Pretty much naturalized. you
could even share handles between Cygwin and non-Cygwin processes.

> but that's not exactly right either (I don't think it has it's own kernel,
> etc). 

> I meant to make an analogy of the different between installing and 
> configuring an OS, and installing/configuring/using applications that 
> run on the OS, to point out that the previous post was more like the 
> latter. I guess I didn't do that very well.

Well, Cygwin in essence is a library. cygwin1.dll
the rest is a collection of tools built over it. But they are hardly
necessary, if you don't need them.

Also, please don't top-post. Thank you.


--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 13.07.2012, <05:10>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple