One thing to watch out for is kudzu. I ran into a similar situation a couple of weeks ago, with kudzu overwriting the ifcfg files and changing them away from what the %post section was doing, right after the %post section had completed, and before the system had rebooted. That is, kudzu will apparently do some final manipulations after the %post section has run. There doesn't seem to be anything one can do about this either. Note that kudzu is a fundamental part of anaconda/kickstart. You simply can't remove it. RedHat defines an absolute minimal installation as consisting of kudzu (and not coreutils + kernel, which one would expect). One can get around this limitation by creating the equivalent of a .firstboot in /etc/rc.d/rc.sysinit, which corrects things when one first boots up. Hope that helps. -dwight- On Wednesday 05 March 2008 12:42:09 pm Bryan Kearney wrote: > Good thing I am clever :) > > -- bk > > Michael DeHaan wrote: > > Caetano, Greg wrote: > >> Bryan: > >> > >> I take care of removing all those "specifics" as part of the > >> %post of a kickstart > > > > So in that case, you still have to run system-config-network at > > firstboot (or equivalent)? That seems reasonable -- you may > > be handing something to someone with a static IP setup, you > > don't know. Rethinking it, if you clear things out in %post and > > also feed it network details in the libvirt XML, maybe that's > > good enough... > > > > Still, I'm not sure of a way to do that fully automatically and > > get them all unique MACs without being rather clever... > > > >> Greg Caetano > >> HP ISS Linux Virtualization Solutions Engineering > >> Chicago, IL > >> greg.caetano@xxxxxx > >> Red Hat Certified Engineer > >> RHCE#805007310328754 > >> > >> -----Original Message----- > >> From: kickstart-list-bounces@xxxxxxxxxx > >> [mailto:kickstart-list-bounces@xxxxxxxxxx] On Behalf Of Bryan > >> Kearney Sent: Wednesday, March 05, 2008 1:33 PM > >> To: kickstart-list@xxxxxxxxxx > >> Subject: Resend: Anaconda modifying network files > >> > >> I am using cobbler/koan to generate xen disk images. After a > >> successful install, if I mount the image I see infomation in > >> various networking files which denote the information about the > >> network I built the image on. Specifically: > >> > >> > >> /etc/hosts has the ip address and dhcp fqdn of the image when > >> anaconda was running. > >> /etc/sysconfig/network has the fgdn of the image when anaconda > >> was running. > >> /etc/sysconfig/network-scripts/ifcfg-eth0 has the MAC address > >> given out by xen. > >> > >> Is there a way to configure anaconda to not mutate these files? > >> > >> Thanks! > >> > >> -- bk > >> > >> _______________________________________________ > >> Kickstart-list mailing list > >> Kickstart-list@xxxxxxxxxx > >> https://www.redhat.com/mailman/listinfo/kickstart-list > >> > >> _______________________________________________ > >> Kickstart-list mailing list > >> Kickstart-list@xxxxxxxxxx > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list@xxxxxxxxxx > > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
