Christopher Faylor
Mon Jul 1 08:19:00 GMT 2002

On Mon, Jul 01, 2002 at 09:44:12AM +0200, Corinna Vinschen wrote:
>On Sun, Jun 30, 2002 at 11:57:32PM -0400, Chris Faylor wrote:
>> On Sun, Jun 30, 2002 at 11:56:40AM +0200, Corinna Vinschen wrote:
>> >- If in evironment, done.
>> >- Else ask /etc/passwd
>> >- Else use environemt vars HOMEDRIVE/HOMEPATH.
>> >
>> >The server is only asked for getting HOMEDRIVE/HOMEPATH and
>> >the values are never used to set the environment or to
>> >evaluate HOME.  So if HOMEDRIVE/HOMEPATH are missing in the
>> >environment, getting the values from the server doesn't help
>> >for setting HOME.  Or do I miss something?
>> Nope, you aren't missing anything.  When I reworked that logic, I
>> thought about using the derived values of HOMEPATH/HOMEDRIVE but that
>> would mean a potentially expensive operation, right?  Maybe it doesn't
>> So, I just added the potential capability to set HOME from
>> HOMEPATH/HOMEDRIVE.  It isn't on yet, though.
>> Boy, I think I hate these environment variables almost as much as I hate
>> Windows 95.  Have I mentioned that lately?
>Not this month...
>> Oh, and currently I made HOME default to / if it can't figure out
>> anything else.  Does that make sense?
>That's ok but I'm still sure it makes sense to use HOMEDRIVE/HOMEPATH
>first.  Setting to "/" should be just the last fallback.  
>What's the problem in trusting these environment variables?

They are trusted if they exist.  I just don't go out of my way to
retrieve the info from the server during startup because that is an
expensive operation.  Avoiding that kind of operation was the impetus
for these changes.


More information about the Cygwin-developers mailing list