From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] boot error walking
Date: Sat, 14 Feb 2004 11:10:34 -0500 [thread overview]
Message-ID: <03f7a1ee21ba07b624ca6f0bf73ec150@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0402140832360.5703-100000@maxroach.lanl.gov>
I've found fossil very trustworthy till I turn on snaps to venti. So
far I'm two for two fossil file servers that worked fine for a long time
till I did a snap -a. I'll see what I can figure it out in my infinite
free time. I pointed rsc to an instance of such a problem we have here
and hopefully will hear from him when he gets time.
I have no intention of discarding kfs. It doesn't cost anything to
keep it. Contrary to popular belief generated by a message recently
on this list, we haven't taken kfs reading support out of 9load
(I didn't even know it was there to tell the truth). I'll find a
machine at work later today and test it out to make sure 9load hasn't
been accidentally broken.
next prev parent reply other threads:[~2004-02-14 16:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:34 Tiit Lankots
2004-02-13 13:46 ` andrey mirtchovski
2004-02-14 4:02 ` boyd, rounin
2004-02-14 3:32 ` boyd, rounin
2004-02-14 7:33 ` Bruce Ellis
2004-02-14 15:45 ` ron minnich
2004-02-14 16:00 ` Charles Forsyth
2004-02-14 16:10 ` David Presotto [this message]
2004-02-14 15:26 ` andrey mirtchovski
2004-02-14 16:12 ` David Presotto
2004-02-14 16:18 ` Bruce Ellis
2004-02-15 0:14 ` Christopher Nielsen
2004-02-15 0:22 ` boyd, rounin
2004-02-15 2:13 ` ron minnich
-- strict thread matches above, loose matches on Subject: below --
2004-02-17 23:21 Herbert B. Hancock
2004-02-13 12:43 Tiit Lankots
2004-02-13 12:28 Herbert B. Hancock
2004-02-13 13:36 ` andrey mirtchovski
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=03f7a1ee21ba07b624ca6f0bf73ec150@plan9.bell-labs.com \
--to=presotto@closedmind.org \
--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).