Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems.

Slides:



Advertisements
Similar presentations
Basic Unix system administration
Advertisements

Week Nine Agenda Announcements Link of the week Review week eighth lab assignment Week nine expected outcomes Next lab assignment Break-out problems Upcoming.
Linux Booting Procedure
Linux can be generally divided into four major components: 1. KERNEL – OS, ultimate boss The kernel is the core program that runs programs and manages.
Introduction to Unix (CA263) File System
Exploring the UNIX File System and File Security
Guide To UNIX Using Linux Third Edition
Linux+ Guide to Linux Certification Chapter 12 Compression, System Backup, and Software Installation.
Linux+ Guide to Linux Certification, Third Edition Chapter 11 Compression, System Backup, and Software Installation.
Operating Systems Concepts 1. A Computer Model An operating system has to deal with the fact that a computer is made up of a CPU, random access memory.
File System and Directory Structure in Linux. What is File System In a computer, a file system is the way in which files are named and where they are.
Chapter 11 Compression, System Backup, and Software Installation.
Chapter 3.1:Operating Systems Concepts 1. A Computer Model An operating system has to deal with the fact that a computer is made up of a CPU, random access.
Linux Operations and Administration
Linux+ Guide to Linux Certification Chapter Three Linux Installation and Usage.
Guide To UNIX Using Linux Fourth Edition
Booting and boot levels
Linux+ Guide to Linux Certification
Lesson 7-Creating and Changing Directories. Overview Using directories to create order. Managing files in directories. Using pathnames to manage files.
Offline File Storage. Module 12 Offline File Storage ♦ Introduction Backup is usually done by first collecting all the data in a single archive file,
Guide to Linux Installation and Administration, 2e1 Chapter 3 Installing Linux.
Agenda Midterm Exam Issues Link of the Week This Week’s Expected Outcomes Review for midterm exam Moving around in UNIX Break-Out Problems Upcoming Deadlines.
Guide to Linux Installation and Administration, 2e1 Chapter 8 Basic Administration Tasks.
Week Nine Agenda Announcements Final exam will be longer, and more specific Document your text files (4 th _log.txt, startup.txt) Link of the week Review.
Week Nine Agenda Announcements Link of the week Review week eighth lab assignment Week nine expected outcomes Next lab assignment Break-out problems Upcoming.
Week Seven Agenda Announcements Link of the week Review week six lab assignment This week’s expected outcomes Next lab assignment Break-out problems Upcoming.
Week Seven Agenda Announcements Link of the week Review week six lab assignment This week’s expected outcomes Next lab assignment Break-out problems Upcoming.
Week Eight Agenda Announcements Link of the week Display inode information This week’s expected outcomes Next lab assignment Break-out problems Upcoming.
Chapter Two Exploring the UNIX File System and File Security.
1 Objectives Manage and install new file systems.
Week Eight Agenda Announcements Link of the week Display inode information This week’s expected outcomes Next lab assignment Break-out problems Upcoming.
Agenda Link of the week Use of Virtual Machine Review week one lab assignment This week’s expected outcomes Review next lab assignments Break Out Problems.
Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Upcoming deadlines.
Guide to Linux Installation and Administration1 Chapter 4 Running a Linux System.
Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems.
Week Six Agenda Announcements (in-class question) Link of the week Review week four lab assignment This week’s expected outcomes Next lab assignment Review.
Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems.
Chapter Two Exploring the UNIX File System and File Security.
Creating and Managing File Systems. Module 5 – Creating and Managing File Systems ♦ Overview This module deals with the structure of the file system,
Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems.
Linux+ Guide to Linux Certification, Third Edition
System Administration – Part 2. Devices in UNIX are files: A device can be accessed with different file names All device files are stored in /dev or its.
Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems.
Week Two Agenda Announcements Link of the week Use of Virtual Machine Review week one lab assignment This week’s expected outcomes Next lab assignments.
Week Nine Agenda Announcements Final exam will be longer, and more specific Document your text files (4 th _log.txt, startup.txt) Link of the week Review.
Week Nine Agenda Link of the week Review week eighth lab assignment Week nine expected outcomes Next lab assignment Break-out problems Upcoming deadlines.
Week Eight Agenda Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems Upcoming deadlines.
Lecture 02 File and File system. Topics Describe the layout of a Linux file system Display and set paths Describe the most important files, including.
Week Eight Agenda Announcements Link of the week Display inode information This week’s expected outcomes Next lab assignment Break-out problems Upcoming.
Week Seven Agenda Announcements Link of the week Review week six lab assignment This week’s expected outcomes Next lab assignment Break-out problems Upcoming.
Week Seven Agenda Announcements Link of the week Review week six lab assignment This week’s expected outcomes Next lab assignment Upcoming deadlines Lab.
Basic UNIX system administration CS 2204 Class meeting 14 *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright
Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems.
Week Nine Agenda Announcements Final exam will be longer, and more specific Document your text files (4 th _log.txt, startup.txt) Link of the week Review.
Week Seven Agenda Link of the week Review week six lab assignment This week’s expected outcomes Next lab assignment Break-out problems Upcoming deadlines.
Week Nine Agenda Announcements Final exam will be longer, and more specific Document your text files (4 th _log.txt, startup.txt) Link of the week Review.
Week Eight Agenda Announcements Link of the week
Guide to Linux Installation and Administration, 2e
Week Nine Agenda Announcements Link of the week
ITEC400 Week Seven Instructor Professor D’Andrea.
Week Nine Agenda Announcements
Week Seven Agenda Announcements Link of the week
Operation System Program 4
Exploring the UNIX File System and File Security
IS3440 Linux Security Unit 7 Securing the Linux Kernel
Presentation transcript:

Week Eight Agenda Announcements Link of the week Review week seven lab assignment This week’s expected outcomes Next lab assignment Break-out problems Upcoming deadlines Lab assistance, questions and answers

Link of the week A Sys Admin's Unixersal Translator (ROSETTA STONE) OR What do they call that in this world? Tasks OSs Adm. GUIAIX File SystemA/UX KernelFreeBSD Start up scriptsHP-UX Create a file systemLinux Mount CDROMNCR Unix Add softwareOpen BSD

Link of the week Software Installation Quick Assist for Mac OS X is a great toolbox that organizes and supports your software collection.

Link of the week Open Source Projects Lab Assignment 13-1 Public Domain/Open Software Evaluation is due December 13. Requirements: APA Style format Cover sheet Three typed pages of information Reference page

Link of the week Lab Assignment 13-1 Public Domain/Open Software Evaluation Bulletin Board: Open Source Presentation Sign Up No two presentations shall be the same. Lab assignment grade components. Paper: 0 – 75 points Presentation 0 – 25 points Presentation dates: November 30 (week 13) December 7 ( week 14)

Review week seven lab assignment Define: Data structure is where information is stored/collected in one place. The stored information may or may not be related. Data structures are unique in their construction so as to deliver a specific usage. Commonly data structures are arrays, hash tables, stacks, and queues.

Review week seven lab assignment inode The inode data structure file mode – file permissions (rwx) count of hard links – how many hard links point to the inode file type – executable, block special owner id group id time of last file access - timestamp time of last file modification - timestamp file size - bytes file addresses – addresses of the blocks of storage containing the files data on a HDD

Review week seven lab assignment

The directory maps file names to inodes. Each file has one inode. The number of inodes is a kernel parameter value set manually or dynamically by the operating system. Each file may have more than one directory entry. Inodes contain a list of disk block addresses. All inodes are data structures

Review week seven lab assignment

