From mboxrd@z Thu Jan 1 00:00:00 1970 From: md@Linux.IT (Marco d'Itri) Date: Mon, 12 Oct 2009 17:54:54 +0000 Subject: Re: PATCH: Network Device Naming mechanism and policy Message-Id: <20091012175454.GA23647@bongo.bofh.it> MIME-Version: 1 Content-Type: multipart/mixed; boundary="EVF5PPMfhYS0aIcm" List-Id: References: <5DDAB7BA7BDB58439DD0EED0B8E9A3AE011CD964@ausx3mpc102.aus.amer.dell.com> In-Reply-To: <5DDAB7BA7BDB58439DD0EED0B8E9A3AE011CD964@ausx3mpc102.aus.amer.dell.com> To: linux-hotplug@vger.kernel.org --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Oct 12, Bill Nottingham wrote: > No, it's not solved. Even if you have persistent names once you install, > if you ever re-image, you're likely to get *different* persistent names; > the first load will always be non-detmerministic. Can somebody remind me what's wrong with establishing a syncronization point in the boot (or installation) process at which time all network devices are enumerated by PCI device order and renamed? I know that this does not solve every problem, but nor do the other methods and this one is more similar to what other operating systems do. --=20 ciao, Marco --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrTbW4ACgkQFGfw2OHuP7EDKwCfUPriJ+ZrTTXI7SZqBVA7Q0tq VIMAn0OXRRT9qkz/YMhSZz3g9btxtvFy =juap -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--