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 Message-ID: <00e801c1b13d$6fe38e30$0200a8c0@lifelesswks> From: "Robert Collins" To: , "Randall R Schulz" References: <5 DOT 1 DOT 0 DOT 14 DOT 2 DOT 20020206082639 DOT 00a9eb48 AT pop3 DOT cris DOT 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 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 09 Feb 2002 07:42:47.0088 (UTC) FILETIME=[5DFA2300:01C1B13D] === ----- 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 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/