Unix Overview

 History of Unix

  • In 1970, Dennis Ritchie and Ken Thompson's started devloping Unix in AT&T.
  • 1972 they developed unix using 'C'.
  • 1975 they spreads outside. (With free license and source code)
  • Its an open source.
  • Different flavours available at free of costs.
  • Unix is case sensitive.
  • Production versions only available in Unix.

Linux

  • Linux is a light weight version of Unix.
  • Linux derived/Inspired from Unix.
  • Linux is an open source but we have to get BSD license for using UNIX. Unix is not a open source. Also GNU license need for installing Unix.
    • BSD (Berkeley Software Distribution)
    • GNU (GNU General Public License)
  • Linux is journal purpose computer operating system.
  • Originally build by Linus Torvalds and released in 1991.
  • Linux is defined by its Kernal which is the core component of the system. It interact computer hardware to software for work.
  • Here the software and OS will be free for free of cost and freely modifiable. (GNU General Public License)
  • Linux is popular from many different applications, Bcoz 100's of variations we can see in this edition. 
    • Ex: From server operating system, super computer system, mobile phones, androids, iphone.
  • Major Distibution based on original OS : Arch, Debian, Red Hat and Slackware, etc. (Debian and Red Hat are popular.)
  • Most of the companies using Debian and Red Hat.
  • Debian  categories : Linux Mint, Ubuntu, Elementary OS, and Kali Linux.
  • Red Hat categories : centOS, Fedora, Red Hat Enterprise Linux.
  • Bash Shell - Available almost everywhere.

Unix Architecture






Kernel

  • Kernal is a heart of system or core of the OS.
  • Will allocate time and memory management.

SHELL

  • SHELL is acting like an interface of users and kernal.
  • Outer layer of OS.
  • Interact with user.
  • Sent request to kernal.
  • Return result to user.
SHELL Variations,

    sh : Thomson Shell (1971)
    sh : Bourne Shell (1977)
    csh : C Shell (1979)
    ksh : Korn Shell (1982)
    bash : Bourne again Shell (1987)
    zsh : Z shell (1990)
  • Thomson shell completely replaced by Bourne Shell on 1977.

OS & Device Category

  • Open Source : BBD, Linux
  • Closed Source : Sun Solaris (Sun micro system), AIX (IBM), HP/UX, Oracle Unix(Oracle)
  • Mixed Source : MAC OS X (Also available in all categories)
Mobile device OS
  • Android, IPhone, IPad are Developed using Unix.
MAC OS X

Its combination of BSD + NeXTSTEP + Apple Code and we can call it as Darwin OS.
  • NeXTSTEP is a discontinued object-oriented, multitasking operating system based on the Mach kernel and the UNIX-derived BSD.
  • Darwin is the core Unix operating system of macOS, iOS, watchOS, tvOS, iPadOS and bridgeOS. It previously existed as an independent open-source operating system, first released by Apple Inc. in 2000.

Working with files and directories

Use below Naming rules,
  • Max of 255 char.
  • Avoid /, \, *, &, $, |, <, > and most other symbol. (Bcoz most of the time it has some functionality.)
  • Use a-z, A-Z, 0-9, period, underscore, hypens.
  • Typically lowercase. (MyFile and myfile would be different)
  • Underscores are better than spaces.
  • File ending (.txt, .png, .html, etc) not required but helpful.

Unix File system

/               Root
/bin          Binaries, Programs
/sbin        System binaries, System Programs.
/dev         Devices, hard drives, key boards, mouse, etc.
/etc          system configuration's.
/home      User home directories.
/Lib         Libraries of code.
/tmp        temporary files.
/var         various, mostly files the system user.
/usr/etc    User Pgm's, tools and libraries (not files).

Linux versions Info


cat /etc/*-release
  • It will display the information of your version using.
  •   For MAC, this command wont work.
uname -a 
  • For MAC, name of Macro.
free -h
  • -h means human readable number format. It will display how much memory we have totally, used, free details.
cat /proc/cpuinfo
  • It will give the details of processor, model, cpu informations.
echo $0
  • Used to view SHELL model. (-bash)

Comments

Post a Comment

Popular posts from this blog

Hive File Formats

Image
 Hive supports several file formats: Text File SequenceFile RCFile Avro Files ORC Files Parquet Custom INPUTFORMAT and OUTPUTFORMAT      The hive.default.fileformat configuration parameter which is avaialble in hive-site.xml determines the format to use if it is not specified in a CREATE TABLE or ALTER TABLE statement.        Text file is the parameter's default value. What is File Format ? File Format is a way in which information is stored or encoded in a computer file.  In Hive it refers to how records are stored inside the file. These file formats mainly vary between data encoding, compression rate, usage of space and disk I/O. Hive does not verify whether the data that you are loading matches the schema for the table or not. However, it verifies if the file format matches the table definition or not. Text File TEXT FILE format is a famous input/output format used in Hadoop. In Hive if we define a table as TEXTFILE it can load data of from csv (Comma Separated Values), tsv, txt
Read more

HDFS Infographic

Image
Already we know, the data will be getting stored in 3 data nodes (replication) for prevention of failures or corruption. It is useless when you storing the same data in same disk/rack as 3 times. Suppose that whole data replicated single disk/rack is corrupted then it won't be going to work out, It is useless to come and do replication process in HDFS. When we are storing all of these 3 replicated data in different data node but in same rack. It is also not helpful. Suppose if you lose whole rack, then won't be going to help. So we have to store it in different data node with different rack then it will be more helpful to protect the data. Here we are going to discuss about how to store the data in different data node with different rack and how to handle Fault Tolerance. Replica Placement Strategy Name node will follow  Rack Awareness Policy  algorithm for replicating data into 3 different data nodes. This Rack Awareness Policy follows Replica placement strategy. Here the
Read more

Why We Need Hadoop?

What is Hadoop? It is an open source framework or system which was fully developed by Java.  It is allow us to implement Big Data.  Hadoop can be used for storing and processing huge datasets with cluster of commodity hardware. Because its stores the data and processing in a distributed manner.  It made up of several components which entirely open source. Doug Cutting is the inventor of hadoop. He used elephant symbol. His child used to play with elephant toy. So he used that toy name as symbol and named for new invention. Why we need to go for Hadoop? 1. High Throughput and Low latency queries Less amount of time it will take to run/process real time queries or near real time queires. We can achieve high throughput in hadoop using below techniques.  Parallel Processing WORM Data Locality 2. Distributed computing A distributed computer system consists of multiple software components that are on multiple computers, but run as a single system.  The computers that are in a distributed sys
Read more