Guide Of Unix

Guide de Unix

Guide Of Unix

Various Unix/Unix commands discussed related to system administration, networking, file editing and other general purpose commands etc.

Main Features

✔ Fully Offline

✔ Optimized Layout for Mobile Reading

✔ Easy Navigation

✔ Mobile Reading Format

✔ Clean Layout

Commands are under these parts:

Access Control

Communications

Programming Tools

Documentation

Editors

File and Directory Management

File Display and Printing

File Transfer

News/Networks

Process Control

Status Information

Image Processing

Sound

Text Processing

X windows

Web

Miscellaneous

- Unix and Unix Commands

- Unix Tutorials

- Unix Administrative and Networking Commands

UNIX FOR BEGINNERS

GETTING STARTED

FILE MANAGEMENT

DIRECTORIES

FILE PERMISSION

ENVIRONMENT

BASIC UTILITIES

PIPES & FILTERS

PROCESSES

COMMUNICATION

THE VI EDITOR

UNIX SHELL PROGRAMMING

WHAT IS SHELL?

USING VARIABLES

SPECIAL VARIABLES

USING ARRAYS

BASIC OPERATORS

DECISION MAKING

SHELL LOOPS

LOOP CONTROL

SHELL SUBSTITUTIONS

QUOTING MECHANISMS

IO REDIRECTIONS

SHELL FUNCTIONS

MANPAGE HELP

ADVANCED UNIX

REGULAR EXPRESSIONS

FILE SYSTEM BASICS

USER ADMINISTRATION

SYSTEM PERFORMANCE

SYSTEM LOGGING

SIGNALS AND TRAPS

More Offline Unix and Unix Tutorials

Originally, Unix was meant to be a programmer's workbench to be used for developing software to be run on multiple platforms, more than to be used to run application software.The system grew larger as the operating system started spreading in the academic circle, as users added their own tools to the system and shared them with colleagues.

Unix was designed to be portable, multi-tasking and multi-user in a time-sharing configuration. Unix systems are characterized by various concepts: the use of plain text for storing data; a hierarchical file system; treating devices and certain types of inter-process communication (IPC) as files; and the use of a large number of software tools, small programs that can be strung together through a command-line interpreter using pipes, as opposed to using a single monolithic program that includes all of the same functionality. These concepts are collectively known as the "Unix philosophy". Brian Kernighan and Rob Pike summarize this in The Unix Programming Environment as "the idea that the power of a system comes more from the relationships among programs than from the programs themselves.