Re: [...] "How does the new naming scheme look like, precisely?"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/14/2017 02:27 PM, Stephen Morris wrote:
> On 3/15/17 3:25 AM, Tom Horsley wrote:
>> On Tue, 14 Mar 2017 09:43:45 -0700
>> Rick Stevens wrote:
>>
>>> Like I said, it's damned difficult to come up with something. If you
>>> have a better idea, then submit it to the various kernel groups.
>> I do have a better idea: Go back to the way it was when you could
>> use udev to permanently assign names to interfaces :-).
>>
>> As you have just shown it is impossible to get it "right" but
>> before they "fixed" it, you could at least get it to remain
>> consistent with the udev rules.
>>
>> Stop trying to solve impossible problems.
> I have several questions around the naming convention.
> 
> My usb wireless adapter is named wlp3s0u2, hence the naming convention
> is saying the adapter is usb device 3. I do have 3 usb devices
> connected. Two of the devices are usb 2 and the adapter is usb 3, hence
> when the device enumeration is done to determine what exists, what
> controls whether usb 2 devices are enumerated first , is it software or
> the motherboard?

Remember, we're talking about network interfaces here and the naming
conventions we've been discussing here ONLY affects network interfaces.

>                  Assuming the naming convention is based on enumeration
> which it may not be given that, I have 2 usb 3 slots on the front of my
> machine and, if on the running system I unplug my wireless adapter and
> plug it into the second slot, when the system recognizes the device
> again the name changes to wlp3s0u1. Also I have 2 usb 2 slots on the
> front of my machine, and if I do the same thing to my adapter and unplug
> it from the usb 3 slot and plug it into the second usb 2 slot the name
> changes to wlp0s19f2u3, hence what does the naming convention actually
> represent?

I'm not sure. It sounds like all the USB hubs in your machine interface
through PCI slot 3. I would have expected that the various hubs would
have different "s" numbers (e.g. one hub on p3s0, one on p3s1, etc.).

> As I said above I have 3 usb devices, the other 2 are a keyboard and the
> transmitter for my wireless mouse. How do I find what the naming
> convention for those two devices is, in terms of what they are actually
> named?

They'd show up in the dmesg log, but they will NOT be named things like
"wlp3". Again, that's just for wireless NICs. I have a Logitech wireless
keyboard and mouse and this is how they appear in dmesg:

[    2.556799] logitech 0003:046D:C517.0001: input,hidraw1: USB HID
v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:14.0-5/input0
[    2.608866] logitech 0003:046D:C517.0002: input,hiddev0,hidraw2: USB
HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:14.0-5/input1

> Lastly, if I plug a flash driver into the usb 3 slot where my wireless
> adapter was what name does it inherit and how do I find out?

It would most likely be /dev/sdX, where "X" was the next sequential disk
number available at the time you plugged the device in.

> 
> regards,
> Steve
> 
>> _______________________________________________
>> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
>> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
> _______________________________________________
> users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx


-- 
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks@xxxxxxxxxxxxxx -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-      We are born naked, wet and hungry. Then things get worse.     -
----------------------------------------------------------------------
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux