GNU bug report logs - #55487
chmod to +w is not defaulting to ALL target in Debian 11.3

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#55487: closed (chmod to +w is not defaulting to ALL target in
 Debian 11.3)
Date: Tue, 17 May 2022 21:39:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Tue, 17 May 2022 14:38:33 -0700
with message-id <8da7ffd9-64b1-e549-32f5-6ad1b7da84e8 <at> cs.ucla.edu>
and subject line Re: bug#55487: chmod to +w is not defaulting to ALL target in Debian 11.3
has caused the debbugs.gnu.org bug report #55487,
regarding chmod to +w is not defaulting to ALL target in Debian 11.3
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
55487: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=55487
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Corey H <user9de1d <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: chmod to +w is not defaulting to ALL target in Debian 11.3
Date: Tue, 17 May 2022 17:51:37 +0000

[Message part 3 (text/plain, inline)]

in Debian 8.32-4+b1 (Debian 11.3) chmod +w isn't working right.

sudo mkdir /etc/whatever
sudo touch /etc/whatever/whatever.conf
sudo chmod +w /etc/whatever/whatever.conf #doesn't work
sudo chmod a+w /etc/whatever/whatever.conf #does work
#in
man chmod
# it states "If none of these are given, the effect is as if (a) were given"
# so in conclusion the `sudo chmod +w /etc/whatever/whatever.conf` should
work

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Corey H <user9de1d <at> gmail.com>
Cc: 55487-done <at> debbugs.gnu.org
Subject: Re: bug#55487: chmod to +w is not defaulting to ALL target in Debian
 11.3
Date: Tue, 17 May 2022 14:38:33 -0700

On 5/17/22 10:51, Corey H wrote:
> sudo chmod +w /etc/whatever/whatever.conf #doesn't work
> sudo chmod a+w /etc/whatever/whatever.conf #does work

It sounds like you're misunderstanding what "chmod +w" means. It doesn't 
mean "turn on all the w bits". It means "turn on the w bits enabled by 
the current umask". So, for example, this is expected behavior:

$ umask
0022
$ touch foo
$ ls -l foo
-rw-r--r--. 1 eggert eggert 0 May 17 14:37 foo
$ chmod +w foo
$ ls -l foo
-rw-r--r--. 1 eggert eggert 0 May 17 14:37 foo
$ umask 0
$ chmod +w foo
$ ls -l foo
-rw-rw-rw-. 1 eggert eggert 0 May 17 14:37 foo

Previous Next

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