Hubbry Logo
TrueOSTrueOSMain
Open search
TrueOS
Community hub
TrueOS
logo
8 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
TrueOS
TrueOS
TrueOS
View on Wikipedia
from Wikipedia
TrueOS
Lumina desktop running on TrueOS
DeveloperiXsystems
OS familyUnix-like
Working stateDiscontinued
Source modelOpen source
Initial release2006; 19 years ago (2006)
Latest release
  • Rolling release (UNSTABLE), based on FreeBSD-CURRENT
  • Long-term support (STABLE) every 0.5 years, based on FreeBSD-STABLE
    • 18.12[1] / 15 December 2018; 6 years ago (2018-12-15)
Package manager
Supported platforms
Kernel typeMonolithic (FreeBSD)
Default
user interface		Lumina
LicenseBSD
Official websitetrueos.org

TrueOS (formerly PC-BSD or PCBSD) is a discontinued[3] Unix-like, server-oriented operating system built upon the most recent releases of FreeBSD-CURRENT.[4]

Up to 2018 it aimed to be easy to install by using a graphical installation program, and easy and ready-to-use immediately by providing KDE SC, Lumina, LXDE, MATE, or Xfce[5] as the desktop environment. In June 2018 the developers announced that since TrueOS had become the core OS to provide a basis for other projects, the graphical installer had been removed.[6] Graphical end-user-oriented OSes formerly based on TrueOS were GhostBSD and Trident.[7] TrueOS provided official binary Nvidia and Intel drivers for hardware acceleration and an optional 3D desktop interface through KWin, and Wine is ready-to-use for running Microsoft Windows software. TrueOS was also able to run Linux software[8] in addition to FreeBSD Ports collection and it had its own .txz package manager. TrueOS supported OpenZFS and the installer offered disk encryption with geli.

Development of TrueOS ended in 2020.[3]

History

[edit]

TrueOS was founded by FreeBSD professional Kris Moore in early 2005 as PC-BSD. In August 2006 it was voted the most beginner-friendly operating system by OSWeekly.com.[9]

The first beta of the PC-BSD consisted of only a GUI installer to get the user up and running with a FreeBSD 6 system with KDE3 pre-configured. This was a major innovation for the time as anyone wishing to install FreeBSD would have to manually tweak and run through a text installer. Kris Moore's goal was to make FreeBSD easy for everyone to use on the desktop and has since diverged even more in the direction of usability by including additional GUI administration tools and .pbi application installers. PC-BSD's application installer management involved a different approach to installing software than many other Unix-like operating systems, up to and including version 8.2, by means of the pbiDIR website.[10] Instead of using the FreeBSD Ports tree directly (although it remained available), PC-BSD used files with the .pbi filename extension (Push Button Installer) which, when double-clicked, brought up an installation wizard program. An autobuild system tracked the FreeBSD ports collection and generated new .pbi files daily. All software packages and dependencies were installed from inside of the .pbi files into their own self-contained directories in /Programs. This convention was aimed to decrease confusion about where binary programs reside, and to remove the possibility of a package breaking if system libraries are upgraded or changed, and to prevent dependency hell.

On October 10, 2006, PC-BSD was acquired by enterprise hardware provider iXsystems.[11][12] iXsystems employed Kris Moore as a full-time developer and leader of the project. In November 2007, iXsystems entered into a distribution agreement with Fry's Electronics whereby Fry's Electronics stores nationwide carry boxed copies of PC-BSD version 1.4 (Da Vinci Edition).[13] In January 2008, iXsystems entered into a similar agreement with Micro Center.[14]

On September 1, 2016, the PC-BSD team announced that the name of the operating system would change to TrueOS.[4] Along with the rebranding, the project also became a rolling release distribution, based on the FreeBSD-CURRENT branch.[15]

On November 15, 2016, TrueOS began the transition from FreeBSD's rc.d to OpenRC as the default init system. Apart from Gentoo/Alt, where OpenRC was initially developed, this is the only other major BSD based operating system using OpenRC.

In July 2018, TrueOS announced that they would spin off the desktop edition into a separate project named Project Trident.[16][17]

Development of TrueOS ended in 2020 and the developers recommended users move to other BSD-based operating systems.[3]

