Discussion skill will be split into two, namely the ability of technical and nontechnical abilities. In the deliberations of the technical skills required, we Admins try to heeding the admin tasks that had been discussed earlier. Of course, one does not need to have all the ability only to become an admin.
In the discussion of the ability of nontechnical, we will discuss how admin can work smarter in resolving problems or maintaining the system, both when choosing a technology or the work culture.
Admin work is technical work. Therefore, technical expertise is to be owned by an admin. The following is an example of technical expertise needs to be owned by the admin:
- Able to work with the hardware of the computer hardware components and understand who's in it. Do not need to follow all the latest developments in hardware, but need to know what the contents of a computer and what if a computer does not want to work (for example, when a process fails on a POST).
- Still around in hardware, an admin should know what are the devices that can be installed on the computer, for sharing your needs. Of course, this skill can be improved along with the field that became a specialty company admin work. If the admin is working on the company that built the tuna netra, then Admins need to know braille devices for example.
- Admins should know a little bit about computer technology that has been developed. Not necessarily new or emerging. For example, the admin needs to know that the current wireless technology has evolved and can be used in place of work where necessary.
- Understood by both the issue of partition and the file system. Including the issue of the swap.
- Admin at least able to install and configure at least Windows (workstation and server) and Linux (at least two kinds of distributions of different families). Installing windows workstation is required because quite possibly used by Windows users. Do not be so highly sophisticated admin install servers but make the user difficulty because windows workstations disetup by admin be complicated to use. Windows server installation or in typical windows services must provide for windows-based users. Linux installation at least two kinds of different distributions (e.g. Debian and SUSE or Debian and Red Hat or SUSE and Red Hat, but not Red Hat and Fedora, or Debian and Knoppix) is required so that the admin is able to install and configure Linux not fixated on one distribution (later will be a dependency).
Able to work in a command line. On Linux this mandatory law. Not wanting to appear cool, geeky or just like to sok-sokan, but make it a habit to work in extreme conditions. Tool-tool core (findutils, coreutils, and others) is required.
- Understand and be able to implement a good setting on the system. Including for Windows.
- Understand and be able to implement the issue of access rights on the system. Including for Windows. Specifically for Linux, because the problem of right of access by default is simple enough and there is enough banyk another project to address this problem, then it's good if the admin was also aware of it and may apply it.
- Understand and be able to set up a network in Windows and Linux operating systems. It absolutely is.
- Able to install programs on Linux, of course an admin should be able to do the installation program utilizes package management distribution, or through source sambill still maintaining the stability of the system. Being able to choose and install the needed packages only.
- Able to manage user in Linux. If the company is using some Wondows for workstations, then the ability to manage user in Windows also need to be very good. On Linux, if necessary, provide for user and filesystem qouta or group.
- Was able to install a new device to the system, either on Windows or on Linux. On Linux, of course the admin need not necessarily successful install hardware due to limited support. However, at the very least, Admins should be looking for in advance as much as possible. Then, do the kernel driver compilation. Don't use the distro that comes with full hardware support (such as SUSE), then handed over entirely to the distro.
- Able to compile the kernel, but do not have to compile the kernel continuously. The kernel that came with a good Linux distribution should have gone through the process of QC. Just replace the kernel when an admin actually knows exactly what he did, and the objective is also clear. In fact, if the admin under supervision (e.g. IT manager), replacing the kernel need approval from his supervisior.
- Able to arrange service of the operating system. Being able to see which service should run and which services should be turned off. When the primary server does not require Apache httpd server, then do not lit. If admins want to do research with respect to the httpd server, get it done on the computer senfiri. If some people want to make IT a research team with respect to the httpd server but it is not a major job, then arrange the httpd installed on another computer or on the computer one of the team members. Bottom line, don't focus the main server with things that don't need to be. Learn about the requested service fine.
So this post first, hopefully can be a lesson for all of you who came here.