Am 03.02.2015 um 11:59 schrieb Ansgar Burchardt:
> Hi Marin,
>
> please remember to also send replies to the bug report (I've not
> forwarded your message).
>
> The debootstrap log looks a bit more scary than I think it should, but
> I'll take a look at only the systemd error:
>
> On 02/03/2015 11:22 AM, Martin Wuertele wrote:
>> Setting up systemd (215-10) ...
>> Failed to open /dev/urandom: Function not implemented
>> dpkg: error processing package systemd (--configure):
>> subprocess installed post-installation script returned error exit status 1
>
> I think this comes from systemd-machine-id-setup which is called in
> systemd's postinst:
>
> core/machine-id-setup.c:140 (in generate):
> r = sd_id128_randomize(&buf);
>
> libsystemd/sd-id128/sd-id128.c:216:
> r = dev_urandom(&t, sizeof(t));
>
> shared/util.c:2371-2373:
> fd = open("/dev/urandom", O_RDONLY|O_CLOEXEC|O_NOCTTY);
> if (fd < 0)
> return errno == ENOENT ? -ENOSYS : -errno;
>
> To make sure, could you try running systemd-machine-id-setup in the
> chroot? And check if /dev/urandom is present in the chroot?I might be missing something obvious, but where is the supposed dependency cycle between systemd-sysv and systemd? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Pkg-systemd-maintainers mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
