From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1750 invoked by alias); 3 Feb 2002 20:07:55 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Received: (qmail 1676 invoked from network); 3 Feb 2002 20:07:53 -0000 Received: from unknown (HELO lnxmain.ns.cabintech.com) (209.113.228.130) by sources.redhat.com with SMTP; 3 Feb 2002 20:07:53 -0000 Received: from localhost (localhost.ns.cabintech.com [127.0.0.1]) by lnxmain.ns.cabintech.com (8.11.0/8.11.0) with ESMTP id g13K7rJ28797 for ; Sun, 3 Feb 2002 15:07:53 -0500 Date: Sun, 03 Feb 2002 12:07:00 -0000 From: X-X-Sender: To: Subject: Re: /dev/registry In-Reply-To: <3C5D8C66.1050003@ece.gatech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SW-Source: 2002-02/txt/msg00100.txt.bz2 > (*) P.S. "back then" somebody mentioned a few problems with file-system > access to registry entries: how do you deal with the various types -- > DWORD, BINARY, STRING, (and the other types that AREN'T accessible via > regedit...) Just something to keep in mind, if somebody actually tries > to write some code for this... File permissions could handle this? Maybe something similar to cygwin's symlinks? *shrug* -rgm -- 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/