The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: George Michaelson <>
Subject: [TUHS] Re: RFS (was Re: Re: forgotten versions)
Date: Mon, 20 Jun 2022 11:02:25 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

I probably tend too much to the sociological more than technical in
this, but I do know we were very prejudiced against RFS. Very. We just
didn't like it.

Probably? This was some kind of bizarre chauvinism about NFS and Suns,
and access to the systems. But, my memory is that RFS as available to
us was not very easy to deploy, and may have been by default a "hard"
mount just at the point we were finding the benefit of having a "soft"
mount, in experience. Sure, a soft mount is significantly less
reliable, but with unreliable campus networks and systems, half a
usable system is better than none at all, and RFS tended to 'all or

This was during the window where Sun was breaking the UDP checksum,
and also Ethernet backoff. So, its UDP checksum gaming meant it was
"faster" because it did less work, and its Ethernet backoff gaming
meant it was always first-to-fire in a contention event on the cable.
Two cheats! I don't think RFS did either, so there was also specious
benchmarking coming into effect,


  reply	other threads:[~2022-06-20  1:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  0:44 Norman Wilson
2022-06-20  1:02 ` George Michaelson [this message]
2022-06-20  4:50 ` arnold
  -- strict thread matches above, loose matches on Subject: below --
2022-06-20 12:28 Paul Ruizendaal via TUHS
2022-06-20 21:53 ` Derek Fawcus
2022-06-18  0:35 [TUHS] Re: forgotten versions Douglas McIlroy
2022-06-18  5:00 ` Kevin Bowling
2022-06-19 20:46   ` [TUHS] RFS (was Re: Re: forgotten versions) Derek Fawcus
2022-06-19 23:07     ` [TUHS] " Larry McVoy
2022-06-19 23:19       ` Brad Spencer
2022-06-20  5:03         ` Arno Griffioen via TUHS
2022-06-20  6:53           ` Theodore Ts'o

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).