Subversion hosting, CVS hosting, Trac hosting, Bugzilla hosting and software collaboration Providing hosted Subversion, CVS, Trac and Bugzilla repositories

June 15, 2009

Broken-Hearted Ports

Filed under: Operating Systems — Tags: , , — Greg Larkin @ 10:07 am

Hi everyone,

As I’ve been writing over the past couple of weeks, there are a large number of FreeBSD ports that are unmaintained and would benefit greatly from a new maintainer. Today, we’ll visit with a particularly tragic strain of port:

Unmaintained and BROKEN!

Bill Fenner sends out a periodic automated email to the freebsd-ports mailing list with links to ports that do not build:

This is a useful page for any port maintainer to visit periodically to make sure all of his/her ports are humming along. If a port remainis unbuildable for too long, portmgr will likely mark it BROKEN after a while, and if it stays BROKEN too long, it will be removed from the tree.

The problem is that when a port is unmaintained, it’s likely that no one will notice that it doesn’t build, and it won’t be fixed in time to save it from removal. One place to start if you’re interested in adopting a port is the page detailing unmaintained ports that are broken on one or more platforms:

There are many different reasons that ports refuse to build, including (sample log follows each):

  • Unfetchable upstream distribution files (log)
  • GNU configure errors (log)
  • Compiler/linker errors (log)
  • Package building problems (log)

Fixing a broken port may be as easy as correcting a download URL or as complex as patching source code so it builds correctly on the AMD64 platform. There are many different ways to get your feet wet, so I encourage you to check some of the broken build log files and see if you can fix, and possibly adopt, one of these ports!

Call me - Greg Larkin: error

June 12, 2009

The Top Five Categories of FreeBSD Unmaintained Ports

Filed under: Operating Systems — Tags: , , — Greg Larkin @ 7:13 pm

Greetings all,

I’m here with some more statistics about the FreeBSD ports tree and the unmaintained ports in it. Today, I calculated the top five categories with the largest number of unmaintained ports in each:

Category Unmaintained Ports Sample Ports
devel 461 ace
games 381 gnomesudoku
textproc 352 diffutils
graphics 298 Coin
audio 245 icecast

There is a huge variety of software to explore in the ports tree, and if you’re interested in maintaining one or more ports, I suggest looking for something you’ve already used in the past or a piece of software in your area of interest.  For instance, there are a number of astronomy and biology-related ports that could use some help!

Another great place to find ports that need some help, be it maintainership or submitting PRs to fix them, is the pointyhat build cluster status page:

If you’re just getting your feet wet and don’t know where to start, subscribe to the freebsd-ports mailing list or browse its archives. You’ll find a lot of questions and solutions to common problems as you learn more about the ports infrastructure.

Call me - Greg Larkin: error

June 11, 2009

The Most Unloved FreeBSD Port of All

Filed under: Operating Systems — Tags: , , — Greg Larkin @ 6:02 pm

Hi everyone,

To prepare for the upcoming inaugural International FreeBSD Adopt-A-Port Day on June 15th, 2009, I am publishing some interesting (???) statistics about the FreeBSD ports tree.

First up (cue the violins): The most unloved FreeBSD port!

This port has been a workhorse since the year 1996, back in the days before the Internet you now know, when a fast connection was 56k and we often disabled image loading in our browsers to speed up the browser! Those days, there were fewer than 500 ports in the tree, a far cry from the 20,000+ we now enjoy.

And now, I give you (drumroll, please)….


The CVS log shows that this port has been unmaintained since 17-Nov-96, so it’s been nearly 13 years that ghostview has been wandering aimlessly through the tree, waiting for someone to adopt her/him/it. The ghostview port won’t require a lot of care and feeding, but if a new upstream version is released, the port would like a FreeBSD maintainer that will submit a PR to keep it in sync.

So, wouldn’t you like to help a port regain its standing in the tree and become all that it can be and more? Contact me at to get involved and help out!

