Displaying 3 results from an estimated 3 matches for "rocinante".
2019 Oct 26
2
ls permissions format changed in CentOS 8
...will install.
BTW, another data point: I chmod'd a file to 0000 and now all I get is "-."
for the mode string. It completely chops everything but the file type and
the ACL indicator. OTOH, if I set it to 0660, I get the full string. It
doesn't truncate the last octet.
[ken at rocinante src]$ chmod 0000 yes.c
[ken at rocinante src]$ ls -l yes.c
-. 1 ken ken 3895 May 13 2018 yes.c
[ken at rocinante src]$ chmod 0006 yes.c
[ken at rocinante src]$ ls -al yes.c
-rw-. 1 ken ken 3895 May 13 2018 yes.c
[ken at rocinante src]$ chmod 0060 yes.c
[ken at rocinante src]$ ls -al yes.c
----rw-...
2019 Oct 26
2
ls permissions format changed in CentOS 8
Found it. It happens from the process buffer inside Lugaru Epsilon. I think
ls thinks it's doing a DIRED output instead of a shell output. Now I need
to figure out why it thinks that. This wasn't happening in CentOS 7.
2019 Oct 25
5
ls permissions format changed in CentOS 8
When I use "ls -al" on a directory, for files with only owner read/write
permission, the displayed attributes are "-rw-", not "-rw-------". That
means the file names don't line up with other files in the directory, which
makes the listing harder to read. What changed where and how do I fix that?