GNU bug report logs -
#23263
cat: missingfile: No such file or directory
Previous Next
Reported by: Jonny Grant <jg <at> jguk.org>
Date: Sun, 10 Apr 2016 18:45:02 UTC
Severity: normal
Done: Paul Eggert <eggert <at> cs.ucla.edu>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#23263: cat: missingfile: No such file or directory
which was filed against the coreutils package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 23263 <at> debbugs.gnu.org.
--
23263: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23263
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
Jonny Grant wrote:
> Hello
>
> I noticed that cat doesn't have an accurate message in the following use-case:
>
> $ cat missingfile
> cat: missingfile: No such file or directory
> $ mkdir testdir
> $ cat testdir
> cat: testdir: Is a directory
The "No such file or directory" message occurs because the operating system does
not have a separate error code for missing directory versus missing file. In the
example you gave, perhaps the working directory is missing (this can happen on
some systems), or perhaps there is no file named "missingfile" in the working
directory; the same code is returned for both situations.
This is not a coreutils issue, but is instead a kernel and C library issue. It's
not something that coreutils can "fix", even assuming it was agreed that it was
a bug. If it really bothers you, I suggest writing the POSIX standardization
committee, but I should warn you that you'll need a strong argument to change
something that has been standardized for decades.
[Message part 3 (message/rfc822, inline)]
Hello
I noticed that cat doesn't have an accurate message in the following
use-case:
$ cat missingfile
cat: missingfile: No such file or directory
$ mkdir testdir
$ cat testdir
cat: testdir: Is a directory
I wrote up the details of the ENOENT problem here:
http://technoramauk.blogspot.co.uk/2015/12/enoent-considered-harmful.html
Please keep my email address in any replies as I am not on this mailing
list.
Cheers, Jonny
This bug report was last modified 9 years and 104 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.