Better history

Aaron Malone submitted (and Hiten Pandya committed) a whole lot of man page changes to account for changes from FreeBSD to DragonFly in system name but not history. Specifically, the HISTORY sections. It’s not glamorous, but it’s good to do it.

https://www.dragonflydigest.com/2004/02/29/279.html#respondfooCategoriesCommitted Code

Matt Dillon takes a spill

Matt Dillon will be coding a little more slowly for the next while – he broke his right clavicle while riding his bike, so his typing speed has been reduced, temporarily.

https://www.dragonflydigest.com/2004/02/28/278.html#commentsfooCategoriesGoings-on

June bugs

Matt Dillon mentioned that June is the current target for a 1.0 release of DragonFly BSD.

https://www.dragonflydigest.com/2004/02/26/275.html#respondfooCategoriesGoings-on

Packaging thoughts

Simon ‘corecode’ Schubert has posted his initial thoughts about a packaging system; discussion about is on the dragonfly.kernel mailing list/newsgroup. Simon wants to move fast – 1-2 weeks for suggestions, then some weeks for implementation planning, and then jump in!

https://www.dragonflydigest.com/2004/02/26/274.html#respondfooCategoriesGoings-on

Permamixer

If you now set mixer_enable="YES" in rc.conf, your mixer settings will get saved, thanks to ibotty’s idea and Joerg Sonnenberger’s commit.

(I’m writing this without trying it, but that’s how I read it…)

https://www.dragonflydigest.com/2004/02/25/273.html#respondfooCategoriesCommitted Code

dfports report

Joerg Sonnenberger has done some major cleanup to dfports. A cvsup would be a good idea.

A quote from him follows:

“Hi all, next time you update your dfports tree, you must update
/usr/share/mk/bsd.port.mk and /usr/share/mk/bsd.dfport.mk too. This should fix a lot of the problems various people mentioned in the past weeks. You should also check the dependencies e.g. of GTK+, if you haven’t rebuild your ports after January 25th. Otherwise the dependencies recorded are supposedly broken.”

https://www.dragonflydigest.com/2004/02/24/271.html#respondfooCategoriesGoings-on

ACPI added

Matt Dillon has brought in the December 2003 release of ACPI (acpica-unix-20031203) from Intel. The old code is still what’s on by default, as the new code builds but does not yet work.

https://www.dragonflydigest.com/2004/02/21/269.html#respondfooCategoriesCommitted Code

Living dangerously

Peter Kadau answered a question from Jonathon McKitrick about getting rid of your boot manager, if you just have DragonFly:

boot0cfg -o noupdate -s 1 -t 0 -B ad0

Matt Dillon followed up on the topic mentioning that the ‘Dangerously Dedicated’ mode from the old FreeBSD installer is probably no longer worthwhile, and may even cause problems.

https://www.dragonflydigest.com/2004/02/19/267.html#respondfooCategoriesGoings-on

ATAng just in case

Matt Dillon posted that if the recent ATAng integration keeps your IDE controller from working (though the opposite is more common), do:

#define NO_ATANG in /usr/src/sys/dev/disk/ata/ata-all.h

https://www.dragonflydigest.com/2004/02/18/266.html#respondfooCategoriesGoings-on

Propolice at least

Tomaz Borstnar noted that propolice support is still there for GCC2 (the only compiler at the time it was added) but not yet for GCC3. Matt Dillon followed up saying that other ‘gcc3isms’ have to be cleaned up first, though integration shouldn’t be hard.

https://www.dragonflydigest.com/2004/02/18/265.html#commentsfooCategoriesGoings-on

SATA support, sorta

Matt Dillon’s added experimental support for the Silicon Image 3512 SATA controller.

Incidentally, credit goes to David Rhodus for generating the base patch for all the ATAng work committed by Matt Dillon yesterday.

https://www.dragonflydigest.com/2004/02/18/264.html#respondfooCategoriesCommitted Code

ATAng added

Matt Dillon has brought in ATAng from FreeBSD 4 except for “the dma chipset changes and the busdma changes”, while retaining the apparently better DragonFly MPIPE version.

https://www.dragonflydigest.com/2004/02/18/263.html#commentsfooCategoriesCommitted Code

Spamfilters on

Spam filters have been turned on for the various DragonFly lists: (Taken from Matt Dillon’s post explaining this)


  • Matches against certain really annoying viruses
  • With a MIME Content-Type header of text/html
  • With a MIME Content-Type header of multipart/alternative
  • Without a working reverse DNS lookup
  • Without a FQDN formatted HELO line
  • With an invalid envelope sender. The spam filter does a realtime
    connect back to the SMTP server associated with the envelope sender
    and attempts to RCPT to it. If this fails the mail will be rejected.

https://www.dragonflydigest.com/2004/02/17/262.html#commentsfooCategoriesGoings-on