No such file, but it's right there
Hi, I'm using cygwin 1.3.15 in WinME: Cygwin DLL version info: DLL version: 1.3.15 DLL epoch: 19 When I try to "ls" a file I know to be there, I'm told it isn't: $ which ftp telnet /usr/bin/ftp /usr/bin/telnet $ cd /usr/bin $ ls -l ftp telnet -rwxr-xr-x 1 unknown unknown 57344 Jan 6 2002 ftp* -rwxr-xr-x 1 unknown unknown 79360 Jan 6 2002 telnet* $ less ftp telnet ftp: No such file or directory telnet: No such file or directory I don't really want to less a binary file, just see whether the file's presence is recognized. I wouldn't think it's a mount problem, but here's the mount information: $ mount C:\cygwin\usr\X11R6\lib\X11\fonts on /usr/X11R6/lib/X11/fonts type system (binmode) C:\cygwin\bin on /usr/bin type system (binmode) C:\cygwin\lib on /usr/lib type system (binmode) C:\cygwin on / type system (binmode) c: on /c type user (textmode) d: on /d type user (textmode) Thanks if you have any suggestions. Fred -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
No such file, but it's right there
>Well the files are, of course, ftp.exe and telnet.exe.
>Cygwin's automagical .exe workarounds seems to not be working when going
>through a mount where there is no underlying directory.
>
>Max.
>
> Cygwin follows the Windows convention of using file file name suffix
> ".exe" for its binary executable files. While Cygwin will locate and
> execute files files given only the base name (sans suffix), other uses
> ("cat," "less," or more apropos "nm," "size" or "file") demand the
> full file name, including the ".exe" suffix.
>
> Randall Schulz
> Mountain View, CA USA
Thanks.
Fred
--
Fred Ma, [EMAIL PROTECTED]
Carleton University, Dept. of Electronics
1125 Colonel By Drive, Ottawa, Ontario
Canada, K1S 5B6
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: No such file, but it's right there
Shing-Fat Fred Ma <[EMAIL PROTECTED]> wrote: > When I try to "ls" a file I know to be > there, I'm told it isn't: No, as you show below, ls works, less doesn't. > $ cd /usr/bin > $ ls -l ftp telnet > > -rwxr-xr-x 1 unknown unknown 57344 Jan 6 2002 ftp* > -rwxr-xr-x 1 unknown unknown 79360 Jan 6 2002 telnet* > > $ less ftp telnet > > ftp: No such file or directory > telnet: No such file or directory > > I don't really want to less a binary file, > just see whether the file's presence > is recognized. Well the files are, of course, ftp.exe and telnet.exe. Cygwin's automagical .exe workarounds seems to not be working when going through a mount where there is no underlying directory. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: No such file, but it's right there
Fred,
Cygwin follows the Windows convention of using file file name suffix ".exe"
for its binary executable files. While Cygwin will locate and execute files
files given only the base name (sans suffix), other uses ("cat," "less," or
more apropos "nm," "size" or "file") demand the full file name, including
the ".exe" suffix.
Randall Schulz
Mountain View, CA USA
At 15:59 2002-11-17, Shing-Fat Fred Ma wrote:
Hi,
...
When I try to "ls" a file I know to be
there, I'm told it isn't:
$ which ftp telnet
/usr/bin/ftp
/usr/bin/telnet
$ cd /usr/bin
$ ls -l ftp telnet
-rwxr-xr-x 1 unknown unknown 57344 Jan 6 2002 ftp*
-rwxr-xr-x 1 unknown unknown 79360 Jan 6 2002 telnet*
$ less ftp telnet
ftp: No such file or directory
telnet: No such file or directory
I don't really want to less a binary file,
just see whether the file's presence
is recognized. I wouldn't think it's a
mount problem, but here's the mount
information:
...
Thanks if you have any suggestions.
Fred
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: No such file, but it's right there
Randall R Schulz <[EMAIL PROTECTED]> wrote:
> Cygwin follows the Windows convention of using file file name suffix
> ".exe" for its binary executable files. While Cygwin will locate and
> execute files files given only the base name (sans suffix), other
> uses ("cat," "less," or more apropos "nm," "size" or "file") demand
> the full file name, including the ".exe" suffix.
Actually, the significant point seems to be that the files are being
accessed via a mount with no underlying directory.
Max.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: No such file, but it's right there
On Mon, Nov 18, 2002 at 12:35:57AM -, Max Bowsher wrote:
>Randall R Schulz <[EMAIL PROTECTED]> wrote:
>>Cygwin follows the Windows convention of using file file name suffix
>>".exe" for its binary executable files. While Cygwin will locate and
>>execute files files given only the base name (sans suffix), other uses
>>("cat," "less," or more apropos "nm," "size" or "file") demand the full
>>file name, including the ".exe" suffix.
>
>Actually, the significant point seems to be that the files are being
>accessed via a mount with no underlying directory.
No, sorry. Cygwin's stat function will find a file with a .exe
extension. Cygwin's open function won't. It has been this way for four
or five years. It has nothing to do with the mount command.
So, if you have a file called foo.exe 'ls -l foo' will work but
'cat foo.exe' won't work.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: No such file, but it's right there
Christopher Faylor <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 18, 2002 at 12:35:57AM -, Max Bowsher wrote:
>> Randall R Schulz <[EMAIL PROTECTED]> wrote:
>>> Cygwin follows the Windows convention of using file file name suffix
>>> ".exe" for its binary executable files. While Cygwin will locate
>>> and execute files files given only the base name (sans suffix),
>>> other uses ("cat," "less," or more apropos "nm," "size" or "file")
>>> demand the full file name, including the ".exe" suffix.
>>
>> Actually, the significant point seems to be that the files are being
>> accessed via a mount with no underlying directory.
>
> No, sorry. Cygwin's stat function will find a file with a .exe
> extension. Cygwin's open function won't. It has been this way for
> four or five years. It has nothing to do with the mount command.
>
> So, if you have a file called foo.exe 'ls -l foo' will work but
> 'cat foo.exe' won't work.
You mean 'cat foo', don't you?
But you are right - I must have been hallucinating when I was experimenting
before I posted that.
Max.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
Re: No such file, but it's right there
On Mon, Nov 18, 2002 at 01:05:10AM -, Max Bowsher wrote: >Christopher Faylor <[EMAIL PROTECTED]> wrote: >> So, if you have a file called foo.exe 'ls -l foo' will work but >> 'cat foo.exe' won't work. > >You mean 'cat foo', don't you? Yes. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
