On Wed, 2013-06-05 at 11:15 -0600, Nathanael D. Noblet wrote: > So does fedup or anything in that chain create connection files? I > would imagine no since no one else is experiencing this issue but wanted > to make sure. Basically, no: all fedup does is install RPMs¹. The only fedup-specific thing I can think of in that area is dracut's ifcfg module, which writes /etc/sysconfig/network-scripts/ifcfg-*² if you bring up the network in initrd³ - but those always have "ONBOOT=yes", so that's probably not it. But: since each individual package upgrade can run up to 12 scriptlets⁴, a lot happens during fedup that isn't actually *in* fedup⁵. So it's likely you'll need to poke around in the scriptlets to see if anything in there might be doing anything weird with connection files. -w ¹ Okay, actually it downloads RPMs and boot images, then sets up the boot images, *then* installs RPMs. But that's all. More or less. ² Actually it writes config files in into /run/initramfs/state, and fedora-import-state.service copies those files into the root filesystem once it's mounted read-write. Details, details.. ³ Note that this is the fedup initrd, not your normal initrd; see note 1 ⁴ See http://goo.gl/PGc5l ⁵ Yes, this is part of why upgrades take so long. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
