FTR, @BastilleBSD beats iocage big time, for the very simple reason that it is not Python.
I use Python, I even like it. I wouldn't write a system utility in Python; starting the interpreter every time is a PITA.
By using simple shell scripts, it is both simpler to hack and significantly faster!
I'm finishing my provisioning with @BastilleBSD (TBA soon), the only deal-breaker for me resulted in a PR which I'd very much like some feedback on; it works-beautifully-for-me (tm) with IPv6-only and dual-stack #FreeBSD jails.
Reach out in the PR or here.
"L'accés a la xarxa és lliure de discriminació (Model Open-Access). Gràcies a la infraestructura pròpia, la ciutat de Zürich pot influenciar el preu, la qualitat, la velocitat de desplegament de la xarxa i garantir l'accés al servei. La ewz (empresa de la ciutat de Zürich) mateixa no ofereix serveis de fibra òptica directament als clients finals."
«For the absurd man it is not a matter of explaining and solving, but of experiencing and describing. Everything begins with lucid indifference.»
These were the error messages, for posterity:
# zfs list
ld-elf.so.1: Shared object "libcrypto.so.111" not found, required by "zfs"
ld-elf.so.1: Shared object "libcrypto.so.111" not found, required by "pkg"
Luckily from when I patched base's pkg, I knew to run:
pkg-static add https://alpha.pkgbase.live/current/FreeBSD:14:amd64/14.snap20210709060648/FreeBSD-openssl-14.snap20210709060648.tzst
Everything is back to normal, but something went seriously wrong there, and I wouldn't know how to reproduce it '-.-.
I wonder if I'm in the wrong when I look at a CV of a "Full Stack Engineer" and basically discard it because it is obvious they didn't put any effort in making it look decent. Care: not original! just decent, any decent-looking template would do.
Then I try to correct for a potential bias, look at it deeper and think "nope, this is all just buzzwords".
Maybe I just dislike most people "in tech".
Contributing to free software requires privilege. Even regular contributors might sometimes find themselves without it.
Time, focus and money. You might find yourself lacking in one of these at various points in your life.
While software projects from startups move like streams, most free software projects move like glaciers. They move slowly but they keep moving for decades.
Being away from a project doesn't mean you have to give it up. You can join back later.
Minor annoyances so far, unless specified they are documented with decent work-arounds:
- bunch of .pkgsave files when pkg detects the file existed previously
- duplicated rc-files (due to .pkgsave) --> things run twice on boot (awkward)
- duplicated .ko files (due to .pkgsave) --> modules "try to load twice" when needed (awkward)
- This is documented, but not with this perspective: Performing a #FreeBSD system upgrade to a new version with pkgbase is a tad awkward due to the ABI change.
I know I could build and run my own repo, but she is a wonderful community member and I am not a fan of rebuilding all the things just because (e.g. these days it is hot enough in Barcelona without compiling :-D).
Accidentally upgraded a bunch of machines to #FreeBSD 13.0-RELEASE-p2 without being aware that p2 was out X-D.
I'm actually a tad surprised at how well Dolibarr
works in general.
Had a couple issues with how it expects the SMTP credentials to be able to send email from anyone, which is a tad absurd, but I managed to add a couple hacks to fix that.
chaos.social – a Fediverse instance for & by the Chaos community