[lkml]   [2012]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: network regression: cannot rename netdev twice
    On Tue, 31 Jan 2012, Kay Sievers wrote:
    > Please make sure nothing tries to swap netif names in userspace. We
    > have given up that approach, because it is far too fragile to
    > temporary rename devices to be able to swap the names, and race
    > against the loading of new kernel network drivers at the same time.

    That's a damn fair reason, but the loss of that functionality could cause
    trouble. In fact, at first glance, to me it looks like this has a large
    potential for unleashing untold pain and suffering in the sysadmin ranks
    unless early userspace can emulate it somehow.

    Is it possible to configure the kernel to use something other than "eth#" as
    its initial namespace for netif names? Or is there some other way to get
    eth1 to be what you need eth1 to be during userland boot?

    "One disk to rule them all, One disk to find them. One disk to bring
    them all and in the darkness grind them. In the Land of Redmond
    where the shadows lie." -- The Silicon Valley Tarot
    Henrique Holschuh

     \ /
      Last update: 2012-02-04 03:17    [W:0.020 / U:43.652 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site