[PATCH 5/5] networking: remove Network() object completely

Radek Vykydal rvykydal at redhat.com
Thu Aug 2 15:28:07 UTC 2012


On 07/27/2012 05:38 PM, Chris Lumens wrote:
>> Do networking initialization in NetworkStandaloneSpoke.__init__.
>> Not completely sure if it is the right place (maybe pre-GUI
>> would be better)
> We have previously talked about the possibility of just trying to bring
> up the network via DHCP very early in anaconda.  I believe this is what
> we talked about at the last design meeting a few weeks ago.  mizmo will
> have to correct me if I am wrong.
>
> If that's the case, there should probably be another thread started up
> at the bottom of the anaconda file, just like there is for storage and
> packaging.
>

That would be a good place for init_networking().

Currently NM activates devices with missing ifcfg files (i.e. basically
those not activated in dracut or specified in kickstart) with auto
connection when it starts but I'd like to create missing ifcfg files
in dracut [1] so that we can control the devices (NM doesn't write
ifcfg files for auto connections). Then we'll really need to run the thread
to activate a device. I'll come with a patch and move init_network to
that place. But first I'd like to clear up the thing with NM
auto-connections [1].

[1] 
https://www.redhat.com/archives/anaconda-devel-list/2012-July/msg00065.html


More information about the anaconda-patches mailing list