On Mon, Jan 11, 2010 at 7:33 AM, Devan Goodwin dgoodwin@rm-rf.ca wrote:
Just trolling for info to see if anyone knows specifics about why Cobbler requires an explicit kernel/initrd on distro's or if there's a unified way they're used. (or expected to be used)
In digging around it seems that if you're doing a physical koan --replace-self, the kernel/initrd specified will be used, although there's also some code in there that will seek the correct pair out if they're not specified or unusable.
In the case of a virt kickstart however (at least KVM) the kernel/initrd isn't used at all, only the install tree is.
Asking around #cobbler-devel I heard that they may just be required for memtest (not something I'm totally familiar with)
Just wondering if this raises any alarms for anyone, or if it's something that needs fixing. Let me know if you have any insight!
Can you explain what you mean a bit more? The distro is generally sucked in from an install tree which (as a side effect) includes a kernel / initrd combo. It would be quite nice to have the kernel/initrd be per-profile instead of per-distro but things like anaconda get really cranky when you don't use the kernel that matches the install tree. Perhaps that is the reason for this?