A running description of activity related to DragonFly BSD.
Simon ‘corecode’ Schubert has a machine set up to build snapshots on a daily basis, at:
http://chlamydia.fs.ei.tum.de/
( pub/DragonFlyBSD/snapshots/i386/ is where you’ll want to go, probably.)
What a euphonious name… New builds will probably finish around 11 AM (GMT+2), which is 4 AM for me in New York, and 1 AM if you are on the Left Coast of the US.
There’s a new documentation newsgroup/mailing list (each posts to the other) for documentation. Check the Forums page for information on all the lists. Hiten Pandya appears to be the instigator.
Matt Dillon’s work diary is updated, too.
Apparently all the old-style prototypes using __P are now gone. Robert Garret is the one to thank for removing the thousands of entries.
Matt Dillon has brought in his slab allocator. This handles memory allocation, and is almost nearly multiprocessor-safe, meaning no fancy locking will (eventually) be required for memory allocation.
I may be wrong, but this sounds like a partial fix to the issue of the “Giant Lock” from FreeBSD 4. Matt Dillon’s description follows…
Continue reading “No more __P, slab allocator in”
The inital installation process for DragonFly BSD was to install FreeBSD 4.8, import the DragonFly BSD code from CVS, and then build over that system. Relatively time-consuming, especially when hitting the mergemaster step. Now, thanks to the efforts of David Rhodus, you can nab the first installation image.
http://dbsd.catpa.com/drhodus/dbsd.iso
It’s just over 150M.
I’ve always thought that one of the problems for the various BSD programs is that there’s a lot of good information that can only be found by digging through the various mailing lists. Nobody in their right mind wants to have to sort through the last 3 months of questions@freebsd.org just for a 5-second answer. So, blog software used to provide a ‘newsfeed’ may be useful.
I’m not a clever enough programmer to contribute code to DragonFly BSD, but I do read the main newsgroups for it. The DragonFly BSD project is small enough that a rolling readout of events may work. So, I’ve got this blog here to do just that. You too can watch me fumble technical terms!
My first goal is to read up and post. This layout just doesn’t work without an article history, or at least more long-winded articles.