Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Date: Tue, 16 Dec 2003 13:08:03 -0500
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Is cygwin_ROOT still there?
Message-ID: <20031216180803.GD9896@redhat.com>
Mail-Followup-To: cygwin@cygwin.com
References: <Pine.HPX.4.44.0312161141550.4583-100000@risc4.numis.nwu.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.HPX.4.44.0312161141550.4583-100000@risc4.numis.nwu.edu>
User-Agent: Mutt/1.4.1i
X-IsSubscribed: yes
Reply-To: cygwin@cygwin.com
Note-from-DJ: This may be spam

On Tue, Dec 16, 2003 at 11:50:32AM -0600, L. D. Marks wrote:
>I'm trying to put togethor a windows version of a (unix) GNU-type
>package.  I've run into a problem that the DOS CYGWIN_ROOT parameter
>does not seem to want to work at least on an XP machine -- no matter
>what I do it seems to be set to /cygwin (or a different location if
>that is how setup was run).

To the best of my knowledge, cygwin has never honored a CYGWIN_ROOT
environment variable.  If it did, it predates both my time on the
project and the CVS repository.  It certainly isn't treated specially
now.

In any event, use the mount table, i.e., "man mount".
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to aaaspam@sourceware.org
and be permanently blocked from mailing lists at sources.redhat.com

--
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/

