Mike Anderson wrote:
Well this may not be kernel issue, the perception to many users is that
something is wrong with the IO subsystem. I would agree we know how to
solve this, but I have need seen any distro based mkinitrd scripts
generate an initrd with a "wait for root dev" step.
Does anyone know of a distro initrd / initramfs creation script that has
this support? As a side note I do not understand historically why one
would every want to leave the initrd without a root dev present and end in
an oops.
s/oops/panic/, you mean.
IMO there are two philosophical positions here:
1) "the Linus position": discovery should be in-kernel, because
otherwise, users with a missing/screwed initrd will simply not be able
to boot.
2) "the purist position": discovery initiated/controlled by userland
gives us a LOT more flexibility, and keeps obviously-userspace code out
of the kernel.
Both have their merits: The Linus position means all users will boot,
but with the disadvantage that the kernel cannot know which SAS WWN is
the desired boot device, and other state such as connection/topology
parameters. The purist position guarantees you the
topology/rootdev/etc. that you want, but you MUST have the necessary
initrd glue, otherwise the driver is useless.
A compromise position might be, do discovery in kernel, using hints from
userspace IF AVAILABLE.
Jeff
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
