Re: scenario: no registry access, C:\ locked out

["Andrew Patrzalek" <apatrza1 at rochester dot rr dot com>]

System administrators are allowed to access the registry to change it, a
non-privileged user is not.  For instance, work stations on many networks
are locked out, for various reasons, preventing a non-privileged user from
running regedit to alter the registry. However, another partition, say d:\,
is allowed for use by this user for programs which don't require the
registry for running. This is where cygwin can really shine, 32-bit
executables, no registry needed. Programs can be compiled, tested and
demonstrated without violating network restrictions and commitments.
----- Original Message -----
From: "Chris Faylor" <cgf@cygnus.com>
To: <cygwin-developers@sourceware.cygnus.com>
Sent: Tuesday, June 20, 2000 8:29 PM
Subject: Re: scenario: no registry access, C:\ locked out


> On Tue, Jun 20, 2000 at 08:09:34PM -0400, Andrew Patrzalek wrote:
> >As I have been somewhat of a spurious lurker, I wonder if the scenario
> >where the end user does not have write access to c:\ and the registry
> >is Adm.  edit access only has been considered.  The end user can still
> >change the user environment but cannot use regedit for instance.  B19*,
> >B20* and v1.1.1 appear not to care.  This is somewhat of a
> >philosophical question that may have impact on portability issues down
> >the road.  Is there a movement toward having more involvement in things
> >that lead to an end user editing the registry to make things work?
>
> I'm sorry but I really don't know what you are talking about.  "edit
access
> only" to what?  The registry?  B19, B20, and v1.1 appear not to care about
> what?  Changing the registry?  Are you talking about mounts?
>
> Can you provide a step by step example to show what you mean?
>
> cgf
>