delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/09/05/12:00:17

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <20000905155636.29010.qmail@web109.yahoomail.com>
Date: Tue, 5 Sep 2000 08:56:36 -0700 (PDT)
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Subject: Re: DLL naming conventions
To: Egor Duda <cygwin AT sources DOT redhat DOT com>
MIME-Version: 1.0

--- Egor Duda <deo AT logos-m DOT ru> wrote:
> Hi!
> 
> Tuesday, 05 September, 2000 Earnie Boyd earnie_boyd AT yahoo DOT com wrote:
> 
> EB> --- Chris Faylor <cgf AT cygnus DOT com> wrote:
> >> 
> >> Of course, if we ever write our "registry as a file system" module for
> >> cygwin, you could have a tar file which extracted executables to /bin
> >> and registry information to /registry/LocalMachine/Software/...
> >> 
> 
> EB> Hey, I like this.  So then, `ls /registry/LocalMachine/Software' should
> then
> EB> list the registry.  Cool, just cool.
> 
> not  so  cool  as  you  can think. i've implemented such "plugin" to
> cygwin  somewhere  around 1998, and ls /registry/LocalMachine/Software
> worked ok. and
> 
> cat "/registry/CurrentUser/Software/Cygnus Solutions/Cygwin/mounts
> v2/cygdrive prefix"
> 
> worked  ok  too. but when i dug into this, i couldn't find good mapping
> from  registry  semantics  to  unix-stype  file  system semantics. for
> example,  registry values can be of several different types -- string,
> multistring,  binary,  dword, etc. what should this be looking like in
> fs tree?
> 

Uhm, the data values would be ok to cat and tar but not ok to ls.  The registry
keys would be the fs tree and the registry data would be the what would be
read.

> putting  /registry/.../ into tar.gz should work, though, if only we'll
> use string type values only.
> 

It should even be ok with the other types of data as long is you ensured the
data was processed in binary mode.

Ok, sure I'm probably oversimplifying it.

=====
--- <http://earniesystems.safeshopper.com> ---
   Earnie Boyd: <mailto:earnie_boyd AT yahoo DOT com>
            __Cygwin: POSIX on Windows__
Cygwin Newbies: <http://gw32.freeyellow.com/>
           __Minimalist GNU for Windows__
  Mingw32 List: <http://www.egroups.com/group/mingw32/>
    Mingw Home: <http://www.mingw.org/>

__________________________________________________
Do You Yahoo!?
Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019