Hi Glenn, Glenn Bailey wrote: > 1) In my current environment we do not track machines by MAC addresses, but rather > by chassis serial #. I'm wanting to modify Anaconda to be able to pull this serial > # via dmidecode, and then use that # as the kickstart file name. Can this be done > in the stage 2, or does it have to know what KS file to use in stage 1? In either > case, can I be pointed in the right direction for making such modifications? The loader normally gets ks.cfg. In ks.cfg the location of stage2 is configured. Therefore I would say you'll have to modify the loader. However there seems to be a new parameter, namely stage2=... I don't know if stage2 is able to load a ks.cfg or if it's too late. If stage2 can do it, updates.img should be a possible solution (like Micah said). > 1) If I roll my own Anaconda from the latest source provided can I use the same > source tree for RHEL 3, 5, and 5 as long as I create the proper stage1 boot? Or > would it be easier to just modify the existing source trees for each distro? Lookin > to do this RHEL distros only (RHEL and CentOS). I think the versions of anaconda between RHEL-3 ... RHEL-5 differ enormously. You'll probably have to modify them separately. Good luck, Niels
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
