[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#8391: chmod setuid & setguid bits
From: |
Bob Proulx |
Subject: |
bug#8391: chmod setuid & setguid bits |
Date: |
Mon, 5 Mar 2012 13:38:54 -0700 |
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Bruno Haible wrote:
> It's because this use of '+' is easy to remember.
> "chmod +x" means "add execution permissions".
> "chmod -x" means "remove execution permissions".
To be pedantic that isn't quite true. To be pedantic it actually is
gated by the process umask in effect at that time. You need the 'a'
or other target in order to avoid the umask layer.
"chmod +x" means "add execution permissions qualified by umask".
"chmod -x" means "remove execution permissions qualified by umask".
"chmod a+x" means "add execution permissions".
"chmod a-x" means "remove execution permissions".
Bob
- bug#8391: chmod setuid & setguid bits, Ondrej Vasik, 2012/03/05
- bug#8391: chmod setuid & setguid bits, Bruno Haible, 2012/03/05
- bug#8391: chmod setuid & setguid bits, Paul Eggert, 2012/03/05
- bug#8391: chmod setuid & setguid bits, Bruno Haible, 2012/03/05
- bug#8391: chmod setuid & setguid bits,
Bob Proulx <=
- bug#8391: chmod setuid & setguid bits, Ondrej Vasik, 2012/03/05
- bug#8391: chmod setuid & setguid bits, Bruno Haible, 2012/03/05
- bug#8391: chmod setuid & setguid bits, Ondrej Vasik, 2012/03/06
- bug#8391: chmod setuid & setguid bits, Paul Eggert, 2012/03/06
- bug#8391: chmod setuid & setguid bits, Jim Meyering, 2012/03/06
- bug#8391: chmod setuid & setguid bits, Paul Eggert, 2012/03/08