From: sqweek <sqweek@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan 9 wiping itself?
Date: Fri, 30 Nov 2007 13:58:59 +0900 [thread overview]
Message-ID: <140e7ec30711292058i16b0d11bjc1d7646e336f2ee7@mail.gmail.com> (raw)
In-Reply-To: <474D93A2.278C7D77@null.net>
On Nov 29, 2007 1:29 AM, Douglas A. Gwyn <DAGwyn@null.net> wrote:
> Instead of delete and later replace, how about create unique-named temp new file then immediately rename to target name?
> If rename is atomic then nothing could ever get lost.
I suspect the submitted patch (ie, don't delete the file in the first
place) is similar enough.
Thanks a lot Russ, for the fixes and explanation.
-sqweek
next prev parent reply other threads:[~2007-11-30 4:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-23 23:29 Pietro Gagliardi
2007-11-24 17:44 ` Antonin Vecera
2007-11-24 17:46 ` Pietro Gagliardi
2007-11-24 18:43 ` Uriel
2007-11-28 4:21 ` Russ Cox
2007-11-28 7:43 ` sqweek
2007-11-28 14:35 ` Russ Cox
2007-11-28 16:29 ` Douglas A. Gwyn
2007-11-30 4:58 ` sqweek [this message]
2007-11-24 20:59 ` erik quanstrom
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=140e7ec30711292058i16b0d11bjc1d7646e336f2ee7@mail.gmail.com \
--to=sqweek@gmail.com \
--cc=9fans@cse.psu.edu \
/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.
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 NNTP newsgroup(s).