This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: ssh + patch + $TMP

On Sun, Feb 21, 2010 at 05:33:56PM -0800, Karl M wrote:
>> Date: Sat, 20 Feb 2010 21:23:22 -0500
>> From: cgf
>> Subject: Re: ssh + patch + $TMP
>> On Sun, Feb 21, 2010 at 12:04:19AM +0100, Cyrille Lefevre wrote:
>> I would really bet that there aren't many programs out there which rely
>> on those environment variables. Just asserting that this is needed
>> doesn't really advance the conversation at all since you're just a lone
>> voice with no credentials which would give your opinion weight. If
>> you have specific examples then please provide them.
>> If this was truly like linux then I believe that most, if not all, of
>> the environment would come from settings in the shell itself. So, in
>> thinking about this more, I think we could probably get away with
>> deleting everything.
>> If someone wanted to run a program which relied on those variables they
>> could always set them themselves.
>Although, we do inherit the windows environment when launching a Cygwin
>bash shell, so I wouldn't carry this argument to an extreme.

It's not the same thing.  If we really had a getty/login processes like
linux we would control the environment precisesly.  In the case of sshd
we're close to the way linux does things.  There is a daemon running
which starts a shell via sshd.


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]