Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-ID: <3CD2152E.3030409@ece.gatech.edu> Date: Fri, 03 May 2002 00:42:22 -0400 From: Charles Wilson 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 CC: Chris January , cygwin@cygwin.com Subject: Re: New snapshot with significant new functionality References: 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/