Message-Id: <200409110313.i8B3DkJG022240@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Gary R. Van Sickle" To: Subject: RE: What Cygwin is Date: Fri, 10 Sep 2004 22:13:04 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: X-IsSubscribed: yes > On Thu, 9 Sep 2004, Corinna Vinschen wrote: > > > On Sep 8 11:31, Brian Ford wrote: > > > No, now we continually have to explain why you can't install said > > > x86 Linux binary/package and run it under our Linux > emulator. Heck, > > > you can't even *compile* said Linux firewall/router/proxy server > > > etc. under our Linux emulator. Doesn't sound like much > of an emulation to me. > > > > You don't think that's the fault of our project page, do > you? Did you > > read it lately? For about three months, there's a pretty > precise text > > with the headline "What Isn't Cygwin?" > > Sorry, no; I had not read it within that time period. I was > going on recollection; my bad. It is much better now. > > However, if Cygwin is "a Linux emulation layer providing > substantial Linux API functionality", then shouldn't Linux > APIs and behavior now trump POSIX and the Single Unix > Specification? Is that what we really want? > No. > I'm just not comfortable with the removal of all all > references to POSIX and UNIX from that description. > Nor I, nor apparently many others, especially when the replacement is simply not correct. And anyway, if it's going to be a "Linux emulation layer", it better be changed to "GNU/Linux emulation layer" or Stallman will throw a hissy fit. -- Gary R. Van Sickle -- 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/