Your message dated Mon, 11 Nov 2024 01:10:26 +0100
with message-id <[email protected]>
and subject line Re: Bug#1033802: (no subject)
has caused the Debian Bug report #1033802,
regarding dropbear-initramfs: sleep and cat not found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1033802: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033802
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dropbear-initramfs
Severity: important

I am trying to sort out this bug, but the machine is blocked in an endless loop

It does /scripts/init-bottom

And then the monitor displays in an endless loop:
/scripts/init-premount/dropbear: line 339: sleep: not found
/scripts/init-premount/dropbear: line 149: cat: not found

I think the source code is at: 
https://salsa.debian.org/debian/dropbear/-/blob/debian/2022.83-1/debian/initramfs/scripts/init-bottom/dropbear#L48

So it's maybe waiting for a non starting dropbear.


I used https://wiki.debian.org/DropBear as an example and did set: 
DROPBEAR_OPTIONS="-p 2222 -s"

--- End Message ---
--- Begin Message ---
On Sun, 10 Nov 2024 at 19:32:15 -0400, [email protected] wrote:
> I don't yet know the failure chain that leads from no adapter present
> to sleep and cat not found.
> […]
> If an ethernet adapter is present in the initramfs stage then this bug does
> not appear to occur, regardless of whether the adapter is configured with an
> IP address or not.

Yup, that's https://bugs.debian.org/1079392#32 and the requirement is
documented.

-- 
Guilhem.

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to