From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id AECA8138010 for ; Tue, 2 Apr 2013 21:36:49 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 37DABE0E34; Tue, 2 Apr 2013 21:36:40 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id C9DBEE0E2E for ; Tue, 2 Apr 2013 21:36:38 +0000 (UTC) Received: from digimed.co.uk (shooty.digimed.co.uk [192.168.1.8]) by mail.digimed.co.uk (Postfix) with ESMTPA id C425A8052C for ; Tue, 2 Apr 2013 22:36:30 +0100 (BST) Date: Tue, 2 Apr 2013 22:36:24 +0100 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Udev update and persistent net rules changes Message-ID: <20130402223624.71e26ab0@digimed.co.uk> In-Reply-To: References: <515701AE.9010509@libertytrek.org> <20130401192628.GA3717@linux1> <5159E551.4050609@gmail.com> <201304020100.25920.peter@humphrey.ukfsn.org> <515B2FA1.9090805@gmail.com> <515B3461.7080603@libertytrek.org> <515B387A.4020002@gmail.com> Organization: Digital Media Production X-Mailer: Claws Mail 3.9.0-156-gf9f793 (GTK+ 2.24.17; x86_64-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/y9hg=m1sPNE0+Jz1xB_Feom"; protocol="application/pgp-signature" X-Archives-Salt: 78cf6ada-8c68-4b27-a4ac-b2ace483a8e8 X-Archives-Hash: b5b417f515e28d76a54d89204d4635c6 --Sig_/y9hg=m1sPNE0+Jz1xB_Feom Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 2 Apr 2013 20:31:10 +0000 (UTC), Grant Edwards wrote: > In Flameyes blog, he showed an example of using udev rules pretty much > identical to the ones I already had, so I couldn't figure out what was > different (other than the default interface names, which still aren't > really predictable). They are totally predictable, since the names are specified in the rules, so you can predict what the interface will be called, it's what the rules file says it will be called. However, the important issue is persistence, whatever name an interface has is the name it will always have. The rules renaming within the kernel namespace, eth, wlan etc, could not guarantee that because of race conditions, and the so-called persistent names from the new udev still cannot do the same for devices that can be physically moved (mainly USB). The simplest solution is to do what the news item suggests, rename the persistent-net rules file and rename the interfaces within it to not clash with the kernel. That's all you need to worry about when going from 197 to 200, upgrading from earlier versions means you should act on the parts about DEVTMPFS and runlevel files. --=20 Neil Bothwick Am I ignorant or apathetic? I don't know and don't care! --Sig_/y9hg=m1sPNE0+Jz1xB_Feom Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlFbT10ACgkQum4al0N1GQMxnwCeMqtei0JUvlnKUl8ZIBsHXfDO UUoAnAu0w0fkQ/ATTSHarK5rxo6OXcbZ =UgY1 -----END PGP SIGNATURE----- --Sig_/y9hg=m1sPNE0+Jz1xB_Feom--