What was the moment Linux finally ‘clicked’ for you?
Posted by Darshan_only@reddit | sysadmin | View on Reddit | 70 comments
Hey everyone, I’ve been learning Linux for a while now and getting comfortable with basic commands, file management, permissions, and some user administration.
But I still feel like I’m just following steps rather than truly understanding how everything fits together.
So I wanted to ask:
-
What was the moment when Linux finally “clicked” for you?
-
Was it a specific concept, project, or real-world problem you solved?
-
What changed in your thinking after that point?
I’m currently practicing on Ubuntu in a VM and trying to move towards system administration / cloud roles, so I’m really interested in knowing what helped you break out of the beginner stage.
Would love to hear your experiences 🙏
bbqwatermelon@reddit
Ignoring desktop environments entirely. I get aggravated every time I find issues like having to research magic commands to get a touchpad working in MX Linux or inconsistent on screen keyboard in Gnome. Getting into containers and managing through web interfaces is actual admin stuff.
gruntbuggly@reddit
A colleague gave me a copy of Debian to play around with. I can’t remember what release it was, but it had a 0.99 kernel. I cannot tell you how many times I had to reinstall it because I kept blowing it up. There was a lot of learning that year.
rookie_one@reddit
Understanding that in unix-based system, everything is truly a file
uptimefordays@reddit
If you’re coming from Windows, learning PowerShell is likely the most effective way to learn Linux. It familiarizes you with the command-line interface (CLI) and pipelines. The conceptual skills acquired by “controlling an operating system (Windows, in this case) through commands rather than pointing and clicking” will enhance your understanding of both Linux and operating systems in general.
chat-lu@reddit
Around 2000. It was a better choice to switch to from Win98 than the alternative.
commsbloke@reddit
About 29 years ago when using Linux I could integrate monitoring Novell Servers into SunNet Manager.
Pertinax1981@reddit
My job forced me from a windows based support team to a linux based team and I had to learn on the fly. Sometimes being thrown to the wolves pays off
thebigshoe247@reddit
That's basically my career summed up... It even includes AS/400
RoboRougar0u@reddit
I'm SysAdmin for a community bank and when i started we had an in house AS/400 and I hated it so much. We recently switched to a co-op that houses the as/400 and provides a web based interface for it. I could not be happier not having to keep that thing updated and manually moving backups to tapes and offsite ftps.
Huge pain in the ass to deal with but damn if they aren't reliable as fuck.
thebigshoe247@reddit
Yup.
I remember being happy about leaving my AS/400 behind when I jumped ship... Only for the AIX guy to have a stroke... Guess what I then inherited?
"It's a UNIX system, you know this!" (Jurassic Park reference)
ofnuts@reddit
Scarred for life?
thebigshoe247@reddit
QSECOFR.
Because it was an IBM shop, I was also forced into Lotus Notes.
Compact, fixup, updall.
These will be burned into me for life...
ofnuts@reddit
Ah, Notes. The most misused software history. Used for what it wasn't really meant for (mail), not used for what it was designed (collaborating on documents, instead they share .DOC as mail attachments).
wanderinggoat@reddit
I honestly thought I'd was the other way. An overbuilt mail client which was used for everything but didn't do email well.
ofnuts@reddit
AFAIK it was never meant to be used for email. It pivoted to email when IBM figured it needed quickly a "strategic" solution for email on the PC (because nobody wanted PROFS) and had nothing.
Pertinax1981@reddit
Sink or swim. That is all it is.
Im a bit young for AS400 , but lot of guys I worked with started with that.
We got a guy that is a SME on DRC Alpha. May have been a year or two since we had to see one though.
Darshan_only@reddit (OP)
Currently I'm also in the window support team, What should I practice to reach ur current level faster?
Pertinax1981@reddit
Since you are on a windows team, install wsl on your machine and start to use it as a daily driver. Wont be long until you get used to it. grep , awk, find, etc will become easy.
I was very lucky to have a great team around me that loved to answer questions. My advice is ask questions, its what i tell all my juniors. if you dont understand, say that you don't, but show you want to learn. You seem to be on the right path if you came to reddit.
Also, I made a lot of cheat sheets. vi would have been a pain.
Darshan_only@reddit (OP)
May I get that cheat shits ? Plzzz
nroach44@reddit
I'm not the person you replied to but I thought I'd give you a little basic example of the commands they were referencing.
Powershell, if you start getting deep into it, is great for structured data (e.g. json, yaml, or "absorbing" spreadsheets into an "object") so it's great for doing weird shit with AD.
Unix and sh/bash is "old school unix style" and absolutely sucks for "objects" but was built for mangling text streams. You can chain the output of one command into another with the pipe symbol
|(also in batch and powershell). You're probably going to be using these commands most of the time:catdump a file out to "stdout" stream (console)lessread a file / buffer an incoming stream and let you scroll through itgrepsearch a file or incoming stream for a word or regexawkvery powerful but to start with just think of it for grabbing a particular column of textfindfind a file on disk (e.g. modified in the last week, is a folder, has this in it's name) and optionally run a command on itsed"Stream EDitor" - run a regex on the stream (so if you wanted to censor a username from a log, you cancat log.log | sed 's/username/placeholder/'Then you can do silly things with sh / bash's syntax:
file $(which grep):$()means runwhich grep(which tells you where the program is), then substitute it's output into the command (e.g. this will "run"file /usr/bin/grep)for user in $(getent group scanner | awk -F: '{ print $4 }' | sed 's/,/ /' ); do echo $user; done:getent group scanner: get the group "scanner"awk -F: '{ print $4 }' : using:` as a separator, print the fourth columnsed 's/,/ /': regex - replace,with(a space)for user in $(...); do .... done: for each item (space separated word) betweeninand; doplace it into a variable calleduser, and run the commandecho $user: print out the variablePertinax1981@reddit
You're a saint and this is 100% what I was getting at
Darshan_only@reddit (OP)
Thanks 🫶
artfully_dejected@reddit
I am not u/Pertinax1981, but I can tell you from my experience that making the cheat sheet is how I learn. Using someone else’s wouldn’t help in the same way.
Pertinax1981@reddit
My sheets are actually physical, and I put them on my board. Lots in onenote, but that is on work computer.
GM0N3Y44@reddit
The question should be what were you willing to give up for full Linux adoption.
BrokenPickle7@reddit
Linux clicked for me around 200-2001 that was after screwing with it for years as a hobby
weekendclimber@reddit
Dude, you've been using Linux for 1800 years!! Lol
oversizedmoosecalf@reddit
This seems suspicious, pretty sure Linux has only been around since January 1970
geekworking@reddit
1770 BCE (before current epoch)
BrokenPickle7@reddit
Lol feels like it, just missed a 0
weekendclimber@reddit
All good fun!! Cheers to you and yours 🍻🍻
hondakillrsx@reddit
1801 years
weekendclimber@reddit
Hey now!! I'm in IT so I don't have to do the maths stuff!!
hondakillrsx@reddit
I asked Ai
weekendclimber@reddit
Damn!! I could have used the rest of this week's tokens and faked being smart!! Missed opportunity!!
UninvestedCuriosity@reddit
Yeah it was about the same time for me too. One of my buddies said, it's all just text. Referring to how much of what was there wasn't precompiled and then I really started to dig around etc with more purpose. Started taking logs more seriously as well. Then transitioning from init to systemd took a bit to get the hang of later on. I really think it made me better at troubleshooting MS stuff as well because you got a better sense of how an OS runs even if they are different. A lot troubleshooting logic applies between both.
Expert-Percentage886@reddit
When I was in college learning systems programming in C and realized Linux is just all C.
From the kernel to the shell, to SSH, it clicked.
mods_are_lame1@reddit
When I found /var/log/messages and learned firewalld. After that, my friendship with windows server was over.
Safe-Ball4818@reddit
It finally clicked for me when I broke a production server and had to manually fix the fstab file to get it to boot again. You really stop following tutorials once you have to dig into logs to figure out why a service won't start. https://prodpath.dev/ was useful when I was learning how to diagnose those kinds of issues without nuking a real box. Just get comfortable breaking things.
Confident_Raccoon218@reddit
I became obsessed after taking an operating systems class in college. Linux clicks when you start to follow your curiosity. <<--- THIS. You have to want to know how things work. You use the man pages when you want to figure something out. You might make notes so you can member command sequences. You decide to make the machine work for you so you write small scripts to perform little tasks. You tweak the window manager so everything looks exactly the way you want it to. You might compile the kernel yourself (maybe 100 times). Try various distros. Set up a small lab with old computers and setting up services (http, ftp, ssh, etc). Use the command line for everything. Find some nerdy computer friends and nerd out all the time. Etc.
bitslammer@reddit
Around 20yrs ago, but I'm an avid gamer so at home I was still doing dual boot for a while until Steam released proton and then it was game over for windows at home. At work we're still mostly a Windows org.
Burgergold@reddit
Started working on AIX
From this point, always prefered to manage unix servers than windows/os2.
Also when I was younger, Inpkayed withhttps://www.linuxfromscratch.org/
ofnuts@reddit
AIX always felt like fossilized Unix.
Burgergold@reddit
Yup
When I began in 2003 as an intern, it was AIX 4.3.3 and I was automating stuff in KSH and Object Rexx
Learned quickly perl and how to conpile stuff myself and it became a lot easier
Nowadays, I work on RHEL and ansible a lot
Invspam@reddit
make ubuntu your main operating system, instead of using it in a VM. this way, it forces you to fix things. put some skin in the game, more fun.
ofnuts@reddit
A manager of mine once said: There are people with Linux certifications, and then there are people with Linux PCs.
SevaraB@reddit
It clicked pretty quickly for me, but I’m also a vet of the old Batch/DOS5 era, so I learned a lot of Windows administrative functions from before Microsoft hid it all behind GUIs and forced people to think in terms of clickops. A filesystem is a filesystem, permissions are permissions, and it’s only Microsoft that likes to pretend they reinvented everything instead of just moving everything to a GUI and stripping out the command shell.
At this point, windows is just a platform for running EXEs, which I don’t really do outside of gaming anymore. All the stuff I make for work is browser GUIs or REST APIs so that it can be used from Windows, Mac, or Linux desktops (if those ever come to fruition at our org- dropping 30,000 Windows licenses would save us a little bit, but our tech support personnel aren’t comfortable enough with Linux yet to support other users; we’re just starting to get there in terms of Mac support).
Shamu432@reddit
Linux academy
fadingcross@reddit
If I were you, I'd go through this:
https://www.youtube.com/watch?v=sWbUDq4S6Y8
This is usally then one I recommend. You can safely skip Chapter 4 and 5, and potentially some of the "here's how to write commands" since A) That transfers from Windows, learning syntax today in memory isn't a relevant skill, B) You seem to have experience.
This one explaining Linux filesystem is great: https://www.youtube.com/watch?v=UFIoRLqhFpo
Linux Processes: https://www.youtube.com/watch?v=TJzltwv7jJs
And lastly, pipe and redirection (A lot similar to Powershell)
https://www.youtube.com/watch?v=mV_8GbzwZMM
Turbulent_Carry_5653@reddit
When i Was a junior i got assigned with doing NetScaler Projects / Support (BSD based reverse proxy). My. Mentor forced me to Do anything on CLI and only used GUI to visualize what i Just did in the shell. Was a pain in the ass but i thank him forever for that as it massively improved my understanding and ability to operate Linux based appliances
randomlyme@reddit
Slackware 0.97a on 28 floppy drives around 1994
ImLookingatU@reddit
Honestly cant say when. I thought I understood that at the end of the day everything is just a file but it wasnt until the last 3 years where I forced my self to daily drive it at work and at home and I think it finally clicking. I very comfortable with it. Im no expert but at work everyone thinks im a Linux SME. I just know how to google or how to ask AI to point me in the right direction.
havikito@reddit
Use desktop for 2-3 months, see it is all just a lie (very limited number of the lines of code that pose as an ecosystem). Use it as a tool to run docker on whatever.
Proxiconn@reddit
Get yourself a giant cheet sheet mouse pad.
Pete263@reddit
I have the same :D
Proxiconn@reddit
Deployed docker, ran apps, had a proxy to access those apps from anywhere.
Entire FOSS stack.
Converted to Linux ~10 years ago.
No_Ionger_interested@reddit
Occurred during personal use back in 2007 (Ubuntu 7.04). Had gotten tired of using Windows
Came gradually once I switched fully from Windows to Ubuntu 7.04 back in the day. But after almost 20 years, I still have a lot to learn.
Proper package management changed everything - no longer manually looking for msi- or exe files to update software and just running apt-get update / yum update / what ever.
It didn't for long, but by now I've really come to like the data manipulation capability from CLI - grep, cut, sed, sort, uniq etc. At work I typically have had Linux VM running on Windows workstation just to play with data (say firewall rule export csv - ctrl+f in excel feels inferior).
mghnyc@reddit
I grew up with home made single board computers with Z80 or 6502 processors. It helps understanding how exactly a computer works on the hardware level. Everything modern is just an endless layer of abstractions. You pull up that curtain and things will click in place.
Away-Sea7790@reddit
Haha the more slashes you have, the deeper down you are in the directory.
goatsinhats@reddit
Well even the pros follow guides
If you really want to learn it tackle some labs/projects with no guides and repeat it across different distributions.
Next step is to combine your projects onto one OS so you can learn about conflicts
Finally go learn about older versions of Linux because in the wild are lots of them.
After that it will click
ntrlsur@reddit
I kind of fell in to it. I went for a 100% windows type role using check point firewalls back in 06ish to 70 / 30 linux windows role using check point. The good ole R55AI days. It was a senior sysadmin role. I spent a lot of time on google and AskJeeves to figure out what I needed to accomplish the job in the pre AI days. Over the years it kind of sticks with ya. I still have to search out how to do something specific but with time in and usage you will remember about 75% which is typically good enough. Currently we are about 80 / 20 linux to windows and my team spends more time dealing with with windows issues. Hang in there with time and experience it will be second nature.
SpectralCoding@reddit
This is going to sound really stupid, but when I discovered the system package manager exists. I got into Linux in high school and could only really afford the old "shell hosts" for like IRC Bouncers and such. They're basically single users on a machine, or a chroot jail. I was compiling everything I wanted to install from scratch using the system build tools. Dependency hell is truly hell when you have to compile everything from source (configure / make / make install).
Then I got a full VPS (Linode) with Ubuntu and I was like "what do you mean I can just run `apt-get install znc`?"
ImCaffeinated_Chris@reddit
Oh man, I remember compiling kernels. One night back in the late 90's in the local Linux users club we did Linux installs in the lab on every Linux flavor we could find.
I'm a former Linux admin and have been using it a long time.
I'll let you guys know when it finally clicks 🤣
nroach44@reddit
I've got an old lab machine that uses NFS over UDP, which has been turned off by default in recent kernels, so I offloaded compiling a new kernel each time to a CI job - one less thing to think about.
Miserable_Pear_6940@reddit
I’m still really new to Linux and don’t even have a RHCSA yet as I do mostly windows or hardware work, but the first time I understood that everything is literally a file I finally got what I was doing.
Colossus-of-Roads@reddit
I started my Unix journey with FreeBSD so it was ages before Linux clicked, in fact it still feels weird to me today.
TerrificVixen5693@reddit
I took an ethical hacking class on Udemy. It was early in my IT career and I just had a blast breaking into my lab’s WEP networks and doing SQL injections and such. I already had a degree in digital media so I understood a lot of web stuff as it was and now better understood the underlying operating system for many applications.
CosmicLovepats@reddit
More or less everything you want to do with computers is a series of steps.
At one point I was a very harried junior engineer managing application deployments and was bullied into automating it by a senior. I didn't really know how, but I knew Enough(tm) bash to do the steps with a little help was able to string them together into a few jenkins pipelines. I turned three-ish hours of work into two button presses and fifteen to thirty minutes of waiting.
It started to dawn then and it's been dawning ever since that everything I want to do is a larger version of that. Break it down into small enough steps and it's just cd/cp/mv/ls/chmod/etc. And you can write those already.
Wise_Guitar2059@reddit
After passing RHCSA
Made_UpWords@reddit
Getting familiar with Ansible. I had a Linux environment, I was sick of it along with all of my coworkers, no one was stepping up, so I automated our linux tasks (i.e., I made an Ansible VM, I stole some scripts from the internet, and I made it work).
I'm not even sure I'd put "experienced Linux admin" on my résumé at this point (I would, who am I kidding) but that when those first updates from my ansible script hit and everything went fine: