From: schwartz+9fans@bio.cse.psu.edu schwartz+9fans@bio.cse.psu.edu
Subject: [9fans] Ghost in the linker?
Date: Thu, 19 Feb 1998 19:15:52 -0500 [thread overview]
Message-ID: <19980220001552.rFQn2FrOecWNS4ebugoyD16U_UmVxhiXf1Nkx-AUBl4@z> (raw)
edorman@Tanya.ucsd.edu (Eric Dorman) writes:
| .. it's mostly pretty cheap these days, particularly compared
| to cheap disks that provide really too much storage
| for this task (plus hassle of having to maintain them).
You could use them with cfs.
next reply other threads:[~1998-02-20 0:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-20 0:15 schwartz+9fans [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-02-20 20:47 Eric
1998-02-20 8:08 Nigel
1998-02-19 23:16 Eric
1998-02-19 20:10 forsyth
1998-02-19 20:02 Eric
1998-02-19 8:57 Nigel
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=19980220001552.rFQn2FrOecWNS4ebugoyD16U_UmVxhiXf1Nkx-AUBl4@z \
--to=schwartz+9fans@bio.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).