Today on the show, we are going to be talking to Jim Brown (of BSD Cert Fame) about his home-brew sprinkler system… Wait for it… That runs FreeBSD!
That plus news & of course your feedback, keep it tuned to BSD Now, the place to B…SD!
– Show Notes: –
- Upgrading… The bane of any sysadmin! Distrowatch has recently done a write-up on the in-place upgrading of various distros / BSDs including PC-BSD and OpenBSD.
- Lets look first at the PC-BSD attempt, which was done going from 9.2 -> 10.
- Ouch! I’m not sure on the particular commands used, but to lose the boot-loader indicates something went horribly wrong. There is good news in this though. After the pain experienced in the 9.X upgrade process, 11.0 has been vastly improved to help fix this going forward. The updater is also self-updating, which means future changes to tools such as package can be accounted for in previously released versions.
- Moving on to OpenBSD, Jesse had much better luck:
- A good read, and they covered some Linux distros such as Mint and OpenMandriva as well, if you want to find out how they fared.
“I soon found trying to upgrade either the base system or pkg would fail. The update manager did not provide details as to what had gone wrong and so I decided to attempt a manual upgrade by following the FreeBSD Handbook as I had when performing a live upgrade of FreeBSD back in May. At first the manual process seemed to work, downloading the necessary patches for FreeBSD 10 and getting me to resolve conflicts between my existing configuration files and the new versions. Part way through, we are asked to reboot and then continue the upgrade process using the freebsd-update command utility. PC-BSD failed to reboot and, in fact, the boot loader no longer found any operating systems to run.”
“The documentation provided explains how to upgrade OpenBSD 5.8 to version 5.9 step-by-step and the instructions worked exactly as laid out. Upgrading requires two reboots, one to initiate the upgrade process and one to boot into the new version of OpenBSD. Upgrading the base operating system took approximately ten minutes, including the two reboots. Upgrading the third-party packages took another minute or two. The only quirk I ran into was that I had to manually update my repository mirror information to gain access to the new packages available for OpenBSD 5.9. If this step is not done, then the pkg_add package manager will continue to pull in packages from the old repository we set up for OpenBSD 5.8. “
- The website awesome-dtrace.com compiles a list of resources, including books, articles, videos, tools, and other resources, to help you get the most out of DTrace
- The list of books includes 2 open source books that are available on the web, and of course Brendan Gregg’s official DTrace book
- There are also cheat sheets, one-liner collections, and a set of DTrace war stories
- A breakdown of different PID providers and the userspace statically defined tracepoints
- The videos from DTrace.conf 2008, 2012, and soon 2016
- And links to the tools to start using DTrace with your favourite programming language, including Erlang, Node.JS, Perl, PHP, Python, or Ruby
- There are also DTrace setups for MySQL/MariaDB, and PostreSQL
- Joyent has even written a mod_usdt DTrace module for the Apache web server
- This seems like a really good resource, and with the efforts of the new OpenDTrace project, to modernize the dtracetoolkit and make it more useful across the different supported operating systems, there has never been a better time to start learning DTrace
- Have you found yourself needing to install OpenBSD from USB, but with a twist, as in no external monitor? Well somebody has and asked the question on stackexchange.
- The answer provided is quite well explained, but in a nut-shell the process involves downloading the USB image and making some tweaks before copying it to the physical media.
- Specifically with a couple of well-placed echo’s into boot.conf, the serial-port can be enabled and ready for use:
echo “stty com0 115200” > /mnt/etc/boot.conf
echo “set tty com0” >> /mnt/etc/boot.conf
+ After that, simply boot the box and you are ready to access the serial console and drive the installation as normal! #bsdhacks
- The NetBSD blog provides a status report on one of the GSoC projects that is nearing its midterm evaluation
- The project to split debugging data into separate pkgsrc packages, so that users can install the debugging symbols if they need them to debug a failing application
- The report is very detailed, and includes “A quick introduction to ELF and how debug information are stored/stripped off”
- It walks through the process of writing a simple example application, compiling it, and dealing with the debug data
- It includes a number of very useful diagrams, and a summary of what changes needed to be make to the pkgsrc makefile infrastructure
- With this as a recipe, someone should be able to do something quite similar for FreeBSD’s ports tree
- iXsystems’ TrueNAS Firmware Update Delivers Compelling Performance, Replication, and Graphing Improvements
Interview – Jim Brown – email@example.com
FreeBSD+BBB Sprinkler System
- A paper by by Douglas McIlroy
- “Selected pages from the nine research editions of the UNIX® Programmer’s Manual illustrate the development of the system”
- “Accompanying commentary recounts some of the needs, events, and individual contributions that shaped this evolution.”
- Interesting insight into the evolution of the origin UNIX operating system
- From the author of the recent post we covered, “20 years of NetBSD code bloat”, comes a new post
- “I found a recent paper that also looks at how the BSD code base has evolved, but from a very different perspective compared to my code-size investigation.”
- The paper “The Evolution of C Programming Practices: A Study of the Unix Operating System 1973–2015” investigates coding style, and tests seven hypotheses by looking at metrics (line length, number of volatile in the source code, etc.) in 66 releases of Unix from 1973 to 2014. The hypotheses are:
- Programming practices reflect technology affordances (e.g. developers may be more liberal with screen space when using high resolution displays)
- Modularity increases with code size
- New language features are increasingly used to saturation point
- Programmers trust the compiler for register allocation
- Code formatting practices converge to a common standard
- Software complexity evolution follows self correction feedback mechanisms
- Code readability increases
- and the result is that they seem to be true, as interpreted through the metrics.
“The data points for the releases have somewhat random dates. One issue is that the paper use each release’s mean file date (the average of the files’ last modification time) instead of the release date (that is why the graphs stop at November 2010, even though FreeBSD 10 was released in 2014). The idea is that this better reflects the age of the code base, but this has the effect of compressing some of the data points (especially the clustering around 1993-1994), and it makes the spline fitting even more suspect.”
“One other problem is that the original data used by the researchers seems to have incorrect timestamps. For example, 4.3BSD Net/1 was released in 1989, but is listed as 1993-12-25 in the paper. The same is true for at least the Net/2 release too, which was released in 1991, but the paper list it as 1993-07-02.”
[old release pictures]
- openbsd 2.1 – 5.9, straight from theo’s bookshelf.
- Speaking of old releases, our Producer JT picked up this gem at Southeast Linuxfest this year
- Noah Axon shares a scan of his NetBSD 1.4 disc
- Jan van den broek shares a pic of his FreeBSD 2.2.5 set
- Another BSDMag goodie this week, we have a small article written by Jonathan Garrido
which details their experience switching to FreeBSD for a NTP server.
- The article is short, but a good read:
“A Few years ago we had a time problem. Suddenly our linux NTP server, for a reason that I still do not know, started to fail giving us a lot of issues within all the equipment and services within our network. After a quick and brief meeting with management, I found out that there was not sufficient budget left for a fancy and well-suited appliance. So, with no time (literally) and no money to spend, I decided to give it a try and utilized a homemade open source solution, and the operating system of choice was FreeBSD 10.0.”
“Now, let’s pause for a second. You may be thinking, why in the world is this guy doing this, when he has never installed a BSD machine in his life? The answer is very simple; here, in the Dominican Republic, in the heart of the Caribbean, FreeBSD has a very good reputation when it comes to reliability and security. In fact, there is some collective thought within the sysadmin community that says something like: “If you want to deal only once with a service, install it over FreeBSD.””
- Jonathan then goes through some of the steps taken to initial deploy NTP services, but with that out of the way, he has a great summary:
“Fascinated with the whole experience, we migrate one of our internal dns servers to a second FreeBSD machine and at the moment of this writing we are testing haproxy, an open source load-balancing proxy into a another server with the same OS.
After all this, no time issues have been reported in the past 2 years, so at least for my environment, FreeBSD came just in time.“
- Harri – Using beadm / zfssnap
- Jonathan – bhyve vs Proxmox
- Mohammad – Bhyve gfx passthrough
- Jeremy – Shapshots and more Snapshots
- Ron – Microphone
- Send questions, comments, show ideas/topics, or stories you want mentioned on the show to firstname.lastname@example.org