Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756431Ab0GIRLD (ORCPT ); Fri, 9 Jul 2010 13:11:03 -0400 Received: from mail-vw0-f46.google.com ([209.85.212.46]:38694 "EHLO mail-vw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757154Ab0GIRLA (ORCPT ); Fri, 9 Jul 2010 13:11:00 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=k/KOlb+3d3gamLSMW0KpfjjNZkYRBGj1bUDQeuKrpYip7UcUpbElYTlOtwyEMpDMoZ QzDd21rMFAN8UswgL7AUShxcqgHKmCudTSFPP5gqF0fBf0RrEANMx2BjrXAUMs7Dk3t0 fYv9Q1I1NbAlhxGxLf6ixAtXLOhFboQCKEK1o= MIME-Version: 1.0 In-Reply-To: References: <20100708012120.GB11419@auslistsprd01.us.dell.com> <82tyo9i0n2.fsf@mid.bfk.de> Date: Fri, 9 Jul 2010 10:10:58 -0700 Message-ID: Subject: Re: nic enumeration From: Steve Fink To: "Loke, Chetan" Cc: Florian Weimer , linux-net@vger.kernel.org, Matt Domsch , Michael Di Domenico , linux-kernel@vger.kernel.org, kay.sievers@vrfy.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1354 Lines: 25 On Fri, Jul 9, 2010 at 9:27 AM, Loke, Chetan wrote: > Ok, no renaming, I would like a reference. And symlink just doesn't work > w/ the udevadm trigger business. We've tried that already. > > What needs to be changed in udev etc to create a soft link? Any place > where I should start digging and gotchas to lookout for? By "soft link", I assume you're talking figuratively? Soft (symbolic) links are a filesystem concept, implemented by filesystem-specific logic that knows how to read a filename out of an inode and restart lookup. In order for something similar to work for network devices, somebody would have had to explicitly implement similar functionality. (Symlinks are a big headache and source of security holes -- access control, loops, pointing to nonexistent files, etc. -- so there's a good reason to NOT have an equivalent for network devices.) But perhaps there *is* an equivalent: what about (ab)using bridges? Create a set of bridges and bind each one to a single NIC. You can name the bridges whatever you want, and set up the mapping through arbitrary logic. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/