Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "John Morrison" <john.r.morrison@ntlworld.com>
To: <cygwin@cygwin.com>
Subject: RE: Odd mount and path problem
Date: Tue, 23 Jul 2002 19:38:27 +0100
Message-ID: <OIENKAGCMBEDKDHGANIKEENBCGAA.john.r.morrison@ntlworld.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <80575AFA5F0DD31197CE00805F650D767B226C@wilber.adroit.com>
Importance: Normal

> On Behalf Of Robinow, David
>  Maybe, but see above.
>  cygwin, if I remember that far back, was originally intended as
> a tool for
> relatively experience unix folks to be able to run their stuff on Windows.

I see Cygwin now as a way to get windows folks to try a *nix environment.
Thats certainly how I started; my (then) project leader decided that the
next project should work on Windows, Linux and Solaris so we used cygwin
and gcc for development.  It's only really since that time that I've started
using linux at home (currently Debian on my firewall and (installing as
we speak) redhat on my test machine).  I certainly couldn't have got as
far as I have without being able to switch between the windows I is/was
used too and the cygwin/linux view of my file system.

*Most* advantagous.

J.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/