Migration from SysVinit to systemd
The most fundamental change in OviOS v6 is the transition of the init system from SysVinit to systemd. This was not a decision made lightly — it reflects a clear and unavoidable shift in the Linux ecosystem.
Why we moved
SysVinit has been in maintenance-only mode for years. Distribution maintainers, package authors, and upstream projects have progressively dropped SysVinit support in favour of systemd's native unit files. Shipping a modern storage appliance on a legacy init system would have meant maintaining an ever-growing pile of compatibility shims — a cost that ultimately falls on you, the administrator.
Specifically: new versions of Samba, NFS utilities, iSCSI tools, and security daemons ship with systemd unit files only. Backporting SysVinit scripts for each new upstream release added fragility and delayed security updates. The move to systemd eliminates this entirely.
| Area | SysVinit (v5) | systemd (v6) |
|---|---|---|
| Service startup | Sequential shell scripts | Parallel, dependency-aware unit activation |
| Log management | Scattered text logs, manual rotation | Structured journald — query with journalctl
|
| Boot time | Longer due to sequential init | Noticeably faster on all hardware |
| Socket activation | Not available | Services start on first connection |
| Upstream compatibility | Declining — most packages drop init scripts | Full — all packages ship unit files natively |
| Service recovery | Manual restart scripts | Built-in restart policies, watchdog timers |
| Cockpit integration | Not possible | Native — Cockpit requires systemd |
Same simplicity, better plumbing. The service command, all
interactive wizards, and every OviOS management tool work exactly as before. The init change is
transparent — you will never interact with systemd unit files directly unless you choose to.
New Features & Capabilities
OviOS v6 introduces a range of new capabilities across monitoring, storage protocols, security, and deployment models.
OviOS Web Monitor
Browser-based dashboard delivering live pool health, ARC statistics, iSCSI session tracking, and network utilisation — plus one-click PDF storage reports.
Cockpit Integration
Full Cockpit web console available alongside the OviOS interface — providing OS-level visibility into processes, storage devices, networking, and logs via a polished browser UI.
S3-Compatible Object Storage
Deploy MinIO S3 endpoint on top of OviOS. Compatible with AWS SDK clients, rclone, and any S3-aware application — no external services required.
NVMe-oF (NVMe over Fabrics)
Present ZFS volumes as NVMe namespaces over TCP or RDMA fabrics. Sub-100µs latency for latency-sensitive workloads — a step beyond iSCSI for modern infrastructure.
auditd — Security Auditing
Linux Audit daemon integrated into the service stack. Log and monitor file access, configuration changes, and administrative actions for compliance and forensics.
Cloud OS — PXE / Network Boot
Run OviOS entirely from RAM via PXE network boot. No local system disk required — ideal for diskless rack deployments, cloud-adjacent infrastructure, and rapid provisioning at scale.
Linux Standard Base Compliance
Full LSB conformance across filesystem hierarchy, init integration, and packaging. Third-party tools and scripts built to LSB standards run without modification.
SMB3 Multichannel
Aggregate bandwidth across multiple NICs for Windows clients automatically. Enable with options smb.multichannel on.
Requires Windows 8+ clients.
Improved ZFS ARC Tuning
Per-pool sync mode, AutoTRIM, and ARC size controls now accessible via the options
command. Live tuning without reboots.
Linux Standard Base Compliance
OviOS v6 achieves full Linux Standard Base (LSB) conformance. This is a practical benefit for administrators integrating OviOS into broader infrastructure — monitoring agents, backup clients, and automation tools built to LSB standards now install and run without modification.
- Filesystem Hierarchy Standard (FHS)
- systemd-based init interface
- POSIX-compatible shell environment
- Standard PAM authentication stack
- journald / syslog integration
- NSS / LDAP / Kerberos conformance
- Standard cron / at scheduling
- LSB-compliant packaging metadata
- Standard network interface naming
- Predictable device naming (udev)
Upgraded Packages
All core storage, networking, and security components have been updated to their current stable releases, resolving numerous CVEs and bringing significant performance improvements.
| Package | v5 | v6 | Notable Changes |
|---|---|---|---|
| Linux Kernel | 6.8 LTS | 7.0 Stable | io_uring, NVMe-oF TCP, improved ZFS integration |
| OpenZFS | 2.4.0 | 2.4.2 | Block cloning, faster scrub, improved ARC eviction |
| Samba | 4.19.5 | 4.23.6 | SMB3 multichannel improvements, AD fixes |
| NFS-utils | 2.6.4 | 2.8.7 | NFSv4.2 xattr & copy_file_range support |
| tgt (iSCSI) | 1.0.82 | 1.0.97 | iSER transport, improved multi-session handling |
| OpenSSL | 3.2.1 | 3.6.2 | TLS 1.3 default, post-quantum readiness |
| OpenSSH | 9.7p1 | 10.3p1 | FIDO2 key support, improved host cert handling |
| smartmontools | 7.4 | 7.5 | NVMe health log, improved PCIe device support |
| Cockpit | — | 362+ | New in v6 — web-based OS console |
| auditd | — | 4.1.4 | New in v6 — Linux audit framework |
Upgrade & Compatibility Notes
In-place upgrade is not supported from v5 to v6. The init system change requires
a clean OS installation. Your storage data on ZFS pools is fully preserved — reinstall OviOS v6
on the system disk and run restore to rebuild all
iSCSI targets, LUN mappings, and share configurations automatically.
All existing configurations migrate without modification:
- ZFS pool data fully preserved
- iSCSI target & LUN mappings
- NFS and SMB share definitions
- Active Directory domain join
- Network interface configuration
- Bonding and VLAN setup
- Custom options (ARC, TRIM, ZIL)
- Snapshot schedules
- Replication tasks (retadm)
- OviOS wizard behaviour unchanged
The restore command reads OviOS metadata stored alongside your pool data and reconstructs the full configuration on the new OS install. A complete recovery from a fresh OS to fully operational storage typically takes under five minutes.
Everything you know still works
OviOS has always been built on a single principle: storage made simple. Every major operation has an interactive wizard. You follow prompts — you don't memorise commands or edit configuration files.
v6 does not change this. The pool, lun, target, vol, service, and options commands work identically
to v5. The ? command still
lists everything. ovios hc
still gives you an instant health overview. If you used v5, you are ready to use v6 today.
The new capabilities — web monitoring, Cockpit, S3, NVMe-oF, network boot — are additional layers available when you need them, not complexity imposed on workflows that were already working.