On 21 Oct 2009, Stephen Hemminger stated: > On Tue, 20 Oct 2009 19:54:02 +0100 > Nix <nix@xxxxxxxxxxxxx> wrote: >> This makes it much easier to use things like netconsole which bring up a >> network interface before userspace has started: presently these will cause >> interface renamings to fail, breaking any userspace that relies on renaming >> devices to avoid reliance on the potentially-unstable kernel-assigned name. [...] > This breaks quagga and other applications that track renames. I've figured out how to do it without patches now. The following doc patch may help other puzzled users. --- Documentation/networking/netconsole.txt | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/Documentation/networking/netconsole.txt b/Documentation/networking/netconsole.txt index 8d02207..11c7b90 100644 --- a/Documentation/networking/netconsole.txt +++ b/Documentation/networking/netconsole.txt @@ -132,6 +132,13 @@ the sender, it is suggested to try specifying the MAC address of the default gateway (you may use /sbin/route -n to find it out) as the remote MAC address instead. +TIP: if you need to rename the network interface (as is done by many +distributions in their startup scripts), you may find that it fails +for interfaces managed by netconsole, because you cannot rename +interfaces that are up. The solution here is to take the interface +down around the renaming, then bring it up again or let the normal +boot process do so. + NOTE: the network device (eth1 in the above case) can run any kind of other network traffic, netconsole is not intrusive. Netconsole might cause slight delays in other traffic if the volume of kernel -- 1.6.5.1 -- To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
