this post was submitted on 15 Mar 2024
1002 points (97.2% liked)

linuxmemes

21210 readers
50 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
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] hperrin@lemmy.world 4 points 7 months ago* (last edited 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