We’ve got a third year in Summer of Code!
The timeline shows about a week and a half for planning, and then student applications begin on the 29th of March, and run to April 9th.
If you want to participate as a student, start planning now by talking with people on IRC (#dragonflybsd on EFNet) or on the mailing lists. You cannot be over-prepared.
Simon ‘corecode’ Schubert’s host for DragonFly, chlamydia.fs.ei.tum.de, is down for good. Since it had excellent bandwidth, it was frequently used as the source for a lot of the DragonFly mirror sites out there.
If you were using it for your own mirror, switch to mirror-master.dragonflybsd.org, and tell Matthew Dillon at @dragonflybsd.org your contact info so you can be notified of changes. (If you’re not mirroring, please download from the nearest site that is.)
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.
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.
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 SSDs. Wear-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.
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.
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.
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 firstname.lastname@example.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.
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.
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.
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.
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.
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.
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.
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.
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.
The 2.4 release has been branched, and the release ISO should be available Wednesday.
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,
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.
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.)
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.
DevFS breaks vinum. Will it be fixed? Yes, hopefully very soon.
DevFS has been added. There’s some issues, each with a workaround. Please test, as it’s certain that a major change like this will cause new problems around video and sound. Once those are fixed, however, device management will be a lot easier.
The DevFS Summer of Code project is going into DragonFly this weekend; be ready for surprises if you update. It’s not complete yet; there’s a few more weeks for Summer of Code, but there’s other work that this code will enable.
The kernel option PCI_MAP_FIXUP has been removed as of July 11th; if you’re upgrading past that point, make sure to remove that option.
There’s going to be a lot of kernel structure changes this week, as Matthew Dillon works on making more system parts multiprocessor-safe. Rebuild everything including your kernel, if you’re running bleeding edge DragonFly.
Subversion isn’t being used for DragonFly, but it is available via pkgsrc. If you’re one of the people using it, the pkgsrc version has been updated to 1.6.2 which may have some upgrading issues.
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.
If you’re running bleeding-edge DragonFly, you’ll need to rebuild world and kernel after this recent change to interrupt counting from Sepherosa Ziehau.
Yonetani Tomokazu discovered a permissions problem under Hammer, so Matthew Dillon made a number of commits to fix this and other issues. An update for 2.2 will get them for you, and DragonFly 2.2.2 will be put together very soon so that there’s a release image with these fixed.
Peter Avalos has made major changes to DragonFly’s libc; you can look at the commits page or check out his git repo for details. If you are running 2.3, you will need to do a full buildworld on your next update.
You may also need to rebuild pkgsrc packages; I’m build a new binary set for 2.3 now.
If you’re a student with a Summer of Code application, make sure to subscribe to it. Doing this will ensure you are automatically notified of any mentor requests for more information.
There’s also some recent stats published by Google on the applications so far; DragonFly is one of the surveyed orgs it mentions, and the results are the same – less applications, better quality.
If you’re a potential student for Google’s Summer of Code, please get your application in ASAP. All student applications are due by 19:00 UTC April 3rd. You can revise a submitted application, even after the April 3rd cutoff, but it has to be in.
If you’re a student, you have from now until the 3rd of April to apply for a Summer of Code slot.
DragonFly BSD is a participating organization in Google’s Summer of Code 2009. (See the lists of participating organizations at the Google site.)
I have an announcement message with more details on the mailing lists; the next important date is the 23rd, when students can apply. If you’re a student, start putting your proposal together and talking with others. If you can mentor, sign yourself up on the Google site and request a mentoring spot.
Big news: Sepherosa Ziehau has managed to remove the Big Giant Lock from the ip and bridge forwarding path. This includes ipfw, though not yet pf. It is in fact possible to make the whole TCP/UDP code path BGL-free. Sepeherosa helpfully posted some benchmarks to show just how significant the improvements can be.
wiki.dragonflybsd.org has been set to be read-only, since the content has been moved to www.dragonflybsd.org. The site hasn’t been turned off yet, because I may have missed something in the move…
The iwi(4) firmware has been updated, and there’s an announcement that tells you where to find it.
If you are interested in the Google Summer of Code project, as a student, a mentor, or just want to suggest a project, write that down:
The application period starts for DragonFly (for the organization, not students) in a week, and it’ll help to see who wants to get in on the action.
Simon ‘corecode’ Schubert has some tips on how to mirror the git repo for DragonFly more exactly; there’s an additional command that can clean up spurious branches.
Sepherosa Ziehau has updated em(4) to version 6.9.6, with some interesting improvements. It does possible require loading a module now. He also has more patches to test.
A vulnerability in telnetd code common to FreeBSD and DragonFly was just discovered; it’s been fixed in DragonFly using code from NetBSD in 1995, strangely enough. (via #dragonflybsd on EFNet)
As Simon ‘corecode’ Schubert notes, DragonFly is now in a ‘Feature Freeze’ for two weeks. Please work on bug fixes in the intervening timeframe, and push them to the ‘master’ branch. Changes for the release will be pushed to the 2.2 release branch. Matthew Dillon has more details.
The ISC DHCP package in pkgsrc is changing as it moves from 4.0 to 4.1; the package names will be different, as will the rc flags. Keep an eye out for this if you use it for your internal network. (This may affect our install CD, too.)
Simon ‘corecode’ Schubert warns that a recent change in the size of struct thread is going to require a buildworld; this only affects people running DragonFly 2.1.
Matthew Dillon noticed that it is possible to have files on a Hammer volume marked ‘nohistory’ even when the volume they are on is retaining history details. He’s fixed the cause, and it will be in 2.0.1 soon. Check for this if you have a Hammer-based /usr/obj.
Somehow I missed this commit, but DragonFly 2.0.1 is out, with many changes to Hammer and other miscellaneous updates.
DragonFly 2.0.1 is going to be rolled this Wednesday, so if there’s anything you need in there, speak up.
As Matthew Dillon writes in a post to kernel@: “The kernel & modules are now being installed in /boot/kernel and /boot/modules instead of /kernel and /modules.”
This means do a full buildworld and installworld if you are using bleeding edge code; this is to clean up the correct files.
Sepherosa Ziehau has enabled intr_mpsafe for bleeding edge code; see his warning if this causes issues for you. Another step closer to removing the big lock from networking…
Read and go!Â Please use a mirror if possible.Â If you’re feeling torrentish, Christian Sturm has a BitTorrent link.
Do you run a mirror?Â Make sure you’re downloading the 2.0 release ISO.Â The release won’t officially happen until there’s enough ISOs floating around for people to actually reach it.
If you want to commit something for 2.0, do it now!
If you are so inclined, test 2.0 building with a ‘cd /usr/src/nrelease; make installer release‘
It’s been 5 years since Matthew Dillon announced DragonFly. Happy 5th birthday, us!
2.0 is going to be released on the 20th.Â If you’re committing, make sure to put it both in the 2.0 and 2.1 branches, please.Â And get it in quickly!Â If you’ve contributed changes to this release, please get them listed in the 2.0 release document that Matthias Schmidt has been conscientiously updating.
The 2.0 release of DragonFly will be on the 20th of this month.Â I’ll be working on a new set of pkgsrc packages to match.
Nuno Antunes has added experimental MPLS over Ethernet support.Â Note that this will require a complete rebuild if you are running bleeding-edge code.
A recent commit from Matthew Dillon improves HAMMER’s write performance, but introduces some potential stability problems.Â They should be solved in the next few days.
Matthew Dillon’s new statvfs() calls in the kernel require a full build/install process for world and kernel, if you are running bleeding edge code.
The 1.12.2 release is out; check the download page and the errata page for details on the changes that went into this minor release.
Matthew Dillon had another patch for his fairq code, adding changed prompted by Max Laier’s suggestion of WFQ, along with other ideas. There is one outstanding issue, however. The code causes an ABI change, so take extra steps if you aren’t doing a full buildworld/buildkernel.
The upstream network provider for dragonflybsd.org is going through some changes, so there may be occasional downtime for some weeks.
I’ll link to my mailing list post about it, as I’ve already summarized there.Â Student signup is the 24-31st of March, so start getting it together if you want to be involved as a student or mentor!
HEAD users will need to do a full buildworld/buildkernel because of Sepherosa Ziehau’s recent changes to ifnet.
Matthew Dillon is going to roll release 12.1 very soon, due to the discovery and fix of a Sendmail bug that can cause segfaults.
1.12 is being released Monday the 25th – test now!Â If something drastic comes up, Wednesday is the backup date.
Matthew Dillon found a memory corruption bug in sendmail; it is patched in the 1.12 release branch and in HEAD.
2.0 will be branched on the 9th and released on the 23rd of this month.Â If you have something you want in that release, hurry!Â HAMMER will be included in an alpha state.
Joerg Anslik found a strange error that turns out to have been a problem in handling floating point states; it’s fixed, but you will need to recompile kernel and libc_r if you are running bleeding edge code.
Simonm ‘corecode’ Schubert has slipped the Preview tag; those of you running 1.11-preview can update and get all recent changes.
Matthew Dillon warns of struct vattr changes being done to support his new filesystem, HAMMER.Â This may cause problems in userland, though of course this can only affect you if you are running the bleeding edge of code.
Apparently Softpedia thinks DragonFly is up to version 1.2 and is yet another Linux distribution. Plus, their DragonFly article would be an exact copy of the DragonFly website’s main page text, if it wasn’t for the errors they added. (via Sascha Wildner)
DragonFly has been updated to 1.10.1, solving a few recently found bugs.
Matthew Dillon found a problem in DragonFly with msdosfs mounts.Â He’s fixing it momentarily.
This is only a problem if you are running the very latest version of 1.11.
Sepherosa Ziehau is switching DragonFly from IPFW1 to IPFW2, which has the same rule syntax.Â Gergo Szakal helpfully pointed out that the differences between the two versions are listed in the IPFW man page under “IPFW2 ENHANCEMENTS”.
A bug in SMP virtual kernels has been fixed; the side effect is that if you are running bleeding edge code, you will need to recompile any SMP vkernels you are using.
1.10 has been released; check the page describing the release and then please use a mirror when downloading the ISO or updating your sources. The release page also has a list of the many changes in this version. Check the errata, as there’s a few small issues that remain within the installer.
Two warnings: the compatibility slice is changing, and disklabel is going through extensive changes.Â If you run bleeding-edge code, you will want to do a full rebuild.
Matthew Dillon has done some careful reworking of the disklabel system; it will require a full make buildworld and etc. process if you are running bleeding edge code and want to upgrade.Â Be careful!
Incidentally, this makes a dynamic /dev possible, for anyone wanting to put it together.Â Â Again, be careful!