From: Russ Cox <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fossil woe
Date: Tue, 6 Dec 2005 17:07:16 -0500 [thread overview]
Message-ID: <ee9e417a0512061407u2142d6d4t6549b52920e49191@mail.gmail.com> (raw)
In-Reply-To: <775b8d190512061302g617669dbl6fb693ae8a6b1e6f@mail.gmail.com>
> cache.c:698: * BUG: if the disk is full, should we flush some of it to Venti?
Should we? It's still not clear to me. There are fossil console
commands you could have typed to free up a little space
and run an archive to venti.
To find your old vac scores, see /sys/src/cmd/venti/dumpvacroots.
Russ
next prev parent reply other threads:[~2005-12-06 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 21:02 Bruce Ellis
2005-12-06 22:07 ` Russ Cox [this message]
2005-12-06 22:19 ` Eric Van Hensbergen
2005-12-06 23:10 ` Bruce Ellis
2005-12-06 23:41 ` Russ Cox
2005-12-06 23:48 ` Bruce Ellis
2005-12-07 21:03 ` rog
2005-12-07 21:07 ` Steve Simon
2005-12-07 21:12 ` Bruce Ellis
2005-12-07 21:36 ` Russ Cox
2005-12-07 21:55 ` Bruce Ellis
2005-12-07 22:09 ` jmk
2005-12-07 22:41 ` Russ Cox
2005-12-07 21:49 ` jmk
2005-12-07 0:17 ` geoff
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=ee9e417a0512061407u2142d6d4t6549b52920e49191@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).