From: Charles Wilson <cwilson@ece.gatech.edu>
To: Daniel Adams <dpa3@cet.nau.edu>
Cc: Cygwin <cygwin@cygwin.com>
Subject: Re: /dev/registry
Date: Sun, 03 Feb 2002 11:14:00 -0000 [thread overview]
Message-ID: <3C5D8C66.1050003@ece.gatech.edu> (raw)
In-Reply-To: <NDBBJHLJOLEMCGOCDEEAGEFCCOAA.dpa3@cet.nau.edu>
Daniel Adams wrote:
> /proc/registry/*
>
> is a GREAT idea!
Okay folks, enough with the "me toos". Suffice it to say that everybody
thinks this is a wonderful idea. Not surprisingly, the suggestion of a
/dev/registry or /proc/registry HAS been made before. And everybody
thought it was a great idea then, too.
There's only one problem: back then, after the initial round of
self-congratulation and "great idea -- me too-ism" -- nobody did the
work. I suspect the same thing will be true this time, as well.
Somebody please astonish me and provide the code.
--Chuck
(*) 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...
--
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/
next prev parent reply other threads:[~2002-02-03 19:14 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 ` Charles Wilson [this message]
2002-02-03 12:00 ` /dev/registry Christopher Faylor
2002-02-03 12:07 ` /dev/registry roland
2002-02-03 23:15 ` /dev/registry Gerald Villemure
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=3C5D8C66.1050003@ece.gatech.edu \
--to=cwilson@ece.gatech.edu \
--cc=cygwin@cygwin.com \
--cc=dpa3@cet.nau.edu \
/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).