From: a@9srv.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vacfs
Date: Sun, 8 Feb 2004 12:30:47 -0500 [thread overview]
Message-ID: <1554eb88912745456a7073c2b609d919@9srv.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0402080932290.13641-100000@maxroach.lanl.gov>
// we'll just stick to fat16 :-)
bah, random-access is overrated. just put a tar file on
raw media and append. ;-)
ア
next prev parent reply other threads:[~2004-02-08 17:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-07 2:37 ron minnich
2004-02-07 2:43 ` ron minnich
2004-02-07 2:57 ` ron minnich
2004-02-07 3:04 ` boyd, rounin
2004-02-09 17:13 ` rog
2004-02-07 4:21 ` ron minnich
2004-02-07 4:35 ` boyd, rounin
2004-02-08 2:41 ` Joel Salomon
2004-02-08 16:32 ` ron minnich
2004-02-08 17:29 ` Charles Forsyth
2004-02-08 22:03 ` Wes Kussmaul
2004-02-08 17:30 ` a [this message]
2004-02-07 5:38 ` vdharani
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=1554eb88912745456a7073c2b609d919@9srv.net \
--to=a@9srv.net \
--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).