Linux needs to grow. Stop telling people it’s ‘tech-y’ or acting like you’re more advanced for using it, you are scaring away people. Linux Mint can be used by a senile person perfectly.
Explain shortly the benefits, ‘faster, more secure, easier to use, main choices of professionals and free’. Ask questions that let you know if they need to dual boot, ‘do you use Adobe, anti-cheat games, or Microsoft Office’, ‘how new is your computer’, ‘do you use a Mac’.
And most importantly, offer to help them install.
They don’t understand the concept of distros, just suggest Linux Mint LTS Cinnamon unless they’re curious.
That’s it, spread Linux to as many people as possible. The larger the marketshare, the better support we ALL get. We can fight enshittification. Take the time to spread it but don’t force it on anyone.
AND STOP SCARING PEOPLE AWAY. Linux has no advertising money, it’s up to us.
Offer family members or friends your help or copy and paste the below
how to install linux: 1) copy down your windows product key 2) backup your files to a harddrive 3) install the linux mint cinnamon iso from the linux mint website 4) use etcher (download from its website) to put the iso on a usb flash drive 5) go into bios 6) boot from the usb 7) erase the storage and install 8) press update all in the update manager 9) celebrate. it takes 15 minutes.
edit: LET ME RE-STATE, DO NOT FORCE IT ON ANYONE.
and if someone is at the level of ignorance (not in a derogatory fashion) that they dont know what a file even is genuinely dont bother unless theyre your parents cause youll be tech support for their ‘how do i install the internet’ questions.
I’ve been using Linux for 30 years now, certified to teach it and everything… Here’s your problem:
“Stop telling people it’s ‘tech-y’”
Compared to Windows or MacOS, yes, it is very techy.
“offer to help them install.” - If they need your help to install it they absolutely have no business running Linux.
“They don’t understand the concept of distros” - If they have no understanding of distros, they have no business running Linux.
Think of it like this… if they can’t wrap their head around a distro, what’s going to happen when you try explaining a package manager?
I get the evangelism, but Linux simply is not for everyone, that’s why Apple invented iPads.
Distros that have so much graphics like ubuntu and their linux mint isn’t (much) :)
there’s a guy even claimed “Linux is almost identical to Windows”. That guy is a “masturbing monkey” that cannot care about anything other than privacy.
correct. I think Torvalds would agree.
Many people have no concept of a computer, offer them running linux is destroying their business and render them jobless
And these guys are so hilarious: switching to linux but want to use windows app with wine !
Switching to linux only to decorate the desktop and neofetch!
They want to switch but never want to learn what a kernel is.
Switching to linux and claim about “free”, “open source” but they hide their proprietary games
I’m curious what have you learn and certified to teach? I want to learn all of them :)
I don’t know that you can learn “all of them”, there are new ones popping up all the time.
I started with Unix in 1988 because I wanted to play on the Internet and back then you either learned Unix or you didn’t go.
Unix is interesting because when Bell labs came up with it, they were told “Look, you can have a monopoly in the telecommunications industry, or you can have a monopoly in the computer industry, PICK ONE.”
So they picked the telecom industry, but at the same time they went “Hey, here’s this computer OS, see what you all can do with it!”
So you ended up with Unix System V, HP-UX, Irix, BSD Unix, and so on and so on. They were all Unix but all also a little bit different.
Roll forward to the early 90s and Linus Torvalds going “Hey! Imma make my own Unix!” and then THAT splintered into all the Linux variants we have today.
When the early days of Linux happened, my reaction was “Well, I already learned Unix, how hard could this be?” :)
The problem was, there was no easy way to collect everything you needed for an install, so I waited until someone put out a CD with all the files I needed, I think that was 1993? 1994? Something like that.
Anyway, my first was Slackware. Since then, I can’t tell you how many I’ve used. Different situations call for different things. I was a Redhat admin for awhile. I installed YellowDog on a PS3 for fun. MacOS X is not Linux, but it’s underpinnings are based on BSD Unix so it’s kind of a kissing cousin. Apple does a lot of goofy shit, but it’s not insurrmountable if you know Unix.
My certifications were done around 2000/2001 through a company called SAIR and I’m not even sure they exist anymore. They got absorbed into Thomson Learning in 2002.
It was a great experience though. Wouldn’t trade it for anything. I made some good money administering Avaya Definity and Intuity phone systems running Unix.
https://en.m.wikipedia.org/wiki/Avaya
The core remains the same. And if I’m not stupid, everything I learned in Linux (yeah, kernel things) can be easily adapted to OpenBSD which I’m using.
My dad always urge me to learn things “around assembly” (binary math, how the kernel operate). I wanted to know how to get started with these :)
The core is the same, the shells are each a little different. I remember juggling 3 different installs and having to keep a cheat sheet to keep them all straight. :)
Do you know how can I get started with things around the kernel?
So when it comes to kernel modifications, I’m old school…
“If it’s not broken, don’t fix it.” :)
https://www.redhat.com/en/blog/balancing-if-it-aint-broke-dont-fix-it-vs-release-early-and-often
Unless there’s some VERY specific need, some security hole that needs patching, some critical flaw that is failing, in general, DO NOT mess with the kernel.
That being said, there are tons of good guides you can find just by googling “linux kernel modifications”, but also specific guides for your installations. RedHat makes it dead simple to do stuff like this.
But before you do it:
Make sure you have a specific need you’re addressing.
Make sure you have all the necessary backups you require.
Have a roll back process in case something goes wrong.
Have a diagnostic testing plan.