GNU bug report logs - #47324
Missing information in documentation

Previous Next

Full log

Message #13 received at 47324-done <at> debbugs.gnu.org (full text, mbox):

From: Walter Harms <wharms <at> bfs.de>
To: Bernhard Voelker <mail <at> bernhard-voelker.de>, "47324-done <at> debbugs.gnu.org"
 <47324-done <at> debbugs.gnu.org>
Subject: AW: bug#47324: Missing information in documentation
Date: Tue, 23 Mar 2021 10:18:08 +0000

In my case there was no security context involved.
It was a loop device mounted (that i was not aware of,
the image was already gone).
and rm -r stoped here because of "in use".

I expected some mentioning of mount somewhere.

re,
 wh


________________________________________
Von: Bernhard Voelker <mail <at> bernhard-voelker.de>
Gesendet: Montag, 22. März 2021 23:21
An: Walter Harms; 47324-done <at> debbugs.gnu.org
Betreff: Re: bug#47324: Missing information in documentation

WARNUNG: Diese E-Mail kam von außerhalb der Organisation. Klicken Sie nicht auf Links oder öffnen Sie keine Anhänge, es sei denn, Sie kennen den/die Absender*in und wissen, dass der Inhalt sicher ist.


On 3/22/21 5:37 PM, Walter Harms via GNU coreutils Bug Reports wrote:
> hi list,
> in the documentation (man page) [...]

According to the GNU guidelines and to avoid double work, the man page of
the coreutils is essentially not much more than the output of --help
(and actually gets generated via that).
Instead, the real documentation is available via the Texinfo manual,
which is available in diverse formats.  In a usual installation, it
is reachable via:
  $ info '(coreutils) ls invocation'
Alternative formats include HTML, PDF etc., see:
  https://www.gnu.org/software/coreutils/manual/

> [...] nice feature is mssing
> when a fs is mounted on a directory ls marks that with a dot
> behing the permission mask (see example)
>
> drwxr-xr-x. 2 1003 users 4096 Mar 22 17:53 vendor
>          ^^
>          notice the dot here
>
> I found nothing mentioned in the documentation.

It is documented in the section about the '-l' option:

  https://www.gnu.org/software/coreutils/manual/html_node/What-information-is-listed.html

  [...]
  Following the file mode bits is a single character that specifies whether an
  alternate access method such as an access control list applies to the file.
  When the character following the file mode bits is a space, there is no alternate
  access method. When it is a printing character, then there is such a method.

  GNU ls uses a ‘.’ character to indicate a file with a security context, but no
  other alternate access method.

  A file with any other combination of alternate access methods is marked with a ‘+’ character.

Assuming that this section is clear enough, I'm hereby marking this as done
in our bug tracker. Of course, the discussion can continue, and we could even
reopen the issue if needed.

Have a nice day,
Berny

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.