From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: Re [9fans] file server again
Date: Fri, 29 Dec 2000 20:38:53 +0900 [thread overview]
Message-ID: <20001229113853.3E63F199D5@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 127 bytes --]
Please read my post again where I wrote all the informations.
Additionally, scsi-II SE means 10Mbps scsi disks.
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 2731 bytes --]
From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re [9fans] file server again
Date: Fri, 29 Dec 2000 19:08:32 -0500
Message-ID: <20001229101540.EEC1C199D5@mail.cse.psu.edu>
Hello
Okamoto said:
>My old disk in file server was crushed, and I tried to replace it by a more recent
>fast scsi disk, which I chose is Seagate ST39236LWV (9GB).
>
>I started to work on the same machine which I had been using for release 3
>Plan 9 file server which had three SE SCSI-II drives and a wide drive. From
>those disks, I chose one of wide SCSI disk, which is Compaq XL32150W(2GB).
>The scsi controler is the same as before, and is tekram DC-390F (53C875E
>scsi chip on it). The Seage 9GB drive is for main filesystem (w0), and the
>other is for other filsystem. This machine has ASUS TX97-E motherboard
>and AMD K6-2/200MHz CPU). The hardware settings are same to those
>of running Plan 9 fileserver before. I used the most recent source trees for
>making 9pcfs(plan9pc), and 9load etc.
>
>Then, I started the machine with booting floppy, and got failed.
>
>PBS... Plan 9 From Bell Labs
>using fd0!dos!plan9.ini
>
>....and stopped here....
I am also in trouble with this problem.
I would like to have informations about the hardware components
(motherboard, cpu, scsi adapter, scsi disk) of PC that can run 9pcfs kernel.
Kenji Arisawa
E-mail: arisawa@aichi-u.ac.jp
next reply other threads:[~2000-12-29 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 11:38 okamoto [this message]
2000-12-30 0:44 ` arisawa
2000-12-30 8:27 ` Eric Dorman
2000-12-30 0:08 arisawa
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=20001229113853.3E63F199D5@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).