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
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
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
7 matches
Mail list logo