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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Subject: RE: New snapshot with significant new functionality
Date: Fri, 3 May 2002 13:57:09 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5F9D@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Charles Wilson" <cwilson@ece.gatech.edu>,
   "Chris January" <chris@atomice.net>
Cc: <cygwin@cygwin.com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g433vZR15011



> -----Original Message-----
> From: Charles Wilson [mailto:cwilson@ece.gatech.edu] 
> Sent: Friday, May 03, 2002 1:46 PM

> That might work --- but I'd make it auto-reset after every 
> atomic write. 
>   So, you have to say
>    $ cat '1' > /proc/registry/.writeable
> 
>   $ <access one single "file" in the registry>
> 
>    $ cat /proc/registry/.writable
>    0

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.

Rob

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