A recent thread about describing DragonFly’s kernel led to this post from Matthew Dillon, tying together monolithic kernels vs. microkernels and how they relate to DragonFly’s Single System Image future.
As I understand it, this is different from Matthew Dillon’s journaling work – this is the traditional form of journaling, while Dillon’s is a mechanism to treat disk activity as a relocatable/rewindable stream.
Things have been quiet on the mailing lists for DragonFly, and I’m in the process of moving house, so news on this page may be intermittent for a week or two…
Simon ‘corecode’ Schubert has posted his patches for using GCC 4 to compile DragonFly – it works for the world, but not for the kernel, yet.
Normally I don’t post about ports that much, but this is a pretty commonly used application: the dfports override for FireFox brings it to the more-secure 1.0.4., thanks to Jeroen Ruigrok/asmodai’s commit.
Joerg Sonnenberger has a fix for libtool in pkgsrc that may allow programs like orbit, arts, etc. to compile on DragonFly.(necessart for the Big Programs like KDE)
Joerg Sonnenberger mentioned some of the gotchas involved in porting a network driver from another BSD flavor.
Joerg Sonnenberger listed a few links describing benchmarks with GCC 4.0, as part of a conversation on why he’s working on GCC 3.4.4 instead.
Colin Percival of the FreeBSD Project discovered a security problem with “Hyper-Threading Technology”, found on newer Pentium 4 processors, where information from one thread can be read by another. He talked about it at BSDCan 2005 today (wish I was there!), and there’s a corresponding security alert for FreeBSD. The FreeBSD securing procedure should work for DragonFly, too.
Matthew Dillon, David Xu, and Joerg Sonnenberger have been having an extended conversation on kernel@ about RTLD, TLS, and other things – look for the “kernel library interfacing layer” topic if you want to browse it. All three of these guys are heavyweight kernel programmers, so it goes in-depth.
A question about the file locore.s led to a little computer hardware history lesson.