X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 9 Jul 2008 22:37:31 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Relation Between Mount System and The Registry?
Message-ID:	<20080710023731.GA28933@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4cee11bc0807091403t38f82ef0lbbe1a8b636d810c6 AT mail DOT gmail DOT com> <48752BF7 DOT 9090100 AT cygwin DOT com> <4cee11bc0807091811m2f2b8315q78cb555af32bfaf4 AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<4cee11bc0807091811m2f2b8315q78cb555af32bfaf4@mail.gmail.com>
User-Agent:	Mutt/1.5.16 (2007-06-09)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Wed, Jul 09, 2008 at 06:11:39PM -0700, Sam Hanes wrote:
>Larry Hall (Cygwin) wrote:
>> Sam Hanes wrote:
>>>
>>> Can someone explain to me when the registry keys in
>>> "HKLM\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2" and the same in HKCU
>>> get read into the mount table? I can find the source for the mount
>>> table itself (in "src/winsup/cygwin/mount.cc") but not where the
>>> information from the registry is initially read in, or were it gets
>>> written out when a new entry is added.
>>
>> Why do you care?  'mount' currently manipulates the registry but it won't
>> come 1.7.0.  The use of the registry for 'mount' is an implementation
>> detail.  If you're doing something that keys off of this, you may want
>> to rethink your strategy.  You may be better off basing your logic on
>> 'mount' as opposed to the keys and values in the registry that 'mount'
>> manipulates.
>>
>
>Oh. I assume 1.7.0 is the one currently in CVS. That would explain why
>I can't find the logic to write the mount registry keys in the CVS
>sources. It's not there. Well, that's one less thing I have to think
>about. Would you mind pointing me to where I should have found that?
>Reading the ChangeLog in "src/winsup/cygwin" I can see a great many
>changes from the process of moving over to the new fstab system, but I
>assume there was an announcement of the change somewhere other than
>cygwin-developers.

We don't make formal announcements about unreleased versions of Cygwin.

However, we have been consistent in telling people not to muck with the
registry but to use the tools instead, and we always mention that the
registry is neither permanent or guaranteed not to change.

cgf

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

- Raw text -