When there are multiple hard links, more directory entries point to the same inode (same file name) An inode can only hold a fixed number of direct data block addresses (10 for Linux). Large files use indirect block addresses. The inode keeps a count of the number of hard links that point to it. Deleting a file deletes and entry from a directory. If the number of hard links is 1, removing or deleting that file will also delete the inode.

Review week seven lab assignment

Define: A symbolic link is a link to a directory or to a file in a different file system. A symbolic path indicating the abstract location of another file. ln –s lrwxrwxrwx 1 root root 10 Jun rc0.d -> rc.d/rc0.d lrwxrwxrwx 1 root root 10 Jun rc1.d -> rc.d/rc1.d Define: A physical link (hard) refers to the specific location of physical data. ln prog1 prog2 -rwx dandrear faculty 318 Jun 14 21:03 prog1 -rwx dandrear faculty 318 Jun 14 21:03 prog2

Review week seven lab assignment Define: tar tar –cf newpack.tar /export/home/dandrear tar –xvf origpack.tar tar –tvf origpack.tar Define: gzip gzip filename.tar gzip –d filename.tar.gz gunzip filename.tar.gz Define: bzip2/bunzip2ip bzip2 filename.tar bunzip2 filename.tar.bx2

Review week seven lab assignment Installing the software package Package FreeBSD Port Usually, the source files are packaged in a compressed archive file (.tar.gz). After downloading, the.tar.gz file, use the tar tool to uncompress the un-package the source files.

Review week seven lab assignment Definition: Installation (computer programs) Installation process: - Condensed package - Unpack package - Customized package - Test the functionality of the system - Configure files

Review week seven lab assignment Two choices for installing a project 1. Install binaries from a package called “rpm” in Red Hat. rpm checks for dependencies and conflicts with other installed packages on the system.

Review week seven lab assignment 2. Install from source code Allows for custom installations Allows for code modifications Optimum compilation for target platform

Review week seven lab assignment rpm is a tool rpm –q sloccount (query to see if tool exists) If the tool isn’t on your system, create a directory named sloccount Download name sloccount i386.rpm rpm –vUh sloccount i386.rpm (install tool) See the man page regarding the rpm tool

Review week seven lab assignment QUERYING AND VERIFYING PACKAGES: rpm {-q|--query} [select-options] [query-options] rpm {-V|--verify} [select-options] [verify-options] rpm --import PUBKEY... rpm {-K|--checksig} [--nosignature] [--nodigest] PACKAGE_FILE... INSTALLING, UPGRADING, AND REMOVING PACKAGES: rpm {-i|--install} [install-options] PACKAGE_FILE... rpm {-U|--upgrade} [install-options] PACKAGE_FILE... rpm {-F|--freshen} [install-options] PACKAGE_FILE... rpm {-e|--erase} [--allmatches] [--nodeps] [--noscripts] [--notriggers] [--repackage] [--test] PACKAGE_NAME...

