@nhbriggs@mastodon.social

· 9mo ago

"Special Software Systems" is associated with the name "Phillip Dennis" -- also seems to be associated with an Atari BASIC compiler and a couple of other programs. I just looked up "Special Software Systems" in the US register of copyright holders and found an entry that includes -- "Party 1 Datasoft, Inc."
"Party 2 Phillip Dennis d.b.a. Special Software Systems."

1

2

0

1

Nick Briggs @nhbriggs@mastodon.social

· 18mo ago

@alanc@fosstodon.org Might I ask a favor? Is there a way to recover from having installed openssl-3 on a personal Solaris 11.4 system which seems to have broken everything relying on openssl 1.0.x -- including "sudo" and the "pkg" system? I haven't been able to find any discussion in the regular places.

2

4

6

0

Nick Briggs @nhbriggs@mastodon.social

· 22mo ago

Replying to

@sgharms @amoroso Point to note - the Unix haters handbook was only 3yrs after the 0.01 release of Linux. One thing Unix haters hated was not having access to all the source and being able to quickly and easily modify the OS they were running on.

2

0

Nick Briggs @nhbriggs@mastodon.social

· 22mo ago

Replying to

@amoroso @sgharms "In the old days" - Interlisp-D was Lisp all the way down, until you got to the microcode implementation of the Lisp instruction set. All features of an OS were present - file system, drivers for the hardware like disks, network stack, process management, everything -- was all running, debuggable, changeable in the same space as any other Lisp functions you wrote. "Teleraid" was like remote GDB - reach in and look at/modify a crashed machine, etc.

2

0

Nick Briggs @nhbriggs@mastodon.social

· 18mo ago

Replying to

@alanc@fosstodon.org Success. Since I still had an unprivileged session active (and nobody else did), got someone with role=root to share their password. Normally I can sudo for admin, but couldn't when libcrypto.so.1.0.0 was not locatable. I recompiled a 1.0.2t openssl, and with su thatuser and su root put libcrypto.so.1.0.0 into the expected place. Everything is back to normal. Now to figure how I screwed it up.

0

1

0

Nick Briggs @nhbriggs@mastodon.social

· 18mo ago

Replying to

@freya@chaosfem.tw @alanc@fosstodon.org LD_LIBRARY_PATH was my first thought - but I can't find a copy of libcrypto.so.1.0.0 (and 1.1.0 isn't compatible). Might be able to build one, though.

0

Nick Briggs @nhbriggs@mastodon.social

· 18mo ago

Replying to

@alanc@fosstodon.org Thanks. I think the previous BE will be the only option. I didn't intend to do a drop-in replacement. I think instead of setting mediators (apparently incorrectly, such that it immediately switched to 3) I should have removed the links that the Userland openssl3 was trying to make for /usr/lib/libcrypto.so that conflicted with the openssl-1.x. Yeah, I've borked the pkg system. Wish Oracle would release Userland compiled packages to those of us with personal machines.

0

2

0

Nick Briggs @nhbriggs@mastodon.social

· 18mo ago

Replying to

@alanc@fosstodon.org Good idea. There were a lot of things I couldn't do even with root, because some system python modules still depend on libcrypto 1.0.0 (ref: no recent updates to CBE) -- I think these are things I can't update because they're not part of userland. I tracked down what burned me - the openssl-3 package got updated, 16e0fabcd61e, "PSARC/2024/024 EOF OpenSSL 1.0.2, 35041813 EOF of openssl-1.0.2 library: Removal" and it replaced openssl@1.0.2 with openssl@3.0.16 removing libcrypto.1.0.0

0

1

0

Nick Briggs @nhbriggs@mastodon.social

· 18mo ago

Replying to

@alanc@fosstodon.org That will make a lot of things much easier! With only the last CBE, when I need to build a modern version of some open-source package, it's pretty error prone tracing back through the dependency chain and getting the right userland packages built and installed.

0

Nick Briggs @nhbriggs@mastodon.social

· 19mo ago

Replying to

@sgharms@techhub.social @amoroso@fosstodon.org *I* certainly expect it to work. I test any changes I make to Maiko on (now) FreeBSD 14.2, though it's via remote display to XQuartz on my Mac. I'm glad to hear it's working with a Wayland desktop (as Paolo notes, probably through XWayland)

0

2

0

Nick Briggs @nhbriggs@mastodon.social

· 19mo ago

Replying to

@sgharms@techhub.social @amoroso@fosstodon.org If it's going to be packaged as a port we should probably settle on a canonical location for at least the Maiko executables - without a lot of thought on the matter I'd probably say /usr/local/bin/ - it would be more Unixy to have ldex/ldesdl in libexec (if not found in the same place that lde/ldeinit was started from), but not clear it's worth it. BTW - does SDL on FreeBSD have a direct Wayland backend?

0

2

0