On May 21, 2013, at 11:20 PM, Adam Williamson wrote:
>
> Are you using a kickstart that installs biosdevname, perhaps?
Nope. I haven't even tried going down that rabbit hole yet.
Chris Murphy
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinf
On May 21, 2013, at 5:50 PM, Doug Ledford wrote:
> On 05/21/2013 04:25 PM, Chris Murphy wrote:
>>
>> On May 21, 2013, at 2:07 PM, Reindl Harald wrote:
>>
>>>
>>>
>>> Am 21.05.2013 22:02, schrieb Chris Murphy:
Maybe someone can explain to me the use case for ONBOOT= where its value
>>>
On Tue, 2013-05-21 at 23:06 -0400, Chris Murphy wrote:
> The configuration files weren't renamed. The ip addr or ip link reported
> device is what's different. The effect is that when the device is p5p1, yet
> there's a configuration file created by anaconda ifcfg-en5s0, even though
> that fil
On May 21, 2013, at 5:14 PM, Dan Williams wrote:
> On Tue, 2013-05-21 at 14:33 -0600, Chris Murphy wrote:
>>
>> Is Gnome > Settings > Network leveraging Network Manager? If so, it's using
>> a different naming convention than systemd, and it seems the two are
>> involved in some non-determini
On Tue, 2013-05-21 at 22:58 -0400, Chris Murphy wrote:
> > Ok, so the issues are with the GNOME control center network panel, not
> > specifically the NM core daemon?
>
> The issue is with Gnome Settings, and anaconda's behavior which has changed
> from F18 to F19. In F18, it sets ONBOOT=on even
On May 21, 2013, at 5:03 PM, Dan Williams wrote:
> On Tue, 2013-05-21 at 14:02 -0600, Chris Murphy wrote:
>> Automatically may work as designed, but it's a flawed design. It makes no
>> sense to have an admin user enable a network through the Gnome shell toolbar
>> icon (Network icon, flip the
Chris Murphy wrote:
> On May 21, 2013, at 2:51 PM, Adam Williamson wrote:
> > On Tue, 2013-05-21 at 14:33 -0600, Chris Murphy wrote:
> >> Is Gnome > Settings > Network leveraging Network Manager? If so, it's
> >> using a different naming convention than systemd, and it seems the two
> >> are invol
On 05/21/2013 04:25 PM, Chris Murphy wrote:
>
> On May 21, 2013, at 2:07 PM, Reindl Harald wrote:
>
>>
>>
>> Am 21.05.2013 22:02, schrieb Chris Murphy:
>>> Maybe someone can explain to me the use case for ONBOOT= where its value
>>> isn't tied
>>> to the current network state. I wasted an inor
On Tue, 2013-05-21 at 14:18 -0700, Adam Williamson wrote:
> On Tue, 2013-05-21 at 15:15 -0600, Chris Murphy wrote:
>
> > Anaconda creates ifcfg-en5s0, but sometimes the interface doesn't get
> > an IP address via DHCP on boot. Sometimes it does. I haven't figured
> > out why. But if I delete this
On Tue, 2013-05-21 at 15:15 -0600, Chris Murphy wrote:
> Anaconda creates ifcfg-en5s0, but sometimes the interface doesn't get
> an IP address via DHCP on boot. Sometimes it does. I haven't figured
> out why. But if I delete this ifcfg- file, and have Gnome > Network
> create a new profile, it cre
On May 21, 2013, at 2:51 PM, Adam Williamson wrote:
> On Tue, 2013-05-21 at 14:33 -0600, Chris Murphy wrote:
>> On May 21, 2013, at 2:08 PM, Adam Williamson wrote:
>>
>>> On Tue, 2013-05-21 at 14:02 -0600, Chris Murphy wrote:
>>
>> I'm just trying to figure out the simple case for now: single
On Tue, 2013-05-21 at 14:33 -0600, Chris Murphy wrote:
> On May 21, 2013, at 2:08 PM, Adam Williamson wrote:
>
> > On Tue, 2013-05-21 at 14:02 -0600, Chris Murphy wrote:
> >
> >> 1. Connect Automatically may work as designed, but it's a flawed
> >> design. It makes no sense to have an admin user
On Tue, 2013-05-21 at 22:07 +0200, Reindl Harald wrote:
>
> Am 21.05.2013 22:02, schrieb Chris Murphy:
> > Maybe someone can explain to me the use case for ONBOOT= where its value
> > isn't tied
> > to the current network state. I wasted an inordinate, unreasonable amount
> > of time
> > tryi
On Tue, 2013-05-21 at 14:02 -0600, Chris Murphy wrote:
> On May 21, 2013, at 1:09 PM, Dan Williams wrote:
> >>>
> >>>
> >>> But this bug has brought me to a plethora of buggy behavior in the Gnome
> >>> Settings Network panel, so maybe the misery was worth it.
> >>
> >> *THIS*. *This* kind of
On Tue, 2013-05-21 at 14:33 -0600, Chris Murphy wrote:
> On May 21, 2013, at 2:08 PM, Adam Williamson wrote:
>
> > On Tue, 2013-05-21 at 14:02 -0600, Chris Murphy wrote:
> >
> >> 1. Connect Automatically may work as designed, but it's a flawed
> >> design. It makes no sense to have an admin user
Am 21.05.2013 22:25, schrieb Chris Murphy:
> On May 21, 2013, at 2:07 PM, Reindl Harald wrote:
>> Am 21.05.2013 22:02, schrieb Chris Murphy:
>>> Maybe someone can explain to me the use case for ONBOOT= where its value
>>> isn't tied
>>> to the current network state. I wasted an inordinate, un
Am 21.05.2013 22:02, schrieb Chris Murphy:
> Maybe someone can explain to me the use case for ONBOOT= where its value
> isn't tied
> to the current network state. I wasted an inordinate, unreasonable amount of
> time
> trying to figure this out before I realized what was going on
why should
On May 21, 2013, at 2:30 PM, Reindl Harald wrote:
>
>
> Am 21.05.2013 22:25, schrieb Chris Murphy:
>> On May 21, 2013, at 2:07 PM, Reindl Harald wrote:
>>> Am 21.05.2013 22:02, schrieb Chris Murphy:
Maybe someone can explain to me the use case for ONBOOT= where its value
isn't tied
On May 21, 2013, at 2:08 PM, Adam Williamson wrote:
> On Tue, 2013-05-21 at 14:02 -0600, Chris Murphy wrote:
>
>> 1. Connect Automatically may work as designed, but it's a flawed
>> design. It makes no sense to have an admin user enable a network
>> through the Gnome shell toolbar icon (Network
On May 21, 2013, at 2:07 PM, Reindl Harald wrote:
>
>
> Am 21.05.2013 22:02, schrieb Chris Murphy:
>> Maybe someone can explain to me the use case for ONBOOT= where its value
>> isn't tied
>> to the current network state. I wasted an inordinate, unreasonable amount
>> of time
>> trying to
On Tue, 2013-05-21 at 14:02 -0600, Chris Murphy wrote:
> 1. Connect Automatically may work as designed, but it's a flawed
> design. It makes no sense to have an admin user enable a network
> through the Gnome shell toolbar icon (Network icon, flip the switch
> from Off to On), reboot, and then hav
On May 21, 2013, at 1:09 PM, Dan Williams wrote:
>>>
>>>
>>> But this bug has brought me to a plethora of buggy behavior in the Gnome
>>> Settings Network panel, so maybe the misery was worth it.
>>
>> *THIS*. *This* kind of thing is why NetworkManager remains unusable
>> for production netwo
On Sun, 2013-05-19 at 09:59 -0400, Nico Kadel-Garcia wrote:
> On Fri, May 17, 2013 at 1:10 AM, Chris Murphy wrote:
> >
> > On May 16, 2013, at 10:49 PM, Dan Williams wrote:
> >
> >> On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
> >>> On May 16, 2013, at 3:36 PM, Chris Murphy wrote:
> >>
On Sun, 2013-05-19 at 09:59 -0400, Nico Kadel-Garcia wrote:
> On Fri, May 17, 2013 at 1:10 AM, Chris Murphy wrote:
> >
> > On May 16, 2013, at 10:49 PM, Dan Williams wrote:
> >
> >> On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
> >>> On May 16, 2013, at 3:36 PM, Chris Murphy wrote:
> >>
On Fri, May 17, 2013 at 1:10 AM, Chris Murphy wrote:
>
> On May 16, 2013, at 10:49 PM, Dan Williams wrote:
>
>> On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
>>> On May 16, 2013, at 3:36 PM, Chris Murphy wrote:
>>>
Rebooted. I still have the problem. Wired connection is Off on each
On 16.05.2013 23:01, Adam Williamson wrote:
> On Thu, 2013-05-16 at 14:57 -0600, Chris Murphy wrote:
…
>> This doesn't happen when booting from Live media, so something's
>> changed since then it seems. The only two things I can think of are
>> the groupinstall virtualization, and creating a VM wit
On May 16, 2013, at 10:49 PM, Dan Williams wrote:
> On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
>> On May 16, 2013, at 3:36 PM, Chris Murphy wrote:
>>
>>> Rebooted. I still have the problem. Wired connection is Off on each reboot.
>>> This happens even if I regress to the 3.9.0 ker
On Thu, 2013-05-16 at 23:49 -0500, Dan Williams wrote:
> On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
> > On May 16, 2013, at 3:36 PM, Chris Murphy wrote:
> >
> > > Rebooted. I still have the problem. Wired connection is Off on each
> > > reboot. This happens even if I regress to the 3
On Thu, 2013-05-16 at 15:44 -0600, Chris Murphy wrote:
> On May 16, 2013, at 3:36 PM, Chris Murphy wrote:
>
> > Rebooted. I still have the problem. Wired connection is Off on each reboot.
> > This happens even if I regress to the 3.9.0 kernel that's used on the Live
> > media, which works on ev
On Thu, 2013-05-16 at 21:47 -0400, Nico Kadel-Garcia wrote:
> On Thu, May 16, 2013 at 5:01 PM, Adam Williamson wrote:
> > On Thu, 2013-05-16 at 14:57 -0600, Chris Murphy wrote:
> >> On May 16, 2013, at 2:17 PM, Chris Murphy wrote:
> >>
> >> >
> >> > OK well this isn't right. On every reboot, wire
On Thu, May 16, 2013 at 5:01 PM, Adam Williamson wrote:
> On Thu, 2013-05-16 at 14:57 -0600, Chris Murphy wrote:
>> On May 16, 2013, at 2:17 PM, Chris Murphy wrote:
>>
>> >
>> > OK well this isn't right. On every reboot, wireless is activated and
>> > connected to. But the wired connection is di
On May 16, 2013, at 3:36 PM, Chris Murphy wrote:
> Rebooted. I still have the problem. Wired connection is Off on each reboot.
> This happens even if I regress to the 3.9.0 kernel that's used on the Live
> media, which works on every boot. Flummoxed.
I found part of the problem:
[root@F19 net
On May 16, 2013, at 3:05 PM, Reartes Guillermo wrote:
> Adam,
>
>> the groupinstall virtualization, and creating a VM with a NIC set to
>> bridged mode.
>
>
> Maybe this refers to creating a macvtap bridge NIC.
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT
link/loopback 00
On May 16, 2013, at 3:05 PM, Reartes Guillermo wrote:
> Adam,
>
>> the groupinstall virtualization, and creating a VM with a NIC set to
>> bridged mode.
>
>
> Maybe this refers to creating a macvtap bridge NIC.
For a handful of tests yesterday it was set to that. All day today it's back to
Adam,
> the groupinstall virtualization, and creating a VM with a NIC set to
> bridged mode.
Maybe this refers to creating a macvtap bridge NIC.
Cheers.
On Thu, May 16, 2013 at 6:01 PM, Adam Williamson wrote:
> On Thu, 2013-05-16 at 14:57 -0600, Chris Murphy wrote:
>> On May 16, 2013, at 2:17
On Thu, 2013-05-16 at 14:57 -0600, Chris Murphy wrote:
> On May 16, 2013, at 2:17 PM, Chris Murphy wrote:
>
> >
> > OK well this isn't right. On every reboot, wireless is activated and
> > connected to. But the wired connection is disabled.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=96395
On May 16, 2013, at 2:17 PM, Chris Murphy wrote:
>
> OK well this isn't right. On every reboot, wireless is activated and
> connected to. But the wired connection is disabled.
https://bugzilla.redhat.com/show_bug.cgi?id=963952
The most relevant line I'm finding is this:
May 16 14:19:22 F19.
37 matches
Mail list logo
