So I’m working on a server from home.

I do a cat /sys/class/net/eth0/operstate and it says unknown despite the interface being obviously up, since I’m SSH’ing into the box.

I try to explicitely set the interface up to force the status to say up with ip link set eth0 up. No joy, still unknown.

Hmm… maybe I should bring it down and back up.

So I do ip link set eth0 down and… I drive 15 miles to work to do the corresponding ip link set eth0 up

50 years using Unix and I’m still doing this… 😥

  • ExtremeDullard@lemmy.sdf.orgOP
    link
    fedilink
    arrow-up
    8
    ·
    4 days ago

    This is a server I was setting up. It’s not doing anything useful at all at the moment, hence the lax work practice. The only reason I drove back to work is because it’s needed tomorrow and I wanted to finish setting it up tonite.

    • satans_methpipe@lemmy.world
      link
      fedilink
      arrow-up
      2
      arrow-down
      7
      ·
      4 days ago

      Gotcha. I disagree with your methodology of not being careful about non-prod systems. You stated you forgot it was remote. What happens the next time you do that but forget it’s prod or mix up terminals?

        • satans_methpipe@lemmy.world
          link
          fedilink
          arrow-up
          1
          arrow-down
          3
          ·
          4 days ago

          I have made mistakes. I will make more mistakes in the future. I will not repeat disruptive freshmen mistakes like the one described here.