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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sat, 9 Feb 2002 13:43:09 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: /dev/registry Message-ID: <20020209184309.GN25500@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020206082639 DOT 00a9eb48 AT pop3 DOT cris DOT com> <00e801c1b13d$6fe38e30$0200a8c0 AT lifelesswks> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00e801c1b13d$6fe38e30$0200a8c0@lifelesswks> User-Agent: Mutt/1.3.23.1i On Sat, Feb 09, 2002 at 06:43:15PM +1100, Robert Collins wrote: > >=== >----- Original Message ----- >From: "Randall R Schulz" >>The suggestion about ioctl() begs the question of where to get the file >>descriptor to which to apply the ioctl() call, and does not open the >>registry to scripting languages that have no direct access to the >>Cygwin or Windows APIs. It does not really simplify the task of adding >>the ability to Cygwin, but obscures the basic access behind the obscure >>and overloaded catch-all interface that is ioctl(). It is true that >>this would make inadvertent registry corruption less likely, but it >>only by virtue of making so much less accessible. > >Yah. I've been quite on this one. I'd like to point out that Cygwin >has had a patch for /dev/registry some time ago. I just did a search and I can't see any formal submittal of a patch. Was this your patch? I seem to find some reference to this in a "work in progress" version of your UMSDOS stuff. cgf -- 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/