Still using these obsolete Linux commands? Perhaps it is time to look for alternatives.

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

  • pkjqpg1h@lemmy.zipEnglish
    83·
    4 days ago

    Replacement:

    • scp → rsync or sftp

    • egrep --> grep -E

    • fgrep --> grep -F

    • netstat --> ss

      • arp --> ip n
      • route --> ip route
      • iptunnel --> ip tunnel
      • nameif --> ip link

    • ifconfig --> ip

    • iwconfig --> iw

    • iptables --> nftables

    • lambalicious@lemmy.sdf.orgEnglish
      27·
      4 days ago

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

      • Brummbaer@pawb.social
        2·
        3 days ago

        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.

        • lambalicious@lemmy.sdf.orgEnglish
          3·
          3 days 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....

    • stewie410@programming.dev
      1·
      4 days 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.