From tuhs at tuhs.org Wed Jun 3 16:57:40 2026 From: tuhs at tuhs.org (Greg 'groggy' Lehey via TUHS) Date: Wed, 3 Jun 2026 16:57:40 +1000 Subject: [TUHS] Announcing The Unix Heritage Society Inc. Message-ID: Announcing The Unix Heritage Society Inc. For over a quarter of a century, Warren Toomey has been running The Unix Heritage Society. What wasn't clear to everybody was that this was a one-man show, and that Warren paid all expenses out of his own pocket. In mid-April, Warren asked for donations to help run the site. The response was overwhelmingly positive, and the donation target (AUD 3,728, about USD 2,600) was reached within 24 hours. Thanks to all for your generosity. Now comes the hard part: who looks after this money? Behind the scenes, Warren has had a few helpers known as the "TUHS Team". We decided that the best way to protect your donations was to create an Association according to Australian law. The state of Victoria has the simplest rules, so we created The Unix Heritage Society Inc. in Victoria. TUHSI has purposes which are legally protected: to preserve and maintain historical UNIX artefacts, and to provide a forum for discussion of UNIX and its history. The cost to run the server will keep both the Unix Archive hosted (the artefacts) and the TUHS mailing list running (the forum). As a not-for-profit organisation, TUHSI must ensure that funds collected are spent only on the TUHSI purposes, and TUHSI must make public the details of how any funds are spent. The term “Inc.” has nothing to do with commercial companies. It's the form required by the Victorian government. The TUHS team will form the initial members of the association. Many will be well known to you. They are: Thalia Archibald David Arnold Kevin Bowling Clem Cole Dan Cross Matt G. (segaloco) Greg Lehey Warner Losh Larry McVoy Will Senn Warren Toomey Frank Wortrner On 30 May (23:00 UTC) we had our inaugural Annual General Meeting, as required by the Victorian rules. We elected the following officers: President: Warren Toomey Vice-president: Clem Cole Secretary: Greg Lehey Treasurer: David Arnold TUHSI is transparent, so we are putting all the relevant documents up at this location: https://www.tuhs.org/Governance/ This includes the association rules and by-laws, list of members, the agendas and minutes of all meetings, the treasurer's reports etc. The minutes of the recent AGM are at http://www.tuhs.org/Governance/Agendas_and_Minutes/20260530-inaugural-agm So now the Unix Heritage Society (i.e. you, the people on the TUHS mailing list) is supported by a legal entity (TUHSI, run by the TUHS team members) to ensure that your donations will go where you want them to go. What happens next? First, we find our feet. We're planning to upgrade the server infrastructure under the leadership of Dan Cross. For you, this means one thing will change: minnie.tuhs.org will not go away, but it will be the name of Warren's personal machine. There is a redirector in place, but if you're used to using this name, please choose to use www.tuhs.org (or just tuhs.org) instead. Every two months, Warren or David will e-mail the TUHS list with an update on what funds have been spent where and the current balance of funds. You can find a FAQ about TUHSI at https://www.tuhs.org/Governance/tuhsi_faq.html. If you have any other questions, please e-mail them to the TUHS mailing list, tuhs at tuhs.org, so we can answer them and/or discuss any arising issues/suggestions. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From tuhs at tuhs.org Wed Jun 3 22:29:21 2026 From: tuhs at tuhs.org (Douglas McIlroy via TUHS) Date: Wed, 3 Jun 2026 08:29:21 -0400 Subject: [TUHS] Announcing The Unix Heritage Society Inc. In-Reply-To: References: Message-ID: Great news! And the span of the board, from grizzled veteran to grad student foretells a robust long life for TUHSI. Doug On Wed, Jun 3, 2026 at 2:58 AM Greg 'groggy' Lehey via TUHS wrote: > Announcing The Unix Heritage Society Inc. > > For over a quarter of a century, Warren Toomey has been running The > Unix Heritage Society. What wasn't clear to everybody was that this > was a one-man show, and that Warren paid all expenses out of his own > pocket. > > In mid-April, Warren asked for donations to help run the site. The > response was overwhelmingly positive, and the donation target (AUD > 3,728, about USD 2,600) was reached within 24 hours. Thanks to all > for your generosity. > > Now comes the hard part: who looks after this money? Behind the > scenes, Warren has had a few helpers known as the "TUHS Team". > We decided that the best way to protect your donations was to create an > Association according to Australian law. The state of Victoria has > the simplest rules, so we created The Unix Heritage Society Inc. in > Victoria. > > TUHSI has purposes which are legally protected: to preserve and maintain > historical UNIX artefacts, and to provide a forum for discussion of UNIX > and its history. The cost to run the server will keep both the Unix Archive > hosted (the artefacts) and the TUHS mailing list running (the forum). > > As a not-for-profit organisation, TUHSI must ensure that funds collected > are spent only on the TUHSI purposes, and TUHSI must make public the > details of how any funds are spent. > > The term “Inc.” has nothing to do with commercial companies. It's the > form required by the Victorian government. > > The TUHS team will form the initial members of the association. Many will > be well known to you. They are: > > Thalia Archibald > David Arnold > Kevin Bowling > Clem Cole > Dan Cross > Matt G. (segaloco) > Greg Lehey > Warner Losh > Larry McVoy > Will Senn > Warren Toomey > Frank Wortrner > > On 30 May (23:00 UTC) we had our inaugural Annual General Meeting, as > required by the Victorian rules. We elected the following officers: > > President: Warren Toomey > Vice-president: Clem Cole > Secretary: Greg Lehey > Treasurer: David Arnold > > TUHSI is transparent, so we are putting all the relevant documents up > at this location: https://www.tuhs.org/Governance/ This includes the > association rules and by-laws, list of members, the agendas and > minutes of all meetings, the treasurer's reports etc. > > The minutes of the recent AGM are at > http://www.tuhs.org/Governance/Agendas_and_Minutes/20260530-inaugural-agm > > So now the Unix Heritage Society (i.e. you, the people on the TUHS mailing > list) is supported by a legal entity (TUHSI, run by the TUHS team members) > to ensure that your donations will go where you want them to go. > > What happens next? First, we find our feet. We're planning to > upgrade the server infrastructure under the leadership of Dan Cross. > For you, this means one thing will change: minnie.tuhs.org will not go > away, but it will be the name of Warren's personal machine. There is > a redirector in place, but if you're used to using this name, please > choose to use www.tuhs.org (or just tuhs.org) instead. > > Every two months, Warren or David will e-mail the TUHS list with an update > on what funds have been spent where and the current balance of funds. > > You can find a FAQ about TUHSI at > https://www.tuhs.org/Governance/tuhsi_faq.html. If you have any other > questions, please e-mail them to the TUHS mailing list, tuhs at tuhs.org, so > we can answer them and/or discuss any arising issues/suggestions. > From tuhs at tuhs.org Thu Jun 4 02:21:38 2026 From: tuhs at tuhs.org (Heinz Lycklama via TUHS) Date: Wed, 3 Jun 2026 09:21:38 -0700 Subject: [TUHS] Announcing The Unix Heritage Society Inc. In-Reply-To: References: Message-ID: <6c559f65-d07c-4fec-8a18-095aa9f1c46c@osta.com> Great news indeed! But thanks is also due to you Doug for your enthusiastic support of work on the UNIX System from the early days of UNIX at Bell Labs to continuing work by many UNIX researchers and UNIX companies in the computing industry over all these years. Heinz On 6/3/2026 5:29 AM, Douglas McIlroy via TUHS wrote: > Great news! And the span of the board, from grizzled veteran to grad > student foretells a robust long life for TUHSI. > > Doug > > On Wed, Jun 3, 2026 at 2:58 AM Greg 'groggy' Lehey via TUHS > wrote: > >> Announcing The Unix Heritage Society Inc. >> >> For over a quarter of a century, Warren Toomey has been running The >> Unix Heritage Society. What wasn't clear to everybody was that this >> was a one-man show, and that Warren paid all expenses out of his own >> pocket. >> >> In mid-April, Warren asked for donations to help run the site. The >> response was overwhelmingly positive, and the donation target (AUD >> 3,728, about USD 2,600) was reached within 24 hours. Thanks to all >> for your generosity. >> >> Now comes the hard part: who looks after this money? Behind the >> scenes, Warren has had a few helpers known as the "TUHS Team". >> We decided that the best way to protect your donations was to create an >> Association according to Australian law. The state of Victoria has >> the simplest rules, so we created The Unix Heritage Society Inc. in >> Victoria. >> >> TUHSI has purposes which are legally protected: to preserve and maintain >> historical UNIX artefacts, and to provide a forum for discussion of UNIX >> and its history. The cost to run the server will keep both the Unix Archive >> hosted (the artefacts) and the TUHS mailing list running (the forum). >> >> As a not-for-profit organisation, TUHSI must ensure that funds collected >> are spent only on the TUHSI purposes, and TUHSI must make public the >> details of how any funds are spent. >> >> The term “Inc.” has nothing to do with commercial companies. It's the >> form required by the Victorian government. >> >> The TUHS team will form the initial members of the association. Many will >> be well known to you. They are: >> >> Thalia Archibald >> David Arnold >> Kevin Bowling >> Clem Cole >> Dan Cross >> Matt G. (segaloco) >> Greg Lehey >> Warner Losh >> Larry McVoy >> Will Senn >> Warren Toomey >> Frank Wortrner >> >> On 30 May (23:00 UTC) we had our inaugural Annual General Meeting, as >> required by the Victorian rules. We elected the following officers: >> >> President: Warren Toomey >> Vice-president: Clem Cole >> Secretary: Greg Lehey >> Treasurer: David Arnold >> >> TUHSI is transparent, so we are putting all the relevant documents up >> at this location: https://www.tuhs.org/Governance/ This includes the >> association rules and by-laws, list of members, the agendas and >> minutes of all meetings, the treasurer's reports etc. >> >> The minutes of the recent AGM are at >> http://www.tuhs.org/Governance/Agendas_and_Minutes/20260530-inaugural-agm >> >> So now the Unix Heritage Society (i.e. you, the people on the TUHS mailing >> list) is supported by a legal entity (TUHSI, run by the TUHS team members) >> to ensure that your donations will go where you want them to go. >> >> What happens next? First, we find our feet. We're planning to >> upgrade the server infrastructure under the leadership of Dan Cross. >> For you, this means one thing will change: minnie.tuhs.org will not go >> away, but it will be the name of Warren's personal machine. There is >> a redirector in place, but if you're used to using this name, please >> choose to use www.tuhs.org (or just tuhs.org) instead. >> >> Every two months, Warren or David will e-mail the TUHS list with an update >> on what funds have been spent where and the current balance of funds. >> >> You can find a FAQ about TUHSI at >> https://www.tuhs.org/Governance/tuhsi_faq.html. If you have any other >> questions, please e-mail them to the TUHS mailing list, tuhs at tuhs.org, so >> we can answer them and/or discuss any arising issues/suggestions. >> From tuhs at tuhs.org Thu Jun 4 03:11:00 2026 From: tuhs at tuhs.org (=?utf-8?q?Cameron_M=C3=AD=C4=8Be=C3=A1l_Tyre_via_TUHS?=) Date: Wed, 03 Jun 2026 17:11:00 +0000 Subject: [TUHS] Announcing The Unix Heritage Society Inc. In-Reply-To: References: Message-ID: Thank you everyone involved in this and getting things to this stage, and welcome TUHSI !!! Best regards to all, Cameron Sent from Proton Mail for Android. From tuhs at tuhs.org Thu Jun 4 03:50:54 2026 From: tuhs at tuhs.org (Briam Rodriguez via TUHS) Date: Wed, 3 Jun 2026 13:50:54 -0400 Subject: [TUHS] Announcing The Unix Heritage Society Inc. In-Reply-To: References: Message-ID: <90384ae3-5ce6-4167-8cc2-c681fe067952@gmail.com> Wow! this is great news! You are all benefactors of the community., Keep up the excellent work! -- Briam R. On 6/3/26 2:57 AM, Greg 'groggy' Lehey via TUHS wrote: > Announcing The Unix Heritage Society Inc. > > For over a quarter of a century, Warren Toomey has been running The > Unix Heritage Society. What wasn't clear to everybody was that this > was a one-man show, and that Warren paid all expenses out of his own > pocket. > > In mid-April, Warren asked for donations to help run the site. The > response was overwhelmingly positive, and the donation target (AUD > 3,728, about USD 2,600) was reached within 24 hours. Thanks to all > for your generosity. > > Now comes the hard part: who looks after this money? Behind the > scenes, Warren has had a few helpers known as the "TUHS Team". > We decided that the best way to protect your donations was to create an > Association according to Australian law. The state of Victoria has > the simplest rules, so we created The Unix Heritage Society Inc. in > Victoria. > > TUHSI has purposes which are legally protected: to preserve and maintain > historical UNIX artefacts, and to provide a forum for discussion of UNIX > and its history. The cost to run the server will keep both the Unix Archive > hosted (the artefacts) and the TUHS mailing list running (the forum). > > As a not-for-profit organisation, TUHSI must ensure that funds collected > are spent only on the TUHSI purposes, and TUHSI must make public the > details of how any funds are spent. > > The term “Inc.” has nothing to do with commercial companies. It's the > form required by the Victorian government. > > The TUHS team will form the initial members of the association. Many will > be well known to you. They are: > > Thalia Archibald > David Arnold > Kevin Bowling > Clem Cole > Dan Cross > Matt G. (segaloco) > Greg Lehey > Warner Losh > Larry McVoy > Will Senn > Warren Toomey > Frank Wortrner > > On 30 May (23:00 UTC) we had our inaugural Annual General Meeting, as > required by the Victorian rules. We elected the following officers: > > President: Warren Toomey > Vice-president: Clem Cole > Secretary: Greg Lehey > Treasurer: David Arnold > > TUHSI is transparent, so we are putting all the relevant documents up > at this location: https://www.tuhs.org/Governance/ This includes the > association rules and by-laws, list of members, the agendas and > minutes of all meetings, the treasurer's reports etc. > > The minutes of the recent AGM are at > http://www.tuhs.org/Governance/Agendas_and_Minutes/20260530-inaugural-agm > > So now the Unix Heritage Society (i.e. you, the people on the TUHS mailing > list) is supported by a legal entity (TUHSI, run by the TUHS team members) > to ensure that your donations will go where you want them to go. > > What happens next? First, we find our feet. We're planning to > upgrade the server infrastructure under the leadership of Dan Cross. > For you, this means one thing will change: minnie.tuhs.org will not go > away, but it will be the name of Warren's personal machine. There is > a redirector in place, but if you're used to using this name, please > choose to use www.tuhs.org (or just tuhs.org) instead. > > Every two months, Warren or David will e-mail the TUHS list with an update > on what funds have been spent where and the current balance of funds. > > You can find a FAQ about TUHSI at > https://www.tuhs.org/Governance/tuhsi_faq.html. If you have any other > questions, please e-mail them to the TUHS mailing list, tuhs at tuhs.org, so > we can answer them and/or discuss any arising issues/suggestions. From tuhs at tuhs.org Thu Jun 4 12:59:22 2026 From: tuhs at tuhs.org (Warren Toomey via TUHS) Date: Thu, 4 Jun 2026 12:59:22 +1000 Subject: [TUHS] President's Message: June 2026 Message-ID: First up, I want to say that it was a big decision for me to stop being the TUHS benevolent dictator and help set up a legal entity to look after TUHS's assets. Now that we have an incorporated association, TUHSI, the decision making and responsibility is now shared across all of the team members. Along with this is a promise to be transparent to you, the people who use the TUHS web site, the Unix Archive and the TUHS mailing list. I will strive, every month, to give you a wrap-up of what the TUHS team members have been doing. If I say "I", that's my personal opinion and not of the team. If I say "We", then this reflects the general team consensus. Now on to the actual report :-) Wow, so it's been a bit of a whirlwind since mid-April when I asked you for donations to help keep the TUHS server running, and you graciously gave way more than I needed in 24 hours. Thanks again. With the money sitting in the GoFundMe account, I realised that I couldn't just transfer it into my own bank account: that would allow me to go spend it on frivolous things and nobody would be wiser. I also realised, with my 60th birthday coming up, that it made sense to set up some form of official succession mechanism for the day when I am no longer able to look after TUHS. I discussed things with the TUHS team of volunteers, and I took the decision to set up a not-for-profit organisation, "The Unix Heritage Society, Inc.". The "Inc." here means that the organisation is officially registered in Victoria, Australia, and we must regularly report publicly on our operations and financial activities. Why Ausralia? I'm Australian and it was easier for me to set it up here. Why Victoria and not another state? Victoria allows non-residents to be public officers, whereas the other Australian states didn't. (I'll refer to The Unix Heritage Society, Inc." as TUHSI below). Thus, TUHSI achieves several objectives: + it legally ensures that your donations must be spent on the TUSHI purposes: to preserve and maintain historical UNIX artifacts, and to provide a forum for discussion of UNIX and its history; + it ensures transparency on the TUHSI operations and financial activities; + and it gives me a succession mechanism: I'm no longer a benevolent dictator and, when I'm no longer around, TUHSI will continue to exist and keep working on Unix's history. We just had the first TUHSI AGM a few days ago. You can find the agenda and minutes here: https://www.tuhs.org/Governance/Agendas_and_Minutes/20260530-inaugural-agm/ The most important action was to accept the nominations of the four public officers: + Warren Toomey as President + Clem Cole as Vice-President + Greg Lehey as Secretary + David Arnold as Treasurer I want to thank Clem, Greg and David for taking on these roles for the next year. You can find our legal roles and responsibilities in our Rules of Incorporation: https://www.tuhs.org/Governance/Rules/TUHSI_Rules.pdf We gave David Arnold the authority to set up a bank account for TUHSI, as your donations have been sitting in the GoFundMe account untouched since mid-April. More on this in a minute. Another AGM action item was to give Dan Cross the authority to work on the design and implementation of a new TUHS server infrastructure, with input from the TUHS team. The existing server is getting a bit outdated in terms of software and configuration, and I'm looking forward to a new system which is simpler to manage and which will have a smaller vulnerability surface. This was also the reason that I moved my personal stuff over to a separate server: the TUHS donations should not be spent on providing hosting for my own files and e-mails. At the AGM we discussed bringing in more team members to add to the existing twelve TUHS team members. Our overall decision was that we are still finding our feet as TUHSI, and we want to bed this new thing down first. That raises the question: who gets to be TUHSI members? As former benevolent dictator and now president, I took the decision that only the team of TUHS volunteers are the people who are members of the incorporated organisation. It means that we can run meetings with a handful of people, make decisions (mostly) quickly and get back to the volunteer work. The alternative would be to open TUHSI membership up to the general public. This would mean: + the Committee has to approve each new member, see Rule 11. We would probably be swamped with approvals. + We would have to deal with membership fees, see Rule 11(2). More work for the treasurer. + We would need to hold general meetings in real-time with dozens or hundreds of people in multiple locations, all trying to give their own opinion on how to do things, and then vote on motions. My decision might not be popular with some of you, but I believe that it is the best one to keep our volunteer work going with as little distraction as possible. Also at the AGM, I proposed a set of by-laws that would augment our rules of incorporation. I drafted most of these and the TUHS team gave valuable suggestions on the meaning and wording of all of them. They were accepted and you can read them here: https://www.tuhs.org/Governance/Rules/By-Laws.html You will note that there are no membership fees and that new volunteer members need to be approved by 3/4 of the existing membership. These rules are to ensure that we recruit volunteers who have a track record of good work and the existing team believe that they would make a good addition to the team. There are also some by-laws that make me somewhat special: my membership is permanent and I retain control over parts of the "tuhs.org" domain which I've traditionally used for personal activities. So these were the main outcomes of the AGM: public officers, by-laws, TUHSI members, work on obtaining a bank account and work on a new server infrastructure. Back to the bank account. Before the AGM I spent some time trying to figure out if we could set up business accounts with any of the Wise and Wise-like on-line groups. The basic answer is no: either they won't accept donations from GoFundMe or they don't want to deal with a not-for-profit organisation, or both the above. It seems likely that we might have to open an account with a more traditional bank. Hopefully we will have solved this by my next report! Apart from setting up TUHSI, there has been other work behind the scenes. Dan has taken the lead with the design of a new server infrastructure which will be more resilient that just the single virtual machine which we have at present. We will also host our own DNS zone rather that have our records hosted by a third party. In terms of deployment, the plan is to move the existing TUHS services over to the new system one at a time: static web pages, the wiki, the Unix Tree, then the mail system and the TUHS & COFF mailing lists. We will give you a heads-up when things are about to be migrated, and we are going to rely on you to tell us when things break :-) Also behind the scenes have been some actual TUHS volunteer work. There has been some reorganisation to the Distributions/UCB/ section of the Unix Archive at https://www.tuhs.org/Archive. We had some additions to the Unix Archive: + Distributions/USDL/Cloutier_USG_PG3 + Documentation/Languages/B_Language_Historic_Information + Documentation/Theses We have team members working on making some commercial releases of Unix publicly available, but this work is embryonic and I can't tell you the specific details as yet. The TUHS team have also discussed if we could leverage our new incorporated status to get us more legal protection in terms of intellectual property issues. For over 25 years, TUHS has effectively been a public museum of Unix software and artifacts. We have had many researchers, academic and otherwise, use our collection for their research work. It would be fantastic if, somehow, some of the Unix artifacts not covered by the Ancient Unix licence could be made available to researchers and/or to the general public under a legal framework. That about it for this, my first monthly report as TUHSI president. Please bear with us as we, this new organisation, find our feet. I look forward to reporting in with more results and work in progress in the next month. Cheers, Warren From tuhs at tuhs.org Sun Jun 7 11:53:01 2026 From: tuhs at tuhs.org (Briam R via TUHS) Date: Sat, 6 Jun 2026 21:53:01 -0400 Subject: [TUHS] Testing 1,2,3 Message-ID: <4B835086-4A8D-451C-9889-AD966E7A7E53@gmail.com> Just checking the list, various responses I’ve sent have not landed. — Briam R. ————————— Sent from my iPhone From tuhs at tuhs.org Sun Jun 7 12:05:50 2026 From: tuhs at tuhs.org (Warren Toomey via TUHS) Date: Sun, 07 Jun 2026 12:05:50 +1000 Subject: [TUHS] Testing 1,2,3 In-Reply-To: <4B835086-4A8D-451C-9889-AD966E7A7E53@gmail.com> References: <4B835086-4A8D-451C-9889-AD966E7A7E53@gmail.com> Message-ID: I saw it! Warren On 7 June 2026 11:53:01 am AEST, Briam R via TUHS wrote: >Just checking the list, various responses I’ve sent have not landed. > >— Briam R. >————————— >Sent from my iPhone -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. From tuhs at tuhs.org Sun Jun 7 12:33:42 2026 From: tuhs at tuhs.org (Greg 'groggy' Lehey via TUHS) Date: Sun, 7 Jun 2026 12:33:42 +1000 Subject: [TUHS] Testing 1,2,3 In-Reply-To: <4B835086-4A8D-451C-9889-AD966E7A7E53@gmail.com> References: <4B835086-4A8D-451C-9889-AD966E7A7E53@gmail.com> Message-ID: On Saturday, 6 June 2026 at 21:53:01 -0400, Briam R via TUHS wrote: > Just checking the list, various responses I’ve sent have not landed. As Warren has said, this one did. Did your previous messages have additional attachments? Postorius (our mail system) is rather fussy about that. If you find that your messages don't arrive, let one of us know and we'll follow up. Greg -- Sent from my desktop computer. Finger grog at lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From tuhs at tuhs.org Wed Jun 10 08:51:12 2026 From: tuhs at tuhs.org (Warren Toomey via TUHS) Date: Wed, 10 Jun 2026 08:51:12 +1000 Subject: [TUHS] C News on 2.11BSD: help! Message-ID: Hi all, I'm trying to bring C News up on 2.11BSD and I'm stuck! The symptom: I can post a news article on one machine and I see it transfer via UUCP over TCP to a second machine. I see it arrive in the X. uucp spool folder. Then it disappears before being put in the news spool area. I'm leaving what I've done here: https://minnie.tuhs.org/211BSD_Cnews/ with a bunch of notes. If anybody has some ideas, I'd love to hear them! Thanks :-) Warren From tuhs at tuhs.org Wed Jun 10 15:41:22 2026 From: tuhs at tuhs.org (Hauke Fath via TUHS) Date: Wed, 10 Jun 2026 07:41:22 +0200 Subject: [TUHS] C News on 2.11BSD: help! In-Reply-To: References: Message-ID: <20260610074122817860.fca6c04e@Espresso.Rhein-Neckar.DE> On Wed, 10 Jun 2026 08:51:12 +1000, Warren Toomey via TUHS wrote: > I'm trying to bring C News up on 2.11BSD and I'm stuck! > > The symptom: I can post a news article on one machine and I see it > transfer via UUCP over TCP to a second machine. I see it arrive in the > X. uucp spool folder. Then it disappears before being put in the news > spool area. That's unfriendly. Can you post an article locally, i.e. is this a general C News issue, or related to spool mechanics? I used to run C News on NetBSD until the time_t change to 64 bit which broke it. Fixing the package is still on the list, but halfway down... Good luck, Hauke -- Hauke Fath Linnéweg 7 64342 Seeheim-Jugenheim Germany From tuhs at tuhs.org Wed Jun 10 16:43:31 2026 From: tuhs at tuhs.org (Kevin Bowling via TUHS) Date: Tue, 9 Jun 2026 23:43:31 -0700 Subject: [TUHS] VAX System V Message-ID: I got a manual set for Digital VAX System V 3.2.1. It appears to be a descendent of AT&T's VAX port, but it was thoroughly extended with large system hardware support (including CI bus) and even sundries like X11R4. Compared to i.e. 3B2 System V which IMHO is pretty bare bones and even a little half baked. The manuals are actually pretty great. I'm not overly familiar with DEC but perusing history it seemed to be that Ultrix was always playing second fiddle to VMS. VAX System V seems like a "more serious" UNIX, it targets the large machines: VAX 11/780, 6000, 8000, 9000. Only in the 3.2.1 release did a MVII pop in. I don't think I've ever seen anything on this in the wild, the main customer appeared to be AT&T itself and the RBOCs. Information online is scare. Regards, Kevin From tuhs at tuhs.org Wed Jun 10 17:04:50 2026 From: tuhs at tuhs.org (Warren Toomey via TUHS) Date: Wed, 10 Jun 2026 17:04:50 +1000 Subject: [TUHS] C News on 2.11BSD: help! In-Reply-To: References: Message-ID: On Wed, Jun 10, 2026 at 08:51:12AM +1000, Warren Toomey via TUHS wrote: > Hi all, I'm trying to bring C News up on 2.11BSD and I'm stuck! My friend Steve Jenkin pointed me at https://github.com/jwbrase/CNews-PiDP-11 which is probably where I should have started, if I'd only known!! Thanks Steve :-) Warren From tuhs at tuhs.org Wed Jun 10 18:04:49 2026 From: tuhs at tuhs.org (Jonathan Gray via TUHS) Date: Wed, 10 Jun 2026 18:04:49 +1000 Subject: [TUHS] VAX System V In-Reply-To: References: Message-ID: On Tue, Jun 09, 2026 at 11:43:31PM -0700, Kevin Bowling via TUHS wrote: > I got a manual set for Digital VAX System V 3.2.1. It appears to be a > descendent of AT&T's VAX port, but it was thoroughly extended with > large system hardware support (including CI bus) and even sundries > like X11R4. Compared to i.e. 3B2 System V which IMHO is pretty bare > bones and even a little half baked. The manuals are actually pretty > great. > > I'm not overly familiar with DEC but perusing history it seemed to be > that Ultrix was always playing second fiddle to VMS. VAX System V > seems like a "more serious" UNIX, it targets the large machines: VAX > 11/780, 6000, 8000, 9000. Only in the 3.2.1 release did a MVII pop > in. > > I don't think I've ever seen anything on this in the wild, the main > customer appeared to be AT&T itself and the RBOCs. Information online > is scare. Discussions tend to mention Manalapan, New Jersey. https://www.tuhs.org/pipermail/tuhs/2004-October/004252.html https://groups.io/g/simh/message/1963 From tuhs at tuhs.org Wed Jun 10 20:43:08 2026 From: tuhs at tuhs.org (Brad Spencer via TUHS) Date: Wed, 10 Jun 2026 06:43:08 -0400 Subject: [TUHS] VAX System V In-Reply-To: (message from Kevin Bowling via TUHS on Tue, 9 Jun 2026 23:43:31 -0700) Message-ID: Kevin Bowling via TUHS writes: > I got a manual set for Digital VAX System V 3.2.1. It appears to be a > descendent of AT&T's VAX port, but it was thoroughly extended with > large system hardware support (including CI bus) and even sundries > like X11R4. Compared to i.e. 3B2 System V which IMHO is pretty bare > bones and even a little half baked. The manuals are actually pretty > great. > > I'm not overly familiar with DEC but perusing history it seemed to be > that Ultrix was always playing second fiddle to VMS. VAX System V > seems like a "more serious" UNIX, it targets the large machines: VAX > 11/780, 6000, 8000, 9000. Only in the 3.2.1 release did a MVII pop > in. > > I don't think I've ever seen anything on this in the wild, the main > customer appeared to be AT&T itself and the RBOCs. Information online > is scare. > > Regards, > Kevin When I was at AT&T / Lucent the product I worked on started out on the Vax running a port of System V from DEC. The department, if I remember correctly, had a number of the systems mentioned above. If I remember the story correctly, AT&T pushed for this with DEC because of the "Thou Shalt Run System V" command that came down inside of AT&T. I do know that when DEC proposed that the Alpha replace the Vax and that the Alpha would not officially run System V (it apparently ran System V unofficially inside of DEC), only OSF/1 (or was it Ultrix... don't remember), the department moved to drop DEC as a vendor. Of course, later in the Lucent days, that directive was more or less ignored. I also remember something someone said to me at the time about the Vax and operating systems, VMS was first with support inside of DEC, followed by Ultrix and then System V at a more distant third place. The department at AT&T I was in fixed a number of kernel and userland bugs for DEC. There was full access to the source code and there existed a kernel and userland build system that could pretty much recreate the system from source code. The product that I was working on ate an entire Vax. We actually created our own set of system tapes that contained the OS as we wanted it configured (the department forced, or at least tried to force, a specific and exact hardware configuration on the customer base) along with the product we were selling. The customers, be them RBOCs or someone outside of the US, would boot the tapes we sent (well, our installer would do that) and this would load the OS and the product in one pass. Much faster then the method used by DEC. -- Brad Spencer - brad at anduin.eldar.org From tuhs at tuhs.org Thu Jun 11 08:55:22 2026 From: tuhs at tuhs.org (Ron Natalie via TUHS) Date: Wed, 10 Jun 2026 22:55:22 +0000 Subject: [TUHS] VAX System V In-Reply-To: References: Message-ID: System V on the VAX was underwhelming. It lacked demand paging which all the BSD variants on the VAX already had four years or so before System V was released on the VAX. System V didn’t finally get real virtual memory until SysVR2.4. Armando Stetner from DEC brought a Vax to one of the UNIX conferences and had it in his room. He had to run cords to various other rooms to get enough power to run it. He made a presentation that for over ten years UNIX and DEC had been pretty much synonymous, not that DEC had noticed and announced the first UNIX license from DEC. He held up a license plate. They gave those plates away (still have mine). It was a few years before an official Ultrix release (4.2BSD based). Later marketing weenies issued new plates that said Ultrix, but they weren’t that interesting. ------ Original Message ------ >From "Kevin Bowling via TUHS" To "The Eunuchs Hysterical Society" Date 6/10/2026 2:43:31 AM Subject [TUHS] VAX System V >I got a manual set for Digital VAX System V 3.2.1. It appears to be a >descendent of AT&T's VAX port, but it was thoroughly extended with >large system hardware support (including CI bus) and even sundries >like X11R4. Compared to i.e. 3B2 System V which IMHO is pretty bare >bones and even a little half baked. The manuals are actually pretty >great. > >I'm not overly familiar with DEC but perusing history it seemed to be >that Ultrix was always playing second fiddle to VMS. VAX System V >seems like a "more serious" UNIX, it targets the large machines: VAX >11/780, 6000, 8000, 9000. Only in the 3.2.1 release did a MVII pop >in. > >I don't think I've ever seen anything on this in the wild, the main >customer appeared to be AT&T itself and the RBOCs. Information online >is scare. > >Regards, >Kevin From tuhs at tuhs.org Thu Jun 11 09:28:23 2026 From: tuhs at tuhs.org (Brad Spencer via TUHS) Date: Wed, 10 Jun 2026 19:28:23 -0400 Subject: [TUHS] VAX System V In-Reply-To: (message from Ron Natalie via TUHS on Wed, 10 Jun 2026 22:55:22 +0000) Message-ID: Ron Natalie via TUHS writes: > System V on the VAX was underwhelming. It lacked demand paging which > all the BSD variants on the VAX already had four years or so before > System V was released on the VAX. System V didn’t finally get real > virtual memory until SysVR2.4. > [snip] I wasn't privy to that particular problem, but I do remember that some earlier versions had poor quality SMP support and that messed with the product I worked on at AT&T with respect to performance. Like I mentioned the product I worked on ate a whole Vax and really needed multiple CPUs to work well. When they fixed SMP in later versions the situation improved for the product. -- Brad Spencer - brad at anduin.eldar.org From tuhs at tuhs.org Thu Jun 11 16:22:16 2026 From: tuhs at tuhs.org (Jonathan Gray via TUHS) Date: Thu, 11 Jun 2026 16:22:16 +1000 Subject: [TUHS] VAX System V In-Reply-To: References: Message-ID: On Wed, Jun 10, 2026 at 06:04:49PM +1000, Jonathan Gray via TUHS wrote: > On Tue, Jun 09, 2026 at 11:43:31PM -0700, Kevin Bowling via TUHS wrote: > > I got a manual set for Digital VAX System V 3.2.1. It appears to be a > > descendent of AT&T's VAX port, but it was thoroughly extended with > > large system hardware support (including CI bus) and even sundries > > like X11R4. Compared to i.e. 3B2 System V which IMHO is pretty bare > > bones and even a little half baked. The manuals are actually pretty > > great. > > > > I'm not overly familiar with DEC but perusing history it seemed to be > > that Ultrix was always playing second fiddle to VMS. VAX System V > > seems like a "more serious" UNIX, it targets the large machines: VAX > > 11/780, 6000, 8000, 9000. Only in the 3.2.1 release did a MVII pop > > in. > > > > I don't think I've ever seen anything on this in the wild, the main > > customer appeared to be AT&T itself and the RBOCs. Information online > > is scare. > > Discussions tend to mention Manalapan, New Jersey. > > https://www.tuhs.org/pipermail/tuhs/2004-October/004252.html > https://groups.io/g/simh/message/1963 Also discussed in an internal DEC video, uploaded to youtube by David Price (around 1:29:27). 1988-03-03 ULTRIX Strategy and Positioning -- DVN #056 https://www.youtube.com/watch?v=s0XikPpbMic&t=5367s "Ed Manning: We at this present time have some confusion in the field regarding exactly what our Unix products are. There is Ultrix, which is for the most part certainly what we've been talking about here today. Ultrix with SVID compliance on the System V side. But then there is this other product that exists, that people keep hearing about, and they keep calling me and asking about. What is this System V in New Jersey? Should I sell it? Do I need it? Is Ultrix really what we're selling? Don McInnis: The New Jersey System V effort, for people who aren't familiar with it. For years, AT&T has paid Digital Equipment to port their operating system, exactly, over to our processors. And they in turn use that on products that they build in the networking environment. Digital has recently made a decision internally, to make that available to other customers in the telecommunication industries. And even outside the telecommunication industries, to people who want what that product offers very specifically. There's a control process in place because we're not able to support many of those sites, even from a field delivery standpoint, even from a distribution standpoint. But for somebody who wants, identically, what System V is from AT&T and none of the value added that Digital provides on top of it, we'll make that available, if it's approved, to those customers." From tuhs at tuhs.org Fri Jun 12 08:29:38 2026 From: tuhs at tuhs.org (Clem Cole via TUHS) Date: Thu, 11 Jun 2026 18:29:38 -0400 Subject: [TUHS] VAX System V In-Reply-To: References: Message-ID: Note that I was the project leader for the last few Ultrix releases, as well as the architect of TruCluster FS and part of Tru64. [In fact, I had lunch yesterday with our old VP from those days]. First, be careful. The System V Vax systems were different from either Ultrix or Tru64. It was done by a DEC team in NJ with a lot of help from the Boston Office of Locus Computing Corp [where I was also the sr technologist for a few years before my later DEC time]. IIRC, the VAX System V 3.2.1 fully supported VM (early VAX releases did not, but by the V3 timeframe, the basic V3 kernel assumed VM hardware, and there would have been no reason not to use it on the Vax). That said, compared to any BSD release or Ultrix, by then *the whole system was fairly vanilla*, just as it was with SVR3 for the 3B20 (also vanilla). ISTR that, unlike Ultrix, even the development tool suite was AT&T's PCC3 at that point. So C and Fortran would not have been much to write about. Frankly, DEC's VAX11/C, VAX Fortran (and Pascal) were all much better compilers, but after the surgery it took to get them to work for Ultrix, I don't think DEC was interested in moving them again (I'm having lunch tomorrow with a number of the Technical Languages folks, and if any of the DEC tool chain was moved to System V they would know). I do remember that for VAX System V, there were some contractual extras, such as X11. But the networking stack was stream-based, not socket-based. I don't remember whether either IP/TCP or NFS was part of the contract, but they had been; I suspect they would have been Lachman's. System V was just too different from Ultrix (which was mostly BSD-like) to make sense. The DEC System V for Vax product was a pure System V code base with only extensions required by ATT. I'm not even sure anyone but AT&T or the RBOCs could order it. It was created to offload ATT’s Summit team (USG) after they wanted to concentrate on their own ISA, while still having many Vaxen running throughout the Bell System. This was really similar to the UNIX team that started in MK as part of the DEC Telephone Industries group (TIG) to support the PDP-11s and Vaxes that DEC's largest customer was buying. The team in MK was moved to the same building (on a different floor) as the VMS when Ultrix became a product. Note that LCC was the primary Ultrix support team towards the end, when the Unix folks started to concentrate on Alpha and became the Tru64 team, but DEC had a large installed base of Vaxen and MIPS systems (for instance, LCC did the MIP 4400 support and all the last Vax and MIPS releases). Certainly, in the TIG timeframe when they were in MK, the UNIX folks were a "redheaded stepchild," compared to VMS (or TOPS-20 at the time). So you are correct that *before **Tru64*, TIG and the original Ultrix teams were often pushed aside by VMS. But that really changed when DEC started to see the sales numbers and the complete industry switch off of proprietary to what was then called the "open systems" marketplace. Once UNIX was driving so much revenue, the UNIX folks (Ultrix) were able to drive the business. In fact, if you know the history of Windows/NT, it was originally called "Mica" and was developed by Cutler and team in Seattle. The whole idea was to switch to a single microkernel and then have the personalities of VMS or Ultrix layered on top, while allowing greater commonality across the layered products. I'll not comment much more than to say, as VMS was starting to be marginalized, Cutler was less than pleased. Eventually, he went to Microsoft†. By that time, the pecking order was Ultrix (later Tru64), VMS, and then the Summit folks. In fact, Alpha ran Ultrix before it ran anything else, and all the debugging was done there or later when OSF/1 was stable. VMS and NT4 were implemented on Alpha only after the core Unix ecosystems had stabilized [it probably helped that many of the old 36-bit folks had joined the Unix team, and there was definite animosity toward how VAX/VMS had shut out the 36-bit products]. There was never a reason to run System V on it, as AT&T and the RBOC had moved on to the different members of the 3B family or to Intel platforms. I'm not sure when the DEC Summit NY office closed, but at some point DEC tossed a bunch of the residual support contracts for AT&/RBOC to folks like Lcc. Clem † I'll add one more historical note, as a risk of diverting this thread a little, NT at Microsoft was originally NT OS/2. Mica/ney NT was designed as a microkernel, which is why Culture could quickly switch to a Windows personality when Microsoft and IBM divorced. On Wed, Jun 10, 2026 at 2:43 AM Kevin Bowling via TUHS wrote: > I got a manual set for Digital VAX System V 3.2.1. It appears to be a > descendent of AT&T's VAX port, but it was thoroughly extended with > large system hardware support (including CI bus) and even sundries > like X11R4. Compared to i.e. 3B2 System V which IMHO is pretty bare > bones and even a little half baked. The manuals are actually pretty > great. > > I'm not overly familiar with DEC but perusing history it seemed to be > that Ultrix was always playing second fiddle to VMS. VAX System V > seems like a "more serious" UNIX, it targets the large machines: VAX > 11/780, 6000, 8000, 9000. Only in the 3.2.1 release did a MVII pop > in. > > I don't think I've ever seen anything on this in the wild, the main > customer appeared to be AT&T itself and the RBOCs. Information online > is scare. > > Regards, > Kevin > From tuhs at tuhs.org Fri Jun 12 10:59:22 2026 From: tuhs at tuhs.org (James Frew via TUHS) Date: Thu, 11 Jun 2026 17:59:22 -0700 Subject: [TUHS] VAX System V In-Reply-To: References: Message-ID: <8cda4fae-1a3b-486f-9f27-032d54e4ac21@ucsb.edu> Still have mine, too. When he held up the plate, some wag (who? someone on this list, perhaps?) shouted, "Hey Armando, where'd you learn how to make those?" /Frew On 2026-06-10 3:55 PM, Ron Natalie via TUHS wrote: > > Armando Stetner from DEC ... announced the first UNIX license from DEC. > He held up a license plate.   They gave those plates away (still have > mine). From tuhs at tuhs.org Fri Jun 12 13:14:10 2026 From: tuhs at tuhs.org (Greg 'groggy' Lehey via TUHS) Date: Fri, 12 Jun 2026 13:14:10 +1000 Subject: [TUHS] VAX System V In-Reply-To: <8cda4fae-1a3b-486f-9f27-032d54e4ac21@ucsb.edu> References: <8cda4fae-1a3b-486f-9f27-032d54e4ac21@ucsb.edu> Message-ID: On Thursday, 11 June 2026 at 17:59:22 -0700, James Frew via TUHS wrote: > On 2026-06-10 3:55 PM, Ron Natalie via TUHS wrote: > >> Armando Stetner from DEC ... announced the first UNIX license from DEC. >> He held up a license plate.   They gave those plates away (still have >> mine). > > Still have mine, too. I picked up mine very late, at the 2001 USENIX ATC. It's not quite kosher: it's full of references to Tru64 and Compaq. Image is at http://www.lemis.com/grog/photos/Onephoto.php?image=/grog/Photos/20260612/UNIX-Live-free-or-die-2.jpeg&size=2 That seems to have been towards the end of the line for Tru64. Does anybody know how long Compaq continued making these “license” plates? Greg -- Sent from my desktop computer. Finger grog at lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From tuhs at tuhs.org Fri Jun 12 23:52:52 2026 From: tuhs at tuhs.org (Ron Natalie via TUHS) Date: Fri, 12 Jun 2026 13:52:52 +0000 Subject: [TUHS] VAX System V In-Reply-To: References: <8cda4fae-1a3b-486f-9f27-032d54e4ac21@ucsb.edu> Message-ID: To my knowledge, there were only two issues of licenses. The original Armando ones that say UNIX with Live Free or Die and Unix is a Trademark, and the later ULTRIX ones (I have them both). If there were others, I somehow missed them. Armando related a story that he had the actual NH UNIX vanity plate on the rear of his car and a DEC one on the front (complete with the license expiration tabs). The front one went missing for a while, and when he inquired, many people wrote to him saying they hadn’t seen it in various parts of the country remote from NH. I think he eventually got it back. Isn’t Armando kicking around here? From tuhs at tuhs.org Sat Jun 13 00:16:33 2026 From: tuhs at tuhs.org (Tom Lyon via TUHS) Date: Fri, 12 Jun 2026 07:16:33 -0700 Subject: [TUHS] VAX System V In-Reply-To: References: <8cda4fae-1a3b-486f-9f27-032d54e4ac21@ucsb.edu> Message-ID: Bill Shannon had the real New Hampshire UNIX plates at the time of moving to California/Sun in 1982. He upgraded to VMUNIX in California. Photo: https://photos.app.goo.gl/QSGYnuxhfvBk1ZUc9 But maybe after Armando. Or did Armando have the Massachusett plate? On Fri, Jun 12, 2026 at 7:02 AM Ron Natalie via TUHS wrote: > To my knowledge, there were only two issues of licenses. The original > Armando ones that say UNIX with Live Free or Die and Unix is a > Trademark, > and the later ULTRIX ones (I have them both). If there were others, I > somehow missed them. > > Armando related a story that he had the actual NH UNIX vanity plate on > the rear of his car and a DEC one on the front (complete with the > license expiration tabs). > The front one went missing for a while, and when he inquired, many > people wrote to him saying they hadn’t seen it in various parts of the > country remote from NH. > I think he eventually got it back. Isn’t Armando kicking around > here? > > From tuhs at tuhs.org Sat Jun 13 00:27:07 2026 From: tuhs at tuhs.org (Kevin Dunlap via TUHS) Date: Fri, 12 Jun 2026 07:27:07 -0700 Subject: [TUHS] VAX System V In-Reply-To: References: <8cda4fae-1a3b-486f-9f27-032d54e4ac21@ucsb.edu> Message-ID: Bill Shannon had NH Unix plate first. After Bill moved to CA, Armando got it. I believe Jon "Maddog" Hall now has it. -Kevin On Fri, Jun 12, 2026, 7:16 AM Tom Lyon via TUHS wrote: > Bill Shannon had the real New Hampshire UNIX plates at the time of moving > to California/Sun in 1982. He upgraded to VMUNIX in California. > Photo: https://photos.app.goo.gl/QSGYnuxhfvBk1ZUc9 > > But maybe after Armando. Or did Armando have the Massachusett plate? > > On Fri, Jun 12, 2026 at 7:02 AM Ron Natalie via TUHS > wrote: > > > To my knowledge, there were only two issues of licenses. The original > > Armando ones that say UNIX with Live Free or Die and Unix is a > > Trademark, > > and the later ULTRIX ones (I have them both). If there were others, I > > somehow missed them. > > > > Armando related a story that he had the actual NH UNIX vanity plate on > > the rear of his car and a DEC one on the front (complete with the > > license expiration tabs). > > The front one went missing for a while, and when he inquired, many > > people wrote to him saying they hadn’t seen it in various parts of the > > country remote from NH. > > I think he eventually got it back. Isn’t Armando kicking around > > here? > > > > > From tuhs at tuhs.org Sat Jun 13 01:00:18 2026 From: tuhs at tuhs.org (Clem Cole via TUHS) Date: Fri, 12 Jun 2026 11:00:18 -0400 Subject: [TUHS] VAX System V In-Reply-To: References: <8cda4fae-1a3b-486f-9f27-032d54e4ac21@ucsb.edu> Message-ID: I obtained (and still have) the the Mass plate about a year before Armand’s got the NH one. I I’ve had three. It has been on my Silver Capri, the Black Jetta, two different Blue Passats, a Silver Passat, my Blue A4 and since 2018, my Blue Model S. The original MA plate was green letters in white (which was similar to the NH plates in those days) and then the red and blue on white when the state reissued them sometime in the early 90s. When that one started to fade and thus that car not pass inspection, I had to get new ones. When Armando moved to CA, he transferred the NH plate to Jon Hall (who still has it along with the Linux plate). IIRC originally Joy had the CA plate on his red Ferrari (that ended up on an island in the Sun pond atone point). As Tom points out, Shannon got vmunix when he moved to CA. But I don’t know what happened to it after he died, just as the late Gobble had the Indiana plate and I don’t know what happened to it. When the Computer Museum was still in Boston, Armando, Shannon, George and I had talked to Gwen Bell about displaying them in some manner. I’m actually glad that never happened because so much the BCMs collection was lost when they closed and the parts weee moved to CA. WRT to the DEC plates, Armando’s version was the first issue. Over the course of a few years, DEC marketing had a number of reissues of the original and I don’t believe that they are distinct in any way from the first batch. After Compaq, they made some others which included things like the Tru64 such as Greg’s were. They also made some others plates such the Java plate. I used to have the original plate that Armando gave me (and I got Dennis to sign) as well as those two all hanging in my Intel office. I’ll also note that the first USENIX after the original issue where Armando announced the plates, Masscomp had “Unix Drivers Licenses” blanks printed on cardboard fan fold with printer holes. If you came to booth and enter your contact info, the team work print a customized license for you to take home. I think I still have handful of the blanks some where in a box if Masscomp stuff. Sent from a handheld expect more typos than usual On Fri, Jun 12, 2026 at 10:16 AM Tom Lyon via TUHS wrote: > Bill Shannon had the real New Hampshire UNIX plates at the time of moving > to California/Sun in 1982. He upgraded to VMUNIX in California. > Photo: https://photos.app.goo.gl/QSGYnuxhfvBk1ZUc9 > > But maybe after Armando. Or did Armando have the Massachusett plate? > > On Fri, Jun 12, 2026 at 7:02 AM Ron Natalie via TUHS > wrote: > > > To my knowledge, there were only two issues of licenses. The original > > Armando ones that say UNIX with Live Free or Die and Unix is a > > Trademark, > > and the later ULTRIX ones (I have them both). If there were others, I > > somehow missed them. > > > > Armando related a story that he had the actual NH UNIX vanity plate on > > the rear of his car and a DEC one on the front (complete with the > > license expiration tabs). > > The front one went missing for a while, and when he inquired, many > > people wrote to him saying they hadn’t seen it in various parts of the > > country remote from NH. > > I think he eventually got it back. Isn’t Armando kicking around > > here? > > > > >