How to use DragonFly BSD Ports (dports)

How to install software in DragonFly BSD? that question came into my mind after I successfully install version 3.6 on my VirtualBox. I know about pkg_add and ports on FreeBSD so I guess I need to know about how ports work on DragonFly BSD and install a software like Apache on this opportunity. In fact its not hard at all.

Create ports skeleton

This command will create dports directory

# cd /usr

# make dports-create-shallow
If problems occur you may have to rm -rf dports and try again.

git clone –depth=1 git://  /usr/dports
Cloning into ‘/usr/dports’…
remote: Counting objects: 124398, done.
remote: Compressing objects: 100% (117288/117288), done.
remote: Total 124398 (delta 5201), reused 94462 (delta 3286)
Receiving objects: 100% (124398/124398), 46.52 MiB | 98.00 KiB/s, done.
Resolving deltas: 100% (5201/5201), done.
Checking connectivity… done
Checking out files: 100% (98096/98096), done.

Install DialogPorts

# cd /usr/dports/ports-mgmt/dialog4ports && make install

Install Apache MPM Worker using Dport

# cd /usr/dports/www/apache22-worker-mpm && make install

Let the options as is and hit OK.

Other dependencies will be installed automatically.

In the middle of installation I got problem with gmake. Its refused to install due to dns problem. I used to overcome it with pkg_add -vr gmake and DragonFly BSD offer almost identical solution.

help2man-1.43.3_1 depends on executable: gmake – not found
===>    Verifying install for gmake in /usr/dports/devel/gmake
===>  Found saved configuration for gmake-3.82_1
===>   gmake-3.82_1 depends on file: /usr/local/sbin/pkg – found
=> make-3.82.tar.bz2 doesn’t seem to exist in /usr/distfiles/.
=> Attempting to fetch

The problem came from my side, internet connection is so slow that make the message appear. After connection restored and retry it everything fine now.

Checking Installed Package / Software

# pkg info
apache22-worker-mpm-2.2.26     Version 2.2.x of Apache web server with worker MPM.
apr-                Apache Portability Library
autoconf-2.69                  Automatically configure source code on many Un*x platforms
autoconf-wrapper-20131203      Wrapper script for GNU autoconf
bind98-9.8.6                   BIND DNS suite with updated DNSSEC and DNS64
ca_root_nss-3.15.2_1           The root certificate bundle from the Mozilla Project
cdrtools-3.00_2                CD/DVD/BluRay and ISO-9660 image creation and extraction tools
curl-7.33.0                    Non-interactive tool to get files from FTP, GOPHER, HTTP(S) servers
cvsps-2.1_1                    Create patchset information from CVS
db48-                  The Berkeley DB package, revision 4.8
dialog4ports-0.1.5_2           Console Interface to configure ports
expat-2.1.0                    XML 1.0 parser written in C
gdbm-1.11                      GNU database manager
gettext-               GNU gettext package
git-                    Distributed source code management tool
gmake-3.82_1                   GNU version of ‘make’ utility
help2man-1.43.3_1              Automatically generating simple manual pages from program output
isc-dhcp42-client-4.2.5        The ISC Dynamic Host Configuration Protocol client
isc-dhcp42-server-4.2.5        The ISC Dynamic Host Configuration Protocol server
libtool-2.4.2_2                Generic shared library support script
libxml2-2.8.0_2                XML parser library for GNOME
lynx-,1                 Non-graphical, text-based World-Wide Web client
m4-1.4.17,1                    GNU m4
p5-Locale-gettext-1.05_3       Message handling functions
pcre-8.33                      Perl Compatible Regular Expressions library
perl5-5.16.3_6                 Practical Extraction and Report Language
pkg-1.1.4_8                    New generation package manager


Configure SSH Server on DragonFlyBSD After First Time Installation

I used to access server via ssh after first time installation of an server and since I use ‘common’ IP then I get famous message.

Get rid of that message :

