Matt Dillon posted an announcement about 1.0RC1 last night on the kernel mailing list; it contins some important notes about ACPI.
The DragonFlyBSD LiveCD is at version 0.3. It was 1.2 previously, so I assume the major number was dropped to emphasize that it’s not released yet. What’s new? I don’t know, as I haven’t been in #dfinstaller (on EFNet) this weekend.
‘walt’ found out that if you switch from GCC 2 to GCC 3 (and probably vice versa), libtool needs to be rebuilt.
Mat Dillon has committed YONETANI Tomokazu’s extensive ACPI changes.
Matt Dillon has enabled the SIO FIFO (1655x) (don’t ask me what that is…) to reduce latency when that little spinning / | \ – bar thing runs during inital boot.
I note this just so I can say: “DragonFly – we even twiddle fast.”
As Erik P. Skaalerud pointed out in the bugs list, there’s been a lot of source changes lately. If you encounter an error when doing a buildworld/buildkernel, update your sources and try again. A number of people have managed to fall right inbetween updates lately.
I’ve committed the initial “port” of the FreeBSD Handbook into the doc repository. It’s not yet built into the site, but you can see a test version at http://forknibbler.com/guide/. Anyone who wants to add/rewrite a section is strongly encouraged – send it to the submit ‘at’ dragonflybsd.org mailing list.
David Rhodus has removed GCC 3.3 from the tree, since GCC 3.4 is in. ‘
make upgrade‘ during upgrade will clean it out.
Beta 1.2a, released as of Fri Jun 23 13:30:40 GMT 2004.
Andre Nathan made some nice “Powered By DragonFly” buttons.
PFIL_HOOKS is now on by default, so it can be removed from kernel configuration files. It’s not in by default normally, so if it’s unfamiliar, ignore it.
Matt Dillon committed code that makes DragonFly computers boot in dual mode – i.e. both the serial console and the video console are active. Use -h at boot to get just serial, and -V to get just video.
A few people using Postfix for mail have reported system hangs at irregular intervals; Joerg Sonnenberger and Matt Dillon have been trying to track this down. Joerg posted these steps to take if you are so fortunate as to encounter this problem:
“Please try to provide the following for us for download:
- a tarball of your
/var/spool/postfix[if this doesn’t contain private mail, save it and try to remove them as long as the problem persists]
- a crash dump of the system when it hangs and the kernel.debug, please test that ‘
gdb -k kernel.debug vmcore.X‘ actually works and gdb doesn’t crash.
- if you can easily reproduce the problem, compile
kern/kern_lockf.cwith -DLOCKF_DEBUG, use the ddb command ‘
w lf_print_ranges 1‘ to set the lockf debugging and give us the
I really want to fix this, but neither Matt nor I can reproduce this problem and the code is not obviously bad. There is some interaction going on, but the crash dump we had so far doesn’t work (see above about testing). It would be nice, if you can use bzip2 or gzip on all this data.”