Permissions, F-16 -

[Bob Goodwin]

Would someone explain the meaning of the permissions in the last
        line below, especially the "+" ?

[root@box6 bobg]# ll /dev/bus/usb/001
            total 0
            crw-rw-r--. 1 root root 189, 0 Feb 28 03:08 001
            crw-rw-r--+ 1 root root 189, 2 Feb 28 03:08 003

I understand read, write, and execute, and generally set them
        with the values of 4, 2, and 1, but the --. and the --+ don't
        seem to be covered in anything I've "googled." "d" for
        directory, but "c" ?

Thanks,

Bob

[Tony Placilla]

-----Original Message-----
From: [e-mail] [mailto:[e-mail]] On Behalf Of Bob Goodwin
Sent: Tuesday, February 28, 2012 10:12 AM
To: Fedora List
Subject: Permissions, F-16 -

Would someone explain the meaning of the permissions in the last
        line below, especially the "+" ?

[root@box6 bobg]# ll /dev/bus/usb/001
            total 0
            crw-rw-r--. 1 root root 189, 0 Feb 28 03:08 001
            crw-rw-r--+ 1 root root 189, 2 Feb 28 03:08 003

I understand read, write, and execute, and generally set them
        with the values of 4, 2, and 1, but the --. and the --+ don't
        seem to be covered in anything I've "googled." "d" for
        directory, but "c" ?

Thanks,

Bob

The c means it's a character special device (or file. ) Possibly a scanner connected via USB?
The + means there are ACL's in affect for it

--
Tony Placilla

[Bob Goodwin]

On 28/02/12 10:24, Tony Placilla wrote:
> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On Behalf Of Bob Goodwin
> Sent: Tuesday, February 28, 2012 10:12 AM
> To: Fedora List
> Subject: Permissions, F-16 -
>      Would someone explain the meaning of the permissions in the last
>      line below, especially the "+" ?
>
>          [root@box6 bobg]# ll /dev/bus/usb/001
>          total 0
>          crw-rw-r--. 1 root root 189, 0 Feb 28 03:08 001
>          crw-rw-r--+ 1 root root 189, 2 Feb 28 03:08 003
>
>      I understand read, write, and execute, and generally set them
>      with the values of 4, 2, and 1, but the --. and the --+ don't
>      seem to be covered in anything I've "googled." "d" for
>      directory, but "c" ?
>
>      Thanks,
>
>      Bob
>
>
> The c means it's a character special device (or file. ) Possibly a scanner connected via USB?
> The + means there are ACL's in affect for it
>
> --
> Tony Placilla

Thanks for the information.

With that and Google I can at least work around my scanner user
        problem.

[root@box6 bobg]# setfacl -m u:bobg:rw- /dev/bus/usb/001/003

I know that will change on reboot, etc. But it's a start.

Bob

[David]

On 29/02/2012, Bob Goodwin  wrote:
>     Would someone explain the meaning of the permissions in the last
>     line below, especially the "+" ?
>
>         [root@box6 bobg]# ll /dev/bus/usb/001
>         total 0
>         crw-rw-r--. 1 root root 189, 0 Feb 28 03:08 001
>         crw-rw-r--+ 1 root root 189, 2 Feb 28 03:08 003

At the bottom of 'man ls' here it says:
"The full documentation for ls is maintained as a Texinfo manual.  If
the info and ls programs are properly installed at your site, the
command
              info coreutils 'ls invocation'
should give you access to the complete manual.
And looking there, your questions are answered in the documentation of
the -l option.

[Bob Goodwin]

On 28/02/12 23:06, David wrote:

At the bottom of 'man ls' here it says: "The full documentation for ls 
is maintained as a Texinfo manual. If the info and ls programs are 
properly installed at your site, the command info coreutils 'ls 
invocation' should give you access to the complete manual. And looking 
there, your questions are answered in the documentation of the -l option.

Interesting. I never read that before. It produces an
        overwhelming amount of information about the basic command "ls."

Now I have to learn to navigate through that!

Thanks,

Bob

[Tim]

On Wed, 2012-02-29 at 02:38 -0500, Bob Goodwin wrote:
> Now I have to learn to navigate through that!

Hint:  Using the pinfo program is easier to read than using info.  For
one thing, it has coloured highlighting of the interactive parts of the
page.

Though reading any info file is like trying to read ten pages of
documentation spread into various different paragraphs spread across a
hundred pages in a book.  You can go around in circles, not quite
finding the part that you need to read.

[David]

On 29/02/2012, Tim  wrote:
> Though reading any info file is like trying to read ten pages of
> documentation spread into various different paragraphs spread across a
> hundred pages in a book.  You can go around in circles, not quite
> finding the part that you need to read.

Yeah, there is a lot of good information hidden behind a dated interface.
It is easy though to dump all subnodes into a text file which I find
easier to search.

Examples:

info --subnodes -f tar -n "Top" >example1
info --subnodes -f coreutils -n "File permissions" >example2