Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
International Rescue Committe

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents
Up to --> Linux Basics

· What Linux is All About
· Guided Tour
· What Linux is Made of
· What Linux Does
· What goes with Linux

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Recommend Us
Surveys

Features
HOWTOs
News
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 250 guest(s) and 5 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  
Linux Tutorial - Linux Basics - What Linux is All About - What Linux Does
  What Linux is Made of ---- What goes with Linux  


What Linux Does

On any operating system, a core set of tasks is performed. On multi-user or server systems such as Linux, these tasks include adding and configuring printers, adding and administering users, and adding new hardware to the system. Each of these tasks could take up an entire chapter in this book. In fact, I do cover all of these, and many others, in a fair bit of detail later on.

I think it's important to briefly cover all of the basic tasks that an administrator needs to perform in one place. There are a couple of reasons for this. First, many administrators of Linux systems are not only novice administrators, they are novice users. They get into the position as they are the only ones in the company or department with computer experience. (They've worked with DOS before.) Second, by introducing the varied aspects of system administration here, I hope to lay the foundation for later chapters. If you are not familar with this issue, you may have trouble later.

Keep in mind that depending on what packages are installed, any Linux distribution can do a lot more. Here we will be discussing just the basic administrative functions.

The average user may not want to get into the details that the later chapters provide. So here I give an overview of the more important components. Hopefully, this will give you a better understanding of what goes into an operating system as well as just how complex the job is that your system administrator does.

The first job of a system administrator is to add users to the system. Access is gained to the system only through user accounts. Although it may be all that a normal user is aware of, these accounts consist of substantially more than just a name and password. Each user must also be assigned one of the shells, a home directory, and a set of privileges to access system resources.

Although the system administrator could create a single user account for all users to use to log in, it ends up creating more problems than it solves. Each user has his/her own password and home directory. If there were a single user, everyone's files would be stored in the same place and everyone would have access to everyone else's data. This may be fine in certain circumstances, but not in most.

Users are normally added to the system through the adduser command. Here, when adding a user, you can input that user's default shell, his/her home directory as well as his/her access privileges.

Another very common function is the addition and configuration of system printers. This includes determining what physical connection the printer has to the system, what characteristics the printer has (to choose the appropriate model printer) as well as making the printer available for printing. Generically, all the files and programs that are used to access and manage printers are called the print spool, although not all of them are in the spool directory.

Adding a printer is accomplished like in many UNIX dialects: you do it manually with the primary configuration file, /etc/printcap file. The printcap man-page lists all the capabilities that your version of Linux supports. You must also add the appropriate directory and enable printing on the port. We'll get into more detail about it as we move on.

What happens when you want to remove a file and inadvertently end up removing the wrong one (or maybe more than one)? If you are like me with my first computer, you're in big trouble. The files are gone, never to show up again. I learned the hard way about the need to do backups. If you have a good system administrator, he/she has probably already learned the lesson and makes regular backups of your system.

There are several ways of making backups and several different utilities for doing them. Which program to use and how often to make backups completely depends on the circumstances. The system administrator needs to take into account things like how much data needs to be backed up, how often the data are changed, how much can be lost, and even how much will fit on the backup media.

There are tasks that an administrator may need to perform at regular intervals, such as backups, cleaning up temporary directories, or calling up remote sites to check for incoming mail. The system administrator could have a checklist of these things and a timer that goes off once a day or every hour to remind him/her of these chores, which he/she then executes manually.

Fortunately, performing regular tasks can be automated. One basic utility in every UNIX version is cron. Cron (the "o" is short) is a program that sits in the background and waits for specific times. When these times are reached, it starts pre-defined programs to accomplish various, arbitrarily defined tasks. These tasks can be set to run at intervals ranging from once a minute to once a year, depending on the needs of the system administrator.

Cron "jobs" (as they are called) are grouped together into files, called cron tables, or crontabs for short. There are several that are created by default on your system and many users and even system administrators can go quite a long time before they notice them. These monitor certain aspects of system activity, clean up temporary files, and even check to see if you have UUCP jobs that need to be sent.

What about a program that you only want to run one time at a specific time and then never again? Linux provides a mechanism: at. Like cron, at will run a job at a specific time, but once it has completed, the job is never run again.

A third command that relates to cron and at, the batch command, differs from the other two in that batch runs the job you submit whenever it has time; that is, when the system load permits.

Linux supports the idea of virtual consoles (VCs), like SCO. With this, the system console (the keyboard and monitor attached to the computer itself) can work like multiple terminals. By default, the system is configured with at least four VCs that you switch between by pressing the ALT key and one of the function keys F1-F6.

Normally, you will only find the first six VCs active. Also, if you are using the X Windowing System, it normally starts up on VC 7. To switch from the X-Windows screen to one of the virtual consoles, you need to press CTRL-ALT plus the appropriate function key.

Keeping the data on your system safe is another important task for the system administrator. Linux provides a couple of useful tools for this: tar and cpio. Each has its own advantages and disadvantages. Check out the details on the respective man-page.

 Previous Page
What Linux is Made of
  Back to Top
Table of Contents
Next Page 
What goes with Linux


MoreInfo

Test Your Knowledge

User Comments:


Posted by 55musician on August 26, 2014 10:02pm:

Curiouser and curiouser. The value of backing up the system hit home. I too ended up deleting files from a Toshiba running Windows 7, only to find that the system was utterly inoperable as a result of my ignorance. Fortunately it was still under warranty and a call to tech support assisted with replacing a driver that had been deleted when I attempted to clean up the system. Despite that fault, I have been neglecting to make back ups. An oversight that will not be neglected any further. These tutorials are driving my interest and, with that, I go on to learn more.


You can only add comments if you are logged in.

Copyright 2002-2009 by James Mohr. Licensed under modified GNU Free Documentation License (Portions of this material originally published by Prentice Hall, Pearson Education, Inc). See here for details. All rights reserved.
  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.12 Seconds