Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT 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: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Charles Wilson" , "Chris January" Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g433vZR15011 > -----Original Message----- > From: Charles Wilson [mailto:cwilson AT ece DOT gatech DOT 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 > > $ > > $ 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/