Project-Trident Release Candidate 1 Installed — Really?
After installing ‘Trident-RC1-x64-20181008.iso’ into a boot environment:
root@trident-2863:/usr/home/rudy # 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-20180910_062826 - - 6.3G 2018-09-10 06:23 12.0-CURRENT-up-20180929_141112 - - 13.7G 2018-09-29 13:52 12.0-CURRENT-201810091443 - - 6.0G 2018-10-09 16:43 12.0-CURRENT-up-20181009_183731 NR / 13.6G 2018-10-09 18:18
everything was suspiciously identical to Project-Trident BETA3. The ‘dhcpcd.re0’ was crashed, Easytag wouldn’t start, Deadbeef was crashing, and even a timezone mismatch needed to be corrected again. The AppCafe is limited to ‘local’. To get sound in Falkon the folder ‘pulse’ in ~/.config has to be deleted again.
After using ‘# trueos-update upgrade’ (the last entry on the list above) everything is working again but this caused a second download of most of the system.
The command ‘about’ is still not existing and ‘# uname -a’ gives:
root@trident-2863:/usr/home/rudy # uname -a FreeBSD trident-2863 12.0-CURRENT FreeBSD 12.0-CURRENT #0: Mon Oct 8 16:37:41 UTC 2018 root@poseidon:/usr/obj/usr/src_tmp/amd64.amd64/sys/GENERIC amd64
After this experience I am not sure this to be an actual installation of RC1. Is there a way to verify which system really is installed?