New release unleashed today


#1

New ISO and packages available now. Trident-18.12-PRERELEASE-x64-20181208.iso

No, this release DOES NOT have the AppCafe bug fix in it. This is being generated with a number of other bug fixes.

Here is the pkg build for this release


#2

My upgrade to this:

[rudy@trident-2417 ~]% about
Project Trident Information
--------------------------------------
OS Version: 18.12-PRERELEASE
Build Date: 2018.12.07-13.45.24
--------------------------------------
TrueOS Sources Used:
  Base Repository: https://github.com/trueos/trueos
  Base Commit Tag: 546305a23bccd6aac4db04c9acb482b24cda25fa
  Ports Repository: https://github.com/trueos/trueos-ports
  Ports Commit Tag: 60c3f94d81e0ea0ce18ec7d7fd57166c73d951a5
--------------------------------------
System Specs:
  Boot Method: BIOS
  AMD A4-3300 APU with Radeon(tm) HD Graphics
  Physical CPUs: 2
  Physical Memory: 3.43 GB
--------------------------------------
GPU Information:
  vgapci0@pci0:0:1:0:   class=0x030000 card=0x84c81043 chip=0x96451002 rev=0x00 hdr=0x00
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Sumo [Radeon HD 6410D]'
    class      = display
    subclass   = VGA
--------------------------------------
Network Device Information
  re0@pci0:3:0:0:       class=0x020000 card=0x84321043 chip=0x816810ec rev=0x06 hdr=0x00
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    device     = 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller'
    class      = network
    subclass   = ethernet

went well via the commands # trueos-update check and # trueos-update upgrade. A little suspicious was the pruning of two boot environments:
12bootenvironment2018-12-12-11-17-34
but I don’t expect to need them ever again since this was the second successful update in a row.
My AppCafe looks fine:


it contains the Trident option and is showing packages not installed locally at the moment.
This time also my individually installed package Deadbeef was upgraded automatically and usable without any further action by myself.

This really looks good! Thank you to all the developers!

Edit:
Interesting that of the removed boot environments only one is actually gone:

[rudy@trident-2417 ~]% beadm list
BE                              Active Mountpoint  Space Created
initial                         -      -            2.5G 2018-05-01 15:06
12.0-CURRENT-up-20180501_155633 -      -            7.5G 2018-05-01 15:54
12.0-CURRENT-up-20180929_141112 -      -           13.7G 2018-09-29 13:52
12.0-CURRENT-201810091443       -      -            7.4G 2018-10-09 16:43
12.0-CURRENT-up-20181009_183731 -      -            6.1G 2018-10-09 18:18
13.0-CURRENT-up-20181112_130401 -      -           21.2G 2018-11-12 12:45
13.0-CURRENT-201811240540       -      -            5.2G 2018-11-24 06:40
13.0-CURRENT-up-20181202_180126 -      -            5.8G 2018-12-02 17:43
13.0-CURRENT-up-20181212_113054 NR     /           18.5G 2018-12-12 11:13 

#3

Can we expect any changes on the installer recognizing ZFS boot environments pools created until 18.03?

I don’t, but I’m asking just in case…


#4

you’ll to take that up with the FreeBSD Devs. changing the bootloader from forth to lua, has changed a lot of things.

And more are not on the plus side


#5
Is there a GitHub issue to track installer, bootloader, UEFI and GELI?
Upstream's 12.0 announcement includes good news:
<URL:https://www.freebsd.org/releases/12.0R/announce.html>
John
groenveld@acm.org

#6

UFEI & GELI, will probably not be included any time soon.

As for the others, have you looked at the Project Trident repo?


#7

Strangely enough I had to install/run this script again:

I initially installed/ran it for the upgrade/update from RC1 to RC3 and didn’t have to repeat this step for the update/upgrade from RC3 to prerelease 1 and PR1 to PR2. But now, before running the script I would get error messages when using “trueos-update check” and “trueos-update upgrade”, respectively. Something about missing certificates and failing access to a repo file. Also an error updating repositories.

With the script re-run update from PR2 to “whatever PR this is” now runs as experienced with the last few updates.


#8
<URL:https://github.com/project-trident/trident-installer/issues/39>

I tested the new installer in FreeBSD 12 and the geli option for root pool
works well.
John
groenveld@acm.org

#9

simple answer 1: then go to FreeBSD

simple answer 2: then roll your own distro.

11 months+, geli was broken, and in “beta”,

when the 2 devs decide to stick it back in then the devs will do just that


#10
Untested on bare metal, but on a VBox guest with EFI, Trident installer
is able to install a BE to the FreeBSD 12 guest with a geli root pool.
John
groenveld@acm.org