$ ssh-keygen -f "/home/alamsyah/.ssh/known_hosts" -R
/home/alamsyah/.ssh/known_hosts updated.
Original contents retained as /home/alamsyah/.ssh/known_hosts.old

Then I try ssh

$ ssh alam@
The authenticity of host ‘ (’ can’t be established.
ECDSA key fingerprint is 25:e4:32:fb:04:35:f8:63:fb:28:d9:55:2d:51:1e:8d.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘’ (ECDSA) to the list of known hosts.
Permission denied (publickey).

Ups, Permission denied.

After google and read manual I got solution for editing ssh configuration


Yes, ee is exist here in case you wondering about text editor here 🙂


Change “PasswordAuthentication” value from no to yes and save the file starting by press ESC button.

Restart ssh service


Retry ssh access from terminal or putty

$ ssh alam@
alam@’s password:
Last login: Thu Jan 16 11:24:46 2014
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
The Regents of the University of California.  All rights reserved.

DragonFly v3.6.0-RELEASE (GENERIC) #10: Sun Nov 24 07:57:21 PST 2013

Welcome to DragonFly!

Having trouble using fetch through a firewall?  Try setting the environment
variable FTP_PASSIVE_MODE to yes, and see fetch(3) for more details.
> su

Great. This step give me more confident to explore the machine.

Install DragonFlyBSD part 2

At previous post I already show about requirement and installation steps of DragonFly BSD till configure area. In this post I’ll continue with Configuration of system. Lets get start.

DragonFly BSD provide the options via ‘sysinstall’ looks like interface as seen on this picture.


Configure TimeZone

Click on “select timezone” to configure timezone.

Continue reading

Install DragonFlyBSD part 1

Since first release I always want to try how DragonFlyBSD work. DragonFlyBSD that I call DFLYBSD is FreeBSD 4.8 version that evolved into new operating system with their own filesystem called HammerFS but of course UFS still supported.
I have spare time and want to install latest version (in time of writing I download version 3.6.0) on my VirtualBox under Ubuntu 13.04 Desktop.

So here we go :

1. Download latest version from here.

2. Create Space on VirtualBox with memory 512MB and 10GB hard disk plus bridge ethernet connection.

3. Use CD connect to iso file and start the machine.


Type ‘installer’ and hit Enter button.

Continue reading


2013 will pass and I want to learn new operating system and use this blog as place of documentation of my learning. OpenBSD is my choose and perhaps NetBSD too. How to get it up and many more. Today I’ve install OpenBSD using VirtualBox under Ubuntu Linux 13.04. Error message came out when I try to ssh newly install OpenBSD box :

$ ssh alam@

Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in /home/alamsyah/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/alamsyah/.ssh/known_hosts:19
remove with: ssh-keygen -f “/home/alamsyah/.ssh/known_hosts” -R
ECDSA host key for has changed and you have requested strict checking.
Host key verification failed.

Get rid of that message :

$ ssh-keygen -f "/home/alamsyah/.ssh/known_hosts" -R

/home/alamsyah/.ssh/known_hosts updated.
Original contents retained as /home/alamsyah/.ssh/known_hosts.old
alamsyah@alamsyah-Aspire-E1-471:~$ ssh alam@
The authenticity of host ‘ (’ can’t be established.
ECDSA key fingerprint is ba:4b:ee:4c:b1:6d:02:41:62:e0:19:1e:c5:11:e7:0b.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘’ (ECDSA) to the list of known hosts.
alam@’s password:
Last login: Fri Dec 20 20:43:20 2013
OpenBSD 5.4 (GENERIC) #37: Tue Jul 30 12:05:01 MDT 2013

Welcome to OpenBSD: The proactively secure Unix-like operating system.

Please use the sendbug(1) utility to report bugs in the system.
Before reporting a bug, please try to reproduce it with the latest
version of the code.  With bug reports, please try to ensure that
enough information to reproduce the problem is enclosed, and if a
known fix for it exists, include that as well.


Good call.

Lesson learned, I used to use same IP for experiment and this message came out. In future I’ll use different ip for different operating system.