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
Message-ID: <3CD20805.800@ece.gatech.edu>
Date: Thu, 02 May 2002 23:46:13 -0400
From: Charles Wilson <cwilson@ece.gatech.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: Chris January <chris@atomice.net>
CC: cygwin@cygwin.com
Subject: Re: New snapshot with significant new functionality
References: <5.1.0.14.2.20020502163048.026f8bb0@pop3.cris.com> <00ea01c1f237$8c421a70$0100a8c0@advent02>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Chris January wrote:

>>Chris & Chris,
>>
>>Cool!
>>
>>Is the registry as reflected in /proc/registry writable?
>>
> I'm torn between writing "no", and "no, not yet".
> The problem with this is that it is inevitable that at some point or other
> someone will post to the cygwin mailing list complaining they typed rm -rf
> /proc/registry/* and now their system is hosed and it's all Red Hat's
> fault...
> Certainly there would have to be some kind of 'safety' mechanism, whereby by
> default /proc/registry was read-only, but somehow it could be made writable,
> perhaps by writing '1' to /proc/registry/.writable or something.


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

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