From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] non-truncating create
Date: Mon, 9 Oct 2006 20:03:01 -0400 [thread overview]
Message-ID: <ee9e417a0610091703p77fa7435s1fa6e625b5b5b5dd@mail.gmail.com> (raw)
In-Reply-To: <W3347329822240921160433527@webmail21>
> And if you are interested in a much deeper discussion,
> look at the archives from 1999.
Actually it was 1998: http://9fans.net/archive/1998/02
especially http://9fans.net/archive/1998/02/17
We explicitly considered this when working on 9P2000
and added the OEXCL flag to create to address this problem.
Russ
next prev parent reply other threads:[~2006-10-10 0:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 22:38 G. David Butler
2006-10-09 23:36 ` Joel Salomon
2006-10-10 0:03 ` Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 6:46 Joel “chesky” Salomon
2006-10-09 7:30 ` Steve Simon
2006-10-09 3:13 Joel “chesky” Salomon
2006-10-09 3:13 Joel “chesky” Salomon
2006-10-09 3:13 Joel “chesky” Salomon
2006-10-09 4:00 ` Russ Cox
2006-10-09 6:09 ` Joel “chesky” Salomon
2006-10-09 15:57 ` Russ Cox
2006-10-09 4:01 ` Felipe Bichued
2006-10-09 5:39 ` Joel Salomon
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=ee9e417a0610091703p77fa7435s1fa6e625b5b5b5dd@mail.gmail.com \
--to=rsc@swtch.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).