Call me - Greg Larkin: error

June 4, 2009

Congratulations to Martin Wilke And Ion-Mihai Tetcu!

Filed under: Misc — Tags: — Greg Larkin @ 3:29 pm

FreeBSD developers know Martin Wilke (miwi@) and Ion-Mihai Tetcu (itetcu@) and their dedication to the success of the project. Martin is the top committer to the ports tree as well as a member of the Security Team, and Ion-Mihai is the creator of the much-revered “QA Tindy” to keep the committers on their toes and improve the overall quality of the ports tree.

Martin and Ion-Mihai have just been honored as the newest portmgrs. Congratulations, Martin and Ion-Mihai, and thank you for your help to me and all other port maintainers and committers as we learned (and continue to learn) the ropes!

Call me - Greg Larkin: error

International FreeBSD Adopt-A-Port Day 2009

Filed under: Operating Systems — Tags: , , — Greg Larkin @ 11:43 am

Hi everyone,

Just for fun, let’s designate June 15th as the inaugural International FreeBSD Adopt-A-Port Day for 2009!

My colleague and co-mentor to Alexander Logvinov, Thomas Abthorpe, posted to the freebsd-ports mailing list in March looking for folks to adopt unmaintained FreeBSD ports and keep them up to date.

I’d like to continue Thomas’ effort and find out who in the FreeBSD community is interested in taking on one or more unmaintained ports. Some current stats:

FreeBSD ports info page (20325 total ports as of June 4th, 2009)

FreeBSD unmaintained port list (4719 as of June 4th, 2009, 77 with build errors)

FreeBSD unmaintained ports that need upgrading (253 as of June 4th, 2009)

If you are interested in maintaining a port, contributing PRs for port upgrades, and perhaps eventually becoming a ports committer, read the following documents to get a good overview of the process:

I started my own path to becoming a FreeBSD ports tree committer by discovering that a web application (WebCalendar) that we use at was not part of the tree.  I read up on how to create a new port, submitted a PR for it, and after review by an existing FreeBSD committer, it was added to the tree.  Now other WebCalendar users can install it on FreeBSD as easily as typing:

cd /usr/ports/www/webcalendar && make install clean

After a port is added to the tree, a maintainer keeps track of upstream package releases, updates the port to track the new version, adds any needed configuration options and makes sure that it builds and installs on the FreeBSD supported platforms. As payback, you’ll often hear from folks using your port, whether sending thanks, enhancement requests or the occasional bug report!

Since submitting that first PR, I have created a number of new ports for tools used at or just in my areas of interest.  I have adopted many as well. Most unmaintained ports are very undemanding and just need some minor TLC! It’s a great way to support a project that has contributed directly to the success of my Real Job.

Have any questions or guidance? Email me at, follow me on Twitter or comment here. We’d love to work with you!

Call me - Greg Larkin: error

December 2, 2008

FreeBSD 8.0-CURRENT I386 (200810 Snapshot) Virtual Appliance Now Available

Filed under: Operating Systems — Tags: , , — Greg Larkin @ 6:27 pm

Hi everyone,

To go along with the FreeBSD 8.0-CURRENT amd64 virtual appliance I released a few days ago, I’ve also prepared one for the i386 architecture.

Get the virtual appliance here: FreeBSD 8.0-CURRENT i386 virtual appliance

As always, comments and feedback to is welcome. Enjoy!

Call me - Greg Larkin: error

December 1, 2008

FreeBSD 8.0-CURRENT Amd64 (200810 Snapshot) Virtual Appliance Now Available

Filed under: Operating Systems — Tags: , , — Greg Larkin @ 12:13 pm

Hi everyone,

Do you want to experience FreeBSD on the cutting edge without devoting a brand-new piece of hardware to it? You can test out the latest and greatest FreeBSD bits by downloading the FreeBSD 8.0 amd64 virtual appliance.

