Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Fri, 13 Oct 2000 17:29:40 -0400 Message-Id: <200010132129.RAA22588@envy.delorie.com> From: DJ Delorie To: tiberius AT braemarinc DOT com CC: cygwin AT sourceware DOT cygnus DOT com In-reply-to: <000b01c03554$562febc0$1d01a8c0@BRAEMARINC.COM> (tiberius AT braemarinc DOT com) Subject: Re: RFC: linux compatibility References: <000b01c03554$562febc0$1d01a8c0 AT BRAEMARINC DOT COM> > 1. POSIX compliant, if for no other reason than it's the right thing to do. We already have this as a goal. However, POSIX doesn't cover everything. Plus, Linux also has POSIX as a goal. Downside: the POSIX specs are expensive to purchase and not available online. > 2. "GNU compliant", by which I mean essentially that anything that links > and runs with glibc should work with Cygwin. Linux already uses glibc (at least, Red Hat Linux does), so tracking linux gets us this already. However, there may be some things that glibc supports that are fundamentally impossible under Windows. I can't think of any off-hand, though. > 3. "Other-Unii compatible", meaning that aything that can be added > to the Cygwin mix that doesn't violate the above and yet allows it > to be more compatible with other distributions should be added. Right. My suggestion is that Linux be the "other Unix" we've chosen to be compatible with. It's much easier to say "it's just like Linux" than to say "this part is like Linux, but this part is like IRIX, and this part is like Solaris". -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com