From: James Johnston <audioskeptic@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: Warren Toomey <wkt@tuhs.org>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: The Web Service on Minnie is 30 Years Old Today
Date: Mon, 19 Feb 2024 13:45:22 -0800 [thread overview]
Message-ID: <CAO2qRdP-DArRCqwGnw=5jkoHV6osjoOGd8LRyOvyZoq8yzR2Dg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2O71+q-_BHMghTR09mKqYedd1bNzrGz=NGn7HE4Qj3_KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
Well done. Has the hardware evolved? I presume so, but I do remember one
legacy machine from the early 1980's at BTL (icarus, an 11/23), that when
it shut down forever in 1996, was a microvax, with its bus connected to a
standard PDP11 bus, that connected to a Q-bus, and the original discs were
still on line. It's uptime was never more than 350+ days, though, because
of once a year UPS testing. In its last incarnation, it did nothing but
mail routing, and that barely. I don't think anything changed on it in the
last 10 years, not even the system.
On Mon, Feb 19, 2024 at 1:15 PM Clem Cole <clemc@ccc.com> wrote:
>
>
> On Mon, Feb 19, 2024 at 4:02 PM Warner Losh <imp@bsdimp.com> wrote:
>
>>
>>
>> On Mon, Feb 19, 2024 at 1:58 PM Rich Salz <rich.salz@gmail.com> wrote:
>>
>>> I think this makes minnie one of the longest running web services
>>>> still in existence :-)
>>>>
>>>
>>> Congrats. In a ship of Theseus sense.:)
>>>
>>
>> *We all sail in the Unix ship of Theseus..*. Every system today had code
>> from Unix directly, or from another ship that was built of the builts of
>> one that was split between a couple of groups. Yes, even Linux: lots of
>> networking userland came from BSD, for example, and while lots have been
>> rewritten, that's kinda the point of the ship of Theseus... :)
>>
> +1
> My observation is that Linux is just the current (and most
> successful) implementation of ideas that Doug, Ken, Rudd, Dennis, *et al.*
> started and others have contributed to over the years. And like the
> thought experiment described, there is no reason why the ship can not be
> changed. It still sails the same way to the same places.
>
>
> ᐧ
>
--
James D. (jj) Johnston
Chief Scientist, Immersion Networks
[-- Attachment #2: Type: text/html, Size: 3874 bytes --]
next prev parent reply other threads:[~2024-02-19 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 19:58 [TUHS] " Warren Toomey via TUHS
2024-02-19 20:05 ` [TUHS] " Dave Horsfall
2024-02-19 20:58 ` Rich Salz
2024-02-19 21:01 ` Warner Losh
2024-02-19 21:14 ` Clem Cole
2024-02-19 21:45 ` James Johnston [this message]
2024-02-20 2:10 ` Douglas McIlroy
2024-02-20 4:53 ` Charles H. Sauer
2024-02-20 7:18 ` arnold
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='CAO2qRdP-DArRCqwGnw=5jkoHV6osjoOGd8LRyOvyZoq8yzR2Dg@mail.gmail.com' \
--to=audioskeptic@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@tuhs.org \
--cc=wkt@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).