Archive for the Heads Up! Category

02/21/2010
Get ready for 2.6

The next release, 2.6, is scheduled for mid-March.  Please make sure things are running well, as there’s a lot of new features already ready for this release.

02/09/2010
Outage Wednesday

Most of the dragonflybsd.org machines will be down for a short period Wednesday; this is for an upgrade that includes an SSD for the recent swapcache work.  Everyone should notice a speedup, since while crater.dragonflybsd.org is getting the SSD/swapcache, a lot of crater’s directories are mounted on other machines via NFS.

02/05/2010
Cache-data-as-swap project started

Matthew Dillon is setting up DragonFly to be able to use a fast disk (like a SSD) for disk cache, reducing the effect swap has on speed.  This means very large amounts of data could be read into memory – greater than the available RAM in the system – without having the normal paging out problems that happen when memory is exhausted.   It’ll work for any filesystem on the machine – HAMMER, UFS, or NFS.  His inital notes have more.  Other notes include details on the NFS benefits, and possibilities with SSDsWear-leveling may make SSDs last much longer.

Work has started, and there’s an update (with examples) that people can try, though it may destroy all your data at this point.  Test results in that update show, if I’m reading it right, a better than doubling of speed on a repeated md5 test on a large file when using the new caching system.  This should be a huge benefit.

01/23/2010
Watch out on the bleeding edge with UFS

If you’re running DragonFly 2.5 and updated in the past week or so, and have UFS disks, there’s some instability introduced by Matthew Dillon’s recent work.  It ought to be better by next week.

Users of Hammer, or of UFS only as /boot, don’t have anything to worry about.

01/06/2010
Hammer downgrade and upgrade bug

Thomas Nikolajsen experienced firsthand a bug where downgrading a Hammer PFS master to a slave and then later making it a master again lost all data.  Lucky him…   The problem’s now fixed.

01/02/2010
Update for spamassassin

This has been bouncing around other news outlets, but I’ll mention it here: There’s an out of data SpamAssassin rule that can potentially mark mail as spam because of the 2010 date.  A mail to tech-pkg@netbsd.org describes the various fixes.

The step of ’sa-update && /etc/rc.d/spamd restart’ seems to have fixed it for me.  Incidentally, if you are using SpamAssassin, sa-update is a good tool to run on a regular basis.

12/28/2009
Multiprocessor work so far

Matthew Dillon is working on moving more of DragonFly out from under the Giant Lock.  This may mean some instability this week if you’re following the bleeding-edge.  He’s already posted a warning and an explanation (with numbers!) of work already completed.

12/15/2009
Time for a buildkernel

If you’re running DragonFly 2.5, Matthew Dillon has changed thread and process structures, meaning that a full rebuild of  kernel and modules is necessary on the next system update.

11/16/2009
Default SSH change

SSH, on DragonFly, now defaults to allowing root logins, but does not allow plaintext password logins.  This is on new installs only, so any existing installations won’t be affected, even after upgrades.  Plaintext passwords are under constant brute-force attack for some years now, so this is probably safer.

10/29/2009
Dragonflybsd.org down today and tomorrow

It’ll be sporadic.

10/28/2009
dragonflybsd.org downtime

dragonflybsd.org will be going down for work somewhere in the next two weeks.  The package archive at avalon.dragonflybsd.org is located elsewhere, so pkg_radd and similar programs will still work.

10/01/2009
DragonFly 2.4.1 released

DragonFly 2.4.1 has been released; this is recommended for any users of 2.4.0, as there’s a lot of little bugfixes.  (Check the tag list to see all the fixes.)  Next time, we may make a release candidate first.

09/27/2009
2.4.1 in a few days

DragonFly 2.4.1 is slated for release this Wednesday, 2009-09-30.  This will have fixes for the installer and 64-bit DragonFly, among other things.

09/19/2009
Watch out for WARNS_WERROR

WARNS_WERROR has been turned on, for i386 and for amd64 builds. This means that warnings will halt a build just like an error.  This should mean that the number of warnings from DragonFly source (already lower because of Sasha Wildner’s efforts, among others) should only decrease from now on.

09/16/2009
2.4 released

The 2.4 release of DragonFly is out.  This is a major release, with a lot of new features packed in, so read the release notes carefully.  There’s a 64-bit experimental version, too

By the way, please use a mirror.  Avalon is a good one, as is chlamydia.

Updating steps I used after the cut.

Continue Reading “2.4 released” »

09/15/2009
Release imminent

The 2.4 release has been branched, and the release ISO should be available Wednesday.

09/08/2009
Watch your step until 2.4

The 2.4 release looks to be about a week and a half away; if you’re a  committer, please plan to make drastic changes after the release, if possible,

08/30/2009
Update libtiff if it’s 3.9.0

The libtiff package has been found to write out incorrect TIFF files in version 3.9.0.  If that’s what is installed on your system, please update now.

08/24/2009
GCC 3.4, kerberos 5 removed from base

Simon ‘corecode’ Schubert has removed GCC 3.4 and Kerberos 5/Heimdal from the base system.  Kerberos hasn’t been building as part of base for a while, and is available in pkgsrc.  It was also the last item that requires GCC 3.4, so buildworlds are little quicker now.  (Cross your fingers that GCC 4.2 the current version doesn’t break somehow.)

08/12/2009
GCC 4.4. and NO_GCC44

As Hasso Tepper pointed out, having GCC 4.4 in DragonFly is unique to DragonFly.  Systems like pkgsrc don’t work due to the changes in headers and etc. between gcc 4.2 and 4.4, and since no other BSD uses gcc 4.4, the fixes would all have to come from DragonFly (and be backward compatible).  This is unlikely to change in the near term, since this newer version of gcc is being refused due to the V3 GNU Public License, not a technical issue.    It’ll stay in DragonFly for now.

However, you can specifically exclude it and speed up buildworlds with the new NO_GCC44 option.    It’s also possible to use NO_GCC34 in make.conf to keep the old version of gcc from building, for those who don’t like to wait.