Bogdan Costescu wrote:
On Sat, 7 Mar 2009, Seewer Philippe wrote:
That would mean adding tons of drivers and another layer of complex
code to decide at runtime what parts of the initrd to run.
I could argue the same for the drivers for the block devices and their
tools. If the root is using NFS, there is no need for a block device
detection; this however is still needed for iSCSI (and possibly FCoE in
the future).
Exactly.
Maybe allow at build time to specify what boot drivers+tools to be
included ? This would certainly reduce the generic-ness of the
initramfs, but would also reduce the size and complexity.
dracut can already do this. I was speaking about an initrd of doom which
would include all manners of drivers and tools to boot from/to anything.
For net-boots I couldn't care less about boot time and the size of the
initrd.
I do. When I boot 100+ cluster nodes at once from a single server, I
want to minimize the network traffic at a minimum, especially a part
that happens over UDP.
He. point taken.
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
