On Wed, Aug 11, 2010 at 05:05, Scott Talbert <talbert@xxxxxxxxxx> wrote: > On Mon, 9 Aug 2010, Kay Sievers wrote: > >> The behavior is undefined, and can only be controlled with >> link_priority= option. >> >> We can't, and don't want to pretend to make any control over 'the >> first one'. In a hotplug world, there is almost never a correct first >> one, because everything runs in parallel. > > I agree with you that if two devices are hotplugged at around the same time, > the result would be expectedly unpredictable. However, if you have your > root partition (with a symlink established at bootup), and then hours later, > you hotplug another device, it would seem to me that the symlink of the > older device would be preferable to keep. Right now, the symlink for the > original device is removed and a symlink for the new one is added. > > I propose a slightly different change. This changes the symlink priority > processing when the priorities are the same. The oldest symlink is instead > preferred, rather than the newest one. Well, other people might want it the other way around, and want to access the device they just plugged-in. Or they want to find the raid device after setting it up, not the member of the raid. Also multiple events run in parallel when a device is discovered, not even partitions from the same device have any defined ordering here. So, there is absolutely no guarantee about that, it's just luck in many cases, which one wins. As said, it does not really make sense to try to optimize anything here, we don't have under control. Kay -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
