A running description of activity related to DragonFly BSD.
DragonFly 1.6 is released, (see announcement) with highlights including:
ISO images and/or source updates are available from a number of mirrors, though I suggest the torrent.
SATA drive donations are being solicited (in the form of cash) for the machine that hosts the FreeBSD Diary, FreshPorts, FreshSource, and BSDCan.
What’s the first thing to check when troubleshooting? Hardware, like power cords, and any other connections.
Simon ‘corecode’ Schubert has more AMD64 patches for testing, and Joerg Sonnenberger has potential support for Tekram controllers (trm(4))
This week on UnixReview.com: 4 articles, the first two of which may be of limited use to this page's audience:
Security: The adventure continues - SELinux Book Review: Unix to Linux Porting Certification: Test Your Knowledge of A+ Essentials Topics Product Review: Spyforce-AI
If you’re thinking about buying a wireless card to use with DragonFly, Sepherosa Ziehau recommends cards supported by the ath(4), ral(4) and acx(4) drivers. No, I’m not sure which those are.
Martti Kuparinen is looking for some testers for Xfce 4.4 beta 2. See his email to pkgsrc-users@ for details.
NYCBSDCon, held in New York City (surprise!) is being held October 28-29th on the Columbia University campus. If you want to present, your abstract is due August 15th.
DragonFly 1.6 has been branched in CVS, with the release happening at the end of the week.
Java 1.4.2_11 and earlier works on DragonFly, and a number of further tips came up on the mailing lists. (See similar previous entry.)
Simon ‘corecode’ Schubert’s vinum changes were recently committed by Matthew Dillon. Simon follows up with a warning: ABI compatibility is broken by this, so vinum will have to be recompiled, if you are using it.
Sepherosa Ziehau has added the ath(4) driver, for many models of wireless card, to DragonFly.
It is possible to build a custom install CD that adds additional packages and/or changed configuration files to the ‘normal’ DragonFly installation. How do you do it? The answer is in ‘man release‘
There’s new bsdtalk interviews every week, but this week, it’s Matthew Dillon, talking about the upcoming 1.6 release. A notable comment he made was that DragonFly is now more stable than even the much-vaunted FreeBSD 4.x releases that it came from. (Credit goes to Sascha Wildner for noticing the interview first.)
Eric Jacobs said “I’d like to work with LWKT“. Matthew Dillon said, “How about userland VFS?” , and Eric said “Sure!“. Then, Matthew Dillon went into unsummarizable details.
I’ve updated the Handbook, and rebuilt the web version and the PDF. Most of the changes are the addition of Adrian Nida and Erik Wikstrom’s updates for pkgsrc.
The DragonFly ISO images (the recent builds) now include system source – not enough to rebuild the whole system, but enough to patch and rebuild the kernel in situations where the source can’t be downloaded. Like, say, network cards that require manual tweaking to support.
The 1.6 release is pushed back to next weekend, instead of this week as originally intended.
Yury Tarasievich was able to get Java 1.5 working, and he mailed out details of the process. Along the same lines, ‘walt’ was able to get Java 1.4 working from the ‘wip’ branch of pkgsrc, which only requires some minor elbow grease.
Simon ‘corecode’ Schubert has been using Roundup as a bug tracker for DragonFly for some time now; it works well, and Matthew Dillon plans to make it official. Tickets are created from traffic on submit@ and bugs@, and it works quite well im my experience.