Picking apart buildinstall

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

We've currently got a PXE/kickstart setup on RH3.0AS that works fine.
Unfortunately, the new hardware that arrived ( HP DL360's ) use a newer
array controller and the version of the driver we have doesn't work.  We got
the newer driver from HP and it only works with kernel versions 2.4.21-9 and
2.4.21-15.  The kernel version we have on PXE is 2.4.21-4.ELBOOT.  I need to
build a new initrd.img for PXE with the new driver and works on 2.4.21-15.
I'm not entirely sure however, how to build the initrd.img that is usuable
by PXE.  It was suggested on another list that I use the anaconda-runtime
buildinstall instead of trying to figure out how to create it myself.

Unfortunately, our setup isn't exactly standard.  We don't have any 'tree'
to speak of.  We have the following:

/opt/kickstart/RedHat/RPMS
/tftpboot

For those unfamiliar with PXE, it requires tftp to grab the initrd.img and
vmlinuz.  So, that's where our initrd.img and vmlinuz are.  In the RPMS dir,
we basically have every single RPM we've ever used.  Often times, we have
several version of the same RPMS in there.  Then, in /opt/kickstart, we have
our separate config.ks files for the types of machines we build.  So I'm not
sure where exactly the 'base' of our tree would be as it doesn't exactly
resemble the typical Redhat CD and I'm figuring this is why I can't get
buildinstall to work.

I did the hdlist and pkgorder, although I don't really need to build a
custom anaconda or anything.  I just want to get buildinstall to build the
PXE initrd.img.

The following happens when running buildinstall:

./buildinstall --product "RedHad Advanced Server" --comp dist-9 --pkgorder
/tmp/pkgorder.txt --version 9 --release "3.0" /opt/kickstart/
Running buildinstall...
/opt/kickstart/buildinstall.tree.4467 /usr/lib/anaconda-runtime
/usr/lib/anaconda-runtime
Going to run buildinstall again

Advanced/RedHat/RPMS
Usage: buildinstall [--comp <component>] [--pkgorder <file>] [--version
<version>] [--product <product>] [--release <comment>] <root>
/opt/kickstart/buildinstall.tree.4467/buildinstall --buildinstdir
/opt/kickstart/buildinstall.tree.4467 --second --pkgorder /tmp/pkgorder.txt
--comp dist-9 --version 9 --release "3.0" --product "RedHad Advanced Server"
/opt/kickstart/

and then it exits.

I was wondering if anyone could help me out in identifying the parts I need
out of buildinstall to just build an initrd.img or even if that's possible.
I'm a little hazy on how the whole thing works to begin with, so please bear
with me.  I'm not sure if I need a custom vmlinuz as well, but at the
moment, I put the 2.4.21-15 vmlinuz ( from the regular kernel rpm ) and our
old initrd.img with the new ccisss.o driver into /tftpboot and it's still
not working.

Any help with this is appreciated.

--
sh


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux