Chris Turner is working on ral(4) support, specifically the eee901’s 2860 network chip.
See the announcement and the release notes.
The index page of the DragonFly site has been updated by Matt Dillon with some notes regarding the status of the 2.8 release. Among these, it is mentioned that the GUI image will be making a return for 2.8! There will be no DVD image this time, only an image suitable for writing to a disk, such as a usb stick.
I’ve coded some tasks on the DragonFly projects page for Google Code-In. (Application is in already.) If there’s any additional DragonFly projects appropriate for 13 to 18-year old students, that’s the place to add it. The application period ends the 29th at 23:00 UTC, so don’t take your time.
If you’re using DragonFly x86_64, and set LANG to something other than English, you will get crashes from programs using pkgsrc’s gettext-lib. Francois Tigeot has a fix which is going into pkgsrc, though I don’t know if this will show up in pkgsrc-2010Q3.
The 2.8 release hasn’t quite happened yet. But soon!
Siju George has been fleshing out his ‘afterboot’ style page, though now it’s “Environment Quick Start“. Good to look at if you are, say, installing a 2.8 DragonFly image.
DragonFly 2.8 (technically 2.8.1; see here for the .1 changes) is due to be released tomorrow. There should be at almost the same time pkgsrc 2010Q3 packages available. There will also be a LiveDVD for this release, too, though the window manager has changed.
DragonFly has shipped with a uniprocessor kernel by default forever. Shipping with a SMP kernel may not work as well for all possible combinations. With some recent changes by Matthew Dillon, both types of kernel are present and can be picked from at boot time – with the LiveCD!
Chris Turner posted details of how he gets jack (“a low-latency audio server”) to run on DragonFly. Your mileage may vary.
There’s still no support for KMS/GEM on any most BSDs, though there are people interested in it for FreeBSD. One of DragonFly’s Summer of Code projects was just that, though it’s not in a state where it can be really used.
Scott Ullrich, who has worked on several BSD-related projects, including DragonFly, has something called vCloudBSD, about which you now know as much as me. It looks to be a FreeBSD auto-installer for virtualization, though I’m sure I’m overgeneralizing.
Hasso Tepper helpfully forwarded announcements for the Call for Papers for both EuroBSDCon 2011 and AsiaBSDCon 2011.
Also, there’s probably going to be DragonFly people at 27C3, and I know there’s going to be some at NYCBSDCon 2010. The early registration discount for NYCBSDCon only lasts about 10 more days, so jump on it while you can; it’s crazy cheap.
I’ve applied on behalf of DragonFly for Google Code-In. It’s similar to Google Summer of Code, but focuses on 13-18-year-olds and smaller tasks. It runs over the year-end, and we’ll know if we’re in by November 5th.
In the meantime, if you have ideas that could fit the program (see task list at the Google site), please put them on the DragonFly project page.
Alex Hornung has some patches that allow KDE4 to build on DragonFly. They aren’t in pkgsrc and not all in KDE yet, so try them out directly if you want KDE4, for now.
Update: based on something Alex said on IRC… they’re in KDE4 now.
The dragonflybsd.org website is a wiki (ikiwiki, to be exact) and any page on it can be edited. You have to create an account, first, which only requires picking a username and password.
However! If you have an account on leaf.dragonflybsd.org where it is hosted, you can check it out via git, edit any number of pages using your favorite editor, and commit it back and the pages will automatically rebuild. The commit will even show up like any other change.
Pratyush Kshirsagar has put together a website describing his proportional RSS work for DragonFly. He may have more content in the future.
DragonFly 2.8 has been branched, with the release anticipated for the end of this month. I’m building packages right now for it, so we should have binary packages ready at release. A convenient git-summarized changelog exists to track differences since 2.7.3, at least.