From: "J.A. Magallon" <jamagallon@able.es>
To: Hirokazu Takahashi <taka@valinux.co.jp>
Cc: ecki@calista.eckenfels.6bone.ka-ip.net, linux-kernel@vger.kernel.org
Subject: Re: cachefs on linux
Date: Thu, 12 Jun 2003 00:26:51 +0200 [thread overview]
Message-ID: <20030611222651.GA2712@werewolf.able.es> (raw)
In-Reply-To: <20030611.201218.66717787.taka@valinux.co.jp>; from taka@valinux.co.jp on Wed, Jun 11, 2003 at 13:12:18 +0200
On 06.11, Hirokazu Takahashi wrote:
> Hello,
>
> I think the main benfit of cachefs is on NFS servers. Cachefs of
> clients can help them to reduce their loads. We know many clients
> may share one huge NFS server.
> (e.g. Streaming systems which contents may be extremly huge.)
>
Tha main use of cachefs I've seen was Sun's network-booting workstations.
We had a bunch of old suns (IPX, that was a 68k), with small disks
used to cache / , /usr and so on from an nfs server. You have the
benefits of just one centralized install and the ones from local
storage for more used files....
--
J.A. Magallon <jamagallon@able.es> \ Software is like sex:
werewolf.able.es \ It's better when it's free
Mandrake Linux release 9.2 (Cooker) for i586
Linux 2.4.21-rc7-jam1 (gcc 3.3 (Mandrake Linux 9.2 3.3-1mdk))
next prev parent reply other threads:[~2003-06-11 22:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 19:26 cachefs on linux Leonardo H. Machado
2003-06-09 20:42 ` Matthias Schniedermeyer
2003-06-09 20:49 ` Shawn
2003-06-09 20:56 ` Matthias Schniedermeyer
2003-06-10 8:29 ` Sean Hunter
2003-06-10 19:15 ` Rob Landley
2003-06-10 20:39 ` Anton Altaparmakov
2003-06-11 0:51 ` Rob Landley
2003-06-11 10:03 ` Bernd Eckenfels
2003-06-11 11:12 ` Hirokazu Takahashi
2003-06-11 22:26 ` J.A. Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-06-10 7:53 john
2003-06-11 21:01 Perez-Gonzalez, Inaky
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=20030611222651.GA2712@werewolf.able.es \
--to=jamagallon@able.es \
--cc=ecki@calista.eckenfels.6bone.ka-ip.net \
--cc=linux-kernel@vger.kernel.org \
--cc=taka@valinux.co.jp \
/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