Week Eight AgendaAnnouncementsLink of the weekReview week seven lab assignmentThis week’s expected outcomesNext lab assignmentBreak-out problemsUpcoming deadlinesLab assistance, questions and answers
Link of the weekhttp://bhami.com/rosetta.htmlA Sys Admin's Unixersal Translator (ROSETTA
STONE) OR What do they call that in this world? Tasks OSsAdm. GUI AIXFile System A/UXKernel FreeBSDStart up scripts HP-UXCreate a file system LinuxMount CDROM NCR UnixAdd software Open BSD
Mac OS X
Link of the weekhttp://support.apple.com/kb/HT1148?viewlocale=en_USSoftware Installation Quick Assist for Mac OS Xis a great toolbox that organizes and supports your
software collection.
Link of the week
Open Source Projectshttp://sourceforge.nethttp://freshmeat.net
Lab Assignment 13-1 Public Domain/Open Software Evaluation is due December 12, 2010.Requirements:
APA Style formatCover sheet (course, instructor name, topic)Three typed pages of information (min)Reference page
Link of the week
Lab Assignment 13-1 Public Domain/Open Software Evaluation
Bulletin Board: Open Source Presentation Sign UpNo two presentations shall be the same.
Lab assignment grade components.Paper: 0 – 75 pointsPresentation 0 – 25 points
Presentation dates: December 7 (week 14)December 14 ( week 15)
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 assignmentinodeThe inode data structure
file mode – file permissions (rwx)count of hard links – how many hard links
point to the inodefile type – executable, block specialowner idgroup idtime of last file access - timestamptime of last file modification - timestampfile size - bytesfile addresses – addresses of the blocks of
storage containing the files data on a HDD
Review week seven lab assignment
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
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 assignment
Review week seven lab assignmentDefine: 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.dlrwxrwxrwx 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: ln <original file name> <new file name>-rwx------ 2 dandrear faculty 318 Jun 14 21:03 prog1-rwx------ 2 dandrear faculty 318 Jun 14 21:03 prog2
Review week seven lab assignmentDefine: tar
tar –cf newpack.tar /export/home/dandrear
tar –xvf origpack.tartar –tvf origpack.tar
Define: gzipgzip filename.targzip –d filename.tar.gzgunzip filename.tar.gz
Define: bzip2/bunzip2ipbzip2 filename.tarbunzip2 filename.tar.bx2
Review week seven lab assignmentInstalling 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 assignmentDefinition: Installation of computer programs.Installation process:
- Condensed package- Unpack package- Customized package- Test the functionality of the system- Configure files
Review week seven lab assignmentTwo 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 assignment2. Install from source code
Allows for custom installationsAllows for code modificationsOptimum compilation for target
platform
Review week seven lab assignmentrpm is a tool
rpm –q sloccount (query to see if tool exists)
If the tool isn’t on your system, create a directory named sloccountDownload name sloccount-2.23-
1.i386.rpmrpm –vUh sloccount-2.23-1.i386.rpm (install tool)
See the man page regarding the rpm tool
Review week seven lab assignmentQUERYING 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 assignmentSoftware 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 assignmentSoftware releases
What are you normally installing?
Interfaces – normally remain the constant.Implementations – actual fixesBehaviors – system changes from one
implementation to another
Review week seven lab assignmentKernel 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 assignmentUNIX/Linux Turnable Parameters
Number of users on a systemMaximum database sizeNumber of global buffersNumber 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 assignment
Buffer cacheAmount 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 outcomesUpon 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 Assignmentfsck
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 -AWalk 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 AssignmentThe 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 Assignment/etc/fstab/dev/vg00/root / ext3 defaults 1 1LABEL=/boot /boot ext3 defaults 1 2none /dev/pts devpts gid=5,mode=620 0 0/dev/vg00/home /home ext3 defaults 1 2/dev/vg00/opt /opt ext3 defaults 1 2none /proc proc defaults 0 0none /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/sysconfigauthconfig gpm ip6tables-config netdump_id_dsa
rawdevicesautofs grub iptables-config netdump_id_dsa.pub
rhnclock harddisks irqbalance apm-scripts
devlabel.d installinfo netdump prelinknetwork sendmailconsole hwconf keyboard networking
syslogcrond i18n kudzu network-scripts
sysstatdevlabel init mouse ntpd xinetd
Next Lab Assignment# inittab This file describes how the INIT process should set
up the system in a certain run-level.# Author: Miquel van Smoorenburg,
[email protected]# Default runlevel. The runlevels used by RHS are:# 0 - halt (Do NOT set initdefault to this)# 1 - Single user mode# 2 - Multiuser, without NFS (The same as 3, if you do not have
networking)# 3 - Full multiuser mode# 4 - unused# 5 - X11# 6 - reboot (Do NOT set initdefault to this)#
Next Lab Assignmentid:3:initdefault:
# System initialization.si::sysinit:/etc/rc.d/rc.sysinit
l0:0:wait:/etc/rc.d/rc 0l1:1:wait:/etc/rc.d/rc 1l2:2:wait:/etc/rc.d/rc 2l3:3:wait:/etc/rc.d/rc 3l4:4:wait:/etc/rc.d/rc 4l5:5:wait:/etc/rc.d/rc 5l6:6:wait:/etc/rc.d/rc 6
Next Lab Assignment# Trap CTRL-ALT-DELETEca::ctrlaltdel:/sbin/shutdown -t3 -r now
# When our UPS tells us power has failed, assume we have a few minutes
# of power left. Schedule a shutdown for 2 minutes from now.
# This does, of course, assume you have powerd installed and your
# UPS connected and working correctly.pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure;
System Shutting Down"
Next Lab Assignment# If power was restored before the shutdown kicked in,
cancel it.pr:12345:powerokwait:/sbin/shutdown -c "Power
Restored; Shutdown Cancelled“
Next Lab Assignment# Run gettys in standard runlevels1:2345:respawn:/sbin/mingetty tty12:2345:respawn:/sbin/mingetty tty23:2345:respawn:/sbin/mingetty tty3###4:2345:respawn:/sbin/mingetty tty4###5:2345:respawn:/sbin/mingetty tty5###6:2345:respawn:/sbin/mingetty tty6
# Run xdm in runlevel 5x:5:respawn:/etc/X11/prefdm -nodaemon
Next Lab Assignment/etc/rc.d/rc_sysinit
• Possibly run fsck on “/”. If the root file system wasn’t unmounted properly, it could be corrupted.
• Remount the root file system (read/write mode).• Run fsck on other file systems, then mount them as
per /etc/fstab• Save the kernel ring buffer. Use dmesg >
/var/log/dmesg_output• It might be necessary to load kernel modules with
modprobe
Next Lab AssignmentThe Installation Exercise is an exercise that requires
following directions. Perform each step in the prescribed sequence and using the installation syntaxfrom this slide presentation.
Create an ASCII file named 4th_log.txtCreate the following directory
/$HOME/itec400/homework/4th
Download the programming language “forth”
Copy compressed “tar” file to your 4th directorycd /$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 AssignmentGrading 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
Break-out problems1. Process ID2. User ID3. fsck4. /etc/fstab5. Turnable parameters6. Multiuser runlevel (Linux)7. /boot/vmlinuz-*8. Single user mode9. /var/mail/dandrear10. inode11. ASCII12. crond13. shared memory14. semaphore15. /etc/sysconfig
Upcoming deadlines• Lab Assignment 6-1, Programming
Assignment I is due October 31, 2010.• Lab Assignment 8-1, Installation Exercise is
due November 7, 2010.• Lab Assignment 8-1, Startup/Shutdown is due
November 14.• Module 4 is for weeks 6, 7, and 8.• Thanksgiving November 25, 2010.
Upcoming deadlinesDemonstrate Power Point Presentation
Summer2010 Face to Face: Wireshark
Summer2010 Online Unix: Secret Maryo
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