RC3 WARNINGS/ERRATA

Version RC3 of Project Trident is the first version based off-of the “trueos-master” branch of TrueOS. Because of this, there are a number of things that were discovered as broken or need some tweaks compared to previous versions:

FreeBSD bootloader was changed from the “forth”-based version to the new “Lua”-based version browse the code here. This has resulted in some (older?) systems being unable to boot properly or cause FreeBSD kernel panics during bootup - particularly if the system is booting with an older UEFI implementation. Some possible solutions are:

Update your system BIOS following the instructions from your system/motherboard manufacturer.

If your system has weird corrupted terminal graphics during bootup, follow this guide

Try switching your BIOS to legacy mode instead of UEFI mode. This may have other consequences though - UEFI is recommended for most modern graphics driver support.

The install ISO appears to not be starting many of the backend services (such as “moused”). If you experience trouble using your mouse within the installer, drop to the terminal and run the following commands:

At the login prompt type: root

Run: service moused start

Re-start the graphical installer by running: start-trident-installer

Some TrueOS branding is still in place for the installed system on RC3. This can be fixed by running the following commands from a terminal:

Reset Icon theme: Open up the Theme engine utility (available in the lumina-config “appearance” section) and change the icon theme over to “le-trident-dark” and apply the change. Some apps may need to be restarted before they start using the new icon theme.

General Release Notes

Application/Package Availability

Every single release includes a manifest of all the packages and versions that are available in the repository.
This plaintext file can easily be downloaded from the package server

If the package does not appear on the list

No Port: You can follow the FreeBSD Porters Handbook to create a new port, and then submit it either to FreeBSD or to TrueOS. Once accepted by either project, the port will become available by Project Trident a short time later.

Known Issues

VirtualBox Guest: When resizing the window for the Project Trident VM, there may be a delay in the session detecting/adjusting to the new “screen” size. When using the Lumina desktop, you may also need to run killall fluxbox from the command-line to re-initialize the window manager if the borders around windows disappear after a session resize from outsize the VM.

Bug Bypass: Use the “Preferences -> Display” settings utility (lumina-xconfig) from within the VM to change the session size. This will ensure that the session resize is performed in a consistent manner for the entire VM.

Migration/Update Paths

Trident RC2 and older

Between RC2 and RC3, the package repository format from TrueOS was moved from 2 repositories (base + ports) to a single “unified” package repository. This requires that the on-disk repository configuration file(s) need to be updated in order to recognize the new location for packages.

We have a script available on our package server in order to perform this update for you as needed, and all that needs to be done is run the following from a terminal:

Once the upgrade has been performed, you will need to install the trident packages with the following command: sudo pkg install trident-core. This will probably remove conflicting packages such as “trueos-desktop”, “trueos-servers”, and other similar meta-packages, but it is a good idea to verify that.

If desired, run the /usr/local/share/trident/scripts/sys-init.sh script to perform the first-time setup routine for Project Trident. This will change things like the branding on PCDM, the default configuration for the Lumina desktop, and similar things.

Reboot the computer. You are all set!

TrueOS “Desktop” (18.03) or FreeBSD

There is no direct upgrade path for these kinds of systems, so you will need to follow these steps to migrate your system over to Project Trident:

WARNING : Always backup all important data to an external location before performing anything as intensive as a system installation!

Install/prepare the ISO just as for a new installation

On the disk setup page of the installer, select the “Boot Environment” option in order to perform a fresh installation into an existing ZFS system layout. This will change the system packages and system configs, but anything within the /usr/home directory should be preserved.

Re-create your user(s) with the same information and uid as before. This will allow those users to immediately start re-using the same home directory and data as before.