public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michael A Chase" <mchase@ix.netcom.com>
To: "Greg Mosier" <Greg.Mosier@USA.Net>, <cygwin@cygwin.com>
Subject: Re: /dev/registry
Date: Mon, 04 Feb 2002 14:53:00 -0000	[thread overview]
Message-ID: <01c201c1adce$b96c5f40$0d00a8c0@mchasecompaq> (raw)
In-Reply-To: <004601c1adcd$1a98b180$0200000a@gregmo>

----- Original Message -----
From: "Greg Mosier" <Greg.Mosier@USA.Net>
To: <cygwin@cygwin.com>
Sent: Monday, February 04, 2002 14:41
Subject: Re: /dev/registry


> Maybe I've missed something here, but are we talking about copying the
> registry to hard drive, or rather providing a 'pathed' means just to read
> the registry?  I'm still a newbie in this area, but to me, it would seem
> that if it's not copied to the HD then we don't need an extention to
> indicate key type, but that those things that called it should know,
and/or
> check, what type of key they were getting the information on.

It would require a new driver similar to the one (ones?) that manages
filesystems, but I would expect it to walk through the registry instead of
directories.  I think adding the type information to the name is just asking
for ambiguties, but it's really up to whoever implements it.  Using the name
to indicate type does minimize the deviation from the file I/O paradigm
though.

The trick at this point is finding someone interested enough to write it.
--
Mac :})
** I normally forward private questions to the appropriate mail list. **
Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm
Give a hobbit a fish and he eats fish for a day.
Give a hobbit a ring and he eats fish for an age.



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

  reply	other threads:[~2002-02-04 22:53 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   ` /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       ` Michael A Chase [this message]
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 Jon Foster
2002-02-03 12:07 ` /dev/registry Michael F. March
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='01c201c1adce$b96c5f40$0d00a8c0@mchasecompaq' \
    --to=mchase@ix.netcom.com \
    --cc=Greg.Mosier@USA.Net \
    --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).