1.0RC1 is released!

Mirror list:
http://home.hackerheaven.org/~coolvibe/mirrors
Devon O’Dell San Jose California, 100Mbit

  • noskill: NYC, NY, 100mbit
  • Devon O’Dell: Amsterdam Zuidoost Holland, 100Mbit
  • vDong: Zeist The Netherlands, idespeed (5400rpm)
  • jage: Stockholm Sweden, 100Mbit.
  • Lukkie: AMS, NL, 10mbit
  • corecode: Germany, 100Mbps
  • hernan43: Minnesota, USA 100Mbit
  • –>
    Torrent:
    http://www.energyhq.es.eu.org/files/dfly-1.0RC1.iso.gz.torrent

    LiveCD at 0.3

    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.

    Rebuildworld

    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.

    Dual-console default

    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.

    Pesky Postfix

    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.c with -DLOCKF_DEBUG, use the ddb command ‘w lf_print_ranges 1‘ to set the lockf debugging and give us the /var/log/messages.

    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.”