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 Message-ID: <001b01c07478$9309e290$9865fea9@timayum4srqln4> From: "Tim Prince" To: "Robert Collins" , , References: Subject: Re: why not use root as root? Date: Mon, 1 Jan 2001 20:57:43 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 mks and cygwin coexist peacefully on my 2K box at the office, with cygwin installed in its own directory, and run only from a window opened by cygwin.bat. Actually, mks resides in its own directory as well, but requires that directory to come first on the PATH in effect outside cygwin. The mks tools which are not duplicated by cygwin show up in the cygwin window as well. Where I don't have mks, I install cygwin on the w2k installation root, in order to be able to run gcc testsuite. mks runs to a limited extent even on the Windows variants which don't support the forking mechanism used by both mks and cygwin. ----- Original Message ----- From: "Robert Collins" To: ; Sent: Monday, January 01, 2001 6:12 PM Subject: RE: why not use root as root? Also the early unix like tools on windows (ie mks as already mentioned here) used c:\ as / - which is why cygwin avoids that. -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple