Week eight agenda
This presentation is the property of its rightful owner.
Sponsored Links
1 / 37

Week Eight Agenda PowerPoint PPT Presentation


  • 77 Views
  • Uploaded on
  • Presentation posted in: General

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. http://bhami.com/rosetta.html

Download Presentation

Week Eight Agenda

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Week eight agenda

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

Link of the week

http://bhami.com/rosetta.html

A Sys Admin's Unixersal Translator (ROSETTA STONE) OR   What do they call that in this world?

TasksOSs

Adm. GUIAIX

File SystemA/UX

KernelFreeBSD

Start up scriptsHP-UX

Create a file systemLinux

Mount CDROMNCR Unix

Add softwareOpen BSD

Mac OS X


Link of the week1

Link of the week

http://support.apple.com/kb/HT1148?viewlocale=en_US

Software Installation Quick Assist for Mac OS X

is a great toolbox that organizes and supports your software collection.


Link of the week2

Link of the week

Open Source Projects

http://sourceforge.net

http://freshmeat.net

Lab Assignment 13-1 Public Domain/Open Software Evaluation is due April 11, 2010.

Requirements:

APA Style format

Cover sheet (course, instructor name, topic)

Three typed pages of information (min)

Reference page


Link of the week3

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:

April 5 (week 14)

April 12 ( week 15)


Review week seven lab assignment

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 assignment1

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 assignment2

Review week seven lab assignment


Review week seven lab assignment3

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 assignment4

Review week seven lab assignment


Review week seven lab assignment5

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 an 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 assignment6

Review week seven lab assignment


Review week seven lab assignment7

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 indicates the abstract location of another file.

Command: ln–s <original file name> <new file name>

lrwxrwxrwx 1 root root 10 Jun 28 2005 rc0.d -> rc.d/rc0.d

lrwxrwxrwx 1 root root 10 Jun 28 2005 rc1.d -> rc.d/rc1.d

Define: A physical link (hard) refers to the specific location of physical data.

Command: lnprog1 prog2

-rwx------ 2 dandrear faculty 318 Jun 14 21:03 prog1

-rwx------ 2 dandrear faculty 318 Jun 14 21:03 prog2


Review week seven lab assignment8

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 assignment9

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 assignment10

Review week seven lab assignment

Definition: Installation of computer programs.

Installation process:

- Condensed package

- Unpack package

- Customized package

- Test the functionality of the system

- Configure files


Review week seven lab assignment11

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 assignment12

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 assignment13

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-2.23-1.i386.rpm

rpm –vUh sloccount-2.23-1.i386.rpm (install tool)

See the man page regarding the rpm tool


Review week seven lab assignment14

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 assignment15

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 assignment16

Review week seven lab assignment

Software releases

Interfaces – normally remain the constant.

Implementations – actual fixes

Behaviors – system changes from one implementation to another


Review week seven lab assignment17

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 assignment18

Review week seven lab assignment

Turnable Parameters

Unix/Linux kernel

Number of users on a system

Maximum database size

Number of global buffers

Number of semaphores (e.g. train track)

Set shared memory allocation

Display: Kernel Tunable Parameters are located under the /proc/sys directory.


Review week seven lab assignment19

Review week seven lab assignment

Different File Systems (CDFS, MEMFS, NAMEFS, NFS, SFS, S5, UFS, VXFS, ext3fs)

Buffer cache

Amount of memory used to transfer a file system data structure such as inodes, direct blocks, indirect blocks, and cylinder groups.

Initially, you want to set up the buffer cache large enough to handle an inode data structure.


Week eighth expected outcomes

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

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 tries to check all file systems in one run. This option is typically used by the /etc/rc system initialization file, instead of trying to use multiple commands for checking a single file system.


Next lab assignment1

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

128 - Shared library error


Next lab assignment2

Next Lab Assignment

/etc/fstab

/dev/vg00/root / ext3 defaults 1 1

LABEL=/boot /boot ext3 defaults 1 2

none /dev/pts devptsgid=5,mode=620 0 0

/dev/vg00/home /home ext3 defaults 1 2

/dev/vg00/opt /opt ext3 defaults 1 2

none /proc proc defaults 0 0

none /dev/shmtmpfs 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 swapswap defaults 0 0

/dev/cdrom /mnt/cdromudf,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 assignment3

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 assignment4

Next Lab Assignment

The Installation Exercise is an exercise that requires following directions. Perform each step in the prescribed sequence and using the installation syntax

from this slide presentation.

Create an ASCII file named 4th_log.txt

Create the following directory

/$HOME/itec400/homework/4th

Download the programming language “forth”

Copy compressed “tar” file to your 4th directory

cd /$HOME/itec400/homework/4th

cp ~dandrear/public_html/itec400/Misc/4th-3.3d2-unix.tar.gz .

The expected output is an executable file called “4th”.


Next lab assignment5

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 assignment6

Next Lab Assignment

Demonstrate Power Point Presentation

Fall2009, Power Point Presentations , seanPassword_Safe


Break out problems

Break-out problems

1. Process ID

2. User ID

3. fsck

4. /etc/fstab

5. Turnableparameters

6. Multiuser runlevel (Linux)

7. /boot/vmlinuz-*

8. Single user mode

9. /var/mail/dandrear

10. inode

11. ASCII

12. crond

13. shared memory

14. semaphore

15. /etc/sysconfig


Upcoming deadlines

Upcoming deadlines

  • Lab Assignment 6-1, Programming Assignment I is due February 28, 2010.

  • Lab Assignment 7-1, midterm exam will be administered from February 15 – 20.

  • Lab Assignment 8-1, Installation Exercise is due March 7, 2010.

  • Midterm outline is posted on the Bulletin Board.

  • Module 4 is for weeks 6,7, and 8.


Questions and answers

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


  • Login