What Should be Included in a Linux Crash Course?

Olivier Van Acker asks: "Since I started working at my current job a year ago I've installed on average one (Gentoo) Linux machine a month. Included are developer desktop machines, development servers, router/firewall, web servers, video server, MPEG encoders, etc. (It's a platform for interactive television). Since I'm the only one who is able to maintain them I want to train two of my colleagues. I've got three days dedicated time, three computers to work with and they are both Linux/Open source newbies (A technician and a programmer). What should this crash course include, what is the best learning method and what resources are available online?" "My background: I'm a programmer, a systems engineer and I used to give IT training. I have been using Unix-based operating systems since 1995.

My list so far:

Linux system Installation

Software installation

General Linux system administration

Network administration

Web server configuration

Database administration

Video server administration

History of Unix and Linux

Philosophy of open source software"

Comments

not enough anyhow

[HawkingMattress]

I'd try to teach them the logic behind Unix, that means explaining how the filesystem works, and doing alot of basic console excercices. Teach them the how to use pipes effectively, bash shortcuts, what you can do with ssh to remote admin lots of servers, how to find the info they need...

Try to teach them cool things so they'll be happy and curious enough to dig more into it later. If it's a pain for them, they'll quickly forget it... And i'd stick at the console, show them how X works and what you can do with it, but have them use a console all the time. There's no way you can understand Unix by using graphical managment apps...

Anyhow, 3 days is of course not enough to learn evrything, so I think you should really learn them how to think the Unix way, and stick to that.. then show them that using this way of thinking, they can resolve the problem themselves most of the time (and google helps alot too...)

Automated installs, packaging managers

[SgtChaireBourne]

Are you covering desktop machines or mostly servers?

Either way, show them how to make a kickstart disk or other ways to automate a custom installation.

Packaging managers are a must. Whether it's dpkg or rpm or yast, show them the different tricks and options. Also, if show how to roll a custom package, but choose one of the simpler ones.

For servers, cover iptables, tcpwrappers, inetd/xinetd, sshd, sudo and apache. System log file analysis is another must.

For desktop machines, cover KDE/Fluxbox/Gnome. Kiosk mode might be useful for some parts of your work environment.

but kill a few GPL myths along the way

[SgtChaireBourne]

Since time is short and the focus is one getting them settled in with administrating the system, history and philosophy don't need a separate section.

That said, a few words here and there to put to rest some of the myths about the GPL can be quite useful. Also, sometimes a little history is needed to put things in context. Just a few words, though.

Documentation

[Spoing]

If you don't have policies and procedures, you might want to start there and slip the Linux-specific stuff in as an implementation of them.

I don't mean creating and enforcing ridgid doctrine, though.

Here's an example -- if you've never done this or need a refresher;

1. Backup procedure;
2. Log the status of all network-based backups in the book (paper journal).
3. Schedule backups so that they occur regularly including moving backups to an off-site location.
4. If a system is added/removed or failed to be backed up note it in the book.
5. If a system can't be backed up over the network or does not require backup, note it somewhere.

The tool(s) used are up to the admin and training in them should be direct and simple. The people who are new to the tools should be given resources (books, notes, and someone experienced to talk to). That the tasks are being performed at all should be easily verifiable. Keep it simple as possible so that it actually gets done, though have it just formal enough that someone else can figure out what should be done -- not necessarily be told how they should do the job.

Basic Linux Training

[Skipworthy]

Its real nice to point and say 'please consult the excellent documentation', but a total newbie probably doesn't even know what they are looking *for*

Teach them:
File system stuff- where, how- make a new directory, find a file, check permissions
- permissions- look at and change
-mounting devices (start above with 'Linux sees everything as a file system'), unmounting devices, names of devices
- text editors. vi, emacs, whatever. start from the gui of your choice and show them the equivalent of notepad (Kate, gedit whatever)
- equivalent apps- openoffice, firefox, thunderbird whatever you use.

All this will make them comfy on the desktop. then:

-review network basics, and show them the basic utilities- how to look at and reconfigure a network connection
- show them top, ps , grep, awk and df/du, DD, cp,

After that, go teach them about more specific stuff. nothing else will make much sense to a Linux newbie...philosphy and pedagogy is important, but should take a back seat unless it relates directly.

And yes, show them the docs, the forums etc, and hand them a book and show them where stuff is.

'RTFM' is just rude and arrogant.

The most important thing can't be taught

[menscher]

I've been looking to train a replacement, and therefore have been thinking about this a lot. The most important "skill" is maturity. They need to be mature enough to prioritize tasks, handle the responsibility of keeping data secure, and not tinker with things too much.

As a sysadmin I've had the opportunity to work with, or closely observe the work of, about 30 other admins. The ones who do well are those that have a healthy respect for the system. I try to keep my setups as default as possible. Any change must have a good reason. This keeps things more stable (defaults are better tested) and easier for my replacement. The "problem" admins are the ones that can't resist tweaking everything. Yes, they might get a 1% performance boost, but they're also more likely to generate system instability.

In terms of priorities, there are a few basic rules: #1 priority is security, #2 is stability, and #3 is performance or other user requirements.

Finally, there's the concept of structuring the environment. Think about dependencies. Try to consolidate services so there's a single point of failure. This means not having multiple fileservers with crossmounts. Running a single OS/distribution will make your life a lot easier, assuming your shop doesn't require the diversity.

As others have said, there's a lot you can teach them about how to read manpages and use google, but without the basic philosophy of how to be an admin, all their knowledge will probably just lead them to manage unstable systems.

linux.org/courses

[olscratch69]

Speaking as someone who is fairly new to world of linux based operating systems, I would suggest the courses on www.linux.org. They are based on a debian system, but most of the basics for all linux systems are there. I learned more from that then any other information I have come accross so far. First take a look at yourself and see what you would like to stress as important and go over those sections in the time you have with them. Then you can give them some homework by having them go over the courses at home.