Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-WM-Posted-At: avacado.atomice.net; Fri, 3 May 02 01:14:53 +0100
Message-ID: <00ea01c1f237$8c421a70$0100a8c0@advent02>
From: "Chris January" <chris AT atomice DOT net>
To: <cygwin AT cygwin DOT com>
References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020502163048 DOT 026f8bb0 AT pop3 DOT cris DOT com>
Subject: Re: New snapshot with significant new functionality
Date: Fri, 3 May 2002 01:14:52 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

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

Regards
Chris



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