Mail Archives: cygwin/2005/10/27/05:50:23
Thorsten Kampe wrote:
> * Chris Taylor (2005-10-26 17:38 +0100)
>
>>Thorsten Kampe wrote:
>>
>>>* Christopher Faylor (2005-10-26 15:37 +0100)
>>>
>>>
>>>>On Wed, Oct 26, 2005 at 10:26:36AM +0100, Thorsten Kampe wrote:
>>>>
>>>>
>>>>>* gtg793x AT mail DOT gatech DOT edu (2005-10-26 00:45 +0100)
>>>>>
>>>>>
>>>>>>Quoting Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>:
>>>>>>
>>>>>>
>>>>>>>See "man mount". Please, please, please don't manipulate the registry
>>>>>>>directly if you want to stay portable. You can easily create a batch file
>>>>>>>to reproduce the mounts properly.
>>>>>>>...
>>>>>>>"User mounts" is the answer. The CURRENT_USER tree is usually writable.
>>>>>>>Make sure you don't write over the existing settings if they are present.
>>>>>>
>>>>>>Current XP computers I am trying to run this into give me: "Registry Editing has
>>>>>>been Disabled by your administrator." even if I try to write to Current_User
>>>>>>
>>>>>>All I am trying to keep portable is the X server thus XWIN.exe is the only
>>>>>>executable I have, the only one I execute. After running the X server as the
>>>>>>background server I am tunneling the packets using Putty / Securecrt.
>>>>>
>>>>>Try "regedit /s" in a batch (instead of double clicking). This
>>>>>sometimes works.
>>>>
>>>>Or, I dunno, if that works, you could just use "mount" and forget about
>>>>regedit entirely.
>>>>
>>>>It's a crazy idea, I know. I wonder why no one has thought of it before.
>>>
>>>*I* didn't know about it (because I was under the impression that all
>>>cygwin programs depend on the mount tables).
>>>
>>>Well, obviously there are a few that don't (mount, cygcheck, ash (?),
>>>etc.?)
>>>
>>>And I think it's easier to just import a reg file than dealing with
>>>multiple mount commands...
>>>
>>
>>Problem with that is that if the sysadmin knows what he's doing, it only
>>takes about 4 seconds to block off almost all possible ways of actually
>>editing the registry...
>
>
> Definitely not. As a user running programs you are almost constantly
> changing the registry (your HKEY_CURRENT_USER). So often importing a
> .reg file is not allowed (by double clicking) and starting regedit in
> GUI mode.
When I say editing the registry, I'm talking about the ability to
directly manipulate it with .reg files, regedit, or other registry
editing tools.
Yes, you are able to make changes to HKCU, but not *directly*.
Your method is flawed and destroys the existing setup, which is bad.
I disable ALL aspects of regedit and other tools, and I know I'm not
alone in this. It's perfectly normal and *common* to do it.
>
>
>>A batch file that checks for an existing mount table and saves it, then
>>mounts it according to what you want is far, far better.
>
>
> This batch file is registry editing, too. If you edit the registry or
> the mount command - that's no difference from a sysadmin's point of
> view.
>
It's not *directly* editing the registry. As a sysadmin, I'm telling you
it *is* different.
The (l)user should *never* be allowed to edit the registry themselves.
That's a recipe for disaster.
In my book, this includes so-called junior sysadmins/techs/whatever.
Using a command that alters the registry as part of it's function, but
does not allow the user to directly alter it is a very different
ballgame. mount would be permissable. Some console app to directly edit
the registry would not be.
--
Spinning complacently in the darkness, covered and blinded by a blanket
of little lives, false security has lulled the madness of this world
into a slumber. Wake up! An eye is upon you, staring straight down and
keenly through, seeing all that you are and everything that you will
never be. Yes, an eye is upon you, an eye ready to blink. So face
forward, with arms wide open and mind reeling. Your future has
arrived... Are you ready to go?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -