From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 8118 invoked from network); 2 Jul 2023 15:14:56 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 2 Jul 2023 15:14:56 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 2C87043680; Mon, 3 Jul 2023 01:14:51 +1000 (AEST) Received: from oclsc.com (oclsc.com [206.248.137.164]) by minnie.tuhs.org (Postfix) with ESMTP id BDCE34367E for ; Mon, 3 Jul 2023 01:14:46 +1000 (AEST) Received: by oclsc.org id CE2784FB13; Sun, 2 Jul 2023 11:14:45 -0400 (EDT) Received: by oclsc.org id D0FED640CDB; Sun, 2 Jul 2023 11:14:45 -0400 (EDT) To: tuhs@tuhs.org Message-ID: <5E562516DD9AED7CEF9BE6FED02623BE.for-standards-violators@oclsc.org> Date: Sun, 2 Jul 2023 11:14:45 -0400 (EDT) From: norman@oclsc.org (Norman Wilson) Message-ID-Hash: NKKTRAQNI7R3N7VZ5HCMDKKPY762Q2MA X-Message-ID-Hash: NKKTRAQNI7R3N7VZ5HCMDKKPY762Q2MA X-MailFrom: norman@oclsc.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Jerq menuhit/mhit List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: I had an experience similar to Tom London's: To: alice!rob Subject: you've spoiled me I can't believe it. I'm sitting here at home in front of my 2621, and I can't work. Damn it. I've got to get a blit at home. When I left Bell Labs, I had an X11 workstation at work, but only a simple terminal at home. Having used a Jerqblit5620 for years at both work and home, I found it incredibly limiting. After a year or so I came across a reseller who had a lot of off-lease 5620s for sale cheap (like USD 150 or so each). I asked around the university I now worked at, found a handful of other people who wanted in, and then a local small company who did System V system-administration consulting who wanted some for themselves, and were willing to handle all the paperwork. All that allowed us to negotiate the price down even more. In the end I bought six, of which I think four are still working, though I haven't turned any of them on for years. None of the Unixes I used at the time came with 5620 support, but the protocol for the basic window system built into the ROM was well-documented and I managed to roll my own host support. I also managed to cobble up my own binary-loading tools sufficient to get sam working (I forget how I compiled the binary for the terminal); that was rather more work, but it was worth it to be able to have sam and multiple windows from home, even though it was the ROM OS and therefore mpx rather than mux. I remember porting my version of the host code to Ultrix, SunOS 4, and IRIX. My workplace at the time had a little bit of VAX/VMS around. I didn't use that much but wanted to try porting my host code to VMS as well. VMS had had a C compiler for some years and some sort of pseudo-terminal for a shorter time, so it ought to have been possible. I didn't get around to it before we finally left VMS behind in the dustbin of history. I wish I'd found time to do it, just to show that there really was nothing Unix-specific about the idea or the implementation. It's just a multiplexing protocol; it needs no kernel support except that needed to run a command-line session not attached to a physical terminal, and networking has long since made that available on any competent OS. Norman Wilson Toronto ON