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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Type: text/plain; charset="iso-8859-1" From: Christopher January To: cygwin AT cygwin DOT com Subject: Re: patch for /proc/registry read/write Date: Mon, 8 Jul 2002 14:50:24 +0100 References: <200207080848 DOT 20302 DOT marek AT bmlv DOT gv DOT at> In-Reply-To: <200207080848.20302.marek@bmlv.gv.at> MIME-Version: 1.0 Message-Id: <200207081450.24031.chris@atomice.net> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g68Dor500954 > I've just downloaded the 1.3.12-2 version and was surprised to see that the > registry-patch (which was heavily discussed in february, if I recall > correctly) has made it into the mainline. > > But one question remains: Is there a patch for read/write support? I know You could always write one... :-) > that this starts the old problem of specifying the kind of value (dword, > sz, multi-sz, binary, ...) but maybe this could by done by the extension > (possibly seperated by a : as this ain't used in cygwin), so eg. name:sz or > value:dword. 1. a : is used to separate the host name and filename with rcp and scp as well as acting as the drive separator for Windows paths. This, IMHO, rules out using a colon as separator. 2. The data type is metadata and should *NOT* be included, therefore, in the filename *if this can possibly be avoided*. Extensions were bad, adding extra metadata to the filename is even worse. 3. : is a valid key and/or value name. The present implementation ignores this, but should escape 'special' characters like colon and forward slash. My preference would be that the type of a registry value would be changed with fcntl (and a command-line program which internally called fcntl) or something similar. > > What I'd like to achieve is to use rsync on the registry - to get the > registry into a known state. You can use regedit in command-line mode for this. It is a lot better suited to the job and should deal with Unicode keys and other such niceities for you. OTOH, it won't set the ACLs, but then a Cygwin implementation is even less likely to support that. > > > I don't think that the naming scheme gives consistency problems - if I > write a file name:sz it isn't guaranteed (in unix semantics) that > name:dword isn't deleted in the same moment. I don't really like the idea of files appearing to be deleted without user intervention. Thanks for your comments. Regards Chris -- 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/