public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: DJ Delorie <dj@delorie.com>
To: tag@ibis.odessa.ua
Cc: cygwin@cygwin.com
Subject: Re: Interix sources and cygwin ?
Date: Thu, 15 Feb 2001 07:57:00 -0000	[thread overview]
Message-ID: <200102151557.KAA31106@envy.delorie.com> (raw)
In-Reply-To: <OCECJNJHOHFDNOOHJFIHKECFFDAA.tag@ibis.odessa.ua>

> Probably you know about Interix (sold to Microsoft).

Yes.  I've worked with their developers on some common projects.

> But Interix was based on Cygwin

No, it isn't.  Interix has absolutely no cygwin sources in it at all.

Perhaps you mistakenly think that tools like gcc and binutils
originate in cygwin?  They don't.  Interix, like Cygwin (and Linux,
DJGPP, and many other systems), is based on the GNU tools, and we
share some common functionality (like support for the PE executable
format), but the runtimes have absolutely nothing in common, and will
never have anything in common, because the projects have different
goals.  Cygwin is a POSIX emulator for the Win32 subsystem, and
Interix is a POSIX *subsystem* that sits directly on the NT core
kernel.  From their own points of view, they are running on two
completely different "operating systems".

> P.S> Why FAQ desolated ??

Because the cygwin project relies on volunteers like you to make it
better.  Nobody has yet volunteered to make that part better.  Please
feel free to volunteer - even the smallest patch - even fixing a
single typo - is helpful.

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2001-02-15  7:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-15  6:21 Andrew G. Tereschenko
2001-02-15  7:57 ` DJ Delorie [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=200102151557.KAA31106@envy.delorie.com \
    --to=dj@delorie.com \
    --cc=cygwin@cygwin.com \
    --cc=tag@ibis.odessa.ua \
    /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).