From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sergey Vlasov Date: Wed, 14 Feb 2007 20:55:20 +0000 Subject: Re: [RESEND] [PATCH] by-path persistence for NICs Message-Id: <20070214235520.7f9dac3b.vsu@altlinux.ru> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============0280556499==" List-Id: References: <45D25492.6050203@kadzban.is-a-geek.net> In-Reply-To: <45D25492.6050203@kadzban.is-a-geek.net> To: linux-hotplug@vger.kernel.org --===============0280556499== Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Wed__14_Feb_2007_23_55_20_+0300_xb1U1DFly3SoDCgN" --Signature=_Wed__14_Feb_2007_23_55_20_+0300_xb1U1DFly3SoDCgN Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Wed, 14 Feb 2007 12:49:36 -0500 Bryan Kadzban wrote: > On Wed, Feb 14, 2007 at 11:22:45AM +0100, Marco d'Itri wrote: > > USB paths change frequently. > > You're right, rats. So would paths for other removable devices. > > Well, I'm not sure whether that's a showstopper, but I think it probably > is. I was only thinking about PCI hardware and what happens when a NIC > dies and is replaced. With MAC-based persistence, the MAC address in > the generated rules file needs to be changed to the new NIC's MAC before > the new NIC is inserted, otherwise the system's configuration (e.g. the > config files for the distro's network boot script) is invalid. Even worse, sometimes you need to change MAC to the value from the old card, because someone dumb at the other end configured static ARP entries supposedly to increase security, and it is easier to change the MAC locally than to make the other end update its config. Then you need to have rules both for the new and the old MAC (the latter for the case when the device is processed by udev again for some reason). > But that's not as big of a deal as forcing the user to use the same USB > port (or more accurately, the same physical path) all the time. > > > Anyway it must not be the default. > > It's not the default (in that patch anyway), but from what you said > about it not working for anything removable, it sounds like it's not a > good idea in any case. I think this kind of persistence would fail more > often than MAC-based persistence does. > > So: Retracted, unless someone wants to pick it up even with this issue. > There's no way around the problem either. It could be possible to detect the device type and use different persistence methods for different kinds of devices. And the first part of the patch (path_id change to support network devices) could be useful by itself at least for manual configuration. --Signature=_Wed__14_Feb_2007_23_55_20_+0300_xb1U1DFly3SoDCgN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.1 (GNU/Linux) iD8DBQFF03c7W82GfkQfsqIRAkvfAJ9jMIin4ggDks519IH7PQAGjMC0oACeKhNR ZFA5sIfjhgJ/ZDfZ0V2HZ0E= =DiMp -----END PGP SIGNATURE----- --Signature=_Wed__14_Feb_2007_23_55_20_+0300_xb1U1DFly3SoDCgN-- --===============0280556499== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV --===============0280556499== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel --===============0280556499==--