OmniOS weekly releases for w/c 14th of June 2021 are now available.
We have backported a number of fixes and improvements to the r151038 LTS release this week as shown below.
The bhyve hypervisor and the bhyve branded zone have received several updates that enable running with fewer resources and fewer privileges than before.
bhyve VNC sessions are now named based on the underlying virtual machine name rather than always being called “bhyve”.
Additional network backends are available for bhyve, including an emulated
e1000 interface type.
SMB3 encryption no longer breaks MacOS Big Sur clients.
Fixes for kernel FPU use.
The ZFS ARC algorithm has been adjusted to restore memory pressure; see illumos issue 13766.
Several ZFS L2ARC fixes and improvements have been incorporated.
zdb command could crash when processing RAIDZ pools, this has been resolved.
segkpsize tunable can now be adjusted using the
eeprom command - see eeprom(1M).
Improvements to the native C++ and rust demangling library.
The CDP daemon (in.cdpd) now runs with reduced privileges;
zpool list -vp now shows parsable sizes in all fields.
nvmeadm now supports parsable output; see nvmeadm(1M)
profiles -l could crash when an LDAP backend was in use, this has been resolved.
For further details, please see https://omnios.org/releasenotes
Any problems or questions, please get in touch.
OmniOS weekly releases for w/c 18th of May 2021 are now available.
A problem that could result in a newly built non-global zone having no functioning system log service has been resolved.
If the global zone is using the rsyslog system logger, newly built non-global zones will now be configured to use the same system log service.
For further details, please see https://omnios.org/releasenotes
Any problems or questions, please get in touch.
The OmniOS Community Edition Association is proud to announce the general availability of the next stable and LTS version of OmniOS - r151038.
OmniOS is published according to a 6-month release cycle, with stable releases being supported for a year. However, as an LTS release, r151038 will be supported for three years, and the previous LTS release (r151030) now enters its last year of support.
The old stable r151034 release is now end-of-life and will receive no further updates; r151036 will be supported for a further six months.
Refer to the release schedule for further details and exact dates.
Direct upgrades to r151038 are supported from r151030, r151032, r151034 and r151036. Upgrades from earlier releases will need to be performed in stages as shown in the table on omnios.org/upgrade.
The highlights of this release include ZFS support for persistent layer 2 ARC, one-time boot environment activation, new pkg commands for managing removable packages and many improvements in the bhyve hypervisor.
There are many more changes and improvements in this release and those are detailed in the release notes, along with upgrade notes.
Since the start of OmniOS Community Edition project, we have predominantly announced our new releases via twitter. We are now also offering a newsletter with announcements of updates, bug fixes and new releases. You can subscribe here.
Have you ever wondered how OmniOS development gets financed? You may have noticed that there is no big company bankrolling it all. The way we keep afloat is by the companies who rely on OmniOS powered servers taking out support contracts for their hardware. How about you? Visit omnios.org/support for more details and to generate a quote. If you aren’t in a position to take a support contract, please consider becoming an OmniOS patron to help secure its future - omnios.org/patron.
About OmniOS Community Edition Association - this Swiss Association is responsible for the ongoing development and maintenance of OmniOS, having been established in Summer 2017 after OmniTI announced their withdrawal from the project.
OmniOSce Association Aarweg 17, 4600 Olten, Switzerland
As a kid, I listened to a lot of talk radio. This was in the 80s, before the internet — and before the AM dial became fringe. I have fond memories of falling asleep to the likes of Bruce Williams who just gave damned good, level-headed advice. It was, at essence, both optimistic and temperate: a cool head to help people work through a tough spot.
Nothing really replaced the call-in show: talk radio devolved into poisonous echo chambers, while social networking gave people other outlets (too many!) to have conversations. But these online conversations — the written word — lack something: Twitter’s tight form gives us the hot take, blogs (ahem!) give us the longer form, but it both cases, the conversations that result seem to either lose their sizzle or go thermonuclear. Video is really great for some stuff (I have spoken about the rise of video and the preservation of oral tradition in software engineering) — but the discussion quality there is even worse. (When did YouTube comments become such a hellhole?!) And of course, TikTok has given us social, short-form video, which can be very entertaining, but isn’t really designed to induce any meaningful discussion.
And of course, I love podcasts, and one of the reasons I was excited to start a company was to get an excuse to make the podcast that we ourselves always wanted. Podcasts are particularly great because you can do something else while listening to them: they fill in that time when you’re doing the dishes or picking up the kids or whatever. But podcasts obviously miss the interactivity entirely. (Or mostly: let us not so quickly forget TWiV reading my letter on-air!)
Into all of this, enter Clubhouse and the rise of social audio. I had immediate Bruce Williams flashbacks, and was excited to participate. But my choice of device makes me unwelcome in Clubhouse’s eyes: their lack of an Android app is clearly not a mere temporary gap, but rather a deliberate deprioritization. (I certainly honor a young company’s need to focus, but how else can one describe an exceedingly well-capitalized company adding in-app payments before addressing 75% of the market?!) To me, the deprioritization of Android reflects Clubhouse’s deeper problem: it is fundamentally elitist and exclusionary. Avid Clubhouse users may claim that this was not always so, but it says it right there on the tin: it is, at the end of the day, a clubhouse — not a cafe or a town square. I personally have no interest in participating in venues that deliberately limit the participants: I want to engage with the broadest possible cross-section, not some subset that has been manicured by circumstance or technology choice. (For this same reason, I do not give talks unless the talk will be recorded and made freely available.)
Given all of this, you can imagine my enthusiasm for Twitter Spaces: it captures the promise that I see in the medium — but addresses many of the problems with Clubhouse’s implementation. I have been participating in them for the past few weeks and (excitingly!) found last week that I have the ability to create Spaces. Here are my takeaways so far:
This is an even bigger deal than I thought it was. All of the strengths that I perceived in the medium seem to be even stronger than I thought they would be, and in particular — as with podcasts — I can have a conversation while I do something else. It is really nice to have social networking time after which one looks back at a clean kitchen or a prepared meal!
Spaces have broadened the people I follow. In every Space I have been in, I have come away following someone new. I find one of the most interesting aspects of Twitter to be able to be a part of conversations and social circles that broaden our perspectives (socially, technically, or otherwise) — and Spaces takes this to a new level: I find that I’m following people based on a comment that they make that I wouldn’t otherwise see in the din of my feed.
Spaces have felt very playful. In so many ways, this reminds me of early social networking circa 2003 — or of first getting online a decade prior. It just feels new, and fresh, and… fun! For example, I was in one space where a security researcher that I revere was with their crew, all trying to find ways to hack the captioning. (They made some interesting discoveries: because the captioning is done locally, they can actually reveal more about you than what you actually say!) I was more or less laughing the whole time; it was delightful.
The content is golden. If I have one complaint about Spaces, it’s that they aren’t publicly recorded — because there’s some great content here! I am hoping that this gets added over time (obviously, opt-in and clear to all participants!), because speaking personally, I want to go back and listen to an awesome Space that I might have missed — and I want others to be able to do the same with any Space that I host.
People have been really nice! Okay, this is a little one, but I think an essential one: in every Space I’ve been in, the people have just been incredibly friendly and welcoming. One of the challenges of the written word is that it’s too easy to be nasty: our mirror neurons don’t fire when our damage is inflicted at a distance. (Take it from the guy still trying to apologize for a Usenet comment from several decades ago!) While it’s still obviously very early for Twitter Spaces, being in a spoken conversation makes us much more predisposed to empathy — and I’m optimistic that the medium will retain the decency that we have lost elsewhere, allowing us a venue to listen to and learn from other perspectives. I also really like Twitter’s emphasis on safety — and I’m hopeful that the inevitable bad behavior that does crop up is taken care of pretty quickly.
Clubhouse is in trouble. I have been in a couple of Spaces where Clubhouse comes up (indeed, one of the Spaces I was in was a security researcher reporting how poorly Clubhouse handled a pretty serious safety issue that she had found), and in all of those conversations, the tenor is more or less the same: there was a brief moment last summer (especially, post George Floyd) when Clubhouse felt really important — profound, even — but their poor execution since has driven people away. In this regard, my early social networking metaphor may be apt in more ways than one: Clubhouse feels like Friendster. And just as Friendster hit on something huge (social networking!) for the wrong reasons (the founder’s desire to find dates!), Clubhouse’s focus on listening to famous people feels misplaced. (Speaking for myself, I am looking for conversations, not outtakes of Behind the Music.)
Hosting has been rewarding. So far, I have hosted one Space, convincing Adam to join me so I wouldn’t die alone. I think it’s fair to say that Adam was somewhat skeptical going in, but came out seeing promise in the medium. For example, one participant was dialing in from central Asia (where it was 4a!), and we ended up in a discussion on how insulated kids can become from the underlying mechanics of how computers actually work. He decribed that growing up needing to rely on second-hand computers was an essential part of his own technical education — that having less made him need to understand more. It was a moment that had everyone reflecting, and I’m honestly not sure how else that little interaction would have happened.
All in all, very positive and promising! Of course, there are still lots of things to stub your toe on; this is still new, after all, and lots of stuff doesn’t work quite right. And there’s also a lot to be figured out by those of us who will use the medium (reminder: retweets were invented by users, not by Twitter!). For my part from a hosting perspective, I am going to take some inspiration from talk radio and experiment with both regularity and time-bounds: Adam and I are going to host a Space again tomorrow (Monday) at 5p Pacific, keeping it again to about an hour. (We appear to be aided in our time bounds last week by a memory leak that caused my app to abort after about an hour!) So if you’re interested, drop on by — we’d love to hear what you have to say, which indeed is very much the whole point!
After another 6 months have passed we are proud to announce the release of our 2021.04 snapshot. The images are available at the usual place. As usual we have automatically received all updates that have been integrated into illumos-gate. This release’s most notably changes are
The following new packages have also been added:
The following packages have been removed:
The following packages have been updated or got security fixes: