I’ve wanted tmpfs or something similar for a while; I have a reoccurring (if not quite realistic) fantasy of building a system with a ridiculous amount of RAM and using it as a disk.
(I’m especially happy about the concept of complete man pages, having been frustrated today by a newly installed Linux system that lacked man pages to match the installed drivers or utilities for the intended hardware. Yeah, I’m talking AsteriskNOW.)
If you were looking to create a very large or very small version of the DragonFly logo, I’ve added .eps and .ai versions of the logo to the images page on the DragonFly website.
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.
Daniel Phillips, who is working on the Tux3 filesystem, posted some more design notes. For those who joined recently, Tux3 is a filesystem similar in some ways to Hammer but being designed for Linux as its primary platform. This is a massively complex idea and project, so it’s good to peruse both the Tux3 site and prior posts about it.
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 added a preference for the emx(4) driver over em(4). This means that loading the emx module or adding the emx device to your kernel config will may turn your em devices into emx. This isn’t dangerous; just a note to keep it from being a surprise.
Edit: Thanks, Sascha Wildner, for pointing out details on which chipsets are affected.
Matthew Dillon notes that a 2.2.1 release will be coming about halfway through March; being a minor release, it’ll be bugfixes for things like the installer and the Hammer undo utility.
Alex Hornung posted a description of the work he’s done so far on a new I/O scheduler, with some details on his ideas on multiple scheduler levels. Feedback is welcomed.
RUE Beltelecom has a DragonFly mirror; it includes images, snapshots, and binary packages. It’s already listed on the download page on the DragonFly website, too.
Matthias Schmidt readded the CVS DragonFly template. However, git being git, you have to manually bring it down to your local clone of the repo. Do this with:
git config --add commit.template /usr/src/tools/gittemplate
Hammer filesystem, meet Hammer OS. Please don’t take this seriously.
For anyone interested in profiling: I posted details on a bulk build of pkgsrc that seem to imply it’s limited by something other than CPU. The ensuing discussion had some ideas on how to speed up the whole process.
I’ve set up another mirror at df.v12.su, on some equipment/space/bandwidth kindly donated by GP Internet.
I’ve updated the website section of the Projects page on the DragonFly website; if you were looking for some things to clear up, some of them are relatively trivial.