delorie.com/archives/browse.cgi | search |
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 |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Date: | Sun, 3 Feb 2002 15:07:53 -0500 (EST) |
From: | <roland AT steeltorch DOT com> |
X-X-Sender: | <roland AT lnxmain> |
To: | <cygwin AT cygwin DOT com> |
Subject: | Re: /dev/registry |
In-Reply-To: | <3C5D8C66.1050003@ece.gatech.edu> |
Message-ID: | <Pine.LNX.4.33.0202031505260.28761-100000@lnxmain> |
MIME-Version: | 1.0 |
> (*) 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |