Best posts made by abulhol

@sebastian-roth Thanks for your work, we are in the process of switching to the dev-branch on Ubuntu 22 now and will report any additional bugs we find.

@JJ-Fullmer and @george1421 thank you so much for the immediate responses. I will follow your advice and see if I can fix it.
Regarding the use case, this is for doing malware analysis on bare metal machines (resetting the machine after each analysis).

@Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

Hi there,
Here is some information for anybody upgrading their installation to Ubuntu 18.04 and getting stuck because of the sysv-rc-conf package which does not exist on Ubuntu 18.

The thing is that if you do a fresh install of Ubuntu 18 and then install Fog, you don’t face this issue.

But if you are coming e.g. from Ubuntu 14, you get stuck and as a solution are told to remove the package from config.sh, see: https://forums.fogproject.org/topic/9998/upgrade-ubuntu-16-10-to-17-04-sysv-rc-conf-fail

This “riddle” has been asked but not answered here: https://github.com/FOGProject/fogproject/issues/258 before.

I noticed when comparing the two that for the install that gets stuck, the output is:

Installing package: sysv-rc-conf..............................Failed! (Will try later)

while for the fresh install that works it is:

Skipping package: sysv-rc-conf..............................(Does not exist)

I wondered what that meant and had a look at /lib/common/functions.sh

What happens here is that the installer calls:

eval $packagelist "$x"

which in this case is:

apt-cache pkgnames | grep sysv-rc-conf

Now on a fresh Ubuntu 18, this will give you no output and return code 1, while on an upgraded Ubuntu, it is

sysvr-rc-conf

and the return code is 0, because the package has been removed, but is still listed by dpkg and marked as “rc”.

To cut a long story short, before you install Fog, completely purge sysvr-rc-conf, and you will be fine:

sudo apt purge sysv-rc-conf

Have fun!

@JJ-Fullmer Just a short update on this issue: The NUC’s BIOS was outdated, and updating it failed for unknown reasons. We now replaced the NUC with a brand new one and hope to see the issue gone.

PR created in dev-branch