Upgrades to Tribblix m35 on SPARC now available, bringing gcc10 to the party. This is a synthetic release, with updated applications atop m34 as the underlying OS.
https://www.tribblix.org/relnotes.html#m35-sparc
#tribblix #illumos #sparc
Remote
Peter Tribble
@ptribble@mastodon.illumos.cafe
mastodon 4.7.3Creator of Tribblix, contributor to illumos, maintainer of the Solaris/illumos/sparc OpenJDK port, was a Solaris sysadmin and member of the OpenSolaris Governing Board
122 Followers
28 Following
17 Posts
Joined August 18, 2025
Just got a refurbed Dell Optiplex 5050, just to get something a bit more modern, and with more storage and RAM. OK, so it's a bit old, but the i7-7700 - like the i7-3770 and i7-4790 before it - is more than adequate.
As expected, Tribblix installed flawlessly in a matter of seconds. And the graphics (the built in HD630) appears to work straight off.
All I now have to do is copy all the data across.
Tribblix and OmniTribblix m41 images suitable for running Droplets on Digital Ocean are now available:
https://www.tribblix.org/digitalocean.html
News for Tribblix on SPARC - upgrades to new m34 release now available.
https://www.tribblix.org/relnotes.html#m34-sparc
No ISO image yet for this release, but I am planning to create one this time.
OK, now is as good a time as any.
Freezing the Tribblix repos and cutting development across to the next release.
(The next release isn't imminent, there's a lot of changes incoming.)
Tribblix for SPARC m34 ISO image:
https://www.tribblix.org/download.html#sparc
(It ought to work, but I don't happen to have a spare machine or LDOM to test it right now. I know m34 in general works, because I've upgraded to it, but haven't explicitly tested the ISO.)
Version 1 of the AWS CLI is coming up on end of support, so we're supposed to move to AWSCLIv2. Sadly it's no longer pure python, but uses the AWS CRT underneath. With a little bit of (decidedly non-trivial) effort I've managed to persuade it to build on illumos, and verified that simple queries of EC2 and S3 work.
(This is one of the things that prompted my earlier comment about just packaging up a whole venv.)
Changes in Tribblix m39:
ISO images for Tribblix m39 available for download:
Replying to
Interesting. Radicle builds cleanly on Tribblix, and initial testing shows it to work as advertised. Need to find some time for a proper investigation.
Observations on Tribblix m39.
https://ptribble.blogspot.com/2026/03/observations-on-tribblix-m39.html
OK, that's my primary and backup home desktops running Tribblix m39 (the backup machine runs OmniTribblix). Onwards!
I've actually been running a mishmash of m38 and m39 for the past couple of weeks, getting the new release built and tested. Which means I end up being well ahead of the repos, and have to be careful not to accidentally "update" anything which would roll things back and break a bunch of packages. But now I'm back in regular supported territory again.
Replying to
@stefano I got loads of those scams for my company. I'm not sure why anyone would want to distribute Peter Tribble in China!
While it's a long way in the future for Tribblix (where I keep invoking laziness as an excuse for not updating from gcc10 to gcc14), an interesting Solaris/illumos change for gcc16:
To handle python modules that have odd or incompatible dependencies, I'm planning on just packaging a whole python venv and be done with it. It's just vendored dependencies by another means.
Idly musing as to whether I should give each Tribblix release a codename.
It's not long before I reach milestone 42, after all, which would have an obvious moniker.