Hi Damien, On Sun, Jul 16, 2023, 13:39 Damien Zammit <dam...@zamaudio.com> wrote: > This standardises the format of the boot parameters so that > they all use the same parameter --next-task to specify the next > task in the boot order.
I mentioned this in some other thread, repeating now: I have this grand plan for reworking server bootstrap; it involves a single task (/hurd/bootstrap) doing basically all bootstrap specifics, and the rest of the tasks running mostly as normal (as if not during boostrap) — certainly not resuming each other in a chain, nor passing host_priv / kernel_task / device_master ports in a special way. This may or may not actually happen depending on my motivation (and on whether y'all approve it in the end), but I have already started writing some of the code. This should not block any of your work, but just please keep in mind that the current way you're doing these early bootstrap things — libmachdev, starting each other in a chain and all being aware of early bootstrap specifics — could get changed / simplified radically. In the same vein, I'm not sure if adding this to GRUB is a good idea, if we're going to rip it out (say) half a year later. Again, I certainly can't promise anything, but this is just something to keep in mind. I'd be happy to share more details about the grand plan if you're interested — and actually it'd be great to discuss this with you since I don't know much about device drivers etc. and you might point out some important shortcomings in my plan. Sergey
