From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] install problems redux
Date: Wed, 9 Oct 2002 12:57:32 -0400 [thread overview]
Message-ID: <34e61e279f492da07d1c7316656f32e4@plan9.bell-labs.com> (raw)
Start the install over. I bet it doesn't happen again.
(Yes, this is a terrible answer. I see what happened
and can't figure out how it did, but I suspect it's
just a really nasty race, and the fact that we haven't
seen it anywhere makes me hope that it's just a
really difficult race to trigger.)
Russ
next reply other threads:[~2002-10-09 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 16:57 Russ Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-09 22:27 Russ Cox
2002-10-09 16:46 John Saylor
2002-10-09 21:02 ` John Saylor
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=34e61e279f492da07d1c7316656f32e4@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).