Release history

[edit]
Version Release date FreeBSD codebase
1.0[18] April 29, 2006 6.0
1.1 May 29, 2006 6.1
1.2 July 12, 2006 6.1
1.3[19] December 31, 2006 6.1
1.4[20] September 24, 2007 6.2-STABLE
1.4.1.x Various 6.3-PRERELEASE
1.5[21] March 12, 2008 6.3-STABLE
1.5.1 April 23, 2008 6.3-STABLE
7.0[22] September 16, 2008 7.0-STABLE
7.0.1 October 17, 2008 7.0-STABLE
7.0.2 December 10, 2008 7.1-PRERELEASE
7.1[23][24] April 10, 2009 7.2-PRERELEASE
7.1.1 July 6, 2009 7.2-STABLE
8.0[25][26] February 23, 2010 8.0-RELEASE-P2
8.1[27] July 21, 2010 8.1-RELEASE
8.2[28] February 24, 2011 8.2
9.0[29][30] January 13, 2012 9.0[31]
9.1[32] December 18, 2012 9.1[33]
9.2[34] October 7, 2013 9.2-CURRENT[35]
10.0[36][37] January 29, 2014 10.0[38]
10.1[39] November 14, 2014 10.1[40]
10.2 August 21, 2015 10.2[41]
10.3 April 4, 2016 10.3[42]
TrueOS 11.0 September 1, 2016 FreeBSD-CURRENT[4]
TrueOS 2017-02-22[43][44] February 22, 2017 FreeBSD-CURRENT
TrueOS 2017-06-01[45] June 2, 2017 FreeBSD-CURRENT
TrueOS 17.12[46] December 14, 2017 FreeBSD-CURRENT
TrueOS 18.03[1][47] March 30, 2018 FreeBSD-CURRENT

Since version 7, PC-BSD began following the same numbering system as FreeBSD.

Since version 9.0, the KDE SC, customized to support tighter application integration and the .txz package management system, was no longer the only desktop environment supported by PC-BSD. While manual installation of other desktops such as Xfce and GNOME had been technically possible in earlier releases, none of these were supported in the earlier versions, and major functionality was lost when not using PC-BSD's special build of KDE SC.[48] Starting with version 9.0, PC-BSD added other desktop environments, including GNOME, Xfce, LXDE, and MATE.

PC-BSD used to support both amd64 and i686 architectures. Support for i686 was dropped in version 9.2.[49][50]

no carrier (underlined red) status message shown in widgets of a PC-BSD 10.1.2 network manager (running on MATE). Three network interface widgets (2 Ethernet and 1 Wi-Fi) showing two network interfaces being up, one being down with no cable plugged in (hence: "no carrier").

Starting in September 2016 with the rebranding of PC-BSD, TrueOS became a rolling release distribution based on FreeBSD's current branch.[4][15]

Package management

[edit]

TrueOS's package manager takes a similar approach to installing software to many other Unix-like operating systems. Instead of using the FreeBSD Ports tree directly (although it remains available), TrueOS uses files with the .txz filename extension packages which contain compiled ports. An autobuild system tracked the FreeBSD ports collection and generated new .txz files daily.

The TrueOS package management system aims to be visually similar to that of major operating systems such as Microsoft Windows and Apple macOS, where applications are installed from a single download link with graphical prompts, while maintaining internally the traditional .txz package management systems that many Unix-like systems use.[51] The TrueOS package manager also takes care of creating categorized links in the KDE menu and on the KDE SC desktop.

Lumina Desktop

[edit]

In 2014, the PC-BSD project announced its development of a new desktop environment, from scratch, named Lumina. Ken Moore is the main developer of Lumina, which is based on the Qt toolkit.[52]

As of July 2016, Lumina has its own web site.[53]

The desktop environment is not an application development toolkit, and aims to be a graphical interface that only uses plugins for customization.[54]

License

[edit]

TrueOS was originally licensed under the GNU General Public License (GPL) because the developers were under the impression that applications using the Qt, which TrueOS uses for its interface development, must be licensed under the GPL or the Q Public License. Upon discovering that there was, in fact, no such restriction, the TrueOS developers later relicensed the code under a BSD-like 3-clause license.[55]

TrueOS and the TrueOS logo are registered trademarks of iXsystems Inc.[56]

Hardware requirements

[edit]

The New York City *BSD User Group runs a service named dmesgd,[57] which provides user-submitted dmesg information for different computer hardware (laptops, workstations, single-board computers, embedded systems, virtual machines, etc.) capable of running TrueOS.

According to the TrueOS wiki,[58] TrueOS has the following hardware requirements:

Minimum

[edit]
[edit]

UEFI

[edit]

UEFI support (for amd64 only) has been added to the installer and the boot manager since version 10.1 with the default EFI boot manager to be rEFInd.[59] This includes ACPI detection and setup of Root System Description Pointer (RSDP),[60] eXtended System Descriptor Table (XSDT),[61] and Root System Description Table (RSDT)[62] pass-through values to the kernel. A new installation is needed in order to install UEFI support as it requires the creation of a small FAT partition. The current UEFI does not support secure boot.

[edit]
  • Screenshot of a PC-BSD 10.1.2 desktop (MATE) with dual monitor (dual head, pivot). The running free and open-source (FOSS) programs are: GIMP, OpenShot, file manager, Eric Python development IDE. Also shown: Minecraft 1.8.7 (with "Forge" mods).
    Screenshot of a PC-BSD 10.1.2 desktop (MATE) with dual monitor (dual head, pivot). The running free and open-source (FOSS) programs are: GIMP, OpenShot, file manager, Eric Python development IDE. Also shown: Minecraft 1.8.7 (with "Forge" mods).

See also

[edit]

Notes

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

TrueOS

View on Grokipedia
from Grokipedia
TrueOS was an open-source operating system derived from , initially designed as an easy-to-install-and-use platform for both desktop and server environments, featuring graphical tools for installation, software management, and system configuration. It emphasized user-friendliness for newcomers to Unix-like systems by including pre-configured desktop environments, support for multimedia, networking, and productivity applications like out of the box. Originally launched as PC-BSD in 2006, the project underwent a significant to TrueOS in to refocus on its foundational operating system components rather than just desktop-oriented features, while maintaining its roots as a downstream distribution of . In 2018, desktop efforts were separated into Project Trident, with TrueOS becoming server-oriented and removing the graphical installer. TrueOS adopted a model starting with version 18.12, drawing from FreeBSD's development branch (-CURRENT) to deliver continuous updates, and it utilized the ZFS for advanced storage management, including features like snapshots and checks. Package management evolved over time, transitioning from PBI (Push Button Installer) and TGZ formats to TXZ binaries, with a graphical software installer to simplify application deployment. Despite its innovations, such as multilingual support and integration with FreeBSD's robust kernel for stability and security, TrueOS faced challenges in sustaining independent development. In May 2020, the core development team announced the discontinuation of TrueOS for the foreseeable future, citing resource constraints and a strategic shift toward related projects like CORE, which builds on similar foundations for solutions. The source code remains available on , allowing for potential community forks or archival use, though no official updates have occurred since the shutdown.

Overview

Description and Purpose

TrueOS was a FreeBSD-based operating system originally designed for easy installation and use on desktops and servers. Its core purpose was to simplify FreeBSD for non-experts, or UNIX novices, by providing graphical tools such as an intuitive installer (available until 2018) and the AppCafe (in earlier versions), along with pre-configured environments for video, sound, networking, and desktop applications to enable stability in everyday tasks like multimedia playback, office productivity, and light server operations. Architecturally, following its from PC-BSD, TrueOS adopted a model that delivered continuous package updates, with a strong emphasis on integrating the for snapshot-based and rollback capabilities during system maintenance. Development continued until 2020, with the last release in October 2019. The project was discontinued in 2020, with its archived on to allow for reference, study, or potential forking by the community.

Key Features

TrueOS distinguished itself from vanilla through several user-centric enhancements designed to simplify installation, , and usage for both desktop and server environments. One prominent feature was its graphical installer, which provided an intuitive interface for automated partitioning and setup, enabling seamless initial configuration without requiring command-line expertise until its removal in 2018. Central to TrueOS was the native integration of as the default , offering advanced capabilities such as efficient snapshots for data protection and rollback, along with built-in support via tools like GELI for full-disk . This integration ensured robust storage out of the box, with features like compression and deduplication to optimize performance and space usage. The operating system supported dual modes for desktop and server deployment, utilizing the lightweight Lumina desktop environment by default for graphical use while allowing easy transitions via the SysAdm administrative tool or package management. Users could add or remove graphical components on a server installation or configure server services on a desktop setup, facilitating flexible role switching without reinstallation. TrueOS employed a rolling-release update model that prioritized system integrity, leveraging boot environments to apply changes atomically—creating a new snapshot before updates and preserving the live system for immediate if issues arose. This mechanism prevented partial updates that could destabilize the OS, with weekly package refreshes available from stable or unstable repositories in TXZ format. Hardware compatibility was enhanced through bundled driver layers, providing out-of-the-box support for adapters, modern graphics chipsets (including Broadwell and Skylake), and common peripherals via updated FreeBSD-CURRENT components. was bolstered by built-in firewall configuration tools accessible through SysAdm, alongside encryption options like PersonaCrypt for portable, encrypted home directories on external media. These features, combined with ZFS's inherent data integrity checks, contributed to a hardened environment suitable for sensitive deployments.

History

Origins as PC-BSD

PC-BSD was founded in early 2005 by Kris Moore with the goal of creating a beginner-friendly desktop distribution based on , aimed at simplifying the installation and use of BSD for non-expert users. The project sought to address the perceived complexity of 's command-line setup by providing an accessible operating system that could compete with popular distributions on the desktop. The initial beta release of PC-BSD arrived in April 2005, featuring a graphical installer as its core component to streamline the setup process for users unfamiliar with BSD systems. This focus on ease of use extended to application deployment through the Push Button Installer (PBI), a self-contained packaging format that allowed simple, point-and-click installation of software without managing dependencies manually. By August 2006, PC-BSD had gained recognition as the most beginner-friendly operating system in a review by the Linux-focused site OSWeekly, highlighting its intuitive design and community support. Development of PC-BSD proceeded under sponsorship from starting in 2006, when the company acquired the project to further promote 's adoption in desktop environments alongside its server applications. Key early milestones included the integration of as the default from the project's inception, providing a familiar graphical interface for users transitioning from other operating systems. In 2008, with the release of PC-BSD 7.0 based on 7.0, support for the was introduced, enabling advanced features like snapshots and data integrity checks during installation and runtime. These enhancements solidified PC-BSD's position as a user-oriented BSD variant, though it later evolved into TrueOS under rebranding efforts.

Rebranding and Evolution

On September 1, 2016, the PC-BSD project announced its rebranding to TrueOS, effective immediately, to expand its scope beyond personal computers to encompass desktops, servers, embedded systems, and other applications while maintaining its foundation. This shift aimed to position TrueOS as a more versatile, security-focused distribution incorporating elements from alongside 's stability. Accompanying the rebrand, TrueOS adopted a rolling release model beginning with its 2017 snapshots, decoupling from FreeBSD's fixed biannual cycles to deliver continuous updates for newer hardware support and software features. TrueOS 2017, based on FreeBSD 11, introduced this approach with weekly ISO and package updates, enabling users to stay current without major version overhauls. The Lumina desktop environment, a lightweight, BSD-licensed option developed specifically for the project, was emphasized as the default interface during this period, serving as an alternative to resource-heavy environments like GNOME and KDE. In 2018, TrueOS transitioned its package management from the legacy PBI (Push Button Installer) system to 's pkgng, streamlining installations and updates while supporting binary diff patching for efficiency. Plans also emerged for integrating as the system and for cryptographic functions to enhance compatibility and security. That June, the project pivoted to operate as a full downstream of , prioritizing cutting-edge software stacks and serving as a base for derivative projects like desktops and appliances. Key releases underscored these evolutions: TrueOS 2017 aligned with 11 for improved stability and integration on root, while TrueOS 18.03 in March 2018 enhanced capabilities with better snapshotting and replication features alongside hardware fixes.

Discontinuation

In May 2020, Kris Moore, Vice President of Engineering at , announced the official discontinuation of TrueOS development, marking the end of official support and updates for the operating system. This decision stemmed from resource constraints within , as the company redirected efforts toward enterprise-focused products like CORE and Enterprise, which demanded greater prioritization. Key contributing factors included insufficient funding for desktop-oriented enhancements and the operational challenges of sustaining a rolling-release model amid evolving FreeBSD upstream changes. The final stable release, TrueOS 18.12 in December 2018, was based on 11.2 and represented the last point release before development halted entirely, leaving users without subsequent security patches or feature additions. In the immediate aftermath, archived the TrueOS source code on under the iXsystems/trueos-core repository to ensure public accessibility for potential forks or personal use. Users were advised to transition to vanilla for a pure base system experience or to community-driven continuations such as Project Trident, which built upon TrueOS components at the time. Project Trident, a desktop-focused continuation, was discontinued in October 2021. Other derivatives, such as , switched back to a direct FreeBSD base following TrueOS's end.

Technical Components

Base Operating System

TrueOS served as a direct derivative of , leveraging the kernel from the development branch (-CURRENT), with minimal modifications primarily focused on enhancing system stability and integrating project-specific components like for cryptographic operations. This approach ensured close alignment with upstream developments while allowing TrueOS to maintain its unique identity as a downstream . The kernel, typically the GENERIC variant, supported standard hardware drivers and modules without extensive custom alterations, prioritizing reliability for both desktop and server deployments. A hallmark of TrueOS's base system was its default configuration of as the root file system, which the installer automatically configured by creating dedicated datasets for key directories such as /usr, /var, and /tmp to enable efficient snapshotting and rollback capabilities. This integration, drawn from 's implementation, provided built-in checks, compression, and deduplication at the core level, setting TrueOS apart from standard installations that may default to UFS. The init system in TrueOS traditionally employed FreeBSD's rc framework, which was BSD-style but compatible with sysvinit conventions for service management and boot sequencing. An experimental shift to OpenRC was adopted starting in 2017, aiming for dependency-based initialization and faster boot times while remaining compatible with FreeBSD's base tools. Security was bolstered through FreeBSD's integrated PF firewall, which offered stateful packet filtering and network address translation as standard components, alongside auditd for comprehensive logging of system events and security-relevant actions. TrueOS ensured full binary compatibility with ports and packages via the tool, enabling users to install and update software directly from upstream repositories with minimal conflicts due to the shared base system. Bootloader support included standard as the primary mode for modern hardware, with legacy fallback available to accommodate older systems, leveraging FreeBSD's loader.efi for secure and versatile initialization.

Package Management System

TrueOS initially utilized the Push Button Installer (PBI) system, a format for self-contained application bundles that facilitated straightforward installation and uninstallation without managing dependencies, as inherited from its PC-BSD origins. In 2017, TrueOS transitioned toward FreeBSD's native for handling binary packages, integrating PBI subsystems with pkgng while maintaining custom repositories hosted by to support this shift. The update process in TrueOS employed an atomic mechanism through the "update" tool (also known as pc-updatemanager), which ensured system-wide consistency by creating snapshots prior to applying changes, allowing users to to a previous state if issues arose during the . TrueOS maintained its own package repositories at pkg.trueos.org, structured around branches such as and CURRENT that mirrored FreeBSD's releases but incorporated TrueOS-specific patches for enhanced compatibility with its customized base system. By 2018, the PBI system was fully removed in favor of complete adoption of pkgng, aligning TrueOS more closely with upstream FreeBSD package management practices and simplifying software distribution.

Desktop Environment

TrueOS featured the Lumina desktop environment as its flagship user interface, developed in-house by the PC-BSD/TrueOS team starting in 2012 under lead developer Ken Moore to provide a lightweight, BSD-focused alternative to Linux-centric desktops. Lumina was fully licensed under the 3-clause BSD license, ensuring compatibility with FreeBSD-based systems like TrueOS, and was built using C++ and Qt5 for theming and cross-platform portability. Its design emphasized minimal resource consumption, with a small footprint suitable for systems with as little as 1 GB of RAM, avoiding dependencies on Linux-specific frameworks such as systemd, D-Bus, or PolicyKit to reduce bloat and enhance stability. This service-oriented, plugin-based architecture promoted modularity, allowing components to operate independently while integrating seamlessly with the underlying operating system. Key components of Lumina included a Fluxbox-based for efficient window handling in its 1.x series, which was the version used in TrueOS releases; the file manager (lumina-fm) for browsing and managing files with features like multi-tab support and snapshot integration; the Lumina tool (lumina-screenshot) for capturing regions or full screens with delay and clipboard options; and an integrated app launcher accessible via desktop widgets or context menus for quick application access. These utilities were tailored for simplicity and performance, with no unnecessary bundled applications, aligning with Lumina's goal of providing essential tools without excess. Lumina served as the default in TrueOS since the project's from PC-BSD in , offering users the option to switch to alternatives like or through the pkgng package management for added flexibility. Customization was extensive, supporting configurations via xrandr integration for dynamic screen management, basic through its , and configurable panel applets for real-time monitoring such as CPU, , and network stats. Compared to heavier environments like , Lumina demonstrated advantages in boot times and RAM usage, making it ideal for resource-constrained hardware while maintaining a responsive, themeable interface.

Deployment and Support

Hardware Requirements

TrueOS requires a 64-bit x86 processor for installation and operation. The minimum hardware specifications, based on final releases from 2018 prior to the 2020 discontinuation, are 1 GB of RAM and 10–15 GB of free hard drive space for server installations without a graphical interface. Desktop installations require 4 GB of RAM and 20–30 GB of storage. Recommended specifications for optimal performance, particularly with the graphical desktop, are a multi-core 64-bit processor, 4 GB of RAM (8 GB or more for intensive desktop tasks), and at least 50 GB of SSD storage. SSDs are preferred over traditional HDDs due to ZFS's reliance on fast random access for features like deduplication and compression, which enhance reliability and speed. ZFS, TrueOS's default file system, necessitates additional considerations for storage and memory; boot environments require a minimum of 128 MB per vdev, but practical installations allocate at least 8 GB to support multiple snapshots and rollbacks without performance degradation. For server deployments utilizing extensively, ECC RAM is advised to mitigate risks from memory errors. Modern installations mandate firmware with GPT partitioning for full compatibility, as legacy MBR schemes limit pool sizes and features. TrueOS inherits broad hardware support from , encompassing and CPUs, and GPUs via open-source drivers (such as amdgpu and ), and common Wi-Fi chipsets including and Atheros models. Limitations include primary focus on x86_64 platforms, with limited support via the discontinued TrueOS Pico variant; potential need for legacy mode on pre-2010 hardware lacking . No official support or updates available since project discontinuation in 2020.

Installation Procedure

TrueOS installation begins with acquiring the ISO , with the last official release (version 18.12) from Q4 2018 available via archived repositories such as the , as the project was discontinued in 2020. Users create bootable media by writing the ISO to a USB drive or burning it to a DVD; on systems, the dd command is used (e.g., dd if=TrueOS-Desktop.iso of=/dev/sdX bs=1M status=progress, replacing /dev/sdX with the target device), while Windows users employ in DD Image mode for hybrid ISOs. To start the process, boot the target machine from the USB or DVD, entering the / settings to prioritize the media and select either desktop or server install mode. TrueOS supports both and firmware, though installations may encounter hardware-specific issues on certain systems, resolvable by disabling Secure Boot and verifying USB formatting. If the standard graphical mode fails due to driver incompatibilities (e.g., video output), opt for the specific-driver graphical variant or text-based installer from the boot menu. The graphical installer presents a step-by-step wizard interface. Initial screens handle hardware detection, keyboard layout selection, and confirmation of the install type. Partitioning follows, defaulting to automatic pool creation on the full disk or selected partition (briefly referencing ZFS details from the base operating system); manual options allow custom layouts, full via GELI, and setups. Network configuration occurs next, with automatic detection for most wired connections, supplemented by manual Wi-Fi or static IP entry if needed. User setup requires setting a password and creating at least one non-privileged account for daily use. Advanced deployment includes PXE-based remote installation for networked environments and building custom images from source code via the project's repositories. The installer completes by copying files and configuring the , typically taking 10-20 minutes depending on hardware. Upon first boot, the system launches into a configuration phase for timezone and locale setup, followed by running the TrueOS Update tool to fetch initial patches (noting package integration). Users may select or switch desktop environments like Lumina or at this stage if not preset during install. For hardware compatibility, briefly cross-reference minimum requirements from the deployment section. Troubleshooting common issues involves verifying UEFI/BIOS mode alignment—BIOS for legacy hardware, UEFI for modern systems with GPT partitioning—and reloading install media drivers via the boot menu's safe mode if graphics fail. Encrypted setups require entering passphrases during boot, and ZFS import errors can stem from mismatched disk labels, resolvable via the installer's emergency shell.

Licensing and Legacy

Licensing

TrueOS, as a derivative of FreeBSD, employs the Simplified BSD License (2-clause) for its core operating system code, which permits redistribution and use in source and binary forms with or without modification, provided that the copyright notice, conditions, and disclaimer are retained. This permissive license ensures broad compatibility and minimal restrictions on derivative works, aligning with FreeBSD's foundational principles. The Lumina Desktop Environment, a key component developed specifically for TrueOS, is distributed under the 3-clause BSD license, which allows free use, modification, and redistribution—including in proprietary distributions—while requiring retention of copyright notices and a disclaimer of liability. Third-party components, such as those in the ports collection and packages managed by the system's package tools, incorporate a variety of open-source licenses including BSD, MIT, and GPL variants, with explicit attribution and licensing details provided in package manifests to facilitate compliance. Project terms emphasize that all falls under the BSD license framework, disclaiming any warranty and, prior to the project's discontinuation, actively encouraging community contributions through public repositories. Distribution of TrueOS is unrestricted for non-commercial purposes, with freely available ISO images and repositories, though retains ownership of the "TrueOS" trademark to protect branding. The base system adheres to FreeBSD's open-source freedoms—comparable to the Debian Free Software Guidelines—with no inclusion of binary blobs.

Community Impact and Forks

TrueOS exerted a notable influence on the broader BSD ecosystem by advancing desktop usability and server-oriented features derived from , particularly through its emphasis on graphical tools and integration. At its peak, the project garnered a dedicated but modest user base, with many installations serving as entry points for users exploring BSD alternatives to distributions. Following its discontinuation in 2020, a significant portion of the community migrated to vanilla , user-friendly derivatives like —which had briefly been a downstream of TrueOS from 2018 to 2021—or Linux-based systems offering similar desktop experiences. The project's contributions extended upstream to FreeBSD, where innovations such as default OpenZFS support and graphical installation mechanisms inspired enhancements in desktop tools and file system adoption within the base system. TrueOS's development of utilities like the SysAdm configuration tool and the Lumina desktop environment highlighted practical approaches to BSD desktop deployment, influencing community efforts to make FreeBSD more accessible for non-server use cases. In terms of forks and continuations, Project Trident emerged in 2019 as a community-driven successor, initially building on TrueOS's base and featuring the Lumina desktop for a lightweight, customizable . The project transitioned to in late 2019 amid challenges with 's development pace but retained TrueOS's core philosophies until its sunset in 2021. Elements of TrueOS's tooling also informed live-session capabilities in projects like NomadBSD, though direct code integration remains limited to shared heritage. The legacy of TrueOS persists through its open-source code, archived on under the trueos organization, where repositories such as trueos-core (with 87 stars) and trueos-ports (14 stars) serve educational purposes and as foundations for custom BSD builds. Broader impacts include the promotion of viable BSD desktop environments, which helped normalize for everyday computing beyond servers. Key figure Kris Moore, TrueOS's lead developer and ' SVP of Engineering, carried forward these efforts into SCALE, a Linux-based storage platform that incorporates refined handling and update mechanisms echoing TrueOS's innovations. As of 2025, TrueOS remains without active official development, with its preserved for archival use and occasional experimentation, though no sustained patches have emerged. classifies it as discontinued since its 2020 shutdown, reflecting its inactive status in the BSD landscape.

References

  1. https://distrowatch.com/trueos
  2. https://distrowatch.com/10156
  3. https://www.truenas.com/trueos-discontinuation/
  4. https://distrowatch.com/table.php?distribution=trueos
  5. https://itsfoss.com/trueos-bsd-review/
  6. https://www.eweek.com/pc-hardware/trueos-succeeds-pc-bsd-desktop-friendly-unix-os/
  7. https://github.com/trueos/trueos
  8. https://www.opensourcefeed.org/distribution/trueos
  9. https://hackmag.com/security/trueos-freebsd-desktop
  10. https://docs.huihoo.com/pcbsd/guide/index_single.pdf
  11. https://www.unixmen.com/bsd-for-human-beings-interview/
  12. https://dot.kde.org/2006/09/05/pc-bsd-interview/
  13. https://www.osnews.com/story/20351/review-pc-bsd-7/
  14. https://www.osnews.com/story/15451/pc-bsd-the-most-beginner-friendly-os/
  15. https://www.ixsystems.com/blog/ixsystems-announces-acquisition-of-pc-bsd-operating-system/
  16. https://www.zippia.com/ixsystems-careers-1405988/history/
  17. https://www.ixsystems.com/blog/ixsystems-announces-professional-freebsd-and-pc-bsd-support-offering/
  18. https://www.ixsystems.com/blog/ixsystems-announces-pc-bsd-10-propelling-the-bsd-desktop-experience-to-new-heights/
  19. https://www.osnews.com/story/29379/pc-bsd-evolves-into-trueos/
  20. https://linux.softpedia.com/blog/pc-bsd-operating-system-gets-renamed-to-trueos-follows-a-rolling-release-model-507866.shtml
  21. https://www.phoronix.com/news/TrueOS-First-Spin
  22. https://www.zdnet.com/article/hands-on-lumina-desktop-1-0-0/
  23. https://www.phoronix.com/news/TrueOS-New-Direction
  24. https://www.trueos.org/blog/trueosdownstream/
  25. https://www.phoronix.com/news/FreeBSD-11.1-12.0-CUR-TrueOS
  26. https://www.phoronix.com/news/No-More-TrueOS
  27. https://forums.freebsd.org/threads/project-trident-sunset.82644/
  28. https://trueos.github.io/pkgbase-docs/
  29. https://forums.freebsd.org/threads/trueos-anyone-using-it-on-a-laptop.63746/
  30. https://docs.freebsd.org/en/books/handbook/audit/
  31. https://www.ixsystems.com/blog/pkgng-the-future-of-packages-on-freebsd-and-pc-bsd/
  32. https://distrowatch.com/index.php?distribution=trueos
  33. https://mangolassi.it/topic/16636/how-to-update-packages-on-trueos
  34. https://distrowatch.com/weekly.php?issue=20190107
  35. https://lumina-desktop.org/post/2021-07-01/
  36. https://www.phoronix.com/news/Lumina-Desktop-1.6.2
  37. https://lumina-desktop.org/features/
  38. https://lumina-desktop.org/faq/
  39. https://docs.freebsd.org/en/books/handbook/zfs/
  40. https://docs.freebsd.org/en/books/handbook/bsdinstall/
  41. https://wiki.freebsd.org/Graphics
  42. https://archive.org/details/true-os-desktop-18.03-x64
  43. https://rufus.ie/
  44. https://github.com/trueos/trueos-core/issues/114
  45. https://computingforgeeks.com/trueos-freebsd-for-desktop-full-review/
  46. https://github.com/trueos/trueos-docs
  47. https://github.com/trueos/build
  48. https://www.freebsd.org/copyright/freebsd-license/
  49. https://lumina-desktop.org/
  50. https://openzfs.org/wiki/OpenZFS:Copyrights
  51. https://www.freebsd.org/internal/software-license/
  52. https://www.theregister.com/2023/11/07/ghostbsd_23_10/
  53. https://www.phoronix.com/news/Project-Trident-Void-Linux
  54. https://news.itsfoss.com/project-trident-discontinues/
  55. https://fossforce.com/2021/11/project-trident-a-linux-distribution-with-bsd-roots-shuts-down/
  56. https://www.phoronix.com/news/ixSystems-TrueNAS-SCALE
  57. https://www.truenas.com/history/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.