#rsync'ing a ~10GB #poudriere package directory /usr/local/poudriere/data/packages/foo elsewhere gets me a ~130GB target directory? What am I missing? #ZFS compression is turned on for both and compressratio is not really great, so that's not it. Using rsync -a, so nothing really special #FreeBSD
Update was smooth, if a little time-consuming on the Pi, and everything seems to be working correctly, which is awesome! Let's do more testing and find out :)
@kta well pointed! So that's why #poudriere seems to be such a popular topic in #FreeBSD discussions. I guess I don't have the same scope as an enterprise environment to me to do, but it's interesting to know. Perhaps I'll play a little more with building things from source using the ports sometime in the future, but for now usually pkg works for me :) thanks for the pointers!
Learn about the distinction between (binary) packages and (source) ports. Installed a few extra console applications courtesy of the pkg package manager. Apparently you are not supposed to mix using packages and ports on the same system? I'll dig into that a bit deeper when the issue arises where I want to compile something from the ports tree. https://docs.freebsd.org/en/books/handbook/ports/
Poll: How frequently do you apply security patches and software updates to your #Linux, #Unix, or #FreeBSD server or desktop? Please boost for reach. TIA. 🙏
@nixCraft#FreeBSD user on both desktop and server (incl. firewall) as well as #ports maintainer here:
My answer (ASAP) is an approximation.
For the base system, I read the published #advisories ASAP. I decide whether I'm affected, and how exposed my different machines are. If necessary, I rebuild base from source and update all machines needing the update ASAP.
For ports, I try to keep an eye on "exposed services" (like e.g. my MTA) for servers and at least browsers for desktops. Actually installing an update can take two or three days because I'm building my own package repository using #poudriere.
It's the sysutils/nix package... er, "port" or whatever. This could be awesome, because I would be able to have reproducible builds an an operating system that provides #ZFS support, which on #Linux is possible but still a bit experimental. And also you can make use of #BSD "jails" or "zones" as app containers, which on #Linux is not possible at all. (And no Docker doesn't even come close to providing the isolation and security features that BSD jails provides.)
But still, so many questions...
so when you install stuff using Nix, does it still build it using the Clang compiler that FreeBSD uses for the rest of it's stuff? Or does it force you to use the #GCC from Nix Packages?
Is there an easy way to configure which compiler you want to use for building all of your stuff?
Or (and I hope this is not the case, but) does it make use of some kind of BSD comparability layer for Linux kind of like what WSL2 does on Windows? I wouldn't think so, but it is possible that this is how it works.
Is it possible to build Nix packages into BSD jail? I know Nix provides support for creating Docker containers, but is there support for jails?
Is there a Nix expression that can construct a Nix derivation from a BSD "port" itself? I would assume so, but then, not necessarily.
@ramin_hal9001 This commit history doesn't look promising. First the original maintainer abandoned it, later someone else marked it broken.
But talking about reproducible builds, you get that with #poudriere (enabling a few options that avoid surpising sources of inconsistencies) and the #ports tree as well. Poudriere builds every package in a clean #jail that only gets the named dependencies installed. Official #FreeBSD packages are built that way.