[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [PATCH] Preserve network config files for upgrade and kickstart installs.
- From: David Cantrell <dcantrell redhat com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: [PATCH] Preserve network config files for upgrade and kickstart installs.
- Date: Fri, 05 Dec 2008 09:58:52 -1000
Jeremy Katz wrote:
> 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?
I was only working within the context that the suggestion described.
I'm not opposed to having the checks work all the time, which would make
things a bit more simple in the code.
New patch coming.
--
David Cantrell <dcantrell redhat com>
Red Hat / Honolulu, HI
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]