Submit #3101

PFI CGI install not working in dragonflybsd 5.0.1 USB install

Added by bnegre82 4 months ago. Updated 26 days ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:


I tried to install dragonflybsd on a PCengines APU2 with the CGI installer interface. I have to do this because there is just a serial console and normal installer don't work.
I added a pfi.conf file in /etc/pfi.conf to the image, but no web interface comes.
It failed because /usr/local/sbin/thttpd_wrapper is not on the USB install image (dfly-x86_64-5.0.1_REL.img.bz2)

The webserver is called by the pfi service at startup (etc/rc.d/pfi) line 203
if [ "X$pfi_frontend" = "Xcgi" ]; then
echo "Starting thttpd..."
/usr/local/sbin/thttpd_wrapper &

Can you fix this for the next release ?
How can I add the web server to the install image ?



#1 Updated by thomas.nikolajsen 3 months ago

Hello Bertrand,

You are right, installer use without syscons(4) (including virtual terminals) is broken.
This should be fixed, hopefully for next release.

But dragonfly can be installed manually without installer use.
Though it does take some UNIX experience.
I had no problem installing dragonfly on my APU2, it works fine.
You might do manual install, if you have experience.

To install you just boot from USB media (or network boot, if it is preferred).
Installing instructions is in gpt(8) manual page in EXAMPLES section under Boot Setup heading.

You might prefer MBR over GPT, i.e. use fdisk(8) to setup boot slice.
I used MBR for APU2. I didn't test if GPT works on APU2.
GPT boot mathos used is non-standard and will not work on all BIOSes, as described in gpt(8) manual page.

The rest of dragonfly install described in gpt(8) manual page is independent of boot setup choosen.

Other source for info on dragonfly setup is /usr/share/examples/rconfig, which has a number of setup options.
(HAMMER2 isn't there yet, but if you would like to try it, I'm sure you can change HAMMER setup to fit your needs.)

#2 Updated by stevensalbert 26 days ago

  • Tracker changed from Bug to Submit

The gpt utility provides the necessary functionality to manipulate GUID
partition tables (GPTs), but see BUGS below for how and where functional-
ity is missing. GPT partitions are accessed as DragonFly disk slices,
with same number as GPT partition, 127 slices per disk device are sup-
ported. The basic usage model of the gpt tool follows that of the cvs(1)
tool. The general options are described in the following paragraph. The
remaining paragraphs describe the individual commands with their options.
Here we conclude by mentioning that a device is either a special file
corresponding to a disk-like device or a regular file. The command is
applied to each device listed on the command line.

General Options
The general options allow the user to change default settings or other-
wise change the behaviour that is applicable to all commands. Not all
commands use all default settings, so some general options may not have
an effect on all commands.

The -p count option allows the user to change the number of partitions
the GPT can accommodate.
This is used whenever a new GPT is created. By default, the gpt utility
will create space for 128 partitions (or 32 sec-
tors of 512 bytes).

The -r option causes the gpt utility to open the device for reading only.
Currently this option is primarily useful for the show command, but the
intent is to use it to implement dry-run behaviour.
The -v option controls the verbosity level. The level increases with
every occurrence of this option. There is no formalized definition of
the different levels yet.

Also available in: Atom PDF