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: Corey H <user9de1d <at> gmail.com>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 55487-done <at> debbugs.gnu.org
Subject: bug#55487: chmod to +w is not defaulting to ALL target in Debian 11.3
Date: Wed, 18 May 2022 17:42:02 +0000

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

Interesting.

On Tue, May 17, 2022 at 9:38 PM Paul Eggert <eggert <at> cs.ucla.edu> wrote:

> 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
>

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

Previous Next

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