Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3C5D64A7.494AB6CD@lapo.it>
Date: Sun, 03 Feb 2002 17:26:15 +0100
From: Lapo Luchini <lapo AT lapo DOT it>
X-Mailer: Mozilla 4.76 [en] (Windows NT 5.0; U)
X-Accept-Language: it,en,fr,es,ja
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: /dev/registry
References: <014a01c1acc9$7324cc80$0100a8c0 AT advent02>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

> How about adding a /dev/registry fhandler to Cygwin? Registry keys would be
> directories and values in the registry files. I'm willing to try coding this
> if people think it's a good idea. It allows shell scripts to easily access
> registry keys as well as programs.

Seems good to me, but it seems better as a /proc/registry/(key/)*value (the
first support of cygwin /proc ? would be cool to also add the ordinary stuff,
processor type, memory.. and so on)

--
Lapo 'Raist' Luchini
lapo AT lapo DOT it (PGP & X.509 keys available)
http://www.lapo.it (ICQ UIN: 529796)



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