wiki.dragonflybsd.org is down, along with gobsd.com. The wiki was on a separate server from the rest of dragonflybsd.org, so the rest of the domain is fine, but there’s currently no details on when the wiki will be running again, as the hosting company has apparently taken the server offline.
With some final changes, version 1.4.4 is available now. This is the recommended download/update for everyone. (Including me, so I’ll have to update tonight.)
Matthew Dillon’s merged a heap of bugfixes from the current code back into the 1.4 release branch; the update to 1.4.4 won’t happen until Friday, however.
Matthew Dillon has moved the Preview release to 1.5.3, as it’s stable enough for more testing. In addition, Release is moving to 1.4.4 in about a week to incorporate recent fixes; details are in his post.
As Matthew Dillon and others have described, if you install the latest bleeding-edge code (1.5) of DragonFly, there is a bug in the installer. To keep from being bit, first log in as ‘root’ and type:
ln -s a /etc/malloc.conf
Then log out and log in as ‘installer’ and proceed normally.
The release version of DragonFly has been brought to 1.4.3 to incorporate the recent Sendmail security update, among other things. Bleeding edge code has been brought up to version 1.5.2, because Matthew Dillon has added (after the bump) his potentially destabilizing BUF/BIO code. If you like running Preview, update and plan to stick with it a while until this new technology gets sorted out.
My house was robbed today; I lost my desktop computer, among other things. Not surprisingly, posting here may be slow for a little while…
Matthew Dillon has issued a warning: HEAD (the bleeding edge code) is currently very stable. Update now, for it’s going to become pretty unstable soon. The base of the cache-coherency management system will be coming in, which he calls “probably the single most complex piece of code that is planned for DragonFly.”
Seen on tech-pkg, the pkgsrc mailing list: the pkgsrc version of Mozilla will, due to a temporary restriction, build without the Mozilla name and logo unless manually set to do so. A recent email copied to tech-pkg@ explains why and how it will be fixed soon.
Joerg Sonnenberger warns that libtool is in need of an update, and new packages should not be built until you have a version of libtool other than 1.5.22 installed.
Matthew Dillon has added the new parallel routing code; expect some destabilization if you are running bleeding-edge code. His near-term plans are also posted, which include a start on the Cache Coherency Management System, and preliminary work to support ZFS.
Freshports.org is changing servers, so it may be intermittently unavailable over the next few days.
Joerg Sonnenberger found a slight problem with linking to gettext, which only can happen when building a pkgsrc package from source; binary users are unaffected. Details and a link to a workaround are in his message.
dragonflybsd.org will be down temporarily; I’m pasting Matthew Dillon’s mailing list message below as it’s silly to link to a message about downtime on the site that’s going down:
There was a lot of lightning last night and then a small explosion outside that sounded like the transformer on the telephone poll. Then the lights starts to flicker continuously and the UPS started clicking in and out and… well, I decided to shut everything down overnight :-)
There will probably be some more downtime tonight. I have a UPS monitor but I never hooked up the client/server feature that shuts down all related machines automatically if power isn’t restored in 20 minutes. I am going to get that working properly tonight.
Oh hell. Power just failed again. I’m gonna probably have to shut things down again soon :-(
Do you use wireless? Specifically, the iwi, ipw, wi, or ndis drivers? Do you need WPA encryption? You need Andrew Atrens’ large patch.
Simon ‘corecode’ Schubert plans to commit this patch before the next release if he can get at least one person using one of each of the drivers listed above to test. That means before December 15th, so time’s a-wasting! Andrew Atrens has already been using this patch in production.
Joerg Sonnenberger posted a warning for those running DragonFly 1.2 systems that plan to move to 1.4: the RC system is changing slightly, removing a keyword issue.
If you’re running the latest Development code, you will need to do a full build/install of world and kernel, because of a libc change. Matthew Dillon says so.
Matthew Dillon is moving the FreeBSD-based pkg binaries out of the regular location to make room for the pkgsrc version, which will be in the next release. That next release, by the way, is coming before the end of the year.
On a related note, Simon ‘corecode’ Schubert has proposed moving to rsync instead of cvsup to get updated code; cvsup works well but requires a lot of resources to build.
Matthew Dillon has committed a number of bug fixes back to Preview, and will bring them into 1.2 Release this weekend.