From: Ish Rattan <ratta1i@mail.cps.cmich.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Which file server is recommended?
Date: Fri, 16 Jun 2000 09:14:38 +0000 [thread overview]
Message-ID: <3948DF01.550EE475@mail.cps.cmich.edu> (raw)
In-Reply-To: <200006151019.GAA12292@cse.psu.edu>
okamoto@granite.cias.osakafu-u.ac.jp wrote:
> I've now solved "key in the car" problem, and now searching the sources
> to make my plan how to install the new release onto my current Plan 9
> system. (Still cannot boot from scsi disks yet)
>
> There are two PC file servers, emellie (16Kbyte block) and plan9pc
> (4 Kbyte block). I suppose emelie for better performance and plan9pc
> for economic... Am I doing anything wrong?
>
> Kenji
Where does find the info for installing a fileserver and a cpuserver? I am
assuming that 2nd edition
printed docs on these are not valid any more..
-ishwar
next prev parent reply other threads:[~2000-06-16 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-15 10:20 okamoto
2000-06-16 9:14 ` Ish Rattan [this message]
2000-06-16 4:14 rob pike
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=3948DF01.550EE475@mail.cps.cmich.edu \
--to=ratta1i@mail.cps.cmich.edu \
--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).