On Thu, 2008-12-04 at 17:30 -1000, David Cantrell wrote: > The suggestion for this patch came from OLPC (or someone with an > @laptop.org email address). The user was doing a kickstart install > and adding a local yum repo that provided an RPM of site-specific > configuration files, including ifcfg-DEVICE files. This package > would get installed just fine, but then anaconda drives over the > configuration files after package installation. > > If doing a kickstart install or an upgrade install, preserve any > network configurations that we want to write over in anaconda. Arguably, the same could hold true on a non-kickstart install. It may not be a likely case, but the whole thing is an uncommon case. So why not just check if the files exist before writing to them and if they do, skip as opposed to only doing so for kickstart or an upgrade? Jerem _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
