Others may know this already, but I thought it was worth passing on.
When a directory has "x" in its permissions, that allows a command to
search in the directory. Selecting an executable file in that directory
by name, seems to be still possible. I had that happen yesterday. Everything in the program worked, except that it couldn't find the configuration file. It was the only essential file the program couldn't find The permissions on the directory were 666, and the command came
from outside it. Changing the permissions on the folder to 776 solved
the problem.
On 25/8/21 4:10 am, Doug Laidlaw wrote:
Others may know this already, but I thought it was worth passing on.=20
=20
When a directory has "x" in its permissions, that allows a command
to search in the directory.=C2=A0 Selecting an executable file in that directory by name, seems to be still possible.=C2=A0 I had that happen yesterday. Everything in the program worked, except that it
couldn't find the configuration file.=C2=A0 It was the only essential
file the program couldn't find=C2=A0 The permissions on the directory
were 666, and the command came from outside it.=C2=A0 Changing the permissions on the folder to 776 solved the problem. =20
exactly! I remember when I delved into the file permission stuff
there was a folder setting that rendered the folder unreadable and
content could not be listed, BUT if the name of a file was known then
it could still be accessed.
File permission is not for the faint of heart - I've always scuttled=20
away.
I've written a long but elaborate tutorial on POSIX permissions and file ownership over at the Manjaro forum. The tutorial is publicly
accessible.
<https://forum.manjaro.org/t/tutorial-understanding-and-working-with-unix-filesystems-and-permissions/65793>
Others may know this already, but I thought it was worth passing on.
When a directory has "x" in its permissions, that allows a command to
search in the directory. Selecting an executable file in that directory
by name, seems to be still possible. I had that happen yesterday. Everything in the program worked, except that it couldn't find the configuration file. It was the only essential file the program couldn't find The permissions on the directory were 666, and the command came
from outside it. Changing the permissions on the folder to 776 solved
the problem.
On 2021-08-24, Doug Laidlaw <laidlaws@hotkey.net.au> wrote:
Others may know this already, but I thought it was worth passing on.
When a directory has "x" in its permissions, that allows a command to
search in the directory. Selecting an executable file in that
directory
No, it allows a command to run or open a specifically named file. It
does not allow you to search or read the filenames in that directory.
Thus ls dir does not work, but if there is a file called abbie, you can
open dir/abbie but only if you know the exact name of the file. Thus ls dir/abbi? does not work, but ls dir/abbie should.
d-wx--x--x 2 root root 60 Aug 26 19:04 .
drwxrwxrwt 16 root root 380 Aug 26 19:03 ..
-rw-r----- 1 root root 0 Aug 26 19:04 abbie #l dir/
/bin/ls: cannot open directory 'dir/': Permission denied #ls dir/abbie
dir/abbie #ls dir/abbi?
/bin/ls: cannot access 'dir/abbi?': No such file or directory
by name, seems to be still possible. I had that happen yesterday.
Everything in the program worked, except that it couldn't find the
configuration file. It was the only essential file the program
couldn't find The permissions on the directory were 666, and the
command came from outside it. Changing the permissions on the folder
to 776 solved the problem.
I've written a long but elaborate tutorial on POSIX permissions and file ownership over at the Manjaro forum. The tutorial is publiclyunix-filesystems-and-permissions/65793>
accessible.
<https://forum.manjaro.org/t/tutorial-understanding-and-working-with-
On Wed, 25 Aug 2021 01:33:33 +0200, Aragorn wrote:
I've written a long but elaborate tutorial on POSIX permissions and
file ownership over at the Manjaro forum. The tutorial is publicly accessible.
<https://forum.manjaro.org/t/tutorial-understanding-and-working-with-
unix-filesystems-and-permissions/65793>
hmmm I guess Copy and Paste is the only way to save this file in the Computer for printing..
On 2021-08-24, Doug Laidlaw<laidlaws@hotkey.net.au> wrote:
Others may know this already, but I thought it was worth passing on.No, it allows a command to run or open a specifically named file. It
When a directory has "x" in its permissions, that allows a command to
search in the directory. Selecting an executable file in that
directory
does not allow you to search or read the filenames in that directory.
On 28/8/21 12:02 am, Jim wrote:
On 2021-08-24, Doug Laidlaw<laidlaws@hotkey.net.au> wrote:
Others may know this already, but I thought it was worth passing on.No, it allows a command to run or open a specifically named file. It
When a directory has "x" in its permissions, that allows a command to
search in the directory. Selecting an executable file in that
directory
does not allow you to search or read the filenames in that directory.
What I was trying to do is what is stated in the last two sentences.
I have seen "search in the directory" used. Maybe the word "search" was meant differently. Whatever the problem was in my case, I seem to have followed the wrong trail. Even making the director searchable by owner
and group was only a temporary fix, and didn't survive overnight. After trying all the hints on the Firestorm Help page and everything else I
could think of, I adopted my usual "repair" in these cases: I ran an
upgrade reinstall (using the "Upgrade Mageia 8" on the installer's
menu.) That procedure does nothing that is apparent, but it seems often
to fix quirks like this one. It hasn't repaired a similar one, however.
Windows is no longer added to the Grub menu, although the folder is visible and searchable from Linux. A stanza I put in 40_custom does
still work, however, so I boot from that.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 49:13:03 |
Calls: | 6,648 |
Files: | 12,200 |
Messages: | 5,330,097 |