corruption less likely, but it
only by virtue of making so much less accessible.
Yah. I've been quite on this one. I'd like to point out that Cygwin
has had a patch for /dev/registry some time ago.
I just did a search and I can't see any formal submittal of a patch.
Was this your patch? I seem
===
- Original Message -
From: Christopher Faylor [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Yah. I've been quite on this one. I'd like to point out that Cygwin
has had a patch for /dev/registry some time ago.
I just did a search and I can't see any formal submittal of a patch
much less accessible.
Yah. I've been quite on this one. I'd like to point out that Cygwin has
had a patch for /dev/registry some time ago. I support a good
implementation of this, and like the .dword etc suffix idea. I also
think that a mount command should be *required* to active /dev/registry
Is the source code for this functionality accessible for download
somewhere ?
Chris January wrote:
1. it's difficult to accidentally cat to a key considering the length of
the
names -
/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/S
hell\
Why can't this /dev/registry stuff be just an ioctl()? Open the
/dev/registry node for the appropriate access, then use some ioctl()'s to
read and write it. Put the /dev/null entry points for the read and write
handlers for /dev/registry and you won't have that accidental corruption
from cat
Why can't this /dev/registry stuff be just an ioctl()? Open the
/dev/registry node for the appropriate access, then use some ioctl()'s to
read and write it. Put the /dev/null entry points for the read and write
handlers for /dev/registry and you won't have that accidental corruption
from
Why can't this /dev/registry stuff be just an ioctl()? Open the
/dev/registry node for the appropriate access, then use some ioctl()'s to
read and write it. Put the /dev/null entry points for the read and write
handlers for /dev/registry and you won't have that accidental corruption
that is ioctl(). It is true that this would make
inadvertent registry corruption less likely, but it only by virtue of
making so much less accessible.
Randall Schulz
Mountain View, CA USA
At 03:23 2002-02-06, Barubary wrote:
Why can't this /dev/registry stuff be just an ioctl()? Open the
/dev
Chris January wrote:
I'll probably add some entries to /proc - ones commonly found on UNIX
platforms maybe. Anyone have any favourites they wish to see?
I don't know about favorite, but the only one that's even close to
standardized across Unices is /proc/pid. And even that is nonstandard
1. it's difficult to accidentally cat to a key considering the length of
the
names -
/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersion/S
hell\ Extensions/Approved/\{BDEADF00-C265-11d0-BCED-00A0C90AB50F\} is a
bit
hard to type in by accident...
At the moment, I
, February 06, 2002 4:56 PM
To: [EMAIL PROTECTED]
Subject: Re: /proc (was: Re: /dev/registry)
1. it's difficult to accidentally cat to a key considering the
length of
the
names -
/proc/registry/HKEY_CURRENT_USER/Software/Microsoft/Windows/CurrentVersi
on/S
hell\ Extensions/Approved
-
From: Stephan Mueller [EMAIL PROTECTED]
To: Chris January [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, February 06, 2002 17:00
Subject: RE: /proc (was: Re: /dev/registry)
Another suggestion (I won't presume to say better):
.reg files refer to this value as @. E.g.
REGEDIT4
The trick at this point is finding someone interested enough to write it.
Nobody seems to notice that the original message writer actually proposed
himself to do the work... now let's only hope he really does it ;)
Subject: /dev/registry
Date: Sun, 3 Feb 2002 15:42:55 -
From: Chris
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Christopher Faylor
Sent: Tuesday, February 05, 2002 6:29 PM
To: [EMAIL PROTECTED]
Subject: Re: /dev/registry
On Tue, Feb 05, 2002 at 02:09:27PM +0100, Lapo Luchini wrote:
The trick at this point
At 04:44 PM 2/5/2002, Ralf Habacker wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Christopher Faylor
Sent: Tuesday, February 05, 2002 6:29 PM
To: [EMAIL PROTECTED]
Subject: Re: /dev/registry
On Tue, Feb 05, 2002 at 02:09:27PM
- Original Message -
From: Ralf Habacker [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 05, 2002 13:44
Subject: RE: /dev/registry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Christopher Faylor
Sent: Tuesday, February
From: Gerald Villemure [EMAIL PROTECTED]
Subject: Re: /dev/registry
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
- Original Message -
From: Greg Mosier [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
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
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf
Of Chris January
Sent: Sunday, February 03, 2002 9:43 AM
To: [EMAIL PROTECTED]
Subject: /dev/registry
How about adding a /dev/registry fhandler to Cygwin? Registry keys would be
directories and values
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.
Well, it looks
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.
Regards
Chris
--
Unsubscribe
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
This sounds like a GREAT idea to me.
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
Hi,
Chris January [EMAIL PROTECTED] wrtote:
How about adding a /dev/registry fhandler to Cygwin?
Registry keys would be directories and values in the
registry files.
UWIN (a commercial alternative to cygwin) has
something similar. See
http://www.research.att.com/sw/tools/uwin/
They use
/proc/registry/*
is a GREAT idea!
Sincerely,
Daniel Adams - [EMAIL PROTECTED]
http://dana.ucc.nau.edu/~dpa3
1 Peter 4:10 (NIV)- Each one should use whatever gift he has received to
serve others, faithfully administering God's grace in its various forms.
--
Unsubscribe info:
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
On Sun, Feb 03, 2002 at 02:15:50PM -0500, Charles Wilson wrote:
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
(*) 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
/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
29 matches
Mail list logo