You’ll need a BitTorrent client, and once the download has completed, you’ll have a .ova file. This is a self-contained virtual appliance running FreeBSD 8.0-CURRENT amd64, and you can either import it directly into certain VMware products (e.g. VMware Workstation, VMware Player 2.x) or use VMware Converter to convert it into virtual machine format for use within VMware Server 1.x and other products that don’t read .ova files directly.

FreeBSD amd64 doesn’t actually require an AMD CPU to run as long as the specific Intel CPU is the correct architecture. Check for supported CPUs on the FreeBSD amd64 project page.

The virtual appliance’s root password is “password” and a minimal number of services and packages are installed. The virtual appliance is perfect for experimentation and testing, and please send any feedback or questions about it to


Call me - Greg Larkin: error

November 26, 2008

Graphical Display of Subversion Repository Revision History in Trac

Filed under: Source Code Control — Tags: , , , — Greg Larkin @ 8:15 pm

Hi everyone,

Once again, I bring you another useful Subversion-related tool. This time, I recently discovered a Trac plugin named RevtreePlugin. If you want to display your Subversion branches and revisions graphically inside of Trac, this is the plugin for you!

As I’ve noted before, I’m a FreeBSD ports tree committer now, so I absolutely had to build a port for this plugin. You can find the details of the port in FreshPorts, and if you’re using FreeBSD (you are, aren’t you?), install it like so:

cd /usr/ports/www/trac-revtree && make install clean

You will be presented with some options to enable some display enhancers. Make sure to enable the mergeinfo enhancer, and you’ll see some interesting graphs if you’ve been merging a lot.

Happy Thanksgiving!

Call me - Greg Larkin: error

October 28, 2008

FreeBSD And Amazon EC2 – Register Your Support!

Filed under: Operating Systems — Tags: , , , — Greg Larkin @ 3:49 pm

Hi everyone,

I caught a posting on Colin Percival’s (FreeBSD Security Officer) blog the other day: 

Like me, he wants to get FreeBSD running on Amazon EC2 and needs your help with funding and to register support for the project with Amazon.  Who knows, if enough people want to use FreeBSD on EC2, Amazon may decide it’s worth funding the development themselves!

If you want to help out with the project, contact Colin directly.

Call me - Greg Larkin: error

August 4, 2008

Host CPU Frequency Control And Too-Fast Guest Clocks

Filed under: Operating Systems — Tags: , , — Greg Larkin @ 5:23 pm

Hi everyone,

Every now and again, a strange problem crops up with VMware Server. In this case, the VMs on one host began running with a very fast clock, even though the .vmx files contained the following line:

tools.syncTime = "TRUE"

Apparently, this setting helps keep the VM clock from slowing down too much, but it doesn’t do much when it’s going 1.5x faster than it should – whoa, Nelly! Running ntpdate every few seconds showed the clock resetting backwards 5-10 seconds each time. That’s going to play havoc with everything – log file messages, email timestamps, Makefiles and many other things.

I searched around Google for solutions, and 99% of the posts say “set kern.hz=100 in your /boot/loader.conf for a FreeBSD guest OS“. That’s great if your clock is slow, but it doesn’t fix this problem. A quick check showed that I had already added that setting a long time ago.

After more and more in-depth searching, a solution emerged. The host OS is RHEL4, and it enables CPU frequency scaling by default with the cpuspeed service. The idea behind this service is great, as it saves power, but it just wrecks the VMware timekeeping accuracy. Disabling the service fixes the problem for good:

# /etc/rc.d/init.d/cpuspeed stop
# cd /etc/rc.d/init.d/
# /sbin/chkconfig --del cpuspeed


One final problem – the VM clock still runs fast until you reboot the host and the VMs on it. To get around the problem temporarily if you are running a high-availability service, add the following lines to your VM /etc/crontab file:

*/5 * * * * root /usr/sbin/ntpdate -s

I hope this posting makes the solution easier for someone else to find in the future!

Call me - Greg Larkin: error
Pages: 1 2 3 Next

Powered by WordPress