> I'm not fluent enough in freebsd boot process to know whether or not this is
> correct.
> My only question is why this wasn't seen before.
>
> Did something change that caused it?
Yes, that was caused by my previous fix of enabling cloud-init for FreeBSD on Azure.
It introduces a dependency on 'ldconfig' which can make sure the *.so library for python were loaded. But 'ldconfig' has already depended on 'FILESYSTEM', so cloudinitlocal should not depend on 'FILESYSTEM' again.
> I'm not fluent enough in freebsd boot process to know whether or not this is
> correct.
> My only question is why this wasn't seen before.
>
> Did something change that caused it?
Yes, that was caused by my previous fix of enabling cloud-init for FreeBSD on Azure.
It introduces a dependency on 'ldconfig' which can make sure the *.so library for python were loaded. But 'ldconfig' has already depended on 'FILESYSTEM', so cloudinitlocal should not depend on 'FILESYSTEM' again.
What is the design purpose of cloudinitlocal?