Re: [lmi] Creating a chroot for cross-building lmi

[Greg Chicares]

[...entering some old notes into the record to establish the
importance of this advice:
  https://wiki.debian.org/chroot#Configuration
to prevent dpkg from starting daemons in the chroot...]

On 2016-09-26 01:35, Greg Chicares wrote:
[...]
> Setting up uuid-runtime (2.25.2-6) ...
> Adding group `uuidd' (GID 109) ...
> Done.
> Warning: The home dir /run/uuidd you specified can't be accessed: No such 
> file or directory
> Adding system user `uuidd' (UID 104) ...
> Adding new user `uuidd' (UID 104) with group `uuidd' ...
> Not creating home directory `/run/uuidd'.
> invoke-rc.d: policy-rc.d denied execution of start.

Earlier (before creating 'policy-rc.d', and also before mounting /proc )
I observed the same thing, except that instead of the last line I got:

Failed to read /proc/cmdline. Ignoring: No such file or directory
[ ok ] Starting uuid generator: uuidd.

Similarly:

> Setting up dbus (1.8.20-0+deb8u1) ...
> invoke-rc.d: policy-rc.d denied execution of start.

Instead of the 'policy-rc.d' line, I earlier saw:

Failed to read /proc/cmdline. Ignoring: No such file or directory
[FAIL] Can't start system message bus - /proc is not mounted ... failed!

[Mounting /proc without creating a 'policy-rc.d' that simply does
"exit 101" allowed that daemon to start, which is not wanted.]

> Setting up rsync (3.1.1-3) ...
> invoke-rc.d: policy-rc.d denied execution of restart.

Instead of the 'policy-rc.d' line, I earlier saw:

Failed to read /proc/cmdline. Ignoring: No such file or directory