Let's be clear: is it dhcpd or dhcpcd that is needed?
~ T
"dhcpcd" !
Not "dhcpd"
And you wont need sudo to search 
Because dhcpcd5 is in the apt repo.
~ D
sudo apt install dhcpcd5
Well, I'm happy to say it installed. The only problem is it can't seem to get the latest version of FTL from github, for some reason:
[i] FTL Checks...
[✓] Detected ARM-hf architecture (armv7+)
[i] Checking for existing FTL binary...
[✗] Downloading and Installing FTL
Error: Unable to get latest release location from GitHub
[✗] FTL Engine not installed
[i] man not installed
[i] Systemd-resolved is not enabled
[✓] Starting lighttpd service
[✓] Enabling lighttpd service to start on reboot
[i] Restarting services...
[i] Starting pihole-FTL service...
Unable to complete update, please contact Pi-hole Support
Progress!
~ T
Hahahahaha ... probably same issue I had earlier today:
Except you need to run the installer again instead of "pihole -up".
I have to step away from the machinery for a bit, but I'll give a try later this evening and post my results.
~ T
So... that allowed the install to proceed, but left me unable to resolve hostnames. (can't apt-get anything) Also, none of the pihole processes appear to be running, and if I go to the admin page, I get either a 403 forbidden, or my browser asks me if I want to download 'index.php'. Yay. 
~ D
OK, another step in peeling the onion. Apparently the pihole-FTL service is attempting to start, then exiting immediately.
Doing systemctl status pihole-FTL.service yields:
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Thu 2018-08-09 01:57:51 UTC; 2min 30s ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 1026)
CGroup: /system.slice/pihole-FTL.service
Aug 09 01:57:49 sparhawk systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 09 01:57:49 sparhawk pihole-FTL[3790]: Not running
Aug 09 01:57:50 sparhawk pihole-FTL[3790]: chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory
Aug 09 01:57:50 sparhawk su[3822]: Successful su for pihole by root
Aug 09 01:57:50 sparhawk su[3822]: + ??? root:pihole
Aug 09 01:57:50 sparhawk su[3822]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 09 01:57:51 sparhawk pihole-FTL[3790]: dnsmasq: illegal repeated keyword at line 35 of /etc/dnsmasq.d/01-pihole.conf
Aug 09 01:57:51 sparhawk su[3822]: pam_unix(su:session): session closed for user pihole
Aug 09 01:57:51 sparhawk systemd[1]: Started LSB: pihole-FTL daemon.OK, at least it is to a point where I can create a debug token. 
2dpxl9t79b
Thanks to all for the fantastic assistance today. I'm very excited about getting this running again.
~ T
cat -n /etc/dnsmasq.d/01-pihole.conf
?
On it.
ubuntu@sparhawk:~$ cat -n /etc/dnsmasq.d/01-pihole.conf
1 # Pi-hole: A black hole for Internet advertisements
2 # (c) 2015, 2016 by Jacob Salmela
3 # Network-wide ad blocking via your Raspberry Pi
4 # http://pi-hole.net
5 # dnsmasq config for Pi-hole
6 #
7 # Pi-hole is free software: you can redistribute it and/or modify
8 # it under the terms of the GNU General Public License as published by
9 # the Free Software Foundation, either version 2 of the License, or
10 # (at your option) any later version.
11
12 ###############################################################################
13 # FILE AUTOMATICALLY POPULATED BY PI-HOLE INSTALL/UPDATE PROCEDURE. #
14 # ANY CHANGES MADE TO THIS FILE AFTER INSTALL WILL BE LOST ON THE NEXT UPDATE #
15 # #
16 # IF YOU WISH TO CHANGE THE UPSTREAM SERVERS, CHANGE THEM IN: #
17 # /etc/pihole/setupVars.conf #
18 # #
19 # ANY OTHER CHANGES SHOULD BE MADE IN A SEPERATE CONFIG FILE #
20 # OR IN /etc/dnsmasq.conf #
21 ###############################################################################
22
23 addn-hosts=/etc/pihole/gravity.list
24 addn-hosts=/etc/pihole/black.list
25 addn-hosts=/etc/pihole/local.list
26
27
28 localise-queries
29
30
31 no-resolv
32
33
34
35 cache-size=10000
36
37 log-queries=extra
38 log-facility=/var/log/pihole.log
39
40 local-ttl=2
41
42 log-async
43 server=8.8.8.8
44 server=8.8.4.4
45 interface=eth0
~ T
I see this also:
ubuntu@sparhawk:~$ sudo systemctl status dnsmasq -l
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2018-08-08 20:45:02 CDT; 1h 46min ago
Aug 08 20:45:02 sparhawk systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server...
Aug 08 20:45:02 sparhawk dnsmasq[1049]: dnsmasq: illegal repeated keyword at line 35 of /etc/dnsmasq.d/01-pihole.conf
Aug 08 20:45:02 sparhawk dnsmasq[1049]: illegal repeated keyword at line 35 of /etc/dnsmasq.d/01-pihole.conf
Aug 08 20:45:02 sparhawk dnsmasq[1049]: FAILED to start up
Aug 08 20:45:02 sparhawk systemd[1]: dnsmasq.service: Control process exited, code=exited status=1
Aug 08 20:45:02 sparhawk systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
Aug 08 20:45:02 sparhawk systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS server.
ubuntu@sparhawk:~$I dont see anything wrong on line 35.
And your config file looks exactly like mine.
Have no idea whats going on.
Thats from yesterday ... think its of no concern and latest Pi-hole isnt using dnsmasq anymore.
OK, I edited /etc/dnsmasq.d/01-pihole.conf and commented out line 35 (cache-size=10000) and then did a pihole restartdns. This seems to have worked!
A couple of other notes: I wasn't getting the admin page to show up. Turns out my BBB distro had the nginx webserver running already. I had to uninstall it and kill the running nginx processes, then allow pihole to restart lighttpd, which got the admin interface up and working.
Only thing that isn't working now is the admin interface is complaining that FTL is offline and 'Lost connection to API'.
More progress!
~ T
It's still Aug 8 where I am located. 
~ T
sudo netstat -nltp | grep ':471'
?
And if that yields no results:
sudo systemctl status pihole-FTL -l
?
Kind of wonder if I just need to reboot the thing and hope everything runs like it's supposed to...
~ T
ubuntu@sparhawk:~$ sudo netstat -nltp | grep ':471'
ubuntu@sparhawk:~$ sudo systemctl status pihole-FTL -l
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated)
Active: active (exited) since Wed 2018-08-08 22:26:38 CDT; 21min ago
Docs: man:systemd-sysv-generator(8)
Tasks: 0 (limit: 1026)
CGroup: /system.slice/pihole-FTL.service
Aug 08 22:26:37 sparhawk systemd[1]: Starting LSB: pihole-FTL daemon...
Aug 08 22:26:37 sparhawk pihole-FTL[10415]: Not running
Aug 08 22:26:38 sparhawk su[10438]: Successful su for pihole by root
Aug 08 22:26:38 sparhawk su[10438]: + ??? root:pihole
Aug 08 22:26:38 sparhawk su[10438]: pam_unix(su:session): session opened for user pihole by (uid=0)
Aug 08 22:26:38 sparhawk pihole-FTL[10415]: dnsmasq: illegal repeated keyword at line 35 of /etc/dnsmasq.d/01-pihole.conf
Aug 08 22:26:38 sparhawk su[10438]: pam_unix(su:session): session closed for user pihole
Aug 08 22:26:38 sparhawk systemd[1]: Started LSB: pihole-FTL daemon.Thats weird as systemctl status pihole-FTL.service was showing date from "Aug 09 01:57:49"
Check timezone:
sudo dpkg-reconfigure tzdata
And maybe reboot after to be sure.
EDIT: ohw and check for duplicates:
grep cache-size -R /etc/dnsmasq.*
My bad. Since this is a fresh install, I didn't change the tzdata until in the middle of all this tinkering, which should explain any timestamp oddness. Sorry!
ubuntu@sparhawk:~$ grep cache-size -R /etc/dnsmasq.*
/etc/dnsmasq.conf:#cache-size=150
/etc/dnsmasq.d/SoftAp0:cache-size=2048
/etc/dnsmasq.d/01-pihole.conf:#cache-size=10000
~ T