reopen 549179
thanks
> please read the answers in the following thread from the Austin ML:
> http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/755640/focus=2959
>
> There have been no more followups, so I believe that, when expecting
> a file, but given a directory, this is a user err
> >The shell scripts are executed in context of . The POSIX standard
> >specifically requires the context to be a readabale in order to run the
> >instructions.
>
> [mirabilos] Yes, but SUSv4 doesn’t say (or I could not find it)
> explicitly what to do with directories. Directories are files.
> Y
Jari Aalto dixit:
>Thorsten Glaser writes:
>> Yes, but SUSv4 doesn’t say (or I could not find it) explicitly what
>> to do with directories.
>
>It doesn't say about many things: context of symlinks, block devices etc.
Indeed. That would probably be implementation-specific behaviour.
[…]
>Does
Thorsten Glaser writes:
> Jari Aalto dixit:
>
>> That is an incorrect reasoning. The POSIX standard mandates ...
>> The shell scripts are executed in context of . The POSIX standard
>> specifically requires the context to be a readabale in order to run the
>> instructions.
>
> Yes, but SUSv4 does
Jari Aalto dixit:
>That is an incorrect reasoning. The POSIX standard mandates:
[…]
>The shell scripts are executed in context of . The POSIX standard
>specifically requires the context to be a readabale in order to run the
>instructions.
Yes, but SUSv4 doesn’t say (or I could not find it) explic
>t...@herc:~ $ mkdir tmp; cat tmp; echo $?
>0
>
>This is consistent with the rest of the operating system,
>ans as such not a bug, unless SUSv4 were to specifiy otherwise.
FYI, In Debian Linux the cat(1) behaves in standards compliant way[1]:
$ cat /tmp
cat: /tmp: Is a di
Thorsten Glaser writes:
>>tags 549179 wontfix
>
> t...@herc:~ $ cat tmp; echo $?
> 0
> t...@herc:~ $ mksh tmp; echo $?
> 0
>
> This is consistent with the rest of the operating system,
> ans as such not a bug, unless SUSv4 were to specifiy otherwise.
That is an incorrect reasoning. The POSIX sta
tags 549179 wontfix
severity 549179 wishlist
thanks
Jari Aalto dixit:
>mkdir tmp
>mksh tmp
>
>=> No error messages, no status code $? to signify an error.
t...@herc:~ $ cat tmp; echo $?
0
t...@herc:~ $ mksh tmp; echo $?
0
This is consistent with the rest of the operating system,
ans
Package: mksh
Version: 38.3-1
Severity: normal
mkdir tmp
mksh tmp
=> No error messages, no status code $? to signify an error.
Please signal an error and terminate on non-zero exit code.
An example from Bash:
bash tmp
tmp/: tmp/: is a directory
C.f. This bug was found from o
9 matches
Mail list logo
