267
After almost half a century, I'm still doing it... (lemmy.sdf.org)
submitted 2 years ago by to c/linux@lemmy.ml
78 comments fedilink hide all child comments
 

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... 😥

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 2 years ago* (last edited 2 years ago) (2 children)

You don't need to install cockpit on the server being configured, you can use it as a gui to connect from other machines via the flatpak, over ssh.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    Right.
    My point is that a wrench was needed and a batmobile was recommended.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 years ago* (last edited 2 years ago)

    No. Netplan uses it's own yaml format, which people would have to learn and use. I don't want to do that, I would rather just configure my existing networkmanager setup, rather than learning another abstraction layer over what is already an abstraction layer.

    I understand that cockpit (and similar type tools) are "the whole kitchen sink" of utilities, and it may seem like they come with more than you may need. But that doesn't change the fact that they get the job done, and in some usecases, are better than dedicated tools.

  • permalink
  • fedilink
  • source
  • parent