Received: by oss.sgi.com id ; Sun, 7 Jan 2001 02:23:09 -0800 Received: from james.kalifornia.com ([208.179.0.2]:23146 "EHLO james.kalifornia.com") by oss.sgi.com with ESMTP id ; Sun, 7 Jan 2001 02:22:54 -0800 Received: from Huntington-Beach.Blue-Labs.org (mail@Huntington-Beach.Blue-Labs.org [208.179.0.198]) by james.kalifornia.com (8.11.0/8.11.0) with ESMTP id f07AMde13475; Sun, 7 Jan 2001 02:22:39 -0800 Received: (from david@localhost) by Huntington-Beach.Blue-Labs.org (8.9.3/8.9.0) id CAA04222; Sun, 7 Jan 2001 02:22:33 -0800 Date: Sun, 7 Jan 2001 02:22:31 -0800 (PST) From: David Ford X-Sender: david@Huntington-Beach.Blue-Labs.org To: Chris Wedgwood cc: Ben Greear , linux-kernel , "netdev@oss.sgi.com" Subject: Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission policy!) In-Reply-To: <20010107162905.B1804@metastasis.f00f.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-netdev@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;netdev-outgoing Content-Length: 706 Lines: 18 On Sun, 7 Jan 2001, Chris Wedgwood wrote: > Virtual IP interfaces in the form of ifname: (e.g. eth:1) IMO > should be deprecated and removed completely in 2.5.x. It's an ugly > external wart that should be removed. > > That said, if this was done -- how would things like routing daemons > and bind cope? Actually, when I think about it they can't cope with > situating like this now: > > tapu:~# ip addr show lo > 1: lo: mtu 3904 qdisc noqueue > link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > inet 127.0.0.1/8 scope host lo > inet 10.0.0.1/32 scope global lo BIND copes just fine, how would it not? I haven't heard any problems with routing daemons either.