You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
Got a couple of errors when the helper script tried to configure the rootfs:
invoke-rc.d: could not determine current runlevel
invoke-rc.d: WARNING: No init system and policy-rc.d missing! Defaulting to block.
Setting up udev (247.3-7+deb11u2) ...
A chroot environment has been detected, udev not started.
Setting up ssh (1:8.4p1-5+deb11u1) ...
Setting up i2c-tools (4.2-1+b1) ...
Failed to send reload request: No such file or directory
Failed to scan devices: No such file or directory
Processing triggers for libc-bin (2.31-13+deb11u6) ...
Errors were encountered while processing:
base-files
bash
passwd: password expiry information changed.
grep: build/armhf/armhf-rootfs/lib/systemd/system/[email protected]: No such file or directory
sed: can't read build/armhf/armhf-rootfs/lib/systemd/system/[email protected]: No such file or directory
sed: can't read build/armhf/armhf-rootfs/etc/systemd/system.conf: No such file or directory
sed: can't read build/armhf/armhf-rootfs/etc/systemd/system.conf: No such file or directory
build/armhf/armhf-rootfs-20230513T052452Z configured
The final rootfs is later not functional and fails to get to a login prompt after:
/bin/sh: 0: can't access tty; job control turned off
The text was updated successfully, but these errors were encountered:
Currently, when using multistrap, this problem will occur in versions above jessie. This will cause bash to not be compiled successfully, and will also cause this fault to be reported when entering debian.
Running:
Got a couple of errors when the helper script tried to configure the rootfs:
The final rootfs is later not functional and fails to get to a login prompt after:
The text was updated successfully, but these errors were encountered: