Jeremy Katz wrote:
> The reason is that I very much like all the mayflower generated
> stuff that happens up to the point of the existing shell escape. I.e.
> setting up an environment where bash can run and I can see my devices.
> By specifying my own init, I'd basically be duplicating the mayflower
> init generation code, except with my program= escape point, at which
> point... hey, I'm back where this proposal started.
init= doesn't replace the initramfs's init -- it's what is supposed to
be run after you've got the real system. eg, init=/bin/bash to just get
dropped to a shell rather than running /sbin/init. But yeah, after a
quick try, something about it is busted with mayflower. Try it on a
"normal" system, though, to get the effect that's intended
Assuming mayflower gets fixed, would there be any issue with the fact
that in my usage scenarios, there is no real root filesystem, and that
the init I'm trying to specify is a program in the initramfs?