this post was submitted on 27 Jun 2024
922 points (96.7% liked)
linuxmemes
20464 readers
330 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is the same problem they had with hard drive names and it seems to have been solved in a sensible way, i.e. /dev/sda still points to the first disk detected by the system, but you can look look in /dev/disk/by-path (or by-uuid, etc) to see the physical address of the devices on the system and what they are symlinked back to, and set your fstab or mdadm arrays to be configured based on those unique identifiers instead.
So, I guess what I'd like to know is why hasn't this been solved the same way? When you boot up they should present every hard wired Ethernet port as
ethX
, and the hardware address interface should be present as well but aliased back to theeth
. Then you can build the your network configs based on either one.Shouldn't be that hard right?
Cries in
nvme1n1p6
, which is my current OS partition.Taking a sip of Rum and chuckles at the look on the name of my OS partition:
/dev/mapper/vg-root
and/dev/mapper/vg-home
🙃That's because you're using LVM though. In most distros you could also use something like:
/dev/vg/root