Separate initrd/vmlinuz for different media / arch?
 

Well, might as well ask here. Distribution I am usually using is latest debian.

Question:
Why is there separate kernel and ramdisk for different install media or even different architecture and not kernel/ramdisk that would ask the installation method and system architecture before starting the load process like the bootloaders distributions comes with can do (isolinux/syslinux/grub 2/hell even G4D thx to chenall) and load "almost" any architecture?

Because the binary kernel is different ( the compilation ) depending on which arch it is. The kernel image would be huge if you tried to pack everything together.

I know it's huge, currently compiling/building one as there is none which I am aware.

I don't see how or why 'size' would be comparable with 'support' which is why I am asking. Also the idea of missing something existing like network,storage hardware or filesystem support is completely none sense as they could be build together. Of course some media formats can be ignored, but at least having all standards supported would be improvement.

Why would it matter, if kernel and ramdisk takes 35MB or 500MB, if it can boot anything existing and would be modifiable at start time? (or only thing I can think of is BIOS INT13 limitation 503,44MB.)