On Sep 14 19:42, Dave Korn wrote:
> Original Message
> >From: Shankar Unni
> >Sent: 14 September 2005 18:55
>
> > Eric Blake wrote:
> >
> >> You'd better check the permissions there. What does
> >> 'getfacl /cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE'
> >> show?
> >
> > [~] 7. ge
On Sep 14 10:28, Shankar Unni wrote:
> Corinna Vinschen wrote:
>
> >Cygwin tcsh does not share its hashing code with the Win32 version, it
> >uses the same code as all other OSes are using. No other OS is using
> >case insensitive hashing, so doesn't Cygwin tcsh.
>
> Thanks for the corrections.
Original Message
>From: Shankar Unni
>Sent: 14 September 2005 18:55
> Eric Blake wrote:
>
>> You'd better check the permissions there. What does
>> 'getfacl /cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE'
>> show?
>
> [~] 7. getfacl /cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE
Eric Blake wrote:
You'd better check the permissions there. What does
'getfacl /cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE'
show?
[~] 7. getfacl /cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE
# file: /cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE
# owner: shankar
# group: Non
> bash-3.00$ ls -l /cygdrive/c/oracle/product/10.1.0/db_1/bin | grep -i
> exp.exe
> --+ 1 shankarNone 405776 Mar 8 2004 EXP.EXE
You'd better check the permissions there. What does
'getfacl /cygdrive/c/oracle/product/10.1.0/db_1/bin/EXP.EXE'
show? ls doesn't think that shan
Corinna Vinschen wrote:
Cygwin tcsh does not share its hashing code with the Win32 version, it
uses the same code as all other OSes are using. No other OS is using
case insensitive hashing, so doesn't Cygwin tcsh.
Thanks for the corrections.
But bash is clearly doing something right, as:
ba
On Sep 14 02:39, Eric Blake wrote:
> > It's clearly something to do with the path hashing, as unhashing fixes
> > this problem (typing "unhash" at the command prompt). And "bash"
> > doesn't seem to have this problem (I guess it doesn't hash things).
>
> Just to avoid the spread of misinformati
> It's clearly something to do with the path hashing, as unhashing fixes
> this problem (typing "unhash" at the command prompt). And "bash"
> doesn't seem to have this problem (I guess it doesn't hash things).
Just to avoid the spread of misinformation, bash also does hashing,
but it doesn't tr
Just a reiteration of
http://sourceware.org/ml/cygwin/2001-09/msg00499.html, I guess.
One of the executables in my PATH is called "EXP.EXE" (in that exact
case). When I type just "exp", tcsh can't locate it. It can if I type "EXP".
It's clearly something to do with the path hashing, as unhash
9 matches
Mail list logo