• cowfodder@lemmy.world
      link
      fedilink
      arrow-up
      13
      arrow-down
      1
      ·
      17 hours ago

      Funny enough, I learned terminal commands initially on a green on black monitor. I can’t use the terminal unless I set it to green on black. My brain literally won’t remember any terminal commands for any flavor of Linux until I change the color scheme.

      • Machinist@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 hour ago

        I’m not quite that bad but I definitely prefer green or amber on black terminals. That’s how a command line is ‘supposed’ to look because that’s what I learned on.

  • x00z@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    ·
    11 hours ago

    It has some of the most accurate hacking logic.

    The plot on the other hand I disliked.

  • Libra00@lemmy.world
    link
    fedilink
    English
    arrow-up
    17
    ·
    16 hours ago

    Heh, I remember tinkering with linux waaay back in the day. I had a shitty Slackware install I farted around with, and something I was doing required bootstrapping gcc. I clung to that man page like it was the last lifeboat off the Titanic, but by the end when it worked I felt exactly like this.

    • Barbarian@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      ·
      15 hours ago

      In Uni I ran Gentoo as my daily driver. It was stupid, but I learned a lot.

      Trying and failing to get a working desktop environment, using IRC on the command line to get help from people who knew what they were doing and could advise a dumb kid like me, following their advice and getting a working DE after a reboot was the most hackerman I ever felt. I was convinced I was real hot shit. In actuality, I’d followed the advice to tweak the kernel config to get working drivers :))

      • Libra00@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        13 hours ago

        Haha, yep. My very first linux install I had to do similar because I had a fucky video card that X11 didn’t support natively, ultimately I had to, er, acquire a commercial X server that did support it to make it work. It was a mess.

    • Geodad@lemm.ee
      link
      fedilink
      English
      arrow-up
      9
      ·
      edit-2
      13 hours ago

      You should never use “sudo su”. That’s a big security no-no.

      ~$ sudo apt update

      [sudo] password for {your user name}:

      -command executes-

      ~$

      • Endymion_Mallorn@kbin.melroy.org
        link
        fedilink
        arrow-up
        1
        ·
        11 hours ago

        Does that1 security no-no matter on a single-user system which (almost) never leaves the sight of said user? Or is that just a matter of ‘don’t do this on a server’?

        • Geodad@lemm.ee
          link
          fedilink
          English
          arrow-up
          4
          ·
          10 hours ago

          It’s not a good habit to get into. Even if you don’t have anyone at homebto mess with your system, these kinds of habits tend to follow people around. You’ll get comfortable at work and run something as root, but forget to deescalate permissions.

          Just using sudo as your user runs only that command or script as root, then drops back to your limited user account.

          Say you got busy or distracted and walked away, anyone who was able to access your system between the end of the command and the time your system auto locked would only have the access level of your user.

    • dunz@feddit.nu
      link
      fedilink
      arrow-up
      15
      ·
      edit-2
      16 hours ago

      Use sudo -i instead, gives you an interactive shell without running the su binary with sudo, which is unnecessary

      Edit: it’s i not I

        • Snot Flickerman@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          4
          ·
          edit-2
          16 hours ago

          It’s a really important switch for doing things like setting up wireguard, which has protected directories, you can’t actually enter the directory for wireguard setup without sudo -i

          (I mean technically you probably can with sudo su, too, but this is more elegant and less redundant)

    • aleq@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      16 hours ago

      What’s the problem exactly? There are many ways to do it, and I think saying you run apt-get update is quite fine even if you’re not explicitly saying that you run it as root. And he may not have flatpaks.

    • Geodad@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 hours ago

      That doesn’t surprise me. North Korea has their own as well.