FreeBSD

poudriere: when renaming sets, also rename *-make.conf files etc

Last last night, after renaming some buildlists, which were actually setnames, for poudriere, I realized that files in /usr/local/etc/poudriere.d also needed to be renamed. In this post: poudriere 3.3.7 nginx 1.20.1_2,2 Both running on FreeBSD 13.0-RELEASE-p4 These are my renamed files: [dan@pkg01:/usr/local/etc/poudriere.d]: $ ls *primary* primary-make.conf primary-poudriere.conf primaryi386-make.conf primaryi386-poudriere.conf The output of svn status illustrates the changes I made: [dan@pkg01:/usr/local/etc/poudriere.d]: $ svn st D master-list-i386-make.conf > moved to primaryi386-make.conf D master-list-i386-poudriere.conf > moved […]

poudriere: when renaming sets, also rename *-make.conf files etc Read More »

poudriere: Warning: Using ‘-‘ in a SETNAME is not recommended as it causes ambiguities with parsing the build name of 122amd64-default-master-list

I like readability. I like it in variable names. I prefer something descriptive and easy to ready. In in this post: FreeBSD 13.0-RELEASE-p4 poudriere 3.3.7 I recently started getting messages like this from my daily poudiere build: I could just rename the sets, everything would be rebuilt, but then clients would be stuck pointing at the old no-longer built trees. To fix this easily, I will use symlinks. This is what clients use

poudriere: Warning: Using ‘-‘ in a SETNAME is not recommended as it causes ambiguities with parsing the build name of 122amd64-default-master-list Read More »

suppressing motd on FreeBSD 13.0+

On one recent FreeBSD 13 host, I noticed a lack of motd. The MOTD (Message Of The Day) appears when you login. Typically, it looks like this: [dan@rose:~] $ r720 Last login: Mon Aug 2 00:30:13 2021 from air01.startpoint.vpn.unixathome.org FreeBSD 13.0-RELEASE-p3 (GENERIC) #0: Tue Jun 29 19:46:20 UTC 2021 Welcome to FreeBSD! Release Notes, Errata: https://www.FreeBSD.org/releases/ Security Advisories: https://www.FreeBSD.org/security/ FreeBSD Handbook: https://www.FreeBSD.org/handbook/ FreeBSD FAQ: https://www.FreeBSD.org/faq/ Questions List: https://lists.FreeBSD.org/mailman/listinfo/freebsd-questions/ FreeBSD Forums: https://forums.FreeBSD.org/ Documents installed

suppressing motd on FreeBSD 13.0+ Read More »

Fixing vulns in poudriere jails

This post was originally a few tweets. It’s not really about upgrading vulnerabilities in poudriere jails either. Read this as if each paragraph was a tweet. When a FreeBSD security alert comes out, or a package is marked as vulnerable, I try to get that fixed as soon as I can. Even if not using the feature. Sometimes a vuln can be leverages against something you are using. Patch it. When it comes

Fixing vulns in poudriere jails Read More »

Are all installed packages available for reinstall?

When you install a package, you want to know it’s still around to reinstall. You’ve probably never given this much thought. Neither had I, until I read this post on Reddit. In my case, I run my own poudriere server which allows me to run my own package server. Why run your own package server? build ports with non-default configuration settings: Want databases/mantis build for PostgreSQL, not MySQL? (and who wouldn’t?) – You

Are all installed packages available for reinstall? Read More »

Upgrading a FreeBSD 12.2 jail to FreeBSD 13 using mkjail

Mark Felder and I have been working on a minimalist set of jail scripts for creating and updating jails. All jail management is accomplished via standard vanilla FreeBSD jails. No jail managers are involved. Everything goes through jail.conf. In this post: FreeBSD 13.0 host, recently update from FreeBSD 12.2 FreeBSD 12.s jail on that host, about to be updated to FreeBSD 13 These jails were NOT created with mkjail Jails are mounted at

Upgrading a FreeBSD 12.2 jail to FreeBSD 13 using mkjail Read More »

Adjusting my ZFS filesystems to conform with standard FreeBSD boot environments

Get FreeBSD 12.2 mfsBSD (because that matches the OS on slocum), burn it to a thumb drive using OSX. NOTE: the following didn’t work. I wound up not having the right values in /lib and /var/db/ I don’t know what I did wrong, but I did manage to fix them up afterwards. I suspect that I still had zroot/usr mounted and did not notice. I will keep my notes here for future reference

Adjusting my ZFS filesystems to conform with standard FreeBSD boot environments Read More »

Updating my FreeBSD 12.2 host to FreeBSD 13.0

I am going to upgrade a FreeBSD 12.2 host to FreeBSD 13.0 with one reboot. Actually, here, because of the zpool update, there is another reboot. This is significantly fewer than the standard upgrade process (yeah, critics claim 1 is not significantly less than 2; sigh). The instructions are taken from vermaden’s blog post on Upgrade FreeBSD with ZFS Boot Environments. I have seen a couple of references to this post lately and

Updating my FreeBSD 12.2 host to FreeBSD 13.0 Read More »

Moving zroot/usr/local to zroot/usr

Today I was updating a FreeBSD server from 12.2 to 13.0 – I was using a new approach for my upgrades. This was my second host to upgrade like this. The first went smoothly. This one, not so much. NOTE: this turned out to be insufficient because /usr was mounted: [dan@slocum:~] $ zfs get canmount zroot/usr NAME PROPERTY VALUE SOURCE zroot/usr canmount on received This system was manually converted, poorly, to a BE

Moving zroot/usr/local to zroot/usr Read More »

snapshot ; ls ; destroy; dataset is busy – WTF?

I have found this bizarre situation where a FreeBSD 12.2 snapshot cannot be destroyed. This is the simple example, which works: [dan@pkg01:~] $ sudo zfs snapshot tank_fast/poudriere@snapshot-for-backup [dan@pkg01:~] $ sudo zfs destroy tank_fast/poudriere@snapshot-for-backup [dan@pkg01:~] $ This is the simple example, which fails: [dan@pkg01:~] $ sudo zfs snapshot tank_fast/poudriere@snapshot-for-backup [dan@pkg01:~] $ ls /usr/local/poudriere/.zfs/snapshot/snapshot-for-backup cache data jails ports [dan@pkg01:~] $ sudo zfs destroy tank_fast/poudriere@snapshot-for-backup cannot destroy snapshot tank_fast/poudriere@snapshot-for-backup: dataset is busy [dan@pkg01:~] $ EDIT: we

snapshot ; ls ; destroy; dataset is busy – WTF? Read More »

Scroll to Top