Some notes on DragonFlyBSD 1.x

* Version 1.4 of DragonFly was made available on January 7, 2006. Information below is about older versions.

• Sample cvsupfile for DragonFlyBSD sources:

  *default host=cvsup.dragonflybsd.org
  *default base=/usr
  *default prefix=/usr
  *default release=cvs tag=DragonFly_Preview
  *default delete use-rel-suffix
  *default compress
  
  cvs-root
  cvs-src
  

• Sample cvsupfile for DragonFlyBSD pkgsrc:

  *default release=cvs tag=.
  *default delete use-rel-suffix
  *default umask=022
  *default host=cvsup.us.NetBSD.org
  *default base=/usr
  *default prefix=/usr
  *default compress
  
  netbsd-pkgsrc
  

  Do not forget to:

  # cd /usr/pkgsrc/bootstrap
  # ./bootstrap
  # cp -i work/mk.conf.example /etc/mk.conf
  

• Simple update procedure, but it is best that you read /usr/src/UPDATING first:

  # make buildworld buildkernel installkernel installworld upgrade && \
  newaliases && reboot
  

• Note on using ftp-proxy(8) on DFLY (Information current for at least 1.3-Preview as built at 2005/06/15):

  DFLY’s inetd listens on all network interfaces and cannot be instructed to bind on one (as does OpenBSD’s inetd). So while the manual says that your /etc/inetd.conf entry should be:

  127.0.0.1:8021 stream tcp nowait root /usr/libexec/ftp-proxy ftp-proxy

  instead for DFLY it should be:

  ftp-proxy stream tcp nowait root /usr/libexec/ftp-proxy ftp-proxy

  and you should use /etc/hosts.allow to wrap/control access to ftp-proxy. You must allow access to ftp-proxy from the networks that you expect to use it. This is somewhat different than what you expect if you have used OpenBSD/pf/ftp-proxy where the redirection is done on 127.0.0.1. So while the manual instructs:

  rdr pass on $int_if proto tcp from any to any port 21 -> 127.0.0.1 port 8021

  you should use:

  rdr pass on $int_if proto tcp from any to any port 21 -> $int_if port 8021

• I cannot install DragonFlyBSD from the install CD. It fails with:

  ad0: READ command timeout tag=0 serv=0 - resetting
  ata0: resetting devices ..
  

  or something similar. Why?

  *** Information current with at least 1.2.0-RELEASE ISO image ***

  Well, some of the newer motherboards cannot fallback at PIO mode if DMA fails. Have no fear, you can still install DFLY. At the boot selection prompt, select option 6 which starts the loader prompt. While there type the following three commands and you are OK:

  > set hw.ata.ata_dma=0
  > set hw.ata.atapi_dma=0
  > boot
  

  Voila!

  PS: You may need to put these values to /boot/loader.conf.local:

  	
  hw.ata.ata_dma=0
  hw.ata.atapi_dma=0
  

  man loader.conf and man ata for syntax and more

• Perl: If you have Perl installed from pkgsrc and you have made a copy or a symbolic link so as to have /usr/bin/perl be the same as /usr/pkg/bin/perl , after runnning make upgrade you have to remake the link in /usr/bin (or recopy /usr/pkg/bin/perl there).