From gaf.linux at gmail.com Thu Apr 1 10:04:36 2021 From: gaf.linux at gmail.com (Jerry Feldman) Date: Thu, 1 Apr 2021 10:04:36 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos Message-ID: We remember the ongoing suit of SCO vs IBM which also was an attack on Linux. And we remember, The SCO Group which was originally the Linux distro Caldera. Many of us watched Groklaw religiously. I guess it is time for a new web site. The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos. https://go.theregister.com/feed/www.theregister.com/2021/03/31/ibm_redhat_xinuos/ -- Jerry Feldman Boston Linux and Unix http://www.blu.org PGP key id: 6F6BB6E7 PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 B B6E7 From bill.n1vux at gmail.com Thu Apr 1 10:50:10 2021 From: bill.n1vux at gmail.com (Bill Ricker) Date: Thu, 1 Apr 2021 10:50:10 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos In-Reply-To: References: Message-ID: Some of us are old enough to remember The Santa Cruz Operation was the preferred provider of legally licensed System III Unix or Xenix. (Before the Caldera folks did the reverse merge taking the good name.) We ran that on Onyx Z8000 for dev servers back when, and I had a client with System III on a 386 with two 8xSerial cards. Alas this story of the zombie arising yet again to eat more brainz is on too many sites to be April Fools but it should be! On Thu, Apr 1, 2021, 10:06 Jerry Feldman wrote: > We remember the ongoing suit of SCO vs IBM which also was an attack on > Linux. And we remember, The SCO Group which was originally the Linux distro > Caldera. Many of us watched Groklaw religiously. I guess it is time for a > new web site. > > > The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group > successor Xinuos. > > https://go.theregister.com/feed/www.theregister.com/2021/03/31/ibm_redhat_xinuos/ > > -- > Jerry Feldman > Boston Linux and Unix http://www.blu.org > PGP key id: 6F6BB6E7 > PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 > B B6E7 > _______________________________________________ > Discuss mailing list > Discuss at lists.blu.org > http://lists.blu.org/mailman/listinfo/discuss > From me at mattgillen.net Tue Apr 13 10:41:41 2021 From: me at mattgillen.net (Matthew Gillen) Date: Tue, 13 Apr 2021 10:41:41 -0400 Subject: [Discuss] resolved and DNSSEC Message-ID: <94530355-3ce8-600b-ed15-4e584da8caf1@mattgillen.net> I did a system upgrade the other day of my main home server/firewall, and for once the problem wasn't email, it was DNS. Fedora 33 moved to resolved, which does some interesting things compared to what I was used to. Amazingly, it maintained the basic contours of the system I had before: systemd-resolved was configured to only talk to the BIND server running on the loopback. I was impressed with that (and even though I've found /etc/systemd/resolved.conf and put the DNS entry as 127.0.0.1 to force it, it was actually doing the right thing before I did that, so I don't which config file it was looking at). The problem I had was a script I was running to check the DNSSEC status of a certain set of hosts that have historically had a lot of issues. So my cron job basically ran delv over a set of hostnames. delv is like 'dig' but for DNSSEC Followed advice of random blog that duckduckgo told me about and enabled DNSSEC for systemd-resolved (https://stanislas.blog/2018/06/enable-dnssec-support-in-systemd-resolve/ ) However, my 'delv' commands kept returning failure. Doing 'dig www.dnssec-failed.org' properly failed, so I know DNSSEC was working between my BIND instance and systemd-resolved, but delv apparently was not able to get signed results from the 127.0.0.53 server (which is what systemd-resolved presents to the rest of the system as the backward-compatible resolver). I solved the problem in the short term by just forcing the delv command to go straight to my BIND server: delv @127.0.0.1 But I liked the idea of the delv command exercising the exact path any other program on my system would use when doing DNS lookups. There is a pretty meaty ticket on this where the issue was closed but people are saying it still doesn't work https://github.com/systemd/systemd/issues/4621 FWIW, here's my config in case any one knows something I might be doing wrong (links 4-7 are just VLANs off physical Link 3; Link 2 is my ISP connection): --------------------- $ resolvectl Global Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=yes/supported resolv.conf mode: stub Current DNS Server: 127.0.0.1 DNS Servers: 127.0.0.1 Link 2 (enp1s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Current DNS Server: 127.0.0.1 DNS Servers: 127.0.0.1 Link 3 (enp3s5) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 4 (noext) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 5 (eap) Current Scopes: LLMNR/IPv4 Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 6 (kids) Current Scopes: LLMNR/IPv4 LLMNR/IPv6 Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported Link 7 (mgmt) Current Scopes: LLMNR/IPv4 Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=yes/supported --------------------- Thanks, Matt From me at mattgillen.net Tue Apr 13 20:41:50 2021 From: me at mattgillen.net (Matthew Gillen) Date: Tue, 13 Apr 2021 20:41:50 -0400 Subject: [Discuss] resolved and DNSSEC In-Reply-To: <20210413190737.GG13788@csail.mit.edu> References: <94530355-3ce8-600b-ed15-4e584da8caf1@mattgillen.net> <20210413162901.GD13788@csail.mit.edu> <33b74010-86c3-176e-519f-f38bc289feb0@mattgillen.net> <20210413180149.GF13788@csail.mit.edu> <61683ce0-303b-c3e5-6483-3a36d205f202@mattgillen.net> <20210413190737.GG13788@csail.mit.edu> Message-ID: <89a1911a-1a4b-6ec8-0022-9f935de0ec82@mattgillen.net> On 4/13/2021 3:07 PM, Gregory Galperin wrote: > On Tue, Apr 13, 2021 at 02:38:14PM -0400, Matthew Gillen wrote: >> So the issue seems to be that the systemd-resolved stub resolver doesn't >> support giving the full signed record to delv like the nss-resolver does. > > allegedly fixed in trunk 7 weeks ago: > https://github.com/systemd/systemd/issues/18714 > --grg Gregory's google-foo is better than mine...looks like I need to either wait for it to be backported or update to F34. Thanks, Matt From gaf.linux at gmail.com Tue Apr 20 18:14:49 2021 From: gaf.linux at gmail.com (Jerry Feldman) Date: Tue, 20 Apr 2021 18:14:49 -0400 Subject: [Discuss] Boston Linux VIRTUAL Meeting Wednesday, April 21, 2021 - Larks' Tongues in ASCII Message-ID: When:April 21, 2021 7:00PM EDT (6:30PM for Q&A) Topic: Larks' Tongues in ASCII Moderators: Kurt Keville,? Eliot Eshelman Location: Online: https://meet.jit.si/blu.org Live stream: https://youtu.be/V2oycK_1Wlc Summary: Updates Updates on HPC, Supercomputing, and Cluster Computing, plus B.U. Student Cluster Contest team Abstract: More details will be added later Bio Eliot's interests span from astrophysics to bacteriophages; high-performance computers to small spherical magnets. He's been an avid Linux geek (with a focus on HPC) for more than a decade. He works as Microway's Vice President of Strategic Accounts and HPC Initiatives. For further information and directions please consult the BLU Web site: http://www.blu.org -- Jerry Feldman > Boston Linux and Unix http://www.blu.org PGP key id: 6F6BB6E7 PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1? 3050 5715 B88D 6F6 B B6E7 _______________________________________________ Announce mailing list Announce at lists.blu.org http://lists.blu.org/mailman/listinfo/announce From gaf.linux at gmail.com Thu Apr 22 13:38:05 2021 From: gaf.linux at gmail.com (Jerry Feldman) Date: Thu, 22 Apr 2021 13:38:05 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos In-Reply-To: References: Message-ID: The first BCS mail server was xenix then upgraded to Sco Unix. I had SCO Unix on my home computer years ago. I think the server was an unused IBM PS2. -- Jerry Feldman Boston Linux and Unix http://www.blu.org PGP key id: 6F6BB6E7 PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 B B6E7 On Thu, Apr 1, 2021, 10:50 AM Bill Ricker wrote: > Some of us are old enough to remember The Santa Cruz Operation was the > preferred provider of legally licensed System III Unix or Xenix. (Before > the Caldera folks did the reverse merge taking the good name.) > > We ran that on Onyx Z8000 for dev servers back when, and I had a client > with System III on a 386 with two 8xSerial cards. > > Alas this story of the zombie arising yet again to eat more brainz is on > too many sites to be April Fools but it should be! > > On Thu, Apr 1, 2021, 10:06 Jerry Feldman wrote: > >> We remember the ongoing suit of SCO vs IBM which also was an attack on >> Linux. And we remember, The SCO Group which was originally the Linux >> distro >> Caldera. Many of us watched Groklaw religiously. I guess it is time for a >> new web site. >> >> >> The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO >> Group >> successor Xinuos. >> >> https://go.theregister.com/feed/www.theregister.com/2021/03/31/ibm_redhat_xinuos/ >> >> -- >> Jerry Feldman >> Boston Linux and Unix http://www.blu.org >> PGP key id: 6F6BB6E7 >> PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 >> B B6E7 >> _______________________________________________ >> Discuss mailing list >> Discuss at lists.blu.org >> http://lists.blu.org/mailman/listinfo/discuss >> > From epp at caramail.com Thu Apr 22 13:43:44 2021 From: epp at caramail.com (Edward) Date: Thu, 22 Apr 2021 13:43:44 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos In-Reply-To: References: Message-ID: Paging Groklaw... On 4/22/21 1:38 PM, Jerry Feldman wrote: > The first BCS mail server was xenix then upgraded to Sco Unix. I had SCO > Unix on my home computer years ago. I think the server was an unused IBM > PS2. > > -- > Jerry Feldman > Boston Linux and Unix http://www.blu.org > PGP key id: 6F6BB6E7 > PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 > B B6E7 > > On Thu, Apr 1, 2021, 10:50 AM Bill Ricker wrote: > >> Some of us are old enough to remember The Santa Cruz Operation was the >> preferred provider of legally licensed System III Unix or Xenix. (Before >> the Caldera folks did the reverse merge taking the good name.) >> >> We ran that on Onyx Z8000 for dev servers back when, and I had a client >> with System III on a 386 with two 8xSerial cards. >> >> Alas this story of the zombie arising yet again to eat more brainz is on >> too many sites to be April Fools but it should be! -- Linux. A Continual Learning Experience. From jabr at blu.org Thu Apr 22 16:15:17 2021 From: jabr at blu.org (John Abreau) Date: Thu, 22 Apr 2021 16:15:17 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos In-Reply-To: References: Message-ID: That's not entirely accurate. I attempted to build the first BCS mail server on a Xenix system, but never got it working, as Xenix was neither BSD nor System V, and the system we had didn't include any developer tools, so I was unable to compile and install sendmail. I eventually dropped Xenix and installed a DOS BBS called WAFFLE that exchanged email via UUCP and used Internet style RFC822 email addresses. The WAFFLE system was our first mail server. A year later, Mike DeGenio, the BCS Resource Center Manager, approved my request to use the NeXT machine in the BCS Resource Center to replace the WAFFLE system. Originally we had planned on running it as the mail server without removing it from use in the Resource Center, but then the leadership of the BCS NeXT SIG unilaterally decided to sabotage the project by locking me out of the system. To be fair, I had tried an experiment that broke the window system, and I was too exhausted after a very long day at the BCS office to diagnose the problem, so I figured I'd go home and fix it the next day when I was rested. I emailed the NeXT SIG's leaders before I headed home to let them know, and when I arrived the next day, I found they had sent me an email demanding that I leave it alone and let them fix it. I didn't want to step on any toes, so I left it to them. A few days later I discovered that they locked me out by changing the root password and adding a BIOS lockout to prevent single-user booting, but they didn't fix the window system. Mike DeGenio lost his temper after hearing about that, then he pulled the machine out of the Resource Center entirely and told me to just make it a dedicated mail server. Bypassing the BIOS lockout took about an hour of digging through USENET for FAQs about the NeXT machine. After that, since I wasn't overly tired, it took just a few minutes to figure out what went wrong and to restore the window system. In any case, the NeXT machine was the second BCS mail server, and a year later, after the BCS office moved from Cambridge to Waltham, we replaced the NeXT machine with a Slackware Linux mail server. On Thu, Apr 22, 2021 at 1:39 PM Jerry Feldman wrote: > The first BCS mail server was xenix then upgraded to Sco Unix. I had SCO > Unix on my home computer years ago. I think the server was an unused IBM > PS2. > > -- > Jerry Feldman > Boston Linux and Unix http://www.blu.org > PGP key id: 6F6BB6E7 > PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 > B B6E7 > > On Thu, Apr 1, 2021, 10:50 AM Bill Ricker wrote: > > > Some of us are old enough to remember The Santa Cruz Operation was the > > preferred provider of legally licensed System III Unix or Xenix. (Before > > the Caldera folks did the reverse merge taking the good name.) > > > > We ran that on Onyx Z8000 for dev servers back when, and I had a client > > with System III on a 386 with two 8xSerial cards. > > > > Alas this story of the zombie arising yet again to eat more brainz is on > > too many sites to be April Fools but it should be! > > > > On Thu, Apr 1, 2021, 10:06 Jerry Feldman wrote: > > > >> We remember the ongoing suit of SCO vs IBM which also was an attack on > >> Linux. And we remember, The SCO Group which was originally the Linux > >> distro > >> Caldera. Many of us watched Groklaw religiously. I guess it is time for > a > >> new web site. > >> > >> > >> The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO > >> Group > >> successor Xinuos. > >> > >> > https://go.theregister.com/feed/www.theregister.com/2021/03/31/ibm_redhat_xinuos/ > >> > >> -- > >> Jerry Feldman > >> Boston Linux and Unix http://www.blu.org > >> PGP key id: 6F6BB6E7 > >> PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 > >> B B6E7 > >> _______________________________________________ > >> Discuss mailing list > >> Discuss at lists.blu.org > >> http://lists.blu.org/mailman/listinfo/discuss > >> > > > _______________________________________________ > Discuss mailing list > Discuss at lists.blu.org > http://lists.blu.org/mailman/listinfo/discuss > -- John Abreau / Executive Director, Boston Linux & Unix Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6 PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6 From jabr at blu.org Thu Apr 22 16:20:58 2021 From: jabr at blu.org (John Abreau) Date: Thu, 22 Apr 2021 16:20:58 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos In-Reply-To: References: Message-ID: Now that I think about it, we also tried SCO Unix after trying Xenix; that may have been the one where I couldn't install sendmail. In any case, the DOS-based WAFFLE system was the system that we finally got working and that became the first BCS mail server. On Thu, Apr 22, 2021 at 4:15 PM John Abreau wrote: > That's not entirely accurate. I attempted to build the first BCS mail > server on a Xenix system, but never got it working, as Xenix was neither > BSD nor System V, and the system we had didn't include any developer tools, > so I was unable to compile and install sendmail. > > I eventually dropped Xenix and installed a DOS BBS called WAFFLE that > exchanged email via UUCP and used Internet style RFC822 email addresses. > The WAFFLE system was our first mail server. > > A year later, Mike DeGenio, the BCS Resource Center Manager, approved my > request to use the NeXT machine in the BCS Resource Center to replace the > WAFFLE system. Originally we had planned on running it as the mail server > without removing it from use in the Resource Center, but then the > leadership of the BCS NeXT SIG unilaterally decided to sabotage the project > by locking me out of the system. > > To be fair, I had tried an experiment that broke the window system, and I > was too exhausted after a very long day at the BCS office to diagnose the > problem, so I figured I'd go home and fix it the next day when I was > rested. I emailed the NeXT SIG's leaders before I headed home to let them > know, and when I arrived the next day, I found they had sent me an email > demanding that I leave it alone and let them fix it. I didn't want to step > on any toes, so I left it to them. A few days later I discovered that they > locked me out by changing the root password and adding a BIOS lockout to > prevent single-user booting, but they didn't fix the window system. > > Mike DeGenio lost his temper after hearing about that, then he pulled the > machine out of the Resource Center entirely and told me to just make it a > dedicated mail server. Bypassing the BIOS lockout took about an hour of > digging through USENET for FAQs about the NeXT machine. After that, since I > wasn't overly tired, it took just a few minutes to figure out what went > wrong and to restore the window system. > > In any case, the NeXT machine was the second BCS mail server, and a year > later, after the BCS office moved from Cambridge to Waltham, we replaced > the NeXT machine with a Slackware Linux mail server. > > > On Thu, Apr 22, 2021 at 1:39 PM Jerry Feldman wrote: > >> The first BCS mail server was xenix then upgraded to Sco Unix. I had SCO >> Unix on my home computer years ago. I think the server was an unused IBM >> PS2. >> >> -- >> Jerry Feldman >> Boston Linux and Unix http://www.blu.org >> PGP key id: 6F6BB6E7 >> PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 >> B B6E7 >> >> On Thu, Apr 1, 2021, 10:50 AM Bill Ricker wrote: >> >> > Some of us are old enough to remember The Santa Cruz Operation was the >> > preferred provider of legally licensed System III Unix or Xenix. (Before >> > the Caldera folks did the reverse merge taking the good name.) >> > >> > We ran that on Onyx Z8000 for dev servers back when, and I had a client >> > with System III on a 386 with two 8xSerial cards. >> > >> > Alas this story of the zombie arising yet again to eat more brainz is on >> > too many sites to be April Fools but it should be! >> > >> > On Thu, Apr 1, 2021, 10:06 Jerry Feldman wrote: >> > >> >> We remember the ongoing suit of SCO vs IBM which also was an attack on >> >> Linux. And we remember, The SCO Group which was originally the Linux >> >> distro >> >> Caldera. Many of us watched Groklaw religiously. I guess it is time >> for a >> >> new web site. >> >> >> >> >> >> The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO >> >> Group >> >> successor Xinuos. >> >> >> >> >> https://go.theregister.com/feed/www.theregister.com/2021/03/31/ibm_redhat_xinuos/ >> >> >> >> -- >> >> Jerry Feldman >> >> Boston Linux and Unix http://www.blu.org >> >> PGP key id: 6F6BB6E7 >> >> PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 >> >> B B6E7 >> >> _______________________________________________ >> >> Discuss mailing list >> >> Discuss at lists.blu.org >> >> http://lists.blu.org/mailman/listinfo/discuss >> >> >> > >> _______________________________________________ >> Discuss mailing list >> Discuss at lists.blu.org >> http://lists.blu.org/mailman/listinfo/discuss >> > > > -- > John Abreau / Executive Director, Boston Linux & Unix > Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6 > PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6 > > -- John Abreau / Executive Director, Boston Linux & Unix Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6 PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6 From gaf.linux at gmail.com Thu Apr 22 16:31:23 2021 From: gaf.linux at gmail.com (Jerry Feldman) Date: Thu, 22 Apr 2021 16:31:23 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos In-Reply-To: References: Message-ID: Xenix kept crashing. And SCO Unix was just too big for the PS2. But, JABR's waffle installation worked. If I recall, xenix was initially a Microsoft product before they spun it off to SCO. -- Jerry Feldman Boston Linux and Unix http://www.blu.org PGP key id: 6F6BB6E7 PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 B B6E7 On Thu, Apr 22, 2021, 4:21 PM John Abreau wrote: > Now that I think about it, we also tried SCO Unix after trying Xenix; that > may have been the one where I couldn't install sendmail. In any case, the > DOS-based WAFFLE system was the system that we finally got working and that > became the first BCS mail server. > > > On Thu, Apr 22, 2021 at 4:15 PM John Abreau wrote: > >> That's not entirely accurate. I attempted to build the first BCS mail >> server on a Xenix system, but never got it working, as Xenix was neither >> BSD nor System V, and the system we had didn't include any developer tools, >> so I was unable to compile and install sendmail. >> >> I eventually dropped Xenix and installed a DOS BBS called WAFFLE that >> exchanged email via UUCP and used Internet style RFC822 email addresses. >> The WAFFLE system was our first mail server. >> >> A year later, Mike DeGenio, the BCS Resource Center Manager, approved my >> request to use the NeXT machine in the BCS Resource Center to replace the >> WAFFLE system. Originally we had planned on running it as the mail server >> without removing it from use in the Resource Center, but then the >> leadership of the BCS NeXT SIG unilaterally decided to sabotage the project >> by locking me out of the system. >> >> To be fair, I had tried an experiment that broke the window system, and I >> was too exhausted after a very long day at the BCS office to diagnose the >> problem, so I figured I'd go home and fix it the next day when I was >> rested. I emailed the NeXT SIG's leaders before I headed home to let them >> know, and when I arrived the next day, I found they had sent me an email >> demanding that I leave it alone and let them fix it. I didn't want to step >> on any toes, so I left it to them. A few days later I discovered that they >> locked me out by changing the root password and adding a BIOS lockout to >> prevent single-user booting, but they didn't fix the window system. >> >> Mike DeGenio lost his temper after hearing about that, then he pulled the >> machine out of the Resource Center entirely and told me to just make it a >> dedicated mail server. Bypassing the BIOS lockout took about an hour of >> digging through USENET for FAQs about the NeXT machine. After that, since I >> wasn't overly tired, it took just a few minutes to figure out what went >> wrong and to restore the window system. >> >> In any case, the NeXT machine was the second BCS mail server, and a year >> later, after the BCS office moved from Cambridge to Waltham, we replaced >> the NeXT machine with a Slackware Linux mail server. >> >> >> On Thu, Apr 22, 2021 at 1:39 PM Jerry Feldman >> wrote: >> >>> The first BCS mail server was xenix then upgraded to Sco Unix. I had SCO >>> Unix on my home computer years ago. I think the server was an unused IBM >>> PS2. >>> >>> -- >>> Jerry Feldman >>> Boston Linux and Unix http://www.blu.org >>> PGP key id: 6F6BB6E7 >>> PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 >>> B B6E7 >>> >>> On Thu, Apr 1, 2021, 10:50 AM Bill Ricker wrote: >>> >>> > Some of us are old enough to remember The Santa Cruz Operation was the >>> > preferred provider of legally licensed System III Unix or Xenix. >>> (Before >>> > the Caldera folks did the reverse merge taking the good name.) >>> > >>> > We ran that on Onyx Z8000 for dev servers back when, and I had a client >>> > with System III on a 386 with two 8xSerial cards. >>> > >>> > Alas this story of the zombie arising yet again to eat more brainz is >>> on >>> > too many sites to be April Fools but it should be! >>> > >>> > On Thu, Apr 1, 2021, 10:06 Jerry Feldman wrote: >>> > >>> >> We remember the ongoing suit of SCO vs IBM which also was an attack on >>> >> Linux. And we remember, The SCO Group which was originally the Linux >>> >> distro >>> >> Caldera. Many of us watched Groklaw religiously. I guess it is time >>> for a >>> >> new web site. >>> >> >>> >> >>> >> The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO >>> >> Group >>> >> successor Xinuos. >>> >> >>> >> >>> https://go.theregister.com/feed/www.theregister.com/2021/03/31/ibm_redhat_xinuos/ >>> >> >>> >> -- >>> >> Jerry Feldman >>> >> Boston Linux and Unix http://www.blu.org >>> >> PGP key id: 6F6BB6E7 >>> >> PGP Key fingerprint: 0EDC 2FF5 53A6 8EED 84D1 3050 5715 B88D 6F6 >>> >> B B6E7 >>> >> _______________________________________________ >>> >> Discuss mailing list >>> >> Discuss at lists.blu.org >>> >> http://lists.blu.org/mailman/listinfo/discuss >>> >> >>> > >>> _______________________________________________ >>> Discuss mailing list >>> Discuss at lists.blu.org >>> http://lists.blu.org/mailman/listinfo/discuss >>> >> >> >> -- >> John Abreau / Executive Director, Boston Linux & Unix >> Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6 >> PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6 >> >> > > -- > John Abreau / Executive Director, Boston Linux & Unix > Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0x920063C6 > PGP-Key-Fingerprint A5AD 6BE1 FEFE 8E4F 5C23 C2D0 E885 E17C 9200 63C6 > > From gruntly at gmail.com Thu Apr 22 19:46:58 2021 From: gruntly at gmail.com (gruntly at gmail.com) Date: Thu, 22 Apr 2021 19:46:58 -0400 Subject: [Discuss] The Register: IBM, Red Hat face copyright, antitrust lawsuit from SCO Group successor Xinuos In-Reply-To: References: Message-ID: On Thu, Apr 22, 2021 at 4:18 PM John Abreau wrote: > I eventually dropped Xenix and installed a DOS BBS called WAFFLE that > exchanged email via UUCP and used Internet style RFC822 email addresses. > The WAFFLE system was our first mail server. I remember WAFFLE! Loved it. My first introduction to the architecture of email and Usenet News. Couldn't help learning a lot of stuff that came in handy when I encountered Unix soon after. Never had much interest in the whole bulletin-board stuff. But WAFFLE (and my trusty Telebit Worldblazer modem) served me email and News for many years. Thanks for the memories! Theodore Ruegsegger From richard.pieri at gmail.com Thu Apr 22 20:19:26 2021 From: richard.pieri at gmail.com (Rich Pieri) Date: Thu, 22 Apr 2021 20:19:26 -0400 Subject: [Discuss] GUI apps in WSL 2 Message-ID: <6082128f.1c69fb81.67a5d.4d39@mx.google.com> It exists: https://devblogs.microsoft.com/commandline/the-initial-preview-of-gui-app-support-is-now-available-for-the-windows-subsystem-for-linux-2/ -- Rich Pieri From david at thekramers.net Sat Apr 24 02:51:36 2021 From: david at thekramers.net (David Kramer) Date: Sat, 24 Apr 2021 02:51:36 -0400 Subject: [Discuss] GUI apps in WSL 2 In-Reply-To: <6082128f.1c69fb81.67a5d.4d39@mx.google.com> References: <6082128f.1c69fb81.67a5d.4d39@mx.google.com> Message-ID: <9af847e6-c5e8-16de-4918-429bca85d65f@thekramers.net> I saw this yesterday.? I'm curious to play with it, but I really don't have much practical use for it.? Not clear to me whether it's just a Linux VM. On 4/22/21 8:19 PM, Rich Pieri wrote: > It exists: > > https://devblogs.microsoft.com/commandline/the-initial-preview-of-gui-app-support-is-now-available-for-the-windows-subsystem-for-linux-2/ > From bill.n1vux at gmail.com Sat Apr 24 13:34:18 2021 From: bill.n1vux at gmail.com (Bill Ricker) Date: Sat, 24 Apr 2021 13:34:18 -0400 Subject: [Discuss] GUI apps in WSL 2 In-Reply-To: <9af847e6-c5e8-16de-4918-429bca85d65f@thekramers.net> References: <6082128f.1c69fb81.67a5d.4d39@mx.google.com> <9af847e6-c5e8-16de-4918-429bca85d65f@thekramers.net> Message-ID: This confuses me, because a Linux c++ Dev I know said he had tested his GUI app running on WSL last year. (Mike C. of Fotoxx, the intentional photo editor. ) I'd have to read closely to see what's different now. From richard.pieri at gmail.com Sat Apr 24 13:59:55 2021 From: richard.pieri at gmail.com (Rich Pieri) Date: Sat, 24 Apr 2021 13:59:55 -0400 Subject: [Discuss] GUI apps in WSL 2 In-Reply-To: References: <6082128f.1c69fb81.67a5d.4d39@mx.google.com> <9af847e6-c5e8-16de-4918-429bca85d65f@thekramers.net> Message-ID: <60845c9c.1c69fb81.64560.9c71@mx.google.com> On Sat, 24 Apr 2021 13:34:18 -0400 Bill Ricker wrote: > I'd have to read closely to see what's different now. What's different in a nutshell is that the upcoming WSL 2 kernel VM includes the XWayland server, the Weston stack, Pulse Audio, and an RDP server to connect these to the Windows desktop. Full OpenGL acceleration, full audio I/O. -- Rich Pieri From bill.n1vux at gmail.com Sat Apr 24 14:14:20 2021 From: bill.n1vux at gmail.com (Bill Ricker) Date: Sat, 24 Apr 2021 14:14:20 -0400 Subject: [Discuss] GUI apps in WSL 2 In-Reply-To: <60845c9c.1c69fb81.64560.9c71@mx.google.com> References: <6082128f.1c69fb81.67a5d.4d39@mx.google.com> <9af847e6-c5e8-16de-4918-429bca85d65f@thekramers.net> <60845c9c.1c69fb81.64560.9c71@mx.google.com> Message-ID: On Sat, Apr 24, 2021 at 2:01 PM Rich Pieri wrote: > On Sat, 24 Apr 2021 13:34:18 -0400 > Bill Ricker wrote: > > > I'd have to read closely to see what's different now. > > What's different in a nutshell is that the upcoming WSL 2 kernel VM > includes the XWayland server, the Weston stack, Pulse Audio, and an RDP > server to connect these to the Windows desktop. Full OpenGL > acceleration, full audio I/O. Ahh. So makes it easier for most apps to run as if native. Mike did it the hard way. Thanks. From david at thekramers.net Thu Apr 29 21:57:11 2021 From: david at thekramers.net (David Kramer) Date: Thu, 29 Apr 2021 21:57:11 -0400 Subject: [Discuss] Flashback humor: Shouting in the Datacenter Message-ID: https://www.youtube.com/watch?v=tDacjrSCeq4