From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] fun with cfs.
Date: Wed, 12 Jan 2005 16:38:35 -0500 [thread overview]
Message-ID: <ee9e417a0501121338377fdba1@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0501121117480.3521@bluesteel.lanl.gov>
> Now here's where somebody tells me: that file system already exists, just
> do x and y and z;
Well, you asked for it.
iostats -df /fd/1 rc
# play with anything
is one way.
srvfs -d foo /
tail -f /tmp/exportdb &
mount /srv/foo /n/foo
# play with /n/foo
is another.
Russ
next prev parent reply other threads:[~2005-01-12 21:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 18:26 Ronald G. Minnich
2005-01-12 18:33 ` Fco. J. Ballesteros
2005-01-12 18:37 ` Ronald G. Minnich
2005-01-12 21:38 ` Russ Cox [this message]
2005-01-12 21:43 ` Ronald G. Minnich
2005-01-12 23:30 ` Charles Forsyth
2005-01-12 23:21 ` Ronald G. Minnich
2005-01-13 0:06 ` Russ Cox
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=ee9e417a0501121338377fdba1@mail.gmail.com \
--to=russcox@gmail.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).