FreeBSD
..Graphics/Tiff & GCC 4.6.4
The latest (as of this writing) GCC port to FreeBSD 9.0 ended up creating some compile problems when I did a portupgrade -ra: /usr/ports/graphics/tiff
couldn’t find some libraries:
g++46: error: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/crtbeginS.o: No such file or directory g++46: error: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/crtendS.o: No such file or directory *** Error code 1
The problem is that there is no more 4.6.3 directory once you install 4.6.4. I didn’t bother debugging the port problem, though I probably should have and informed the port maintainer and all of those good citizenship steps but instead took a shortcut that solved the problem:
cd /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/ ln -s 4.6.4 4.6.3 cd /usr/ports/graphics/tiff make clean portupgrade -ra
And all is good.
math/fftw3:
If you get a “Variable CFLAGS is recursive.” error when doing a portupgrade -ra on freeBSD, it appears the make file is broken. “break19” debugged it in this post.
at line 64 change #CFLAGS+= to #CFLAGS:=
his fix worked for me.
OpenSSL 1.0.0_4 Install Issues
Updating my server’s install of OpenSSL on FreeBSD 8.1 to 1.0.0_4 (openssl-1.0.0c) I ran into a problem where some of the patch files had been updated but the distinfo file in /usr/ports/security/openssl hasn’t (hadn’t?) been updated to match.
The symptoms are that the update of OpenSSL fails with two errors:
- tls-extractor.patch line count is 1235, distinfo says 1234,
- dtls-sctp-20.patch SHA256 hash is wrong,
- (the tls-extractor.patch hash is wrong too, but the line count hits first).
- SHA256 (openssl-1.0.0c/tls-extractor.patch) = bb1aa486327fd96f9d6b870f0a1ad2c83dd4c06a96284eb64dde3f833ba5e0d0
- SIZE (openssl-1.0.0c/tls-extractor.patch) = 1234
- SHA256 (openssl-1.0.0c/dtls-sctp-20.patch) = 3b451618b64d7dbc917942759c26cbc717be3077e9d73cb3c5bd12a82a132268
+ SHA256 (openssl-1.0.0c/tls-extractor.patch) = b7dfb15b6ab7d62348eaa191fc8ba06565c92ecdd5d08bb5e9eb01a2e7433bb2
+ SIZE (openssl-1.0.0c/tls-extractor.patch) = 1235
+ SHA256 (openssl-1.0.0c/dtls-sctp-20.patch) = f002b13fead7c08270a9cfaf556be49c62be5b46f492ad59db29af4d3e9a4e67
Postie Image Resize Seems Broken
I updated Postie for the first time in many years, and it seems my fix for ImageMagick is now obsolete, but another fix may be necessary.
It may be that Postie just doesn’t like the FreeBSD environment. The ImageMagick fix was mostly to point Postie’s hard-coded targets to BSD standard locations. This time through I haven’t found the right code yet as postie-functions.php has been completely rewritten.
Updating an IBM 335
I’m bringing up an old IBM 335 for use as a pfSense Firewall. It is a fine computer, with almost everything you’d want except dual power supplies (the 336 has those plus 64 bit hardware).
The first step is updating the machine:
- BIOS to 1.16: download the flash image, it writes itself to a floppy, boot with that floppy and flash the BIOS. I had to go through a bunch of 1990’s era software disks until I found a few floppies that would format without errors. This also updates the LSI 1030 disk controller.
- Internal Diagnostics to 1.07: these are disk images (.img) diskcopy didn’t seem to do the right thing on my XP box, so I used diskwriter 0.9 to create the disks. You boot off the BIOS update disk then select update diagnostics.
- Configure the disks with ServeRAID. I didn’t flash the BIOS on the controller, but I did reformat the disks and set them up as RAID 1.
- Update the System Management Processor to 1.06. This is a self-booting floppy.
- Update the Broadcom NetXtreme NICs to 209h. This is a self-booting floppy that creates a RAM disk then runs the update. The command for the 335 is
UPDATE 8830
This gets the core hardware up to date. You might also want to flash the firmware in the disks, though I did not as my box is loaded with unsupported disks. Plus 36GB SCSI disks aren’t exactly going through a lot of teething pains these days.
Then I installed pfSense from the LiveCD (verify the hash). This is pretty effortless. The only important bit of data is to set up the NICs: in the 335 under FreeBSD bge0 is the lower port and bge1 is the upper port.
At a later date I will install a 73P9265 Remote Supervisor II adapater, but the cable I have (73P9312) is for newer boxes. The 335 needs the 02R1661: oddly it is cheaper to buy the cable with a card than just the cable. This will probably need flashing of the firmware, but is a nice tool with remote KVM and a lot of other slick features.
cannot connect to saslauthd
I recently ran some updates on my FreeBSD server and ran into a problem that resulted in the following error in /var/log/maillog
warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
The update process tends to kill saslauthd which will generally restart itself properly on reboot, but if you’re in the middle of a long rebuild and need to restore mail service quickly some or all of the following may help:
/etc/rc.d/inetd restart
/usr/local/libexec/courier-imap/imapd-ssl.rc stop
/usr/local/libexec/courier-imap/imapd-ssl.rc start
/usr/local/etc/rc.d/saslauthd stop
/usr/local/etc/rc.d/saslauthd start
In the years since, I’ve moved to Dovecot.