suse-9.3 initrd wonkyness

[Net Llama!]

I've been fighting with this bizarro problem for the past 3 days, and I'm
about at my wit's end, so hopefully one of you suse experts can help.

I'm trying to create a suse auto-install CD that will use autoyast to
install the packages from a separate box on the network.  I've got suse
9.3-x86, 10.0-x86, and 10.0-x86_64 all working perfectly.

For reasons which remain a mystery, 9.3-x86_64 seems to have this perverse
requirement that both a 32 & 64bit initrd be included on the CD or I end
up with a br0k3n installation, or the installer kernel panics cause it
can't find init.

Now, maybe both initrds aren't a requirement, but everything i'm reading
seems to suggest that they are.  At this point, i don't even care why it
needs both, when 10.0 doesn't, i'd just like to understand where they are
called/named so that I rename them to something other than 'initrd' and
'initrd64'.  Anyone know?

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman                        netllama at linux-sxs.org
LlamaLand				http://netllama.linux-sxs.org