Forcing SYSTEMROOT (opinions needed)
Wed May 2 07:30:00 GMT 2001
On Wed, May 02, 2001 at 09:44:45AM -0400, Earnie Boyd wrote:
>Christopher Faylor wrote:
>> On Wed, May 02, 2001 at 01:14:39PM +1000, Robert Collins wrote:
>> >> -----Original Message-----
>> >> From: Christopher Faylor [ mailto:email@example.com ]
>> >> Sent: Wednesday, May 02, 2001 1:21 PM
>> >> To: Christopher Faylor
>> >> Subject: Re: Forcing SYSTEMROOT (opinions needed)
>> >> So we have to trade the possibility of someone wanting
>> >> complete control of
>> >> his environment versus the possibility of someone not
>> >> specifying SYSTEMROOT
>> >> but needing it for the program that is about to be run.
>> >This ones easy. Remove winsock/socket support from cygwin. See the
>> >problems gone :]
>> Yeah, but then people would claim that Cygwin was "unstable" and "always
>> breaking network support".
>> >>Should I flip a coin?
>> >I'd add systemroot. If it's needed from cygwin running, not having it
>> >is like trying to run hurd without a microkernel - if you want it
>> >different you have to fiddle yourself!
>> >We can always do a switch to control it down the track.
>> I guess we could add a cygwin_keep_environment_clean () call or something.
>> Is there a standard way to control this type of behavior on UNIX. I'm thinking
>> that there is something like sysconf or ulimit or something but more generic
>> than that. I'm drawing a blank, though.
>The other option is to leave it alone and document it. We've discovered
>the problem how many times in the past how many years?
I guess my memory is failing because I don't recall this problem.
More information about the Cygwin-apps