Search for a command to run...
Series
Backend developer transitioning to DevOps/Infrastructure. Daily learning logs.
1. Basic Commands Command Description pwd Print current working directory ls -la List all files including hidden ones with permissions cd Change directory mkdir Create directories (multipl
1. Redirection (> vs >>) Both redirect command output to a file, but they handle existing content differently. > → Overwrite (truncates the file, then writes). Same as C's fopen("w") >> → Append (ad
After typing ls > out.txt hundreds of times, a strange question hit me: Does ls somehow detect that its output is being redirected? Does it have some logic like "oh, output is going to a file now, let
After Day 4 on fork/exec/file descriptors/pipes, one thing still nagged me. In that post I wrote: "The child duplicates that fd onto fd 1 with dup2(3, 1) — then closes the original fd 3." Why close
Yesterday in Day 5, while digging into why rm doesn't immediately reclaim disk space, I wrote this line: "Files, pipes, sockets — they're all fds." But that was just words. The only thing I actually
In Day 6, I watched a single connection arrive at the server and saw two fds show up instead of one. The listening socket (fd 3) stayed at the door, and a new connected socket (fd 4) was created for t
