Re: Bug in $PATH initialization?

[Lennart Borgman <lennart dot borgman at gmail dot com>]

On Tue, Jun 9, 2009 at 12:28 AM, ABCD<en.ABCD@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Lennart Borgman wrote:
>> I am trying to get "bash -i" to start up with $PATH having
>>
>> Â Â/usr/local/bin:/usr/bin:/bin
>>
>> at the beginning. I believe I need to do this without any init file
>> running so I set the windows Path variable to contain the
>> corresponding windows directories first. So I set Path in cmd.exe with
>>
>> Â set Path=c:\cygwin\bin;%Path%
>> Â set Path=c:\cygwin\usr\bin;%Path%
>> Â set Path=c:\cygwin\usr\local\bin;%Path%
>>
>> and then I do
>>
>> Â bash -i
>>
>> However $PATH starts with
>>
>> Â Â/usr/local/bin:/usr/bin:/usr/bin
>>
>> I thought the last dir above should be /bin, not /usr/bin.
>>
>> Is this intentional or is it a bug. If it is intentional can I somehow
>> do what I want another way?
>>
>
> In Cygwin, /bin and /usr/bin both always point to the same place, so it
> does get the effect you seem to want, just not in the way you expected.

Thanks, but why do I see both /usr/bin and /bin in a cygwin shell
started with --login then?

--
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/