OmniOS 151056 stable (OpenSource Solaris fork/ Unix)

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

gea

Well-Known Member
Dec 31, 2010
3,621
1,429
113
DE
OmniOS is known to be a ultra stable ZFS that is compatible to OpenZFS. The reason is that it includes new OpenZFS features only after additional tests to avoid the problem we have seen the last year in OpenZFS. Another unique selling point are SMB groups that can contain groups and the kernelbased SMB server with Windows ntfs alike ACL with Windows SID as extended ZFS attribute, no uid->SID mapping needed in Active Direcory to preserve ACL

Note that r151052 is now end-of-life. You should upgrade to r151054 or r151056 to stay on a supported track. r151054 is a long-term-supported (LTS) release with support until May 2028. Note that upgrading directly from r151052 to r151056 is not supported; you will need to update to r151054 along the way.


btw
You need a current napp-it se to support Perl 5.42
 
Last edited:

gea

Well-Known Member
Dec 31, 2010
3,621
1,429
113
DE
OmniOS r151056d (2025-11-26)

Weekly release for w/c 24th of November 2025.
This update requires a reboot

Security Fixes
Update Intel CPU microcode to 20251111.
Update AMD CPU microcode to 20251030.
Disable the faulty RDSEED instruction on vulnerable Zen5 processors.

Bug Fixes
Fix for a NFS client regression with macOS 14 server.
 
  • Like
Reactions: gb00s

gea

Well-Known Member
Dec 31, 2010
3,621
1,429
113
DE
OmniOS r151056k (2026-01-14)
Weekly release for w/c 12th of January 2026.

This update requires a reboot

Security Fixes

Curl updated to version 8.18.0.

The bhyve mouse driver could de-reference a NULL pointer in some circumstances.

Other Changes

SMB Active Directory joins now fall back to seting the machine password via LDAP if kerberos fails. Many AD sites block kerberos for this,
more Topicbox

NVMe devices used as a system boot device would previously end up with a single I/O queue, limiting performance.

NVMe devices could incorrectly return an error on queue saturation that is interpreted by ZFS as a device failure.

The IP Filter fragment cache table could become corrupt, resulting in a kernel panic.
 
Last edited: