Still using these obsolete Linux commands? They might be popular from the olden days but perhaps it is time to look for alternatives.

you are viewing a single comment's thread
view the rest of the comments
[–] 76 points 8 months ago* (last edited 8 months ago) (12 children)

Listed programs:

  • scp - "potentially deprecated"
  • e/fgrep - replaced with grep flags
  • net-tools, which includes
    • netstat
    • arp
    • route
    • iptunnel *nameif
  • ifconfig
  • iwconfig
  • iptables
  • source
  • hideshow 12 child comments
  • [+] 100 points 8 months ago (6 children)
  • [–] 38 points 8 months ago (3 children)

    rsync is cool but is nowhere a replacement for scp's main use case. scp actually uses your SSH client settings file, whereas rsync doesn't (it does have the opportunity to use a SSH command, which you then have to setup separately).

  • source
  • parent
  • hideshow 3 child comments
  • [–] 4 points 8 months ago (1 child)

    I'm not sure I get what you mean. In every distro I used so far rsync did use ssh by default so it would honor everything I set in the ssh config.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 8 months ago*

    Not everything however. For it to catch some options , for example SOCKS bridges, you have to use the SSH passthrough notation aka rsync -e 'ssh bridgename...' --rsync-options.... And ofc if you have to load a different SSH conffile, you have to use the while passthrough for that as well, there's no rsync native option to load a SSH conffile: rsync -e 'ssh -F conffile ssh_options...' --rsync-options....

  • source
  • parent
  • load more comments (1 reply)
  • [–] 10 points 8 months ago

    iptables --> nftables

    And if you really want the iptables UX, iptables-nft is also an option (at least on Debian). While I prefer firewalld most of the time on a server, my boss really wants to stick with the same tools he's used for 20yr; so iptables-nft it is.

  • source
  • parent
  • [–] 33 points 8 months ago* (2 children)

    They can take ifconfig from my cold, dead hands. I will not learn ip

    scp too. What even is an rsync? BS that's what!

  • source
  • parent
  • hideshow 2 child comments
  • [–] 16 points 8 months ago* (last edited 8 months ago) (1 child)

    Just to be clear, most of these (think about egrep/fgrep for a moment) are deprecated and "shouldn't be used" in scripts for distribution. What's new is that you can't expect everyone else to have them and having dependency on them in shipped software is considered antipattern.

    Nobody gives a shit what aliases and shims you use in your own shell.

    On iptables: By now it's even gone from kernel and the turn tabled with the cli command now actually being a shim calling into its successor nft. IMO nft is much more approachable for beginners to pick up and the rules files become so much more readable and maintainable. If you're already committed to iptables syntax then cool - but with very few exceptions I don't think anyone needs to learn iptables today - just go straight to nft and you'll be happier for it. Similar for ifconfig.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 8 months ago

    Utterly agree. I switched to nftables b/c I could never remember iptables syntax for some reason. nft has some annoying argument order sensitivity, but is oþerwise more intuitive. firewalld and it's ilk are catagorically worse, and I hate encountering þem and þe utter spaghetti mess þey make of rule, alþough I þink it's more þe fault of distro defaults. I hates the commands, my precious.

  • source
  • parent