DOCSLIB.ORG

What Is Uclinux What Is a Linux Distribution?

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
What Is Uclinux What Is a Linux Distribution? Linux z Linux has come a long way since its humble beginnings in 1991 z Today Linux supports a very wide range of Embedded Linux platforms, from Embedded Systems based on ARM, PowerPC, Intel, and Hitachi microprocessors to name a few, all the way up to workstations, servers, and clusters z It also served as a launch pad for the open source movement, and consequently lead to great interest from academia and business alike Babak Kia Adjunct Professor Boston University 2 College of Engineering Email: bkia -at- bu.edu ENG SC757 - Advanced Microprocessor Design What is Linux? Why Linux? z Linux is free open source operating system which z Due to its open source nature, Linux has a highly is fully featured, portable, and extremely versatile qualified code base z It runs on everything from PDAs to the largest z The Kernel can be very small, it could fit onto a single Mainframes 1.4MB floppy disk drive, while including all the fundamental operating system tasks! z Unlike traditional proprietary software, Linux is z It is highly portable, it is available for almost every developed by a multitude of developers across microprocessor system in existence today the world z It is highly supported, it draws on the open source z People often (and mistakenly) use the term Linux community across the globe for both development and to refer to one of three disparate concepts: support • A Linux Distribution z It supports a multi-user environment with a built in • A Linux System capability to concurrently execute applications belonging to 2 or more users • The Linux Kernel z Supports multi-processor systems z Our focus is primarily on the Linux Kernel, and therefore the term Linux refers to the Kernel itself z Well documented. The source code is available! 3 4 What is uClinux What is a Linux Distribution? z uClinux is not Linux, it is a variant of it which runs z A Linux distribution is a collection of software on processors which lack memory management components, including the Linux Kernel itself, as z Without memory management, there is no well as the GNU toolchain (compiler, linker, etc.), differentiation between user space and kernel and a number of free and open source software space, and therefore all applications run at such as Emacs, X11, FTP, etc. Privilege Level 0 z There are many companies involved in creating z Without memory management, all code runs in a distributions, such as RedHat, SUSE, and flat memory space, and therefore doesn’t require Mandriva, and there are many community projects a virtual memory subsystem dedicated to creating distributions (or distros) such as Debian and Gentoo Linux z Therefore in this configuration all processes have direct access to memory and I/O resources, and z There are over 300 active Linux distribution device drivers are not necessary projects in existence today 5 6 1 Linux Distribution The Linux Kernel z Without distros, a person interested in Linux z The most important element of Embedded Linux would have install everything manually which is its core, called the Linux Kernel basically required a great expertise of the Unix z The Linux Kernel is maintained and distributed by Operating System Linus Trovalds, who initially wrote the Kernel z Distros therefore making the process of installing when he was a student at the University of Linux easier, they usually provide both binaries Helsinki and source, and are segmented into packages, z Unlike proprietary Operating Systems, its source each package providing one component of the code is available for anyone to freely use, system such as font, web browser, etc. distribute, or modify z Some popular Package Management Systems are: z The latest released version of the Linux Kernel is • RPM – The RPM package manager version 2.4, though development of the Linux • deb – The Debian package Kernel is of course ongoing and newer versions • tgz, or tar.gz – Archived tar and gzipped file, used to become available on a regular basis distribute simple hand made packages 7 8 The Linux Kernel GNU z Like any Operating System, the Linux Kernel is z GNU is an acronym for GNU’s Not Unix, and is responsible for managing resources (memory and pronounced guh-noo I/O), contains device drivers, networking stack, file z The GNU project was started in 1983 with the goal system, and performs other OS tasks of creating a UNIX flavored operating system which was freely distributable z Linux implements different privilege levels, where a module, which is a Kernel function runs in z GNU is not Linux! GNU is used in conjunction with the Linux kernel to form a completely kernel space (supervisor mode), and user operational Operating System. This GNU/Linux applications run in user space (user mode) combination (distribution) is often mistakenly z Linux can mange both multiple processes and called Linux multiple processors (symmetric multiprocessing, z Some software developed by the GNU project are: or SMP systems). As such, all kernel code is Bash (command shell), Emacs (text editor), gzip reentrant (data compression), and GNOME (graphical desktop environment) 9 10 General Public License General Public License z The GNU General Public License, or GPL as it is z The GPL has been at the center of controversy recently, otherwise known is the free software license under opponents of GPL often call it viral, implying that the which Linux is written and distributed license acts as a virus in that once it comes in contact z The GPL grants the recipient of a computer program the with proprietary code, then the proprietary code following rights: becomes GPL • The freedom to run the program for any purpose z This is an incorrect assessment as GPL simply requires • The freedom to study how the program works and to all copies of derived work to be GPL licensed modify it z In another example, in 2003 the SCO group sued IBM • The freedom to redistribute copies of the program claiming that the latter had contributed portions of • The freedom to improve the program, and to redistribute SCO’s copyrighted code to the Linux Kernel and went the improvements to the public further by threatening legal action against a number of z The GPL is in contrast to the end-user licenses that companies and demanding licensing fees from them plague proprietary software, which rarely grant the end- z To date, there is no proof to SCO’s claims of the use of user any rights copyrighted code 11 12 2 Other Licensing Models The Copyleft z GPL is not the only licensing model available z The right to redistribute GPL-based code is granted only if the licensee includes the source code in the z Some licenses such as BSD permit distribution of redistribution (including all modifications!) a modified BSD-based code as proprietary software z The redistributed copies themselves are required to include and be licensed under GPL in a mechanism z The difference between GPL and BSD licenses is known as copyleft legal mechanism known as copyleft, invented by z Copyleft actually derives its legal impact from the fact Richard Stallman (initiator of GNU project and that the program is copyrighted! founder of Free Software Foundation) z Under a copyright, a licensee does not have the right to z Copyleft requires that derivative works of a GPL- modify or redistribute the code unless under the terms licensed application also be covered by the GLP outlined in copyleft license z Therefore copyleft uses copyright law to accomplish an almost opposite effect – granting modification and redistribution rights 13 14 The GNU Toolchain The GNU Toolchain z Linux relies on the GNU development z The GNU toolchain is an overall term given to the toolchain series of programming tools developed by the GNU project z A toolchain is series of programming z The projects include: tools (assembler, compiler, linker, etc.) • GNU make – Build and compilation automation which are used to create another • GNU Compiler Collection (GCC) – Compilers for computer program several programming languages • GNU Binutils – Linker, assembler, and other tools z The tools are used sequentially, or in a • GNU Debugger (GDB) – Interactive debugger chain, in such a way that the output of z Other related projects are: one program becomes the input of • GNU C Library – A standard C library another one, hence the term toolchain • CVS – Concurrent Version System 15 16 CVS CVS z The Concurrent Versions System z The way CVS works is as follows: implements a version control system to • Any number of clients (developers) can check- keep track of all the work and changes in out a full copy of a given project • One or more developers can work on the same a set of files copy of the code and then check-in their z This enables developers from across the modifications globe to collaborate on a project and as • The CVS server automatically attempts to merge the different changes such as become a popular component of • If it is unsuccessful, for example in the case the open-source development community where two developers are trying to modify the same line of code, it rejects the second developer from updating the code, and directs the two developers to merge the code manually 17 18 3 Developing a Linux System Starting up Linux z There are three basic setup mechanisms which z From system power up to the time the developers use to develop code for Linux system is up and running, there are three • The Permanent Link Setup is where the host and the distinct steps the must be completed target are permanently connected together via an Ethernet cable for example.
Load more

