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: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com content-class: urn:content-classes:message Subject: RE: Forcing SYSTEMROOT (opinions needed) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Date: Wed, 2 May 2001 13:14:39 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Forcing SYSTEMROOT (opinions needed) Thread-Index: AcDStb6eaTa9EtIERPSnplC2emJTfgAAA9dQ From: "Robert Collins" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id XAA03835 > -----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 :] > 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. Rob > cgf >