DragonFly BSD Digest

There’s pictures of a prototype of the plush DragonFly mascot. It’s missing one set of legs, but it’s otherwise accurate to what is being sold.

Steve Mynott brought up pmap and vmmap as utilities he’d like to see in DragonFly.

Tobias Florek has plush Freds – the dragonfly mascot for DragonFly. He’s in Europe, and it costs 16 Euros plus shipping – mail fred at ibotty.net. First come, first serve. If you live on the western side of the Atlantic, shipping costs make it prohibitive, so no luck for U.S. and Canada residents yet. (A U.S. distributor is being worked on.)

Joerg Sonnenberger added to the partion discussion:

The alternative for /tmp is to have lots of swap and MFS for /tmp. This is often faster and avoids the lots of old crap in /tmp problem.
In that case you should make /var/tmp its own partition. In general /tmp and /var/tmp as world writable locations should be on partitions
on there own. Making /usr/obj a filesystem of its own has the advantage
of faster cleaning — just unmount, newfs and remount it :)

He also noted that having specific partitions for things like news spools (/news/) and mail stores (/var/spool/) is that it allows the blocksize to be set much smaller, which decreases wasted space when dealing with lots and lots of small files.

Matt Dillon responded to a question from David Cuthbert about partition letters; as part of that, he recommended this sort of partion layout:

If you have a large system, it is often a good idea to separate out oft-written directories such as /usr/obj, and to make /tmp larger. /var/tmp is usually made a softlink to /tmp. If you have or intend to process a lot of mail, making /var larger is a good idea. If you are running a mail server it is often a good idea to make /var/spool its own partition (and /var/mail its own partition if you are running a large mail pop service or have a lot of users). If you are running a large web server making /usr/local/www its own partition (the base of Apache’s site directory) is a good idea.

Matt Dillon’s changes to buildworld are done; the next make buildworld you do will take a bit longer, but you should be able to do make quickworld thereafter, which should be… quicker!

Be careful, for the time being, doing a make -j, though. If that fails, Matt asks:

In one xterm: make -j 4 buildworld >& /tmp/bw.out
In another xterm: tail -f /tmp/bw.out | fgrep ===

Save the results, and post a link to it in the kernel discussion group.

Matt Dillon has changed some settings on the DragonFly news server that mirrors the mailing list traffic; now, all posts ever made are visible.

For those readers who follow the emacs religion: Andreas Fuchs found that the emacs build expects /usr/lib/crtbegin.o, which does not exist on DragonFly. Rahul Siddharthan removed the mention of crtbegin.o from the makefile for emacs, and that seems to fix it.

Updated: Hiten Pandya added a port override for emacs, made by Aaron Malone. That solves it.

Since “MFC” (Merged From Current) is used to denote a feature brought from FreeBSD 5 to FreeBSD 4, what would these be? MF4? In any case, Hiten Pandya has a lot of FreeBSD 4 commits he may want to bring into DragonFly. How many? This many.

‘esmith’ pointed out that the FireFox NetBSD binary at mozilla.org is available for download and appears to work fine on DragonFly.

Chris Pressey, style(9) maven, is now a committer. This is probably due to the large quantity of cleanup patches he has already submitted. Congratulations, Chris.

There’s a new ‘known good’ ISO on the DragonFly download page (2004-3-17b) that includes, among other things, a fixed OpenSSL and a number of USB improvements – there’s a /README.USB file now.

Matt Dillon posted some numbers on performance of NFS over Gigabit Ethernet – using TCP, he was able to hit 80-something megabytes per second right off the bat, and saw nearly 90 using UDP. This improvement stems from Hiten Pandya’s work on the em driver and NFS block size changes.

As seen on Daemonnews, The Jem Report has a comparison of FreeBSD 5 on an AMD64 machine and a Pentium 4 machine. FreeBSD 5 performance is not directly comparable to DragonFly, but the architecture comparison is useful.

While talking about his (many, many) code cleanups, Chris Pressey pointed at the Erlang Programming Rules as a good guideline for programming style.

Shadow Committer Jeffrey Hsu is presenting a paper on DragonFly at AsiaBSDCon, and his paper can be downloaded now.