From: ianb@cs.york.ac.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] file server problems
Date: Thu, 13 Jul 2000 10:01:11 +0100 [thread overview]
Message-ID: <200007130901.KAA03291@pc095.cs.york.ac.uk> (raw)
Yes, please! I don't really want to go out an buy scsi disks and
cards when I have a pile of spare ide machines.
Ian
>> <chuckle>
>> 'had' is somewhat strong, eh? it's just a software problem.
>> i have an interface that allows using IDE drives for
>> the fileserver. i have 2 3.5Gb IDEs striped together.
>
>oh yeah, if you'd like a snapshot of it i can provide it. i don't
>see it getting rolled into the base tree (however that works) but
>it might be useful for some people.
>
>--eld
next reply other threads:[~2000-07-13 9:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-13 9:01 ianb [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-15 15:05 jmk
2000-07-14 4:09 jmk
2000-07-13 5:09 Russ Cox
2000-07-12 9:04 ianb
2000-07-13 1:33 ` Eric Dorman
2000-07-13 2:28 ` Eric Dorman
2000-07-13 4:15 ` Lucio De Re
2000-07-13 4:33 ` Scott Schwartz
2000-07-13 12:19 ` Lucio De Re
2000-07-11 11:24 forsyth
2000-07-12 1:49 ` Eric Dorman
2000-07-12 18:48 ` splite
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=200007130901.KAA03291@pc095.cs.york.ac.uk \
--to=ianb@cs.york.ac.uk \
--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).