this post was submitted on 15 Mar 2024
30 points (100.0% liked)

linuxmemes

20933 readers
1595 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
rtxn@lemmy.world
30
Yeah yeah, we know you're special (lemmy.dbzer0.com)
submitted 6 months ago by 0x4E4F@lemmy.dbzer0.com to c/linuxmemes@lemmy.world
37 comments fedilink hide all child comments
 
all 38 comments
sorted by: hot top controversial new old
[–] dan@upvote.au 7 points 6 months ago* (last edited 6 months ago) (3 children)

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.

[–] 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.

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

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

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

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

[–] 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

[–] 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

[–] redditReallySucks@lemmy.dbzer0.com 2 points 6 months ago (1 children)

A yes, my beloved nvme1p2 partition that changes name every reboot

[–] ordellrb@lemmy.world 1 points 6 months ago

thats a reason to use the uuid in the fstab

[–] KillingTimeItself@lemmy.dbzer0.com 1 points 6 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.

[–] DumbAceDragon@sh.itjust.works 1 points 6 months ago* (last edited 6 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.

[–] MonkderZweite@feddit.ch 1 points 6 months ago* (last edited 6 months ago) (1 children)

https://superuser.com/questions/1449499/why-does-linux-list-nvme-drives-as-dev-nvme0-instead-of-dev-sda#1449520

In short; sd stands for SCSI Disk and SSD and USB all use the SCSI protocol. While SD-cards/emmc (flash-on-CPU) are named emmcblkpX for emmc block device, partition X. And NVME have additionally namespaces, which is the nX part.

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

So, EMMC is even worse

[–] Anarch157a@lemmy.world 1 points 6 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.

[–] mrbaby@lemmy.world 1 points 6 months ago

Mine is easy - /dev/nvme[tab][tab][tab]

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

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.

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

Ummm... replying to the wrong thread I think 😁.

[–] jadedwench@lemmy.world 1 points 6 months ago

Thank you! I will give that a shot tomorrow and test it

[–] sleepmode@lemmy.world 0 points 6 months ago (1 children)

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

[–] anarchy79@lemmy.world 0 points 6 months ago (1 children)

I just run arch. It self compiled.

[–] hperrin@lemmy.world 0 points 6 months ago (1 children)

It’s called that because it’s Never the Value you Might Expect.

[–] Eyck_of_denesle@lemmy.zip 0 points 6 months ago (1 children)

Can you elaborate? I like mine a lot. It's super fast.

[–] hperrin@lemmy.world 1 points 6 months ago

If you reboot, it might have a different name in /dev/, just like ethernet ports.

[–] anarchy79@lemmy.world 0 points 6 months ago (1 children)

NO IT IS YOU WHO DONT UNDERSTAND IT IS PERFECT LOGIC

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

Dude, chill, it's a meme... sheesh.

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

You're a meme

I'm a Linux admin

Grovel before me or I will go through your browsing history

(hit me up if you want to hear what distro i run btw)

[–] Damage@slrpnk.net 0 points 6 months ago (1 children)

What distro? Tho if you're an admin it should be multiple distros, no?

[–] anarchy79@lemmy.world 0 points 6 months ago (1 children)

Nope. Just the one.

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

He did say BTW in the end, so... it's NOT Arch!