From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] df for fossil?
Date: Tue, 14 Jan 2003 15:57:33 +0100 [thread overview]
Message-ID: <7f141a65922d5fa74df962c7721f4a69@plan9.escet.urjc.es> (raw)
In-Reply-To: <9533f40c80c76a7dea30952dda479c8d@plan9.bell-labs.com>
Yep. I already saw flck, but I was wondering about
some field in some hdr about the # of blocks. I found no
such thing.
In any case, flck is enough for me now; I'm using fossil
as our file server for daily work, don't know how it behaves
when the partition gets full and was a bit scared about that.
thanks a lot
next prev parent reply other threads:[~2003-01-14 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 9:12 Fco.J.Ballesteros
2003-01-14 12:52 ` Russ Cox
2003-01-14 13:23 ` Russ Cox
2003-01-14 14:57 ` Fco.J.Ballesteros [this message]
2003-01-14 15:06 ` Russ Cox
2003-01-14 15:34 ` Fco.J.Ballesteros
2003-01-14 15:48 ` Russ Cox
2003-01-14 15:57 ` Fco.J.Ballesteros
2003-01-14 16:10 ` Russ Cox
2003-01-14 16:16 ` Fco.J.Ballesteros
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=7f141a65922d5fa74df962c7721f4a69@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--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).