Re: mkroot quickstart (was RE: Testing on lots of architecture targets with mkroot.)
"Roberto A. Foglietta" <[email protected]> Tue, 2 Jun 2026 07:52:29 +0200
| Newsgroups | org.kernel.vger.linux-embedded |
|---|---|
| Message-ID | <CAJGKYO4Gbq7OAyS-73aMghSx+=j67mGzU-_KXCQHT3=7HJGEwA@mail.gmail.com> |
On Sat, 30 May 2026 at 23:58, Rob Landley <[email protected]> wrote: > > > In theory the toybox list, although that's in the process of migrating > from dreamhost to osuosl because osuosl is the same host busybox is using (not a question, a statement) > Your absolute minimum is rdinit=/bin/sh or similar, but the mkroot init > is trying to do the minimum work to bring up a usable environment with > mount points and networking before running the $HANDOFF program. from a PoV of the kernel it matters the /init timestamp from a PoV of the kernel what precedes t=0 is unknown / uncertain from a PoV of the real-world observer what precede kernel t=0 matters and /init timestamp depends by the hardware and the kernel version/config IMHO, the minimum boot time is a question as well-defined as: what "boot" means and where? Best regards, R-