Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 30 Mar 2000 20:48:30 -0500 To: "cygwin-developers AT sourceware DOT cygnus DOT com" Subject: Re: Mo Dejong's install problems Message-ID: <20000330204830.B30076@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cgf AT cygnus DOT com, "cygwin-developers AT sourceware DOT cygnus DOT com" References: <38E3E670 DOT 51F2DCBA AT attglobal DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.1.8i In-Reply-To: ; from mdejong@cygnus.com on Thu, Mar 30, 2000 at 05:45:00PM -0800 On Thu, Mar 30, 2000 at 05:45:00PM -0800, Mo DeJong wrote: >I realize that there are ways to work around the problem, like adding >the entries to the PATH in the autoexec.bat file, but Cygwin needs to >install and work "out of the box". Changing the PATH in the >autoexec.bat file or the system settings on NT should be avoided if at >all possible. I don't know why Cygwin would be different from every other Windows program in this regard. There are established procedures for modifying the PATH. I don't see why a Cygwin installer should avoid using them. cgf