Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <00e801c1b13d$6fe38e30$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: <cygwin@cygwin.com>, "Randall R Schulz" <rrschulz@cris.com>
References: <F119CHnbNWIWGjBM6VN000137e9@hotmail.com> <5.1.0.14.2.20020206082639.00a9eb48@pop3.cris.com>
Subject: Re: /dev/registry
Date: Sat, 9 Feb 2002 18:43:15 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


===
----- Original Message -----
From: "Randall R Schulz" <rrschulz@cris.com>
> 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 support a good
implementation of this, and like the .dword etc suffix idea. I also
think that a mount command should be *required* to active /dev/registry,
and that a read-only and read-write mode should be provided... to allow
for users with different needs, allowing read only requirements to
result in lower risk.

Rob


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