I’ll start:

  • Tmux
  • vim
  • ghidra
  • okteta (hex editor)
  • speedcrunch (calculator with bit manipulation)
  • python3 with IPython for nice reply and embed(), pwntools
  • vegemash
    link
    fedilink
    12 years ago
    • fzf
    • git + lazygit
    • neovim
    • ranger
    • cargo
    • btm
    • starship
    • tmux
    • fish
    • @[email protected]
      link
      fedilink
      42 years ago

      It’s a signed archive of deployable files along with meta-data. Usually a cpio archive (which is similar to a tarball) with that extra signature wrapper and meta-data (which, itself, should be a list of files and checksums).

      A proper package can validate a project’s installation, either from the local database or from remote resources, at any time, which gives positive assurance that what is installed is what should be installed.

      As well, proper package info is exported by SNMP to be consolidated centrally and validate what is vs what should be installed at the group level.

      TL;DR? Like a tarball with tracking info, signatures, checksums, and top-to-bottom validation. If it’s a good package, anyway.

      • @[email protected]
        link
        fedilink
        12 years ago

        So it’s basically like installing a program in windows but, idk how to phrase it, more through and less prone to errors during installation?

        • @[email protected]
          link
          fedilink
          22 years ago

          You’re really close, yeah .

          But because like every layer is checksummed both in delivery AND when it’s installed, so you can easily validate a delivered file, and it’s all signed with signatures you can easily check, you can at least be assured that

          • what you installed is what that package delivered
          • which is what the authors wanted
          • and the package probably hasn’t been tampered with
          • even weeks after install

          the chance of problems should be reduced.

          Bonus1: with a proper repo config, you can check for updates so fast. It’s like the chocolatey windows repo but more formalized and usually vendor-maintained.

          Bonus2: bad upgrade? Enterprise packages on Linux (long description; trust me) can be reverse-installed over what’s there so you can back-revise or downgrade with almost no pain. It’s a good oh-no fix. At every point you can still validate that what is there should be there, according to hard signatures at every stage.

          Bonus3: grabbing os version 6.1 and upgrading to 6.5 OR just installing 6.5 fresh gives the same final content - files and services - when you’re done. (almost entirely) No cruft, since package installs (because of the locking below) just install over themselves in a way Linux people just accept and windows people may freak over.

          Linux bonus: Linux locks file differently; again, long description, so trust me or look it up. You can upgrade many files and services without stopping them, and then bounce a service or a host, so your patch-and-bounce process is fast, it happens after the upgrades, and is like 2 min or with systemd 3min.

          Ultimately

          • use packages for wayyyy easier, consistent, reliable, tested, quasi-roll-back-able updates that you can validate all the way down.
          • and still that SNMP connection to check content remotely. It’s so great.
      • @[email protected]
        link
        fedilink
        22 years ago

        Correct, the reason they are called packages, is that the package can contain other resources besides usable programs, like libraries used by other programs.

  • @[email protected]
    link
    fedilink
    4
    edit-2
    2 years ago

    Adding to that:

    • neovim for workstations
    • curl
    • wget
    • zsh

    Edit: So essentially for me, I forgot to include it: vim, my beloved, always and for ever

      • @[email protected]
        link
        fedilink
        12 years ago

        Im not really into the bash simplicity, but it’s proven and stable.

        I just have a git repo with configs on my git Server, I make changes regularly and roll them out with a quick bash script.

  • @[email protected]
    link
    fedilink
    62 years ago
    • zsh+ohmyzsh
    • tilix
    • neovim
    • fzf
    • exa
    • pv
    • htop+iotop+nethogs
    • iperf3
    • nc
    • socat
    • nmap
    • python3
    • ansible
    • lolcat
    • nakal
      link
      fedilink
      22 years ago

      If you like exa and fzf, you’ll also like fd (or sometimes fd-find).

      • @[email protected]
        link
        fedilink
        12 years ago

        Woah, how I missed this? Thanks! Seems very comfy and way faster, btw on my deb machines it’s fdfind

  • @[email protected]
    link
    fedilink
    3
    edit-2
    2 years ago

    Stuff that I insist on regardless of platform (that is, I install these even onto Windows systems if I’m forced to use them):

    • Pale Moon (web browser)
    • Claws Mail
    • GIMP
    • vbindiff (command-line hex editor + diff utility for binary files)
    • mercurial
    • perl

    Stuff that I require only on Linux systems for desktop use:

    • Pan (yes, really, I still use a Usenet newsreader on a daily basis)
    • qemu
    • conky
    • Aqualung (music player—I like odd software)
    • Inkscape
    • Scribus
    • PySol ;)
    • rdesktop (less a favourite than a regrettable necessity)
    • various TDE built-ins: konqueror (as file manager only), kedit, kate, konsole, ark
    • @[email protected]
      link
      fedilink
      12 years ago

      Is there a reason you use mercurial (like work) or are you using it, because you like it better than git or fossil?

      • @[email protected]
        link
        fedilink
        12 years ago

        Fossil I’ve never tried, but I utterly hate git. Nothing about how it works makes sense to me. Mercurial is, in my opinion, better-designed and easier to understand for my rather simple use cases. (I should note that I graduated from university around the time svn was replacing csv, so I was coding before there was such a thing as distributed version control.)

  • @[email protected]
    link
    fedilink
    22 years ago

    The first 3 things I always add after a fresh install: aptitude emacs (-nox for servers) tree

    Then it depends what the machine is for.

  • @[email protected]
    link
    fedilink
    -22 years ago

    None of those are must-haves…

    Shouldn’t you have posted this to /c/archlinux or other meme-distro communities?

  • @[email protected]
    link
    fedilink
    12 years ago

    neovim, zsh, firefox, vlc, mpv, zsh plugins for autocomplete, ripgrep, zerotier vpn,fzf, pip3, htop, i am not sure what else

  • mfz
    link
    fedilink
    52 years ago

    To add to all great comments here I have one that I’ve used for ages and not seen mentioned here: lftp

    It supports many protocols for ftp like over ssh and allows for shaky connections with resume and back in the days when this was more common I used to just run it in the background to download huge files that took days to download and it would gracefully just reconnect/resume/retry until done.

  • redcalcium
    link
    fedilink
    5
    edit-2
    2 years ago

    Every time I setup a new system, I always install these:

    • vim
    • zsh
    • git
    • rsync
    • tmux
    • mosh
    • btop
    • autossh
    • mc
    • direnv
    • asdf-vm

    If the system is a desktop/laptop for personal use, then I’ll install these too:

    • virt-manager
    • vscode
    • firefox
    • filezilla
    • mpv
    • yt-dlp
    • kdeconnect
    • onlyoffice