Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Message-ID: <3CD2152E.3030409@ece.gatech.edu>
Date: Fri, 03 May 2002 00:42:22 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Robert Collins <robert DOT collins AT itdomain DOT com DOT au>
CC: Chris January <chris AT atomice DOT net>, cygwin AT cygwin DOT com
Subject: Re: New snapshot with significant new functionality
References: <FC169E059D1A0442A04C40F86D9BA7600C5F9D AT itdomain003 DOT itdomain DOT net DOT au>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Robert Collins wrote:


> Two things: if /proc/registry isn't writable, cating 1 to
> /proc/registry/.writeable won't work - without special case code. I'd
> suggest /proc/sysopts/fs/registry/writeable.
> 
> Two, why not have two options:
> writeable
> nextwrite
> 
> one is persistent (until all cygwin processes end). The other is for a
> single transaction.


Because I don't want to make it easy.  Besides, if you really want 
"persistence", here's how to shoot yourself in the foot (or head):

-------
#!/bin/sh
echo '1' > /proc/sysopts/fs/registry/writeable
$*

-------


--Chuck



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