Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
X-Apparently-From:	<earnie?boyd AT yahoo DOT com>
Message-ID:	<3AF00F4D.B3F70233@yahoo.com>
Date:	Wed, 02 May 2001 09:44:45 -0400
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To:	Cygwin Apps <cygwin-apps AT cygwin DOT com>
X-Mailer:	Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin-apps AT cygwin DOT com
Subject:	Re: Forcing SYSTEMROOT (opinions needed)
References:	<EA18B9FA0FE4194AA2B4CDB91F73C0EF08EF74 AT itdomain002 DOT itdomain DOT net DOT au> <20010501232846 DOT C26438 AT redhat DOT com>

Christopher Faylor wrote:
> 
> On Wed, May 02, 2001 at 01:14:39PM +1000, Robert Collins wrote:
> >
> >> -----Original Message-----
> >> From: Christopher Faylor [mailto:cgf AT redhat DOT 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?

Earnie.

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

- Raw text -