public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gerald Villemure" <GVillemure@ik.ca>
To: <cygwin@cygwin.com>
Subject: Re: /dev/registry
Date: Sun, 03 Feb 2002 23:15:00 -0000	[thread overview]
Message-ID: <000701c1ad4c$8282e260$0200000a@dyn.ik.ca> (raw)
In-Reply-To: <009f01c1ace4$41b7a580$0200000a@dyn.ik.ca>

> /proc/registry/*
>
> is a GREAT idea!

> (*) 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...)

Why not use a file name extention (vary microsoft like thing to do)

First lets use standard Root key Name Abbreviations
HKEY_CURRENT_USER        HKCU
HKEY_LOCAL_MACHINE    HKLM
HKEY_CLASSES_ROOT        HKCR
HKEY_USERS                         HKEY_USERS
HKEY_CURRENT_CONFIG  HKEY_CURRENT_CONFIG

As for value data types, we could use:
REG_SZ                     .sz
REG_DWORD          .dword
REG_BINARY          .binary
REG_EXPAND_SZ  .expand
REG_MULTI_SZ      .mutli

So this:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"WinVNC"="data goes here"

would become:
/proc/registry/HKLM/SOFTWARE/Microsoft/Windows/CurrentVersion/Run/WinVNC.sz

Good or bad idea?

One more things to be carefull of, is the use of roming profiles.... HKCU
can change.

Gerald


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

  parent reply	other threads:[~2002-02-04  7:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-03 12:07 /dev/registry Chris January
2002-02-03 10:49 ` /dev/registry Gerald Villemure
2002-02-03 11:02   ` /dev/registry Daniel Adams
2002-02-03 11:14     ` /dev/registry Charles Wilson
2002-02-03 12:00       ` /dev/registry Christopher Faylor
2002-02-03 12:07       ` /dev/registry roland
2002-02-03 23:15   ` Gerald Villemure [this message]
2002-02-04  0:36     ` /dev/registry Corinna Vinschen
2002-02-04 14:43     ` /dev/registry Greg Mosier
2002-02-04 14:53       ` /dev/registry Michael A Chase
2002-02-05  5:28         ` /dev/registry Lapo Luchini
2002-02-05  9:28           ` /dev/registry Christopher Faylor
2002-02-05 13:46             ` /dev/registry Ralf Habacker
2002-02-05 14:03               ` /dev/registry Larry Hall (RFK Partners, Inc)
2002-02-05 14:07               ` /dev/registry Michael A Chase
2002-02-03 12:07 ` /dev/registry Michael F. March
2002-02-03 12:07 ` /dev/registry Jon Foster
2002-02-03 12:07 ` /dev/registry Lapo Luchini
2002-02-04 18:50 ` /dev/registry Gary R. Van Sickle
2002-02-10  0:18   ` /dev/registry Robert Collins
2002-02-04 19:57 /dev/registry Gareth Pearce
2002-02-06  3:23 ` /dev/registry Barubary
2002-02-06  8:56   ` /dev/registry Randall R Schulz
2002-02-08 23:42     ` /dev/registry Robert Collins
2002-02-09 10:43       ` /dev/registry Christopher Faylor
2002-02-09 13:17         ` /dev/registry Robert Collins

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000701c1ad4c$8282e260$0200000a@dyn.ik.ca' \
    --to=gvillemure@ik.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).