I’m talking about like your mom if she started using Linux, and just needs it to be able to open a web browser and check Facebook or her email or something. A student that just needs a laptop to do homework and take notes, or someone that just wants to play games on Steam and chat on discord.
I’m working on a Windows - > Linux guide targeting people like this and I want to make sure it can be understood by just about anybody. A problem that I’ve noticed is that most guides trying to do something like this seem to operate under the assumption that the viewer already knows what Linux is and has already made up their mind about switching, or that they’re already pretty computer savvy. This guide won’t be that, I’m writing a guide and keeping my parents in mind the whole time.
Because of this there’s some things I probably won’t talk about. Do these people really need to know that it’s actually GNU+Linux? No, I don’t think so. Should I explain how to install, use and configure hyprland, or compile a custom gaming kernel? I dont think that’s really necessary. You get what I’m saying? I don’t want to over complicate this and scare people off.
That being said I also want to make sure that I’m not over simplifying by skipping on key things they should know. So what are some key concepts or things that you think even the most basic of Linux users should understand? Bonus points if you can provide a solid entry level explanation of it too.
Package managers:
- Repositories
- Update mechanism. Many of my friends and family are used to updates being either automatic, nagged, or nonexistent. Not an issue on auto-updating distros, but could get ugly on vanilla Arch or Debian.
- Resisting the urge to install loose executables from websites
File system:
- Write caching. Windows doesn’t do this for most USB drives so people get away without safely ejecting for years. On Linux, the safe eject button does matter.
- File hierarchy and mount points. When I first used Linux, I was very confused by the lack of the Program Files and Users folders, My Computer page, and drive letters.
- File permissions, especially executables
- Partitioning and how to format drives in the absence of a format dialog in the file explorer
Bash shell:
- It’s not the incomplete mess that made
cmdor Powershell so intimidating - Resisting the urge to paste in commands and scripts without knowing what they do
This may be a controversial inclusion, and it’s based on my relatively unsophisticated understanding of Linux. I believe the reason casual computer users hate Linux (generalizing here) is that “Linux” is not one thing.
Commercial operating systems are monoliths. Windows 11 is Windows 11. macOS is macOS. Apart from a few surface-level settings, all instances of them are the same. If you know how to use that operating system, you can go to almost any computer running that OS and start using it, just like you use the one you have at home.
“Linux” is entirely modular. There’s no single thing called “Linux.” You can pick and choose each component to build up your own customized OS from the ground up, and distros take advantage of this. I know just within my household, I have three Linux systems, and casual usage varies wildly across the three. One is a SteamDeck, which is a different kind of thing, but if I just take the two computers as an example, on one, you have an application menu in the top left where the other has an application menu in the bottom left. Also, those menus look completely different. That alone is enough to frustrate a casual user. Now take the fact that they each have different settings panels, different bundled apps, etc. and you have a recipe for making users always feel lost when moving from one system to another.
I don’t think this means you need to teach how to use every available desktop environment, window manager, or sound settings panel, but I do think it would be useful to introduce this concept as part of your curriculum. The sad part is that I think a lot of your audience will tune out at this point because they never had to know that on the commercials OSes, but I think it’s important to be forthcoming about it rather than having your audience blindsided by it.
Sorry to grin at you. But in OS theory Linux is known as a monolith kernal. So you choice of words would have given my lecturers a freakout.
But while your terminology is a bit crossed. The ideal you are explaining is fine.
Better Technical way to put it. Linux is just the kernal. Much of the interface you see is actually programs or apps running above that kernal. A d can be changed amd selected.
Windows is also started multipart. But has become less so over time. And it’s single distributer makes it way less obvious. By preventing any competition within it’s internal structure. The original monolithic kernal of Windows was the MS Dos command.com program. But I no lying those of us from the 80s and early 90 remember using it.
I’d just like to interject for a moment. What you’re referring to as Linux, is in fact, GNU/Linux, or as I’ve recently taken to calling it, GNU plus Linux. Linux is not an operating system unto itself, but rather another free component of a fully functioning GNU system made useful by the GNU corelibs, shell utilities and vital system components comprising a full OS as defined by POSIX. Many computer users run a modified version of the GNU system every day, without realizing it. Through a peculiar turn of events, the version of GNU which is widely used today is often called “Linux”, and many of its users are not aware that it is basically the GNU system, developed by the GNU Project. There really is a Linux, and these people are using it, but it is just a part of the system they use. Linux is the kernel: the program in the system that allocates the machine’s resources to the other programs that you run. The kernel is an essential part of an operating system, but useless by itself; it can only function in the context of a complete operating system. Linux is normally used in combination with the GNU operating system: the whole system is basically GNU with Linux added, or GNU/Linux. All the so-called “Linux” distributions are really distributions of GNU/Linux.
I think there’s a certain kind of user who doesn’t really learn concepts, but rote actions. They click the start menu and then excel to open excel, but they don’t really understand that the start menu is an application launcher and Excel is an application that can be opened in other ways. It’s very one dimensional.
Then when something changes, like the application launcher is moved, they freak out. They don’t have a mental model.
That’s how my mother is, anyway. It’s all magic with no underlying coherent anything. Not sure how to fix that, because it usually comes up when they’re mad or scared, and that’s not a time anyone will learn.
This is something that I actually planned on explaining! A big reason I myself like to use Linux is because it’s modular and can be customized and used in so many ways just to meet your needs which I think is ideal. An operating system shouldn’t be a one size fits all kind of thing!
- Linux isn’t Windows. I know that is a no-brainer but it needs to be said so it won’t be as 1:1 to Windows.
- How to install software both in terminal and as well as software manger GUI. Bonus points about compiling software from places like GitHub.
- Packages type and their pros and cons
- Trying to run Windows application via Wine (or some manager like Bottles or Lutris) as well as comparing running same Windows Application from Linux and Windows.
- Alteratives to popular software and list out what it can do and what it doesn’t have so user can see if that feature it doesn’t have would affect them. For example, GIMP doesn’t have full CMYK support which for most users, it isn’t a big idea but for people that want to edit images to be ready for printing, they might want to keep that in mind.
I’m talking about like your mom if she started using Linux, and just needs it to be able to open a web browser and check Facebook or her email or something.
Nothing. Just set up Elementary or Mint or something with a shortcut to Firefox and there’s nothing else to do. Any apps they might need would come from an app store, so point that out.
A student that just needs a laptop to do homework and take notes
So how to open a text editor? Recommending an easy-to-use and standard one like Kate would be good, but a polished distro will have one preinstalled.
someone that just wants to play games on Steam and chat on discord.
They need concepts like filesystems (e.g. the concept of a root directory, mounting, and device files), software repositories (since steam comes from a non-default repo in many distros), an awareness of the whole graphics driver situation, and hardware both appropriate to their needs and to running Linux.
One thing that many guides tend to skip is how to install software. People coming from Windows might try to install software the “Windows way” by going to the website and downloading them. That is just likely to cause pain and suffering for a number of reasons.
Instead, every beginner friendly distro has its own flavour of software centre that users should be encouraged to use instead. Maybe even include a link to flathub in the guide or something.
I think the biggest fundamental concept for any computer regardless of operating system is filesystem hierarchy. The concept of nested folders is core to using a personal computer, but for the last two decades UI/X teams have done everything in their power to obscure and abstract it away. Many younger people conceptualize the storage on their device as just an amorphous blob that apps manage autonomously. Windows is starting to go this way as well with OneDrive being sold as the way to manage all your data, but on Linux the file system is still king.
Your mom is presumably old enough to have some experience with desktop PCs, so hopefully that basic hurdle is already cleared. And honestly once someone is at that level of base competence, along with basic interface concepts like how to use a mouse and keyboard, clicking on icons, use of a web browser etc, with the right distro you really don’t need to explain much else. There might be a few quirks of the UI to explain depending on what you choose, but most of that can be handled by just watching them use the computer for a bit, and/or asking them to give you a list of questions and annoyances after they use it for a few days.
The biggest difference is one that most “I just want it to work” users will actually love, and that’s relearning how to install software. Having one central location to install verified software from is a change from the wild west of downloading installers from the internet, but it shouldn’t be a difficult transition. Most people these days don’t even install software beyond maybe Zoom, so you can probably get away with just installing any third party software they need in the initial setup.
I recommend an immutable distro like Fedora Silverblue, at least if a) you’re setting it up and are reasonably technical, and b) you don’t want to go over and help them fix stuff often. I set my mom’s laptop up with it 4+ years ago and she’s only had one problem since then.
Yo mama so old she has experience with desktop computers.
Was not expecting a yo mama joke in this 🤣🤣
Hard to summarize, because it differs so much from person to person.
I installed Linux on my parent’s computer. They don’t need to know anything about Linux, because everything they use is identical to their old Windows PC. They click the icon for Chrome to open the browser. They Click the icon for LibreOffice to type up a “Word” doc and print it by clicking “file > print”
As far as they’re concerned, they are still using Windows.
For a gamer, they will need to know a little about Proton, possibly Lutris and the Hero launcher. They might need to know about installing nVidia drivers or tweaking a few things in the Steam launch options to get games to run better.
It’s tough to know exactly what a new Linux user will “need” to know in order to use Linux.
Graphics driver installation is pretty key on any system but AMD graphics systems.
For example if your parents want to watch any videos without them stuttering or being weird, whether Intel or Nvidia, they will need the non-free graphics drivers installed so it doesn’t run like shit.
To my knowledge nearly every AMD chipset already works out of the box on Linux.
True, it still does vary even chipset to chipset. Some Nvidia and Intel cards do just work depending on the distro, others require more work.
It also depends on how “techie” the user is. My parents are 0% techie, so I have to do anything and everything for them if they have questions or issues.
But a Windows power user can handle some terminal use and other basic system modifications. And honestly now days, most of that stuff is super easy. Like Linux mint has a dedicated driver app that allows you to use a simple GUI to install Nvidia drivers, it’s super easy.
IME, beyond the install, it’s all distro- and desktop-specific.
- How to find and install apps varies from distro to distro. IIRC, the Mint menu item is something obvious, like “Install software”, but on Arch (you’d have to hate your newbie to throw them into Arch), it requires a chicken/egg finding and installing a graphical installer. If you know the distro, this would be good information - or if you’re helping with the install, create a desktop launcher.
- Showing them where settings are. Surprising to me, this has been super-not-obvious to my newbs. Even though the KDE Settings app is called “settings”, I think Windows and Mac folks are used to looking for settings in a specific place, rather than an app name - and in Windows, there’s can be several ways to get up different settings, like changing display stuff is always in a weird place. Again, maybe a desktop or panel shortcut would help.
- One of my newbs used Mint for two years without opening a shell, so I don’t think that’s an issue. He even found and installed a piece of software he wanted, but I can’t remember if I originally showed him how to the first time. But that’s Mint. He did, however, need help setting up a printer, but that’s because he couldn’t find the settings program; he came from Windows originally.
- Edge cases, like printers and other peripherals, can be hard, and I don’t think any amount of extra documentation is going to help, because almost every difficulty is practically unique. There’s a ton of online help for stuff like that already. And then, if they want to, eg, attach a game controller… well, that’s very specific and again varies by controller. I don’t think you can cover all of these edge cases.
- Games can be hard only because of the indirection of having to install some other software, like Proton or Steam, creating an account, knowing how to check for compatability - there’s a lot of moving parts. It’s not just: go to the game’s web site, buy, download, and install something and run it, like I imagine it is on Windows. So maybe that would be useful - or - again - pre-installing one of the game stores and (surprise) making a shortcut would eliminate that.
- Network connections. Again, I always find figuring out how to get to network configuration in Windows to be hard, and bizarrely having multiple ways of accomplishing the same task, so I’d guess going the other direction would be confusing. Having a note about how to get to the configuration would be handy.
As I think about it, I realize that configuration under KDE of way more encapsulated and clear than on Windows, and people having learned the byzantine and myriad ways of Windows, KDE’s relative simplicity is confusing. Windows people look for configurations in places they’ve learned to look, which aren’t always where they are under KDE (I can’t speak much about Gnome - I don’t use it or set people up with it). MacOS isn’t as bad, having a similar configure-everything-through-a-single-settings-program approach.
Anyway, that’s my experience.
At least a basic primer about finding your way around in Linux in command line, and where various configuration files live.
When shit goes wrong (and it likely will at some point) knowing how to dump to another tty and log in via the console and fix issues via command line is pretty key. This has saved my ass more times than I can count now.
Having trouble finding a CLI focused course, but this is a free course that covers a lot of basics:
https://training.linuxfoundation.org/training/introduction-to-linux/
As a Linux noob, this is not as basic as you think it is. It’s probably cool to show them “sudo apt install [program]” as a neat trick to dip their toes into the command line. All the other things you mentioned would scare me away if it was presented as beginner essential knowledge. I legit have no idea what you’re talking about.
It’s basic in the sense that Linux is always a work in progress and no matter how hard you try, you’re going to need it at some point.
When your system randomly turns on to a black screen and there is seemingly no way to log in, knowing how to switch to the command line and at bare minimum back up your settings and documents before you wipe and start over is pretty key. To be clear, I have been in that exact situation and even more confusing situations where the PC has basically become unusable but I was able to fix it via CLI.
Just imagine losing months or years of work because you don’t know that you can probably fix it all from command line and likely don’t even need to wipe your computer and start over if you can narrow down what is going wrong and remove it via the command line.
I dunno seems pretty important to me.
True, first time I ran into catastrophic problems (caused by entering in commands I copied from online, knowing damn well it was a bad idea), I got annoyed having to fish out corrupted files and shit, but I realized that anytime something had gone wrong with Windows I had no tools to fix it and could only check in on a loading screen that lasts hours. It was a learning experience
For me personally, I would remember none of that if taught to me. I’m stubborn and handy enough to figure it out during an emergency. For the kind of noob OP is describing that benefits from a handheld on-ramp, they will probably never be able to do what you’re describing.
I think a good compromise would be mentioning a few things that you can do in case of emergency so a more savvy person would know what to look for in an emergency. You don’t have to teach them so much as tell them there is something they can do. If there’s a fire, idk where the fire extinguisher is but I know there is one and I can go looking.
I’m in the minority who thinks Linux isn’t for everyone and that people who approach computing from that standpoint should really stick with macOS or Windows. Linux gives you more freedom to be in control, but that freedom to be in control also demands more knowledge and involvement to be able to be in control. “With great power comes great responsibility” kind of thing.
For an analogy Windows is like being a passenger in a car with someone else driving, and Linux you’re in the drivers seat of the car. You simply are required to be aware and involved in driving more because you are in control, and that control requires knowledge. You don’t get to sit back and go “I don’t need to know what all this stuff does because I don’t want to.” Understanding how the pedals and steering wheel work is a requirement for driving, as is paying attention to what is going on around you on the road. As a passenger, you aren’t required to know or pay attention to as much because you’re not being given the freedom of control, you’re just along for the ride. Linux is giving you that freedom of control of being the driver, but you have to know a lot more to do it than you need to know just being a passenger (Windows).
I know everyone else thinks Linux is ready for the prime time and ready for regular users who don’t want to have to learn and just want something that works… but I personally don’t. Simply because Linux is a lot less guaranteed to “just work” than the other options.
TBH, I agree with you. However a lot of people’s PCs are no longer supported with no practical way to change that. For those people that are trying Linux out timidly and reluctantly, I’m fine with a little handholding. I wouldn’t recommend someone switch to Linux unless I knew they were a bit savvy. But if they’re worried about going behind on security updates and can’t afford a new PC, I will suggest their one option, even if I know it will be challenging at times.
Agreed on that, it’s not the best solution, but for people who need access to computing and whose devices have aged out of other support, it’s pretty much the only option available.
- The difference between the OS and the DE.
- How to install apps in Flatpak, AppImage, and dnf/apt
- maybe user help programs like tldr or trash-rm? Those are both cmd programs though, so that might be too advanced for beginners.
Distrobox is useful so you don’t have to think you miss out on another distro and don’t hop around.
cd command.
No joke, when I started, it was the thing I stalled on the most as it’s so basic no one explains
file manager works pretty much the same on Linux as it does on windows. you really can search for files yourself
text editor really does work the same on Linux as it does with notepad on windows, you really can just open files and read them
Hmm, I think that’s where experiences will differ. I’m unable to search for files within file manager (thunar) easily, and use catfish file search instead.
deleted by creator
I don’t think that’s a guide… it’s a hands on class. Maybe even a good idea to pitch to your local community college, community center, or adult edu department.
It’ll shock you how low the average person’s technical literacy is. And since you’re talking about a guide for a lot of things that update independently, the guide will begin to be outdated before you even publish it. It’s exceptionally hard to keep technical documentation in sync with software and hardware that you don’t control, and when the users of your guide hit those spots where the doc doesn’t match, they bail quickly.
What key concepts to cover probably depends on what you’re trying to teach. If it’s just how to use a web browser, the mainstream distros all do that pretty well out of the box once they’re installed (although installation can still a bit of a challenge from one laptop to the next). Maybe the greatest communal benefit would be to teach foundational concepts of online security.
Eh, go for something simple like Fedora KDE and teach them how to update and install stuff through Discover - it’s like App/Play/Microsoft store + the System update all in one.
I imagine Linux Mint and OpenSUSE has similar GUIs to introduce if that’s more up your alley.This was going to be my suggestion. Most noobs will be familiar with phone app stores. You can present a distro’s software manager like an app store. People coming from another OS will probably be happy they don’t have to find, download, and install their programs.
