What to tell from GNU/Linux to fairly experienced PC users in 20 minutes?

Question

linux

Good day.
What can you tell fairly experienced users about Linux in a 20-minute time frame?
I think I have time to capture the rights, the network, and the installation of software, in fact this is the main thing.
Naturally, very briefly and give direction where to look and what to read, if you want to learn.
Who else can offer?
AP
The bottom line is this, I work in those provider support, in the whole department, in fact, only I am friends with nixes. The chief offered to hold a small educational program. So when a client asks a simple question, in fact, only I can answer it! It is necessary to give some basics and very briefly. Installing programs, why the Internet is not working (check if the interface is up), if the user cannot run the program, the specialist must understand that the user either launches something wrong or has no rights or something else, well, in general, as is customary in almost any support, tell the user which button to press so that everything works, and not write a letter to the application developer department for nothing.
something like this...

Answer 1

I think you need to start by writing out a list of typical problem cases with Linux machines encountered in practice, grouping them by topic - network, lack of software, viewing downloads ...
After that, show/demonstrate ways to solve them, first telling how launch the console (various types of terminals, including virtual ones). For example, network problems can be solved like this: look at ifconfig, ip addr|link|route, route, dig, pppoe. Check whether the software is running or not: ps, netstat, top.
Then you can show the differences between the usual utilities familiar to networkers (traceroute, ping) from win-systems. Tell that all the configs are in different files.
Well, at the end, show how to get help on the system: mana, logs.
Technical support does not need to know that users, files, and folders exist. In general, this is similar to win-systems.
UPD: I already taught networkers linux, but not TP, but operational units

Answer 2

So when a client asks a simple question, in fact, only I can answer it! It is necessary to give some basics and very briefly. Installing programs, why the Internet is not working (check if the interface is up), if the user cannot run the program, the specialist must understand that the user either launches something wrong or has no rights or something else, well, in general, as is customary in almost any support, tell the user which button to press so that everything works, and not write a letter to the application developer department for nothing.

You create a FAQ on questions, distribute them to your listeners and explain what's what in the allotted 20 minutes.

Answer 3

> fairly experienced users about Linux
> I think I have time to capture the rights, the network, and the installation of software, in fact this is the main thing.
Why tell fairly experienced users the most basic things?
It is better to tell the features of something tricky. controversial issues in bash, why it is better to do it in python and not in perl, how to deploy ansible..

Answer 4

So you need to tell experienced users or not very experienced colleagues? If the second, then the very basics of the command line, how to restart the service, how to open the file, where the logs are.

Answer 5

nothing ). It is impossible for an experienced user to keep within 20 minutes. if he is experienced, he has already tried. and to those to whom you start to carry nonsense about bash and they didn’t see him ... zero sense

Answer 6

I think you should start by assessing your current level of knowledge, like:
What is bash ?
how to learn what are active network interfaces?
Who else can offer questions?

Answer 7

Hmm .... those. provider support ... not by any chance Rostelecom?
In my practice (10-15 years ago) there was a case when I began to explain to girls with a "freshly baked" diploma of a software engineer in an office how to configure computers in our network. I see - they do not understand anything. It turned out that they have practically zero knowledge of network technologies - they simply did not know what dhcp, dns, etc. were. I had to teach girls how to use reference information, which I advise you to do with your "experienced" users. Those methods are different in distributions (deb and rpm, upstart and init). I think if people know the basics, then the difference in linux or windows tools is not important. I think it’s not possible to teach people to think and learn in 20 minutes, but you can try to motivate.

Answer 8

I think your idea will not be successful .....
It would be smarter to take 1-2 people who want to and analyze incoming problems with linux with them at the same time they will create understandable manuals that can then be included in a general manual on typical problems
and explain something 10 -20 without illustrative examples and direct control over their work, there is no point in the config of working servers - do not master it,
take a couple, and when they learn, they will help you teach the rest

Answer 9

all sorts of interesting things that greatly automate the work of redirecting grep output, creating several files at once through touch, installing programs where to look at logs, ifconfig how to add additional ip.