Goals for DragonFly

This blog post talks about the identified reasons Ubuntu has been so successful in growth over the past few years.  The post uses it as a comparison to Perl, but it holds some lessons for DragonFly.  Some items we have now – a Live CD, simple install, regular release schedule – and they’ve been very useful.

On the other hand, the available applications is something that can improve – as nice as it it to build from source, immediate installation of binaries is best.  Heck, some companies base their business around it.  Pkgsrc is getting closer to creating an “app store” for DragonFly.  We’ve got a civil community, but I’d like to figure out ways to make it even more accessible.

(Nobody mentions this when talking about Ubuntu’s success, but having a large, privately-funded company backing your open source project also helps.)

While on the subject, I would love to have a job like Jono Bacon’s.  He works with all the issues that I think about.

Bulk build speed stats

I recently did a bulk build of pkgsrc on two similar machines; the only significant difference being extra CPU work being done on one system, and Hammer snapshots on the other.  However, they’re diverging in speed over time, which is interesting but not yet conclusive.  Read my post about it for more details.

A good benchmarking project would be testing Hammer with snapshots on and with snapshots off.

Upcoming pkgsrc freeze; new binaries now

The freeze for pkgsrc’s 2009Q2 release starts this Sunday, the 14th.   The 2009Q2 release should follow two weeks afterwards, which will be very close to the time of the next planned DragonFly release.  (2.4, in case you weren’t counting.)

I’ve just finished a new build of the 2009Q1 packages for DragonFly 2.2, and it’s available on http://avalon.dragonflybsd.org/packages – setting BINPKG_SITES or using pkg_chk can get you these latest versions.

I plan to have a 2009Q2 package set for DragonFly 2.4 as soon as possible after release.

2 separate bugs: threading, Xorg

Hasso Tepper has a “BIG FAT WARNING” about two new issues: threaded programs are broken on bleeding-edge DragonFly because of a possible GCC bug that was only recently exposed, and Xorg in pkgsrc has issues with the Intel driver.

Simon ‘corecode’ Schubert already has one change in that may fix the issue with threaded programs, and is working on the Intel driver issue.

Update: more threading changes.

xorg updates for testing

Hasso Tepper has some xorg updates to fix problems he’s seen with the intel video driver.  The versions of these packages in pkgsrc are old enough that the changes can’t be committed ‘upstream’ to xorg, so he’s attacking the problem from the opposite direction and upgrading the software.

He reported significant EXA performance improvements, so it’s definitely worthwhile.  It’s tested on DragonFly but will probably benefit other pkgsrc-using platforms too.

pkg_dry usage and updates

Antonio Huete Jimenez wrote up his experiences using pkg_dry on DragonFly, which were mostly successful.

He followed up with a script that takes care of the initial setup for pkg_dry, and noted that following pkg_dry in CVS is the best idea at this point, as it’s going through rapid development.

It should be possible to point pkg_dry at  pkgbox.dragonflybsd.org or one of the mirrors, and perform binary-only remote installs and upgrades of pkgsrc packages.

New pkgsrc tool: pkg_dry

There’s a new tool being put together for pkgsrc installation and management, called pkg_dry.  There’s an initial version for download with instructions from its creator, Emile “iMil” Heitor.  It looks to duplicate the functionality of apt-get or yum, by handling binary-only remote package management.

Someone please test this on DragonFly, though not on a production machine…  If it does end up matching apt-get (the only thing I like in Debian) in terms of functionality, that will be fantastic!  I have wanted something like this for a while.