Re: grab-boot-data.sh fails on mkroot (zombies abound)

On Mon, 29 Jun 2026 at 23:00, Bird, Tim <[email protected]> wrote:
>
>
>
> > -----Original Message-----
> > From: Rob Landley <[email protected]>
> >
> > On 6/18/26 13:40, Bird, Tim wrote:
> > > Hey Rob,
> > >
> > > I tried grab-boot-data.sh on mkroot, using 'toybox sh' as interpreter.
> > > I got some weird behavior that I'd like to report.  (I was planning on experimenting
> > > more to see if I could determine the issue, but I'm going on vacation next week.)
> > > Maybe you have an idea off the top of you head what might be the problem...
> > >
> > > When I use init=/bin/sh, and then try to run grab-boot-data.sh, it always
> > > goes zombie after execution.
> >
> > Do you mean rdinit=? (Or does 7.0 make init= apply to initramfs now?)
>
> Actually, I was doing:
> KARGS="quiet initcall_debug log_buf_len=1M HANDOFF=/bin/sh" root/i686/run-qemu.sh
> (which I presumed, mistakenly, turned into 'init=/bin/sh' on the kernel command line.)
>
> But, upon closer inspection HANDOFF is handled by root/i686/fs/init, which is a shell script
> with this line in it:
>   setsid -c <>/dev/$(sed '$s@.*[ /]@@' /sys/class/tty/console/active) >&0 2>&1 \
>       $HANDOFF
>

The init ROB fs is referring to toybox's Rob Ladley, not Rob(erto)

https://github.com/robang74/bare-minimal-linux-system/blob/main/update/initrobfs/init

feel free to help yourself, R-