search for: buildstamp

...fo/x/xterm ./init/etc/terminfo/v/vt100 ./init/etc/terminfo/v/vt100-nav ./init/etc/terminfo/b/bterm ./init/etc/passwd ./init/etc/arch ./init/etc/keymaps.gz ./init/etc/screenfont.gz ./init/etc/lang-table ./init/etc/loader.tr ./init/etc/font.bgf.gz ./init/etc/pcmcia/config ./init/etc/ramfs.img ./init/.buildstamp ./init/.profile Any help is appreciated. At the moment, we're prevented from installing RH on any of our new hardware until this starts working. Thanks, sh

Hi, Any one know how the Centos 5 kickstart initrd.img was built? I'll be very appreciated if any light can be shed on this topic. The basic problem to be solved here is: how to build a custom vmlinuz+initrd.img for Centos 5 kickstart with my own custom built kernel? I am not sure mkinitrd is the right tool for this purpose? If do, which are the modules I should include with

...dules (it's probably ignoring the run-time arch and relying on the compile time one) - the space savings from using a single initrd aren't that much (1.5), so using the two separated initrds is still feasible (and l32or64 supports it), but the x86_64 initrd needs it's .buildstamp replaced with the one from i386. * single 32 bits minstage2 and stage2 - anaconda support for space separated list of available archs in .discinfo (attachment discinfo.patch) (anaconda has at least 4 different places where it parses the .discinfo file. something should be done ab...