On Oct 7 10:52, Christopher Faylor wrote: > On Thu, Oct 07, 2004 at 10:20:53AM +0200, Corinna Vinschen wrote: > >On Oct 6 21:53, Christopher Faylor wrote: > >> Or, even better yet, Corinna could we force SYSTEMROOT to be used > >> somehow but masked if someone removes it from the environment? > > > >Hmm, usually applications which suffer from a missing SYSTEMROOT are > >spawned by a parent process which has explicitely created a new > >environment block for the child and then calls execvp. So the new > >child is already missing SYSTEMROOT on process startup. What about > >always adding SYSTEMROOT to the windows env created in build_env, > >if it's missing? > > That's what I was thinking. And then lying about its existence if > someone queries the environment via getenv and SYSTEMROOT is "not > supposed to be there". > > What an amazingly lame requirement...
Why is that a requirement anyway? Why is it necessary to hide $SYSTEMROOT? I don't see a reason for that? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:[EMAIL PROTECTED] Red Hat, Inc. -- 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/
