Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date: Sun, 30 Apr 2000 23:33:55 -0400
Message-Id: <200005010333.XAA17259@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <20000430135053.B1501@cygnus.com> (message from Chris Faylor on
	Sun, 30 Apr 2000 13:50:53 -0400)
Subject: Re: Added crude update ability to setup.exe
References: <20000429234822 DOT A870 AT cygnus DOT com> <200004301258 DOT IAA11235 AT envy DOT delorie DOT com> <20000430135053 DOT B1501 AT cygnus DOT com>


> The usual place to install this stuff on a windows system is in the
> registry.

I seem to recall reading somewhere that in such cases, the registry
should be used to store the location of a database, not the contents
of the database.  Since we already have the mount table in the
registry, it can point to some file that contains the configuration
information, simply by putting that file in "/".

Besides, storing the information in a text file makes it available to
scripts.