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 1 points 6 months ago (1 children)

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

[–] sxan@midwest.social 2 points 6 months ago

Labels are better. IMO; they're semantic.

[–] jadedwench@lemmy.world 0 points 6 months ago (2 children)

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 points 6 months ago* (last edited 6 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 points 6 months ago* (last edited 6 months ago) (1 children)

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.

[–] jadedwench@lemmy.world 0 points 6 months ago* (last edited 6 months ago) (1 children)

It is only the nvme drives that do it. That damn PCI busses and iommu groups get renumbered every damn time I remove or add one. The SATA is safe though.

[–] Laser@feddit.de 1 points 6 months ago

The arch wiki lists some methods to permanently name network interfaces at https://wiki.archlinux.org/title/Network_configuration#Change_interface_name

[–] PsychedSy@sh.itjust.works 0 points 6 months ago (2 children)

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

[–] lea@feddit.de 1 points 6 months ago (1 children)

According to Arch Wiki they get generated and stored in the partition when it is formatted. So kinda like labels but automated and with (virtually) no collision risk.

[–] PsychedSy@sh.itjust.works 1 points 6 months ago (2 children)

I could have RTFM but you guys are more fun.

[–] Hexarei@programming.dev 1 points 6 months ago

It's fun to have people around who read the friendly manual

[–] 0x4E4F@lemmy.dbzer0.com 1 points 6 months ago

Yeah, you get the best Linux info when reading meme comments 😁.

[–] taaz@biglemmowski.win 0 points 6 months ago (1 children)

Uuids are part of the gpt (table) on the disk.

[–] Supermariofan67@programming.dev 1 points 6 months ago

You're thinking of partuuid, regular uuids are part of the filesystem and made at mkfs time