Open Source

Making my pkg.conf configuration version independent

In this post, I will talk about how I modified my pkg configuration so I don’t have to modify it after upgrading a host/jail from one version of FreeBSD to another. You might say that you don’t have to do that. Perhaps you have a different configuration and aren’t doing what I’m doing. HEADS UP: I hit a problem with this approach when updating a jail using mkjail: see https://github.com/mkjail/mkjail/issues/30 In this post: […]

Making my pkg.conf configuration version independent Read More »

freebsd-update fetch install -> Cowardly refusing to proceed any further.

Today I encountered this. [r720-01 dan ~] % sudo freebsd-update fetch install 14:39:01 Looking up update.FreeBSD.org mirrors… 2 mirrors found. Fetching metadata signature for 13.0-RELEASE from update1.freebsd.org… done. Fetching metadata index… done. The update metadata is correctly signed, but failed an integrity check. Cowardly refusing to proceed any further. I confirmed it was just the fetch portion. [r720-01 dan ~] % sudo freebsd-update fetch 14:42:08 Looking up update.FreeBSD.org mirrors… 2 mirrors found. Fetching

freebsd-update fetch install -> Cowardly refusing to proceed any further. Read More »

Monitoring FreeBSD jails from the host

It was May 2021 when I tweeted about monitoring FreeBSD jails which had jail IP addresses only in the 127.0.0.0/8 range. Yesterday, nearly 6 months later, I did the first test of this. This came up because I’m getting a new FreshPorts node ready. I’ve created a file in the jail to be run from the host. That script runs in the jail but it initiated by a process on the host. In

Monitoring FreeBSD jails from the host Read More »

Turning off SASLCLIENT for databases/mysql57-client

This started off as a Twitter thread earlier this morning. databases/mysql57-client has an optional dependency on security/cyrus-sasl2 which defaults to on. Let’s try turning that off and see if it also removes openldap-client from the dependency list. Why? I install net-mgmt/nagios-plugins in just above every jail and host. Even hosts which don’t use MySQL. I use poudriere to build all my own packages. I added this entry: # Trying to avoid pulling in

Turning off SASLCLIENT for databases/mysql57-client Read More »

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 »

Running net/mosquitto on FreeBSD as non-root and with a different pidfile

net/mosquitto is an open source (BSD licensed) message broker that implements the MQ Telemetry Transport (MQTT) protocol. I use it for event notification. Related posts: mosquitto: upgrade from 1.x to 2.x requires configuration changes to keep working Using mtqq to create a notification network: mosquitto, mqttwarn, hare, and hared Installing Owntracks recorder on FreeBSD In this post: FreeBSD 13 mosquitto 2.0.10 My configuration Here is what I have in my /etc/rc.conf related to

Running net/mosquitto on FreeBSD as non-root and with a different pidfile 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 »

Accessing a Dell iDRAC 7 via Nginx reverse proxy

HEADS UP: this is still under review. Until this notice is removed, I recommend not using this. I have a Dell R720 at an ISP. The iDRAC connection is filtered, by the ISP, and is accessible only from a small number of IP addresses. Sure, this talks about a web proxy. It works. So does the ssh forwarding shown at the bottom of this post. NOTE: I should start monitoring that IP addr

Accessing a Dell iDRAC 7 via Nginx reverse proxy Read More »

Scroll to Top