Looking at TrueOS (2)

Continued from part 1:

I am more used to pf than ipfw, but it’s nice that at least *some* kind of configuration is automajick on TrueOS.

TrueOS makes good use of the multiple boot environment that is a feature that dovetails nicely with the capability of ZFS.  When an auto-update is performed, a new boot environment is created for the update.  On a subsequent boot, the new updated environment takes off with all the updates and improvements.  Such is the theory.

If there’s a problem, one can simply select another (initial, for instance) environment, and still have a usable system.  There’s some hiccup in all of this however; maybe due to a rapidly changing (TrueOS pulls the CURRENT FreeBSD) codebase.  It means that I did at least one update that forced me to select the original boot environment (the updated verion of the system kaboshed itself somehow).   So, the initial boot environment saved the day, and all was good.  However; it is intoned that TrueOS is a hands-off version of its papa OS.  Being forced to use the boot selector is not super beginner-friendly.

I looked for an answer to this on the forum, and read that the connection to CURRENT is not literal.  They pull snapshots that are (apparently) vetted in some way.  IMO there may be a few mice that get in under the door sometimes.  Maybe that’s a low price to pay for being ahead of the pack.  It’s a choice I guess.  In any case, it’s one of the reasons I changed the auto-update to “manual”.

TrueOS (thank’s to its heredity) – has the unbound local caching resolver baked in, which is nice.  I use it all the time, and I think I have another page or two on this site devoted to pontificating about it.  Using unbound, one can cut one’s DNS traffic down to a low level (or even eliminate it).  I’m also a big fan of using hostapd on FreeBSD, but haven’t yet tried it on TrueOS (shouldn’t really be any difference, IMO).

I haven’t installed many packages beyond what the ISO comes packed with, so can’t say much about how cleanly the packages and ports play here. Again I wouldn’t expect behaviours to be too much different than what happens on the upstream OS.   In fact, I installed a few ports (to build the desktop debug version), and a few packages (mainly to install Gimp, so I could put the silly graphic at the top of the page 🙂

 

Advertisements