Recommended publications
  • Also Includes Slides and Contents From
    The Compilation Toolchain Cross-Compilation for Embedded Systems Prof. Andrea Marongiu ([email protected]) Toolchain The toolchain is a set of development tools used in association with source code or binaries generated from the source code • Enables development in a programming language (e.g., C/C++) • It is used for a lot of operations such as a) Compilation b) Preparing Libraries Most common toolchain is the c) Reading a binary file (or part of it) GNU toolchain which is part of d) Debugging the GNU project • Normally it contains a) Compiler : Generate object files from source code files b) Linker: Link object files together to build a binary file c) Library Archiver: To group a set of object files into a library file d) Debugger: To debug the binary file while running e) And other tools The GNU Toolchain GNU (GNU’s Not Unix) The GNU toolchain has played a vital role in the development of the Linux kernel, BSD, and software for embedded systems. The GNU project produced a set of programming tools. Parts of the toolchain we will use are: -gcc: (GNU Compiler Collection): suite of compilers for many programming languages -binutils: Suite of tools including linker (ld), assembler (gas) -gdb: Code debugging tool -libc: Subset of standard C library (assuming a C compiler). -bash: free Unix shell (Bourne-again shell). Default shell on GNU/Linux systems and Mac OSX. Also ported to Microsoft Windows. -make: automation tool for compilation and build Program development tools The process of converting source code to an executable binary image requires several steps, each with its own tool.
    [Show full text]
  • Riscv-Software-Stack-Tutorial-Hpca2015
    Software Tools Bootcamp RISC-V ISA Tutorial — HPCA-21 08 February 2015 Albert Ou UC Berkeley [email protected] Preliminaries To follow along, download these slides at http://riscv.org/tutorial-hpca2015.html 2 Preliminaries . Shell commands are prefixed by a “$” prompt. Due to time constraints, we will not be building everything from source in real-time. - Binaries have been prepared for you in the VM image. - Detailed build steps are documented here for completeness but are not necessary if using the VM. Interactive portions of this tutorial are denoted with: $ echo 'Hello world' . Also as a reminder, these slides are marked with an icon in the upper-right corner: 3 Software Stack . Many possible combinations (and growing) . But here we will focus on the most common workflows for RISC-V software development 4 Agenda 1. riscv-tools infrastructure 2. First Steps 3. Spike + Proxy Kernel 4. QEMU + Linux 5. Advanced Cross-Compiling 6. Yocto/OpenEmbedded 5 riscv-tools — Overview “Meta-repository” with Git submodules for every stable component of the RISC-V software toolchain Submodule Contents riscv-fesvr RISC-V Frontend Server riscv-isa-sim Functional ISA simulator (“Spike”) riscv-qemu Higher-performance ISA simulator riscv-gnu-toolchain binutils, gcc, newlib, glibc, Linux UAPI headers riscv-llvm LLVM, riscv-clang submodule riscv-pk RISC-V Proxy Kernel (riscv-linux) Linux/RISC-V kernel port riscv-tests ISA assembly tests, benchmark suite All listed submodules are hosted under the riscv GitHub organization: https://github.com/riscv 6 riscv-tools — Installation . Build riscv-gnu-toolchain (riscv*-*-elf / newlib target), riscv-fesvr, riscv-isa-sim, and riscv-pk: (pre-installed in VM) $ git clone https://github.com/riscv/riscv-tools $ cd riscv-tools $ git submodule update --init --recursive $ export RISCV=<installation path> $ export PATH=${PATH}:${RISCV}/bin $ ./build.sh .
    [Show full text]
  • Operating Systems and Applications for Embedded Systems >>> Toolchains
    >>> Operating Systems And Applications For Embedded Systems >>> Toolchains Name: Mariusz Naumowicz Date: 31 sierpnia 2018 [~]$ _ [1/19] >>> Plan 1. Toolchain Toolchain Main component of GNU toolchain C library Finding a toolchain 2. crosstool-NG crosstool-NG Installing Anatomy of a toolchain Information about cross-compiler Configruation Most interesting features Sysroot Other tools POSIX functions AP [~]$ _ [2/19] >>> Toolchain A toolchain is the set of tools that compiles source code into executables that can run on your target device, and includes a compiler, a linker, and run-time libraries. [1. Toolchain]$ _ [3/19] >>> Main component of GNU toolchain * Binutils: A set of binary utilities including the assembler, and the linker, ld. It is available at http://www.gnu.org/software/binutils/. * GNU Compiler Collection (GCC): These are the compilers for C and other languages which, depending on the version of GCC, include C++, Objective-C, Objective-C++, Java, Fortran, Ada, and Go. They all use a common back-end which produces assembler code which is fed to the GNU assembler. It is available at http://gcc.gnu.org/. * C library: A standardized API based on the POSIX specification which is the principle interface to the operating system kernel from applications. There are several C libraries to consider, see the following section. [1. Toolchain]$ _ [4/19] >>> C library * glibc: Available at http://www.gnu.org/software/libc. It is the standard GNU C library. It is big and, until recently, not very configurable, but it is the most complete implementation of the POSIX API. * eglibc: Available at http://www.eglibc.org/home.
    [Show full text]
  • A.5.1. Linux Programming and the GNU Toolchain
    Making the Transition to Linux A Guide to the Linux Command Line Interface for Students Joshua Glatt Making the Transition to Linux: A Guide to the Linux Command Line Interface for Students Joshua Glatt Copyright © 2008 Joshua Glatt Revision History Revision 1.31 14 Sept 2008 jg Various small but useful changes, preparing to revise section on vi Revision 1.30 10 Sept 2008 jg Revised further reading and suggestions, other revisions Revision 1.20 27 Aug 2008 jg Revised first chapter, other revisions Revision 1.10 20 Aug 2008 jg First major revision Revision 1.00 11 Aug 2008 jg First official release (w00t) Revision 0.95 06 Aug 2008 jg Second beta release Revision 0.90 01 Aug 2008 jg First beta release License This document is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License [http:// creativecommons.org/licenses/by-nc-sa/3.0/us/]. Legal Notice This document is distributed in the hope that it will be useful, but it is provided “as is” without express or implied warranty of any kind; without even the implied warranties of merchantability or fitness for a particular purpose. Although the author makes every effort to make this document as complete and as accurate as possible, the author assumes no responsibility for errors or omissions, nor does the author assume any liability whatsoever for incidental or consequential damages in connection with or arising out of the use of the information contained in this document. The author provides links to external websites for informational purposes only and is not responsible for the content of those websites.
    [Show full text]
  • Debian Med Integrated Software Environment for All Medical Purposes Based on Debian GNU/Linux
    Debian Med Integrated software environment for all medical purposes based on Debian GNU/Linux Andreas Tille Debian OSWC, Malaga 2008 1 / 18 Structure 1 What is Debian Med 2 Realisation 3 Debian Med for service providers 2 / 18 Motivation Free Software in medicine not widely established yet Some subareas well covered Medical data processing more than just practice and patient management Preclinical research of microbiology and genetics as well as medical imaging ! Pool of existing free medical software 3 / 18 Profile of the envisaged user Focus on medicine not computers Unreasonable effort to install upstream programs No interest in administration Interest reduced onto free medical software Easy usage Security and confidence Native-language documentation and interface 4 / 18 Customising Debian Debian > 20000 packages Focus on medical subset of those packages Packaging and integrating other medical software Easy installation and configuration Maintaining a general infrastructure for medical users General overview about free medical software Propagate the idea of Free Software in medicine Completely integrated into Debian - no fork 5 / 18 Special applications 6 / 18 Basic ideas Do not make a separate distribution but make Debian fit for medical care No development of medical software - just smooth integration of third-party software Debian-Developer = missing link between upstream author and user 7 / 18 Debian - adaptable for any purpose? Developed by more than 1000 volunteers Flexible, not bound on commercial interest Strict rules (policy) glue all things together Common interest of each individual developer: Get the best operating system for himself. Some developers work in the field of medicine In contrast to employees of companies every single Debian developer has the freedom and ability to realize his vision Every developer is able to influence the development of Debian - he just has to do it.
    [Show full text]
  • Annual Report
    [Credits] Licensed under Creative Commons Attribution license (CC BY 4.0). All text by John Hsieh and Georgia Young, except the Letter from the Executive Director, which is by John Sullivan. Images (name, license, and page location): Wouter Velhelst: cover image; Kori Feener, CC BY-SA 4.0: inside front cover, 2-4, 8, 14-15, 20-21, 23-25, 27-29, 32-33, 36, 40-41; Michele Kowal: 5; Anonymous, CC BY 3.0: 7, 16, 17; Ruben Rodriguez, CC BY-SA 4.0: 10, 13, 34-35; Anonymous, All rights reserved: 16 (top left); Pablo Marinero & Cecilia e. Camero, CC BY 3.0: 17; Free This report highlights activities Software Foundation, CC BY-SA 4.0: 18-19; Tracey Hughes, CC BY-SA 4.0: 30; Jose Cleto Hernandez Munoz, CC BY-SA 3.0: 31, Pixabay/stevepb, CC0: 37. and detailed financials for Fiscal Year 2016 Fonts: Letter Gothic by Roger Roberson; Orator by John Scheppler; Oswald by (October 1, 2015 - September 30, 2016) Vernon Adams, under the OFL; Seravek by Eric Olson; Jura by Daniel Johnson. Created using Inkscape, GIMP, and PDFsam. Designer: Tammy from Creative Joe. 1] LETTER FROM THE EXECUTIVE DIRECTOR 2] OUR MISSION 3] TECH 4] CAMPAIGNS 5] LIBREPLANET 2016 6] LICENSING & COMPLIANCE 7] CONFERENCES & EVENTS 7 8] LEADERSHIP & STAFF [CONTENTS] 9] FINANCIALS 9 10] OUR DONORS CONTENTS our most important [1] measure of success is support for the ideals of LETTER FROM free software... THE EXECUTIVE we have momentum DIRECTOR on our side. LETTER FROM THE 2016 EXECUTIVE DIRECTOR DEAR SUPPORTERS For almost 32 years, the FSF has inspired people around the Charity Navigator gave the FSF its highest rating — four stars — world to be passionate about computer user freedom as an ethical with an overall score of 99.57/100 and a perfect 100 in the issue, and provided vital tools to make the world a better place.
    [Show full text]
  • GNU Toolchain for Atmel ARM Embedded Processors
    RELEASE NOTES GNU Toolchain for Atmel ARM Embedded Processors Introduction The Atmel ARM GNU Toolchain (5.3.1.487) supports Atmel ARM® devices. The ARM toolchain is based on the free and open-source GCC. This toolchain is built from sources published by ARM's "GNU Tools for ARM Embedded Processors" project at launchpad.net (https://launchpad.net/gcc-arm-embedded). The toolchain includes compiler, assembler, linker, binutils (GCC and binutils), GNU Debugger (GDB with builtin simulator) and Standard C library (newlib, newlib nano). 42368A-MCU-06/2016 Table of Contents Introduction .................................................................................... 1 1. Supported Configuration ......................................................... 3 1.1. Supported Hosts ................................................................... 3 1.2. Supported Targets ................................................................. 3 2. Downloading, Installing, and Upgrading ................................. 4 2.1. Downloading/Installing on Windows .......................................... 4 2.2. Downloading/Installing on Linux ............................................... 4 2.3. Downloading/Installing on Mac OS ........................................... 4 2.4. Upgrading ............................................................................ 4 3. Layout and Components ......................................................... 5 3.1. Layout ................................................................................. 5 3.2. Components
    [Show full text]
  • The GNU Toolchain for ARM Targets HOWTO Wookey Chris Rutter Jeff Sutherland Paul Webb
    This chapter contains information on building a GNU toolchain for ARM targets. The GNU Toolchain for ARM targets HOWTO Wookey Chris Rutter Jeff Sutherland Paul Webb This document contains information on setting up a GNU toolchain for ARM targets. It details both some pre-compiled toolchains which you can install, and how to compile your own toolchain, as either a native or a cross-compiler. 1. Credits This document is based on the work of Chris Rutter (now, sadly, deceased) who’s ’Building the GNU toolchain for ARM targets’ document was gospel for some time. It eventually became out of date so Wookey (<[email protected]>) updated it and gave it a substantion rewrite, adding the pre-built toolchain info at the same time. Paul Webb (<[email protected]>) did the initial conversion to DocBook, Phil 1 The GNU Toolchain for ARM targets HOWTO Blundell (<[email protected]>) provided info on the current state of the art and comments on the draft. Jeff Sutherland (<[email protected]>) then fixed the bits that were still wrong, and now maintains the doc, along with Wookey. Thanx to all. As well as being on-line as a stand-alone HOWTO, this document is also available as a chapter of the book: A ’Guide to ARMLinux for Developers’ (http://www.aleph1.co.uk/armlinux/thebook.html) 2 This chapter contains information on building a GNU toolchain for ARM targets. 1. Toolchain overview The toolchain actually consists of a number of components. The main one is the compiler itself gcc, which can be native to the host or a cross-compiler.
    [Show full text]
  • GNU Texmacs User Manual Joris Van Der Hoeven
    GNU TeXmacs User Manual Joris van der Hoeven To cite this version: Joris van der Hoeven. GNU TeXmacs User Manual. 2013. hal-00785535 HAL Id: hal-00785535 https://hal.archives-ouvertes.fr/hal-00785535 Preprint submitted on 6 Feb 2013 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. GNU TEXMACS user manual Joris van der Hoeven & others Table of contents 1. Getting started ...................................... 11 1.1. Conventionsforthismanual . .......... 11 Menuentries ..................................... 11 Keyboardmodifiers ................................. 11 Keyboardshortcuts ................................ 11 Specialkeys ..................................... 11 1.2. Configuring TEXMACS ..................................... 12 1.3. Creating, saving and loading documents . ............ 12 1.4. Printingdocuments .............................. ........ 13 2. Writing simple documents ............................. 15 2.1. Generalities for typing text . ........... 15 2.2. Typingstructuredtext ........................... ......... 15 2.3. Content-basedtags
    [Show full text]
  • Introduction to Autotools
    Introduction to Autotools July 8, 2007 Jim Huang (jserv) <[email protected]> Overview ● Autoconf, Automake, and libtool working together ● Address portability, configuration needs ● Support GNU Coding Standards ● Provide consistent user experience ● Very popular in Free/Open Source World The Bad Old Days ● 1990 ● Edit Makefile ● Edit source ● Build ● No ªmake installº Handy Quote It it easier to write a portable shell than to write a portable shell script. -- Larry Wall Useful tools ● colormake – make with colorful decoration ● remake – modified version of GNU make with debugging and tracing support TheThe realreal ProblemProblem How do we handle platform specific issues? Providing a different Makefile for each architecture Using Autoconf, Automake and Libtool The installer needs only Bourne shell C compilers Make program SomeSome advantagesadvantages whenwhen usingusing GNUGNU autotoolsautotools The installation of a program is straightforward: ./configure; make; make install This procedure checks for system parameters, libraries, location of programs, availability of functions and writes a Makefile ./configure supports many options to overwrite defaults settings Development Use Cases GNU toolchain flow (simplified) Developer User configure.in autoconf configure ./configure Check for required libraries automake Makefile.in Generate Makefile Makefile.am Makefile Autotools Overview (no libtool) Under source control Starting, Source [autoscan] [configure.scan] configure.ac occasional files configure.ac autoconf configure Developer,
    [Show full text]
  • GNU Toolchain for Atmel ARM Embedded Processors: 4.8.4.371
    RELEASE NOTES GNU Toolchain for Atmel ARM Embedded processors: 4.8.4.371 Introduction The ARM GNU Toolchain supports Atmel® ARM devices. The ARM toolchain is based on the free and open-source GCC. This toolchain is built from sources publlished by ARM's "GNU Tools for ARM Embedded Processors" project at launchpad.net (https://launchpad.net/gcc-arm-embedded). The toolchain includes compiler, assembler, linker, binutils (GCC and binutils), GNU Debugger (GDB with builtin simulator) and Standard C library (newlib, newlib nano). 42368-MCU-/ Table of Contents Introduction .................................................................................... 1 1. Supported configuration .......................................................... 3 1.1. Supported Hosts ................................................................... 3 1.2. Supported Targets ................................................................. 3 2. Downloading, Installing and Upgrading .................................. 4 2.1. Downloading/Installing on Windows .......................................... 4 2.2. Downloading/Installing on Linux ............................................... 4 2.3. Downloading/Installing on Mac OS ........................................... 4 2.4. Upgrading from previous versions ............................................ 4 3. Layout and Components ......................................................... 5 3.1. Layout ................................................................................. 5 3.2. Components ........................................................................
    [Show full text]
  • Linux Programming [R15a0527] Lecture Notes
    LINUX PROGRAMMING [R15A0527] LECTURE NOTES B.TECH IV YEAR – I SEM (R15) (2019-2020) DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING MALLA REDDY COLLEGE OF ENGINEERING & TECHNOLOGY (Autonomous Institution – UGC, Govt. of India) Recognized under 2(f) and 12 (B) of UGC ACT 1956 (Affiliated to JNTUH, Hyderabad, Approved by AICTE - Accredited by NBA & NAAC – ‘A’ Grade - ISO 9001:2015 Certified) Maisammaguda, Dhulapally (Post Via. Hakimpet), Secunderabad – 500100, Telangana State, India Syllabus (R15A0527) LINUX PROGRAMMING Objectives: • To develop the skills necessary for Unix systems programming including file system programming, process and signal management, and interprocess communication. • To make effective use of Unix utilities and Shell scripting language such as bash. • To develop the basic skills required to write network programs using Sockets. UNIT I Linux Utilities - File handling utilities, Security by file permissions, Process utilities, Disk utilities, Networking commands, Filters, Text processing utilities and Backup utilities. Sed- Scripts, Operation, Addresses, Commands, Applications, awk- Execution, Fields and Records, Scripts, Operation, Patterns, Actions, Associative Arrays, String and Mathematical functions, System commands in awk, Applications. Shell programming with Bourne again shell(bash) - Introduction, shell responsibilities, pipes and Redirection, here documents, running a shell script, the shell as a programming language, shell meta characters, file name substitution, shell variables, command substitution, shell
    [Show full text]