this post was submitted on 17 Feb 2026

87 points (86.0% liked)

Linux

12407 readers

606 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago

MODERATORS

Ategon@programming.dev

anzo@programming.dev

dwraf_of_ignorance@programming.dev

87

Deprecated Linux Commands You Should Not Use Anymore (itsfoss.com)

submitted 3 days ago by mesamunefire@piefed.social to c/linux@programming.dev

45 comments fedilink hide all child comments

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

[–] Brummbaer@pawb.social 4 points 2 days ago (1 children)

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.org 2 points 1 day ago* (last edited 1 day 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....