On Dec 19, 2008, at 3:05 PM, Seewer Philippe wrote:
Jeremy Katz wrote:
[snip]
And yes, everywhere is really more like everywhere(*) -- the stock
config being "local block devices" but with the ability to expand
out and support the more esoteric cases.
Hmmm... if we are realle talking about integrating this _into_ the
kernel why not introduce something like <Mi> "Build as module,
integrate into initramfs?" into kernel config?
Mostly because we have to walk before we can run. :)
[snip]
On the other hand, "early-userspace" is necessary as stated. As a
further suggestion: Why not restrict initramfs really to the "only
mount-/" problem domain. On failures or errors, a fallback ram-image
could be used and switchroot'ed into normally like any other root
which would then do the job. I think this would solve the busybox/
user-needs-shell problem as well, which could reside in the ram-image.
I've similarly thought that this could be a good way to take care of
things like the kdump case which while they use an initramfs are
really a more specialized install image that should be mounted as a
rootfs.
Jeremy
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
