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

Previous Next

Package: coreutils;

Reported by: Corey H <user9de1d <at> gmail.com>

Date: Tue, 17 May 2022 18:32:01 UTC

Severity: normal

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log


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

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




This bug report was last modified 3 years and 8 days ago.

Previous Next


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