Strange 'ls' listing

[Rick Stevens]

On 04/07/2010 03:02 PM, jack craig wrote:
> ls -l looks like the old format on my fc11...
>
> -rwxr-xr-x 1 jackc jackc 10413 2010-02-23 13:35 build_chnum
> -rwxr-xr-x 1 jackc jackc 18056 2010-04-05 14:54 build_ev
> -rwxr-xr-x 1 jackc jackc  4314 2010-03-15 17:47 build_hx
> -rwxr-xr-x 1 jackc jackc   265 2010-04-05 12:41 chk
> -rwxr-xr-x 1 jackc jackc   837 2010-04-05 15:35 chk_key_date

Not on mine:
[root at prophead ~]# ls -l /tmp
total 172
-rw-r--r--. 1 root root 26878 2010-04-07 10:12 fred
drwx------. 2 rick rick  4096 2010-04-02 09:42 keyring-IghpvV
drwx------. 2 rick rick  4096 2010-04-07 12:01 ksocket-rickvkbmo3

[root at prophead ~]# rpm -qa | grep ^coreutils
coreutils-7.2-7.fc11.x86_64

And from "info ls" in the "What information is listed" section:

      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 an SELinux
      security context, but no other alternate access method.

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

----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, C2 Hosting          ricks at nerd.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-     The trouble with troubleshooting is that trouble sometimes     -
-                             shoots back.                           -
----------------------------------------------------------------------