I’m removing the links for the old (DragonFly 2.3 and older) pkg_radd paths on avalon.dragonflybsd.org. If you have one of those older systems, you can update one line in pkg_radd if it’s useful to you.
As previously foreshadowed, BIND has been removed from the DragonFly base system. Instead, it’s installed from pkgsrc. Note that this includes tools like nslookup or host. Instructions after the jump.
From my email to users@:
- I almost have pkgsrc-2010Q1 builds done for every architecture, so I’ll point the default load location for pkg_radd to them within the next 24 hours.
- Are you still using a DragonFly system older than 2.4 and downloading binaries? If so, tell me.
- A project: enhancing pkg_search and pkg_radd to be able to tell when a package is missing because of license restrictions. Anyone want to try it?
If you use Apache, as many people do, some of the default building choices have changed in pkgsrc. Read Matthias Scheler’s post for details.
Matthew Dillon identified a possible data corruption bug in Hammer with a nearly-full filesystem. It’s dramatic enough he’s tagged 2.6.2 and 2.7.2 so that people can update; his message about it describes how to check for corruption.
The naming convention for the daily snapshots of DragonFly has changed, to make the file names more readable. This may lead to some confusion as the mirrors settle, but it’ll pan out. If you run a mirror, double-check your downloads.
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 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.
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.
It’ll be sporadic.
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.