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

linuxmemes

21180 readers
832 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    top 11 comments
    sorted by: hot top controversial new old
    [–] DumbAceDragon@sh.itjust.works 0 points 7 months ago* (last edited 7 months ago) (1 children)

    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.

    [–] frathiemann@feddit.de 0 points 7 months ago

    Yea, I get that the s in sdX stands for sata, but why cant we have an ndX with n for nvme?

    [–] dan@upvote.au 0 points 7 months ago* (last edited 7 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.

    [–] PsychedSy@sh.itjust.works 0 points 7 months ago (1 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 0 points 7 months ago

    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.

    [–] toynbee@lemmy.world 0 points 7 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 1 points 7 months ago

    Labels are better. IMO; they're semantic.

    [–] jadedwench@lemmy.world 0 points 7 months ago (1 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?

    [–] Laser@feddit.de 0 points 7 months ago* (last edited 7 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 7 months ago* (last edited 7 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 0 points 7 months ago

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