@gumnos

I mentioned Guckes's list not having Heirloom vi in that other thread.

I haven't thought about these in years, and they are an understandable additional blind spot in Guckes's list; but the MKS Toolkit had a vi, as did Interix.

https://www.mkssoftware.com/docs/man1/vi.1.asp

The :open test indicates that vi in the MKS Toolkit was actual Joy+Horton vi.

#Interix (at least according to an old Scott Mueller book) had both vi and nvi, so I wouldn't be surprised if that turned out to have been Bostic #nvi by two names.

As I recall, Central Point PC Tools, the Norton Utilities, and the Graham Utilities had text editors of varying degrees but did not have vi.

@cks
#vi #ComputerHistory #retrocomputing

ex, vi, view -- display-oriented interactive text editor

Linux 4.19 requires at least OpenSSL1.0.0. @ncommander decides to use OpenSSL3.0 branch.
So he tries to compile OpenSSL3.0 which needs ≥Perl5.10. #Interix has Perl5.6. So he decides to compile Perl5.10.
https://github.com/openssl/openssl/blob/OpenSSL_1_0_0-stable/Configure#L8C1-L8C15 <- "require 5.000;"

Other people would use OpenSSL1.0.0 instead of OpenSSL3.0.x and have probably less problems.

openssl/Configure at OpenSSL_1_0_0-stable · openssl/openssl

TLS/SSL and crypto library. Contribute to openssl/openssl development by creating an account on GitHub.

GitHub
Watching https://youtube.com/watch?v=JvAN3XtQo2E feels a bit like watching paint dry with a commentator.
#interix
LIVE: Struggling To Build The Linux Kernel on Windows XP due to MORE GCC issues

YouTube

#pkgsrc 2025Q1 will be the last branch to support several platforms listed below,
due to bitrot and lack of use. If you'd like to speak up, please use the
following threads:

#MirBSD https://mail-index.netbsd.org/tech-pkg/2025/03/12/msg030607.html
GNU/kFreeBSD https://mail-index.netbsd.org/tech-pkg/2025/03/11/msg030600.html
#Interix https://mail-index.netbsd.org/tech-pkg/2025/03/08/msg030572.html
BSD/OS https://mail-index.netbsd.org/tech-pkg/2025/03/17/msg030646.html

Removing MirBSD support

@whophd @ajsadauskas @Naich @ardi60
I've wondered about the history of the naming before [1], anyone knows why they shortened the subsystem name when they moved from UNIX to Linux?

[1] https://social.sdf.org/@njsg/112036879129063493

#Windows #Interix

njsg (@[email protected])

@[email protected] @[email protected] I was wondering if they had gotten too lazy when they "updated" the previous name or something, but it seems "Windows Subsystem for UNIX-based Applications" was officially part of "Windows Services for UNIX", so that kind of name already existed, even if the subsystem itself had a better name? (Now another question I'm curious about is: were these names already defined at the time of the Microsoft Korn Shell fiasco, or did these come later?)

SDF Social