The Windows equivalents of the most used Linux commands
elsadek
39 points
22 comments
April 01, 2026
Related Discussions
Found 5 related stories in 49.1ms across 3,471 title embeddings via pgvector HNSW
- Things Linux Can Do That Windows Still Can't mikece · 22 pts · March 16, 2026 · 57% similar
- Time to Dump Windows? llm_nerd · 30 pts · March 20, 2026 · 44% similar
- Linux Applications Programming by Example: The Fundamental APIs (2nd Edition) teleforce · 58 pts · March 20, 2026 · 43% similar
- Why does AI tell you to use Terminal so much? ingve · 35 pts · March 11, 2026 · 43% similar
- DirectX: Bringing Console-Level Developer Tools to Windows haunter · 13 pts · March 12, 2026 · 43% similar
Discussion Highlights (11 comments)
jpease
CTRL-ALT-DEL?
jmclnx
Not bad, but one big criticism, never do a 'kill -9' first, that will stop the program from cleaning up after itself if killed using -9. Use one of these instead: -TERM then wait, if not -INT then wait, if not -HUP then wait, if not -ABRT If you are sure all of these fail, then use -9 (-KILL). But assume the program has a major bug and try and find another program that will do the same task and use that instead.
WaterRun
I recently had a similar idea. https://github.com/Water-Run/Cmdset
Akuehne
My most used windows command is, and will always be, `ls`. Then I'm reminded that it's not a know file or directory.
8note
ok, but how do i get the only linux command i know? ctrl+r
malbs
findstr is an underappreciated command line tool. I use it a lot
hackyhacky
> Author's note: From here on, the content is AI-generated Kudos to the author for their honesty in admitting AI use, but this killed my interest in reading this. If you can use AI to generate this list, so can anyone. Why would I want to read AI slop? HN already discourages AI-generated comments. I hope we can extend that to include a prohibition on all AI-generated content. > Don't post generated comments or AI-edited comments. HN is for conversation between humans.
themafia
> Windows: netstat -n -a | findstr "https" (//note the double quotes) netstat works perfectly fine on linux as well. If you're looking for https connections it's certainly far more efficient than 'lsof'. also if you use '-n' then you're not going to get service names translated, so that probably should be: netstat -n -a | find "443"
HDBaseT
traceroute vs tracert always catches me out.
not_a_bot_4sho
A great non-AI resource on this topic: https://ss64.com/
flexagoon
> Finding a specific file by name across the system > Linux: find / -name "config.txt" This is not how you find a file across the entire system, you use plocate for that. find would take ages to do what plocate does instantly