Where are we at with this week's pkg upgrade

thedaemon said:
This seems like gatekeeping to me. Stable means not broken, thanks. Webster's Dictionary defines it as: "not changing or fluctuating". So I say, having missing packages, is changing and fluctuating. https://www.merriam-webster.com/dictionary/stable
Click to expand...
For linux applications that ported to freebsd this is a normal problem. A simple change needed to broke freebsd patch!
usually some maintainers not responding to this situation and package become missing.
 
thedaemon said:
boot environments do nothing for your /usr/local/bin that's going to need a snapshot.
Click to expand...
I don't think that is correct.

What go in BE are datasets that have their zfs property canmount set to off.
From bectl() manpage:
zroot/usr has canmount set to off, thus files in /usr typically fall into the boot environment because this dataset is not mounted.
Click to expand...

Code: 
 ~ % zfs list -o name,canmount,mountpoint | grep off
zroot/usr                                  off       /usr
zroot/var                                  off       /var

The article (written by Dru Lavigne) shows precisely the case for an update via ports-mgmt/pkg, I've tested it yesterday and it seems to do the job correctly.
 
gotnull is correct at least based on my experience and my reading of lots of stuff. If one takes the defaults as presented by the installer (as in don't do things by hand) /usr/local/bin, /usr/local/etc are definitely part of a boot environment. Since ports/packages install into /usr/local, if you have a service like openntpd installed the configuration gets inherited by every boot environment.

"canmount" is the key to this.
/var has canmount off, so something like /var/db is part of a boot environment unless one explicitly creates a /var/db dataset.
/usr has canmount off, so if you do not explicitly create /usr/local as a separate dataset, it's part of the BE.
If you explicitly create /usr/local/whatever as a separate dataset, then it will not be part of the BE.
/usr/home is usually a separate dataset so is not part of a BE.

If one wants to handcraft things, one must be very careful in execution or you can wind up with a BE that is not a full BE.
 
When I tried BE's it only backed up the base FreeBSD, not any of my /usr files so I had to wipe and reinstall the entire thing. I guess I missed the step to activate it or followed the wrong guide.. Snapshots saved me though! Thanks for the correction.
:)
 
You must log in or register to reply here.
Back
Top