PC-BSD becomes TrueOS
trueos.org
PC-BSD becomes TrueOS
1–10 of 31 posts
Re: PC-BSD becomes TrueOS
#2Well and good. The ® slapped everywhere is very annoying.
Re: PC-BSD becomes TrueOS
#3So why would one want to use TrueOS instead of FreeBSD? When it was still called PC-BSD some people claimed ease of use, but I never understood that; since it used the same ports as FreeBSD, you could install the same ports or packages on FreeBSD.
Now they abandoned this desktop focus. So what is the selling point here?
Re: PC-BSD becomes TrueOS
#4How pretentious can they be.
Re: PC-BSD becomes TrueOS
#5So why would one want to use TrueOS instead of FreeBSD? When it was still called PC-BSD some people claimed ease of use, but I never understood that; since it used the same ports as FreeBSD, you could install the same ports or packages on FreeBSD. Now they abandoned this desktop focus. So what is the selling point here?
I use PC-BSD on my desktop. The reason that I chose it over FreeBSD is due to their upgrade process and their use of ZFS boot environments (beadm). And the fact that X "just worked" with their installer.
In terms of packages and uppdates: The way a pkg update on FreeBSD goes is that you do pkg-update && pkg-upgrade, and it updates your packages in place. In PC-BSD, it makes a new clone of your current root environment, and does the upgrade there. It makes this the new boot environment, and at reboot, you boot into the updated system. This is much cleaner, and allows you to easily roll back in the rare event of something blowing up.
I hope TrueOS keeps this.
Ugh, The name reminds me of Tru64 from DEC in the 90s..
Re: PC-BSD becomes TrueOS
#6So why would one want to use TrueOS instead of FreeBSD? When it was still called PC-BSD some people claimed ease of use, but I never understood that; since it used the same ports as FreeBSD, you could install the same ports or packages on FreeBSD. Now they abandoned this desktop focus. So what is the selling point here?
I use PC-BSD on my desktop. The reason that I chose it over FreeBSD is due to their upgrade process and their use of ZFS boot environments (beadm). And the fact that X "just worked" with their installer. In terms of packages and uppdates: The way a pkg update on FreeBSD goes is that you do pkg-update && pkg-upgrade, and it updates your packages in place. In PC-BSD, it makes a new clone of your current root environmen…
> It makes this the new boot environment, and at reboot, you boot into the updated system.
So you have to reboot to apply the changes? Sounds familiar :)
Re: PC-BSD becomes TrueOS
#7How long till it's forked and prefixed with "TheOne"?
Re: PC-BSD becomes TrueOS
#8So why would one want to use TrueOS instead of FreeBSD? When it was still called PC-BSD some people claimed ease of use, but I never understood that; since it used the same ports as FreeBSD, you could install the same ports or packages on FreeBSD. Now they abandoned this desktop focus. So what is the selling point here?
They didn't abandon the desktop focus. That's "TrueOS Desktop."
Re: PC-BSD becomes TrueOS
#9Earlier quoted context omitted.
I use PC-BSD on my desktop. The reason that I chose it over FreeBSD is due to their upgrade process and their use of ZFS boot environments (beadm). And the fact that X "just worked" with their installer. In terms of packages and uppdates: The way a pkg update on FreeBSD goes is that you do pkg-update && pkg-upgrade, and it updates your packages in place. In PC-BSD, it makes a new clone of your current root environmen…
> It makes this the new boot environment, and at reboot, you boot into the updated system. So you have to reboot to apply the changes? Sounds familiar :)
You can always overwrite in place (that was how it worked before beadm), but it's riskier.
Re: PC-BSD becomes TrueOS
#10Wait -- TrueOS follows FreeBSD-CURRENT?
How...brave.