backup config files

  • MidsizedSedan@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    10 hours ago

    Are you SURE that is the first command new users type? I remember adding neofetch to my .bashrc (infact, I might don’t again)

  • jaybone@lemmy.zip
    link
    fedilink
    English
    arrow-up
    30
    arrow-down
    1
    ·
    2 days ago

    Until your shit got all fucked up because you added a third party repository. And then you have to manually remove lock files and fix the pkg database and mess with .conf files and manually uninstall specific versions of dependent packages, and then manually re-enable some remote repo.

    Then you actually kind of do feel like a hacker.

    Until you’ve done it like 10 different times, then you are just annoyed. Still a better love story than Twilight.

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      2 days ago

      You copy paste the command.

      $ sudo apt update
      -bash: sudo: command not found
      $
      

      Your distro doesn’t set up/install sudo by default, so your first task is installing sudo, then understanding /etc/sudoers syntax and understanding why the command to atomically replace /etc/sudoers is visudo and why on a multiuser system there’s value to atomic replacement. In the meantime, you probably learn about su and maybe, if your distro has disabled them, how to enable switching to the kernel virtual consoles on tty1 through tty7 so that in the meantime, you can do things as root while staying logged in. Also, you’re going to learn about environment variables, so as to set EDITOR, and where your shell config files live, what a login shell is, and in what shells ~/.bash_profile, ~/.profile, and ~/.bashrc run. Also, you first try running visudo as a regular user, but your distro places visudo in /usr/sbin instead of /usr/bin, so you can’t figure out why it’s not installed and are going to learn about the FHS and mlocate and updatedb so that you can find /usr/sbin/visudo and dpkg -S so that you can figure out which package it’s in and confirm that it’s actually installed and learn about PATH.

    • corsicanguppy@lemmy.ca
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      2 days ago

      shit got all fucked up because you added a third party repository

      Dependency hell is always, always, self-inflicted.

      apt is only SLSA1 or 2 anyway, so there’s a lot more wiggle room.

    • conartistpanda@lemmy.world
      link
      fedilink
      arrow-up
      2
      ·
      2 days ago

      This fucking idiot here changed their debian branch to sid then wondered why the software store didnt work. Luckly I always backup config files. I mean, it’s not that complicated to change some lines back, but still.

      Also it’s a vbox vm so I could always restore a snapshot. And it exists to tweak so it was meant to be.

  • thebestaquaman@lemmy.world
    link
    fedilink
    arrow-up
    36
    ·
    2 days ago

    Let’s be reasonable: We were all at some point at the stage where doing anything at all in the terminal made us feel like a god.

    • bryndos@fedia.io
      link
      fedilink
      arrow-up
      18
      ·
      2 days ago

      It’s weird to have grown up with things like bbc micro and MS-DOS and see how alien the terminal is to people who didn’t.

      Back then CLIs were all over, even like library catalog terminals, were CLI. TBF some still had card indexes though.

      At university everyone had to ssh in to the email server from whatever tty client even on windows (nt4/nt5/98/2k/mackintosh PCs).

      You definitely didn’t feel like any hacker. The hacker level thing was to successfully connect via GUI mail client and actually have your emails update and sync properly - very few bothered.

        • bryndos@fedia.io
          link
          fedilink
          arrow-up
          5
          ·
          2 days ago

          Very possibly.

          I vaguely remember using putty on port 22 which i thought was ssh, but maybe it was telnet. we were leaving the 90s by then, so I think ssh was around. Might also have been different protocol on the uni LAN vs WAN connections.

          The libraries I remember might have been direct terminals to local server. Few catalogs were available even on the uni-wide LAN. No big deal really since you’re going to have to go there to find the book anyway.

          The catalog room was an acceptable place to have a chat or lament the size of the reading list.

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 days ago

      We were all at some point at the stage where doing anything at all in the terminal made us feel like a god.

      Some of us were at the point where GUIs weren’t a thing and the terminal was the only option.

      • FudgyMcTubbs@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        5 hours ago

        Msdos on my family’s Commodore taught me my foundation of computer literacy. Then Q-Crack and editing the Duke Nukem 3D config file and sharing it with a friend so we could play over the modem together expanded my understanding and confidence. Linux paired with google searches/forums just seemed like a natural progression to me.

      • thebestaquaman@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        1 day ago

        Fair enough, I guess my overall point was more that we’ve all at some point taken that first step of doing something that now feels mundane, but at the time felt like we were doing something very advanced.

  • rumba@lemmy.zip
    link
    fedilink
    English
    arrow-up
    1
    ·
    23 hours ago

    LOL, I was at my sons track meet. Opened my laptop to play a game. Decrypted NixOS, and was waiting for it to splarg pre-ui the kids in the tent said… ARE YOU HACKING!!!

  • juipeltje@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    1 day ago

    Me when i fork dwl just to add a few patches that i did not create myself, just so i can make my own package for it.

    “You know, i’m something of a developer myself.”