Review week seven lab assignment Software Installation of UNIX/Linux typically goes something like this: Download the software, which might be distributed in source code format, or as a binary. Unpack the software from its distribution format (typically a tarball compressed with compress, gzip, or bzip2 Locate the documentation (perhaps an INSTALL or README file, or some files in a doc/ subdirectory) and read up on how to install the software. If the software was distributed in source format, compile it. This may involve editing a makefile, or running a configure script, and other work. Test and install the software.

Review week seven lab assignment Kernel is the central component of most operating systems. It’s responsibility is to manage the system’s resources and communicate between the hardware and software. Kernel space is allocated for the kernel. Users aren’t able to access this area. Kernel space is generally larger than user space. User space is a memory area where all user mode applications are performed. This memory area is swappable if necessary.

Review week seven lab assignment Turnable Parameters Unix/Linux kernel semmni, semmns, and semmsl reflect the number of semaphores per set/Cache uses shmmax, shmmni, shmseg, and shmall reflect shared memory allocation maxusers, pt_cnt, use_mxcc_prefetch Example of semaphore. train track

Review week seven lab assignment File Systems (CDFS, MEMFS, NAMEFS, NFS, SFS, S5, UFS, VXFS) Buffer cache Amount of memory used to transfer a file system data structure such as inodes, direct blocks, indirect blocks, and cylinder groups.

Review week seven lab assignment Software releases Interfaces – normally remain the constant. Implementations – actual fixes Behaviors – system changes from one implementation to another

Week eighth expected outcomes Upon successful completion of this module, the student will be able to: Create make file scripts for software programs. Use pattern rules in make files. Create an effective PowerPoint presentation. Create make files with multiple targets. Install software packages on a server.

Next Lab Assignment fsck fsck is used to check and optionally repair one or more Linux file systems. If no filesystems are specified on the command line, and the -A option is not specified, fsck will default to checking filesystems in /etc/fstab serial. fsck -A Walk through the /etc/fstab file and trys to check all file systems in one run. This option is typically used from the /etc/rc system initialization file, instead of multiple commands for checking a single file system.

Next Lab Assignment The exit code returned by fsck is the sum of the following conditions: 0 - No errors 1 - File system errors corrected 2 - System should be rebooted 4 - File system errors left uncorrected 8 - Operational error 16 - Usage or syntax error 32 - fsck canceled by user request Shared library error

Next Lab Assignment /etc/fstab /dev/vg00/root / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode= /dev/vg00/home /home ext3 defaults 1 2 /dev/vg00/opt /opt ext3 defaults 1 2 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/vg00/tmp /tmp ext3 defaults 1 2 /dev/vg00/usr /usr ext3 defaults 1 2 /dev/vg00/var /var ext3 defaults 1 2 /dev/vg00/swap swap swap defaults 0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0 /mnt/floppy auto noauto,owner,kudzu 0 0 /dev/vg02/shome /export/home ext3 defaults,acl 1 2 #/dev/vg01/oracle /mnt/pkg1/orac ext3 noauto 1 2

Next Lab Assignment /etc/sysconfig authconfig gpm ip6tables-config netdump_id_dsa rawdevices autofs grub iptables-config netdump_id_dsa.pub rhn clock harddisks irqbalance apm-scripts devlabel.d installinfo netdump prelink network sendmail console hwconf keyboard networking syslog crond i18n kudzu network-scripts sysstat devlabel init mouse ntpd xinetd

Next Lab Assignment The Installation Exercise is an exercise that requires following directions. Perform each step in the prescribed sequence and syntax. Create an ASCII file named 4 th _log.txt Create the following directory /$HOME/itec400/homework/4 th Download the programming language “forth” Copy compressed “tar” file to your 4 th directory cd /$HOME/itec400/homework/4 th cp ~dandrear/public_html/itec400/Misc/4th-3.3d2-unix.tar.gz. The expected output is an executable file called “4 th ”.

Next Lab Assignment Grading Criteria The size of the file “readme.txt” is recorded in “4th_log” : 0 – 15 points The prerequisites for the target ‘4th’ are recorded in “4th_log”: 0 – 15 points The size of the executable named “4th”, in bytes, is recorded in “4th_log”: 0 – 20 points

Next Lab Assignment Demonstrate Power Point Presentation

Break-out problems rpm BIOS fsck /etc/fstab Turnable parameters Multiuser runlevel (Linux) Virtual memory /boot/vmlinuz-* Single user mode Paging inode ASCII FreeBSD software shared memory semaphore /etc/sysconfig

Upcoming deadlines Lab Assignment 6-1 is due November 1, Lab Assignment 8-1 is due November 8, Lab Assignment 9-1 is due November 15, Lab Assignment 10-1 is due November 22, Lab Assignment 10-2 is due November 22, Lab Assignment 13-1 is due December 13, 2009.

Questions and answers Questions Comments Concerns I am available after this Franklin Live session to discuss any problems and/or concerns regarding the lab assignments