lloram239, 7 months ago ls reaction to this is unexpected: <span style="color:#323232;">$ mkdir foo </span><span style="color:#323232;">$ echo Foo > foo/file </span><span style="color:#323232;">$ chmod a-x foo </span><span style="color:#323232;">$ ls -l foo </span><span style="color:#323232;">ls: cannot access 'foo/file': Permission denied </span><span style="color:#323232;">total 0 </span><span style="color:#323232;">-????????? ? ? ? ? ? file </span> I expected to just get a “Permission denied”, but listing the content it can still do. So x is for following the name to the inode and r for listing directory content (i.e. just names)?
ls reaction to this is unexpected:
ls
<span style="color:#323232;">$ mkdir foo </span><span style="color:#323232;">$ echo Foo > foo/file </span><span style="color:#323232;">$ chmod a-x foo </span><span style="color:#323232;">$ ls -l foo </span><span style="color:#323232;">ls: cannot access 'foo/file': Permission denied </span><span style="color:#323232;">total 0 </span><span style="color:#323232;">-????????? ? ? ? ? ? file </span>
I expected to just get a “Permission denied”, but listing the content it can still do. So x is for following the name to the inode and r for listing directory content (i.e. just names)?
x
r