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 Message-ID: <3CD20805.800@ece.gatech.edu> Date: Thu, 02 May 2002 23:46:13 -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: Chris January CC: cygwin AT cygwin DOT com Subject: Re: New snapshot with significant new functionality References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020502163048 DOT 026f8bb0 AT pop3 DOT cris DOT com> <00ea01c1f237$8c421a70$0100a8c0 AT 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 $ $ 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/