OmniOS 151054 long term 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,599
1,420
113
DE

OmniOS is a Unix OS based on Illumos, the parent of OpenZFS. It is a very conservative ZFS distribution with a strong focus on stability without very newest critical features like raid-z expansion or fast dedup. Main selling point beside stabilty is the kernelbased multithreaded SMB server due its unique integration in ZFS with Windows SID as security reference for ntfs alike ACL instead simple uid/gid numbers what avoids complicated mappings, lokal Windows compatible SMB groups. Setup is ultra easy, just set smbshare of a ZFS filesystem to on and set ACL via Windows.

To update to a newer release, you must switch the publisher setting to the newer release.
A 'pkg update' initiates then a release update. Without a publisher switch, a pkg updates initiates an update to the newest state of the same release.

Note that r151050 is now end-of-life. You should switch to r151054lts or r151052 to stay on a supported track. r151054 is an LTS release with support until May 2028, and r151052 is a stable release with support until Nov 2025.

Update older releases in steps over last lts editions.
 
  • Like
Reactions: liv3010m

gea

Well-Known Member
Dec 31, 2010
3,599
1,420
113
DE
OmniOS r151054r (2025-09-04)

Weekly release for w/c 1st of September 2025

This update requires a reboot
Changes
  • SMB failed to authenticate to Windows Server 2025.
  • Systems which map the linear framebuffer above 32-bits caused dboot to overwrite arbitrary memory, often resulting in a system which did not boot.
  • The rge driver could access device statistics before the chip was set up.
  • The rge driver would mistakenly bind to a Realtek BMC device.
 

MarieKBaker

New Member
Dec 27, 2025
1
0
1
OmniOS r151054r (2025-09-04)

Weekly release for w/c 1st of September 2025



Changes
  • SMB failed to authenticate to Windows Server 2025.
  • Systems which map the linear framebuffer above 32-bits caused dboot to overwrite arbitrary memory, often resulting in a system which did not boot.
  • The rge driver could access device statistics before the chip was set up.
  • The rge driver would mistakenly bind to a Realtek BMC device. geometry dash
Thank you for sharing
 
Last edited: