```suggestion * System updates are **fast** and clean. All updates are performed within a new Boot Environment, ensuring the live system is never touched while in use. Reboot to finish the update procedure and boot into the newly-updated system. ```

```suggestion * The OS and packages are always in sync. A single system update can be used for the entire end-to-end update of the system, even when OS changes like a new kernel are provided during a major release cycle. ```

```suggestion TrueOS uses the package system for installing the OS itself in addition to the pre-compiled "ports". This functionality is called "base packages" and allows a single package repository to contain both the OS and all the available applications in a single, unified collection of files. This functionality provides these features: ```

```suggestion * Example 2: `service network.wlan0 restart` restarts the networking associated with the first wireless device. ```

```suggestion * Example: `service dbus stop` stops the **dbus** service when it is running. ```

```suggestion * The "service" utility is used identically to FreeBSD for interacting with services. ```

```suggestion * Example 2: `rc-update delete dbus default` removes the **dbus** service from the **default** runlevel and prevents it from starting during bootup. ```

```suggestion * Example: `rc-update add dbus default` adds the **dbus** service to the **default** runlevel and enables it to automatically start on bootup. ```

```suggestion * The *[service-name]_enable="YES"* entries on FreeBSD are no longer needed to enable services on bootup. Instead, OpenRC provides a method for grouping services together (called "runlevels"), and the `rc-update` utility is used to add/remove bootup registrations for services within these groups. ```

```suggestion * Example: The **network.wlan0** service controls the first wifi device, and should be started/stopped instead of the **network** service when re-configuring the Wi-Fi settings. ```

```suggestion * Many OpenRC services are "multiplexed" for individual device/profile management. ```

```suggestion * Service files are located in `[/usr/local]/etc/init.d` rather than `[/usr/local]/etc/rc.d`. ```

```suggestion * Some services have different names: **dhcpcd** instead of *dhclient*, **network** instead of *netif*. ```

```suggestion * Better status reporting. The `rc-status` utility provides an instant look at all system services and their current status. ```

```suggestion * Project Trident uses a [customized build configuration](https://github.com/project-trident/trident-build/blob/master/trident-master.json/) for both OS and ports. Everything in Project Trident is built specifically to be used for a graphical operating system. ```

```suggestion * Dynamic loading of the video driver and any associated kernel modules on bootup. This allows the system hard drive to move between systems as needed with little or no loss of functionality. This requires that the video drivers for both systems are installed already, or one of the failover drivers can be used. ```

```suggestion * Automatic failover to one of two different graphical drivers (**vesa** or **scfb**) if the main graphics driver fails to work for some reason. ```

```suggestion * While this is typically a manual task on TrueOS/FreeBSD, Project Trident provides a suite of scripts and utilities which handle all of the setup and maintenance of the graphical systems. These utilities run during the bootup routine and dynamically provide these features: ```

```suggestion *Note: Differences listed here also generally apply to other TrueOS-based distributions* ```

```suggestion Due to the addition of OpenRC to TrueOS for service management, the TrueOS project maintains a version of the FreeBSD ports tree which includes many additional files. These extra files ensure that OpenRC versions of service files are available alongside the traditional *rc.d* service files from FreeBSD. They also provide a testing area for other TrueOS changes before submission back to FreeBSD, including new ports, new versions of ports, and more. TrueOS also uses GitHub for managing it's ports repository[1], whereas FreeBSD still uses a privately-hosted SVN repository[2]. ```

```suggestion All of the applications which are available in the form of packages are built from the exact same "ports tree", which is a source repository of build instructions for over 35000 applications, libraries, and more. These "ports" generally result in binaries which are compiled to run specifically on different FreeBSD-based operating system architectures. ```

```suggestion The base operating system and kernel are identical between the various projects, as they are all built directly from the same source code, although at different times or from different branches of the source repositories. This includes the kernel, hardware drivers, file systems, and more. ```

```suggestion The discontinued desktop portion of TrueOS was adopted by Ken Moore and J.T. Pennington, two desktop-focused TrueOS developers, and rebuilt into Project Trident. ```