@Sebastian-Roth
Interesting, and good questions. I definitely didn’t install anything, but curl, and openssh.
The Ubuntu install was a stock “Quick Create” on Hyper-V; the first thing I did with all 5 VM’s was to download and install Fog.
My exact steps were this:
sudo apt-get install net-tools
sudo apt-get install openssh-server
sudo apt-get update
sudo apt-get install curl
curl https://codeload.github.com/FOGProject/fogproject/tar.gz/1.5.6 --output 1.5.6.fog.tar.gz
tar -xzvf 1.5.6.fog.tar.gz
cd fogproject-1.5.6/bin
sudo ./installfog.sh
This was based on this page: https://fogproject.org/download
Side note: Ah ha! sudo -i works on a Raspberry Pi. Su does not; root is disabled, so I got in the habit of doing “sudo” for everything. So it never occured to me the sudo ./installfog.sh was a problem. I get you on the path issues; I ran into this with Debian, so much so I just ran “su” there and did everything as root 🙂
The root user is disabled on Raspbian (I do a lot of work on embedded systems), so I got out of the habbit of su.
I had hoped to run Fog on a PineH64, but couldn’t get it to boot with Armbian, and the supporters of Armbian said “I was wasting their time” trying to debug why it wouldn’t boot without a $20K payment to them. I won’t be doing Fog with Armbian! I may try it on the Pi 4, it’s got a Gigabit network, and USB3, so might get some OK speeds. If I get it in time, I’ll let everyone know.
For now, I’ll use the Debian VM, but for completeness will check the above commands.
The proposed fix here again more or less hung stuff up.
sig@sig-fog-3:~$ sudo fuser -vki /var/lib/dpkg/lock
[sudo] password for sig:
sig@sig-fog-3:~$ sudo apt purge snapd
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
sig@sig-fog-3:~$ sudo dpkg --configure -a
Setting up libgstreamer-plugins-base1.0-0:amd64 (1.14.4-1ubuntu1.1~ubuntu18.04.1) ...
Setting up libpython3.6-stdlib:amd64 (3.6.8-1~18.04.1) ...
Setting up gstreamer1.0-plugins-base:amd64 (1.14.4-1ubuntu1.1~ubuntu18.04.1) ...
Setting up gir1.2-gtk-3.0:amd64 (3.22.30-1ubuntu3) ...
Setting up libdrm-amdgpu1:amd64 (2.4.97-1ubuntu1~18.04.1) ...
Setting up libedataserver-1.2-23:amd64 (3.28.5-0ubuntu0.18.04.2) ...
Setting up cups-browsed (1.20.2-0ubuntu3.1) ...
Setting up plymouth-label (0.9.3-1ubuntu7.18.04.2) ...
Setting up usb-creator-gtk (0.3.5ubuntu18.04.1) ...
Setting up gstreamer1.0-pulseaudio:amd64 (1.14.4-1ubuntu1~ubuntu18.04.1) ...
Setting up plymouth-theme-ubuntu-text (0.9.3-1ubuntu7.18.04.2) ...
update-initramfs: deferring update (trigger activated)
Setting up gvfs-fuse (1.36.1-0ubuntu1.3.3) ...
Setting up libgnome-bluetooth13:amd64 (3.28.0-2ubuntu0.2) ...
Setting up libgbm1:amd64 (19.0.2-1ubuntu1.1~18.04.1) ...
Setting up libevdocument3-4:amd64 (3.28.4-0ubuntu1.2) ...
Setting up python3.6-minimal (3.6.8-1~18.04.1) ...
Setting up cups-ppdc (2.2.7-1ubuntu2.6) ...
Setting up libebackend-1.2-10:amd64 (3.28.5-0ubuntu0.18.04.2) ...
Processing triggers for initramfs-tools (0.130ubuntu3.8) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-47-generic
Setting up libqmi-glib5:amd64 (1.22.0-1.2~ubuntu18.04.1) ...
Setting up libqmi-proxy (1.22.0-1.2~ubuntu18.04.1) ...
Setting up libebook-contacts-1.2-2:amd64 (3.28.5-0ubuntu0.18.04.2) ...
Setting up snapd (2.39.2+18.04) ...
md5sum: /etc/apparmor.d/usr.lib.snapd.snap-confine: No such file or directory
snapd.failure.service is a disabled or a static unit, not starting it.
snapd.snap-repair.service is a disabled or a static unit, not starting it.
Just in case I messed something up … I’ll create a sixth Ubuntu “quick start” 18.0.4 LTS image for Hyper-V and immediately check the snapd stuff.
== John ==