DragonFly BSD Digest

Hiten Pandya asked that anyone (committers or not) working on a task for DragonFly mail him the following data:

“(1) Name
(2) Owner (name and email address) — can be multiple
(3) Current status (work-in-progress, suspended, done)
(4) Description of the Task (300 chars is good!)
(5) Priority (if any) (If any)”

Send it to hmp@backplane.com with a subject of [TODO ITEM]. Will this show up online? I don’t know.

Robert Garrett <rg70@sbcglobal.net> is working on the aforementioned OSL Beaver Challenge; if you are interested in participating for “Team DragonFly”, contact him

KDE 3.2 is out. It should be possible to compile at least the base parts on DragonFly thanks to Dave Leimbach.

Wouter Clarie posted about the OSU Beaver Lab Challenge, where the OSU Lab wants to benchmark a number of operating systems (Linux and BSD flavors) against each other, with teams for each operating system to tweak as needed. There’s no DragonFly team at this point, though it may not be useful to ‘compete’ before an inital release.

Matt Dillon is doing what he did with binutils-214 – He’s bringing in a prerelease version of gcc 3.3.3 to replace the FreeBSD 5 specific version of gcc 3.2 currently used. This version of gcc (and binutils) are straight from the vendor, which should mean staying in sync with new releases will be much easier.

Note: using gcc3 may/will lead to breakage right now…

As part of the discussion about CVS and similar products, Garance A Drosihn pointed out that he was working on a C++ version of cvsup, meaning that it wouldn’t require Modula-3 installed to build as it does now. He stopped work because these is apparently a C version in the works, which he hopes would be out by the time of FreeBSD 5.3’s release, somewhere in the next year. That’s good news for DragonFly, too, as cvsup is the method for code updates for the foreseeable future.

There was discussion some time ago of using rsync for updates, which is certainly possible… Binary updates would be nice, too.

Pedro F. Giffuni brought up the idea of using subversion instead of cvs for storing DragonFly source. Bakul Shah pointed out that subversion was not yet mature enough for a switch from cvs in his experience, and Matt said we are continuing with cvs.

Thanks to Jeroen Ruigrok, the version of autoconf now in CVS knows what a ‘DragonFly’ system is.

Jeroen Ruigrok posted an interesting link about moving machine state between machine.

Matt Dillon’s planning to work on AMD64 support for February. He listed these steps:

“* build support and cross compilation work
* kernel build
* boot 64-bit kernel almost to single user
* 32 bit userland support
* boot kernel to single user
* basic device driver and filesystem testing
* boot kernel to multi user (fully working system at this point)
* everyone w/ 64 bit boxes start banging on it, fixing additional
device drivers, get 64 bit buildworlds working, and so forth.”

Matt Dillon’s been working on this patch, described as so:

“These are dyamic[sic] interrupt-driven timers. They replace the old fixed periodic ‘hardclock’ interrupt that exists now and allow per-cpu multiple periodic or one-shot timer interrupts to be registered with the system. Systimers operate outside the MP lock, so any code developed to use it has to be MP safe. Systimers are intended to be able to make use of per-cpu timers (e.g. LAPIC), when available, and will eventually be augmented to use them.”

It also has the added bonus of making nanosleep() very accurate.

‘esmith’ reported successfully building OpenOffice 1.1 using the base version of GCC 3.3 now in.