On 09/20/2013 12:30 AM, Chaiken, Alison wrote: > Stephen Warren writes: >> Patches to make mmc block devices have static names have been proposed >> in the past and rejected. I think the main reason is that the block >> device names are (or can be) dynamic, so anything that assumes a >> particular naming scheme is simply broken. > > Why may network devices have static IPs and yet storage devices can't have static names? Ethernet devices have MAC addresses as their unique ID. Block devices have PARTUUIDs and filesystems have UUIDs. The IP address is keyed to the MAC address. (In desktop distributions these days, I believe that MAC address typically drives device name via renaming, and then device name indexes the network configuration, which then determines the IP. Alternatively, MAC address drives IP address via DHCP). To my mind, using UUIDs as the key rather than device name is exactly the same situation, not a different one. ... > I understand that there is a widespread desire to institute a new level of quality control in the device-tree, but if we are agreeing on a new rule, let's be explicit about it. (please word-wrap your email) I don't believe this has anything at all to do with device tree; my first experience with this issue was long before DT. The issue is that block device IDs cannot be equal to controller IDs, since: * Mount an SD card -> assigned an ID at run-time * Physically unplug it -> ID kept since it's still referenced * Plug a new card back in -> assigned a new ID at run-time Therefore, there's no 1:1 match possible between SD/MMC controllers and SD/MMC block device names. It's dynamic. The same is true of USB mass storage devices too, I believe. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
