DragonFly and Summer of Code, week 7

Everyone passed their Summer of Code midterms!  Not that this was a surprise; all the students have been consistently working and overcoming problems, but a 100% pass rate makes me happy.

Here’s the status reports:

Lazy Reading for 2013/08/04

These have been very easy to create over the last few weeks; there’s been a torrent of reading.  Can I say torrent without making it sound like this is all downloaded large files?  The word is overloaded.  Anyway:

Your unrelated link of the week: What goes on when you are not there!

In Other BSDs for 2013/08/03

How many tags can I fit on this post?  I think I’ll aim for Saturday for these BSD catchup posts.  In theory, I can prep this and the Sunday Lazy Reading posts ahead of time, since they tend to be all-week items, and have the whole weekend covered.

 

Google Summer of Code Doc Camp

Every year, people ask “Why can’t writing documentation be part of Summer of Code?”  (Not necessarily for DragonFly, but in general)  Google has a “Doc Camp”, where a whole lot of documentation gets produced in sprints, and anyone can participate – not just Summer of Code students.

If this sounds interesting to you, your application has to be in by August 7th 9th.  (URL and date updated)

My dports upgrade experience

Since there’s a newer set of dports binary packages uploaded, I thought I’d spend my weekend upgrading, to catch up.

‘pkg upgrade’

And that was it.  Well, not really.  I had to dump and restore my Postgres databases, cause of the switch from 9.0 to 9.2 as default.  I had to build php5 from source to get the Apache module.  Those two things together took longer than the entire download and upgrade of the rest of my system – some ~200 packages?

Lazy Reading for 2013/07/28

So many links came up recently that I had already finished this week’s entry when last week’s Lazy Reading was posted.

Your unrelated link of the week: Release the Kraken!

About dports, packages, and servers

In part of a long thread about dports packages on the users@ list, Matthew Dillon notes that a new set of packages for i386 and x86_64, for 3.4 and for “3.6” (meaning bleeding-edge DragonFly, even though that’s numbered 3.5) is mostly uploaded.  He also notes that a Haswell-processor-based blade server for DragonFly is in the works, so much of the dragonflybsd.org infrastructure is going to move from his house to a datacenter, with the benefits that provides.  It’ll also help automate binary package building.

In Other BSDs summary

Here’s what jumped out at me from reading source change mailing lists:

I’m going to have to set a specific day of the week aside for these.