From: Paul Eggert <eggert@cs.ucla.edu>
To: Robert Pluim <rpluim@gmail.com>, 37884@debbugs.gnu.org
Cc: bernardo.bacic@pobox.com
Subject: bug#37884: 27.0.50; Cannot write to a file in VirtualBox shared directory
Date: Thu, 31 Oct 2019 14:24:18 -0700 [thread overview]
Message-ID: <a4c01363-94e4-0a4e-94d3-8d57a93048b5@cs.ucla.edu> (raw)
In-Reply-To: <m2d0edfjos.fsf@gmail.com>
On 10/31/19 12:38 AM, Robert Pluim wrote:
> I thought there
> was a strong desire to keep the file read-only, otherwise why bother
> with the fchmod in the first place?
The desire was quite weak, not strong. I put in that fchmod in commit
2013-03-05T22:35:41!eggert@cs.ucla.edu only because mkostemp creates the
lock file with mode 0600 but we want the file world-readable and so
Emacs must OR 0044 into the mode. At the time, I thought there was no
reason to have the file be writable to anybody once written, so I
fchmod'ed it to 0444. But Bug#37884 means the file should be
user-writable (to work around the compatibility issue with the
nonstandard filesystem), so fchmod'ing to 0644 is a better choice.
prev parent reply other threads:[~2019-10-31 21:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 10:28 bug#37884: 27.0.50; Cannot write to a file in VirtualBox shared directory Bernardo
2019-10-24 16:10 ` Robert Pluim
[not found] ` <87blu2emi3.fsf@pobox.com>
2019-10-27 15:34 ` Robert Pluim
2019-10-27 15:52 ` Eli Zaretskii
2019-10-27 16:01 ` Robert Pluim
2019-10-27 16:34 ` Eli Zaretskii
2019-10-28 9:23 ` Bernardo
2019-10-28 12:32 ` Robert Pluim
2019-10-29 8:50 ` Bernardo
2019-10-29 9:04 ` Andreas Schwab
2019-10-29 13:41 ` Robert Pluim
2019-10-30 8:44 ` Bernardo
2019-10-30 13:31 ` Robert Pluim
2019-10-30 16:25 ` Eli Zaretskii
2019-10-31 1:41 ` Paul Eggert
2019-10-31 7:38 ` Robert Pluim
2019-10-31 14:37 ` Eli Zaretskii
2019-10-31 21:24 ` Paul Eggert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4c01363-94e4-0a4e-94d3-8d57a93048b5@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=37884@debbugs.gnu.org \
--cc=bernardo.bacic@pobox.com \
--cc=rpluim@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).