From: Jon Forrest <nobozo@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] /bin vs /sbin
Date: Tue, 21 Jul 2020 19:17:18 -0700 [thread overview]
Message-ID: <5489aab7-efb4-8bcd-3ca7-9b47e9b7b305@gmail.com> (raw)
In-Reply-To: <CAEoi9W7J3GfPSZ2fduVZj7NfwbTgmE049XcG1AU_z-eW=5D4cQ@mail.gmail.com>
On 7/21/2020 6:44 PM, Dan Cross wrote:
> When I first came on the scene, there was a convention that I thought
> worked well: the "dataless" node. I have no idea why it was called that;
I don't know either, but I implemented a dataless architecture for
all the OSF/1 machines in the CS department at UC Berkeley in the
1990s. I wrote this up (see
https://groups.google.com/forum/#!msg/comp.unix.osf.osf1/-s1xW80zXPE/OGENDhH2Sc0J
and it eventually made the OSF1 FAQ.
It made a huge difference back when disks were small.
This was done with NFS 3.X which had no local caching.
I've always wondered how a dataless environment would
work on NFS 4.X, which could do local caching.
Jon
next prev parent reply other threads:[~2020-07-22 2:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 17:55 Grant Taylor via TUHS
2020-07-21 18:15 ` Warner Losh
2020-07-21 22:42 ` David Arnold
2020-07-22 3:33 ` Warner Losh
2020-07-21 18:22 ` arnold
2020-07-21 18:33 ` Warner Losh
2020-07-21 18:43 ` Larry McVoy
2020-07-22 1:16 ` tytso
2020-07-22 3:27 ` Grant Taylor via TUHS
2020-07-22 3:35 ` Warner Losh
2021-01-27 5:56 ` Greg A. Woods
2021-01-27 19:06 ` Grant Taylor via TUHS
2021-01-27 22:22 ` Warner Losh
2021-01-27 22:35 ` Greg A. Woods
2021-01-28 5:24 ` Grant Taylor via TUHS
2020-07-22 1:44 ` Dan Cross
2020-07-22 2:17 ` Jon Forrest [this message]
2020-07-22 2:20 ` Adam Thornton
2020-07-22 13:30 ` Clem Cole
2020-07-22 13:43 ` Richard Salz
2020-07-22 2:27 ` Kurt H Maier
2020-07-21 19:24 ` Clem Cole
2020-07-22 13:39 ` Clem Cole
2021-01-29 23:50 ` Chris Hanson
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=5489aab7-efb4-8bcd-3ca7-9b47e9b7b305@gmail.com \
--to=nobozo@gmail.com \
--cc=tuhs@minnie.tuhs.org \
/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).