Can you put the results of your work online?
I think i'll try to play a little bit with the booting disc image. I did
some customised Red Hat installers in the past, so i think there should
be no problem now.
I really want to get the damn installer working... :-)
On Tue, 2002-05-14 at 15:10, Michael Best wrote:
> Perhaps someone knows how to do the step that I stopped on, which was to
> generate a disk/disc image for booting from the cdrom. The default
> Redhat installer uses a 2.8M installer image in the dosutils/autoboot
> directory of the cd:
> 2.8M cdboot.img
> 1.9M initrd.img
> Which appears to be a 2.8M boot image which contains:
> 784k of vmlinuz (kernel) and
> 1.9M of initrd.img plus
> various bootup files.
> I need to make one of these and then I can probably make a cd that boots
> with a different kernel. By simply using mkinitrd it makes a minimalist
> initrd image.
> I already did these other steps too:
> *) Added the xfs utilities to RedHat/base/stage2.img
> *) Added the xfs utility rpms to Redhat/RPMS on disc1 and disc2
> *) modified RedHat/base/comps to include xfs util rpms
> *) updated hdlist/hdlist2 in Redhat/base/ using genhdlist from the
> anaconda 7.3 source
> *) learned about embedding the MD5 into the implantisomd5 and
> checkisomd5 from the anaconda 7.3 source
> *) examined the anaconda source code for claimed xfs support
> (it appears to append XFS to the list of available filesystems
> if that filesystem choice is available, more work here is needed)
As many as three times a week, on average, XP users see a little window
pop-up at the bottom of their computer screens announcing the
availability of another new update for their system. This plethora of
patches has left many users wondering whether their hard drives are big
enough to handle "Trustworthy Computing."