• dan@upvote.au
    11·
    7 months ago

    and you shouldn’t be using any of those, since the order can and will change. The numbers are based on the order the devices and device drivers are initialized in, not based on physical location in the system. The modern approach (assuming you’re using udev) is to use the symlinks in /dev/disk/by-id/ or /dev/disk/by-uuid/ instead, since both are consistent across reboots (and by-id should be consistent across reinstalls, assuming the same partitioning scheme on the same physical drives)

    This is also why Ethernet devices now have names like enp0s3 - the numbers are based on physical location on the bus. The old eth0, eth1, etc. could swap positions between Linux upgrades (or even between reboots) since they were also just the order the drivers were initialized in.

    • toynbee@lemmy.world
      2·
      7 months ago

      I’m sure you know this, but to to supplement your comment for future readers, UUIDs are also a good solution for partitions.

    • 🐍🩶🐢@lemmy.worldEnglish
      0·
      7 months ago

      I have a hatred for the enp id thing as it isn’t any better for me. It changes on me every time I add/remove a hard drive or enable/disable the WiFi card in the BIOS. For someone who is building up a server and making changes to it, this becomes a real pain. What happens if a drive dies? Do I have to change the network config yet again over this?

      • hperrin@lemmy.world
        1·
        7 months ago

        Use a systems rule to give it a consistent name based on its MAC address, driver, etc. I just had this exact same problem setting up my servers.

        root@prox1:~# cat /etc/systemd/network/10-persistent-10g.link 
[Match]
Driver=atlantic

[Link]
Name=nic10g

root@prox1:~# cat /etc/systemd/network/10-persistent-1g.link 
[Match]
Driver=igb

[Link]
Name=nic1g
      • Laser@feddit.de
        0·
        7 months ago

        How is that happening? The number on the bus shouldn’t change from adding or removing drives. I could imagine this with disabling a card in UEFI / BIOS if that basically stops reporting the bus entry completely. But drives?

        Anyhow, if I’m not mistaken, you can assign a fixed name based on the reported MAC.

    • PsychedSy@sh.itjust.works
      0·
      7 months ago

      Are UUIDs built into the hardware, or something your computer decides on based on the drive’s serial number and shit?

  • DumbAceDragon@sh.itjust.worksEnglish
    2·
    7 months ago

    Well it’s sdx because they both use the SATA interface. The sdx convention actually comes from scsi though, and the fact that SATA and USB drives use it might point to some code reuse, or maybe a temporary solution that never got fixed due to breaking backwards compatibility.

    Fun fact: IDE drives use the hdx naming convention.

  • KillingTimeItself@lemmy.dbzer0.comEnglish
    1·
    7 months ago

    babe wake up, we heard you like dynamic interface IDs that happen to be mostly static, so we applied it to your nvme drives, because fuck it, why not.

  • Anarch157a@lemmy.world
    1·
    7 months ago

    No one mentioned the Solaris convention yet ?

    /dev/cXtXdXsX

    The letters mean controller, SCSI target, disk and slice (Solaris equivalent to a partition).

    I always thought this was the most elegant naming scheme in the Unix world.

  • 🐍🩶🐢@lemmy.worldEnglish
    1·
    6 months ago

    I will take a look at it, but the fundamental issue is it screws with the iommu groups too and then I have to go fix that in proxmox. If I can at least guarantee a network connection then I can remote in and fix it in the event something goes really wrong.

  • sleepmode@lemmy.worldEnglish
    0·
    7 months ago

    Kinda miss the Wild West days where you’d recompile and suddenly there’d be a whole new device naming convention.