public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@freemail.ru>
To: LMH <lmh_users-groups@molconn.com>, cygwin@cygwin.com
Subject: Re: pthread help
Date: Fri, 13 Jul 2012 01:20:00 -0000	[thread overview]
Message-ID: <571052876.20120713051457@mtu-net.ru> (raw)
In-Reply-To: <4FFF556D.9080201@molconn.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

      reply	other threads:[~2012-07-13  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-12 19:48 emon
2012-07-12 21:19 ` marco atzeri
2012-07-12 21:52 ` LMH
2012-07-12 22:29   ` Larry Hall (Cygwin)
2012-07-12 22:53     ` LMH
2012-07-13  1:20       ` Andrey Repin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=571052876.20120713051457@mtu-net.ru \
    --to=anrdaemon@freemail.ru \
    --cc=cygwin@cygwin.com \
    --cc=lmh_users-groups@molconn.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).