DOCSLIB.ORG

Reading IBM® Standard Label Tapes Under UNIX

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Reading IBM® Standard Label Tapes Under UNIX NESUG 16 Posters PS006 Reading IBM® Standard Label tapes under UNIX Hugh Kawabata, Bristol-Myers Squibb Evangelito Gascon, Novartis ABSTRACT mainframe operating systems use this information when- ever files stored on tape are read; this information is One problem that many data centers that use UNIX sys- written when a file is written to the tape. tems have is the handling of IBM tapes (and cartridges). While there does exist hardware that will attach to UNIX Programs that can process this information on UNIX sys- systems and physically read IBM tapes, little processing tems are relatively rare. The program described here util- is done of any 'metadata' by the UNIX commands. This izes the information stored in these header and trailers to poster shows the use of SAS® to process such informa- generate the UNIX command to copy the files, converting tion. each record from EBCDIC (IBM’s character coding sys- tem) to ASCII (commonly used in UNIX). The informa- One of the advantages of IBM's standard label tapes is tion on the tape is used to construct the UNIX command that useful information (metadata) about the tape and the with the appropriate record size and block size options, files on the tape is stored in headers on the tape itself. and executes the UNIX system command. Every tape has a volume header, an 80-byte record that contains information about the tape. Each file also has a SAS PROGRAM header, two 80-byte records and a trailer, additional two 80-byte records. IBM mainframe operating systems use In this program, a SAS macro was written to utilize a 10- this information whenever files stored on tape are read; cartridge auto-loading cartridge reader. This macro, this information is written when a file is written to the readtape, is passed the number of cartridges to be read tape. (num_tapes). The program described here utilizes the information in %macro readtape(num_tapes); these headers and trailers to generate the UNIX command to copy the file, passing the record and block size infor- %doi=1%to&num_tapes; mation to the UNIX command, and executes the com- mand. Using a tape autoloader, this program allows mul- A message is displayed on the UNIX console, using the tiple tapes to be read without operator intervention. SAS system call, x, and the UNIX command, echo. INTRODUCTION x "echo Reading tape &i"; One problem that many data centers that use UNIX sys- Two SAS macro variables are assigned names for a log tems have is the handling of IBM tapes (and cartridges). file, to keep a log of what happened, and a label file, While there are hardware that will attach to UNIX sys- which contains the contents of the IBM standard label. tems and physically read IBM tapes, and UNIX systems Note the use of the SAS automatic variables, sysdate and have commands that allow such tapes to be used, little systime, which contain the system date and time, respec- processing is done of any “metadata” on the tape, such as tively. IBM’s standard labels. This short paper uses SAS to proc- %let log = readtape.&sysdate.. ess such information. &systime..log; %let lbl = readtape.&sysdate.. One of the advantages of IBM’s standard label tapes is &systime..lbl; that useful information (metadata) about the tape and the files on the tape is stored in headers on the tape itself (see The filename statement sets the handle “hdr” to a UNIX Figure 1). Every tape has a volume header, an 80-byte pipe pointing to the output of the UNIX dd command. record that contains information about the tape, the most The dd command here reads from the tape an 80-byte useful being the actual volume serial number (volser). record, converts them to ASCII and passes it to SAS; the Each file also has a header, a block of two 80-byte records command results is appended to the log file. and a trailer, another block of two 80-byte records. IBM Page 1 NESUG 16 Posters input @6 blksize $5. filename hdr pipe "dd if=/dev/rmt/0mn @11 lrecl $5. cbs=80 ibs=80 conv=ascii 2>>&log"; ; The options for this command that does this are typical of and the values are stored in SAS macro varibles. most UNIX systems: call symput ('blksize', if = the input file, /dev/rmt/0mn, on our server is the trim(left(blksize))); tape device call symput ('lrecl', cbs = conversion block size, in this case, 80 characters trim(left(lrecl))); ibs = input block size, in this case, 80 characters end; conv=ascii = specifies conversion to ASCII 2>>&log = redirects the output of the command to a Now the contents of the header records are stored in the file and the console label file. Now the tape header can be read in a SAS data step. And, file "&lbl" mod; since the UNIX dd command had already converted the put _infile_; data into ASCII, no conversion is necessary in the SAS run; input statement. The information that was read is now used to copy the file There are three types of header records, each of which onto the UNIX disk, using the UNIX dd command. The contain different information. The two that are of interest UNIX file will have a name consisting of the original here are the “header 1” record, which contain the dataset dsname, plus the volume serial number (volser) of the name, volume serial number and volume sequence num- tape. ber (and other information that is not used here). The sec- ond record is the “header 2” record, which contain the x "dd if=/dev/rmt/0mn ibs=&blksize block size and the record length of the dataset. cbs=&lrecl conv=ascii of=&dsname..&vol..raw 2>>&log"; In this program, the first four characters are read and the input line is held. If the dataset was large enough to span several tape vol- umes, the volume sequence number should also be used in data _null_; the dataset name, like this: infile hdr pad lrecl=80; input @1 hr $4. @; x "dd if=/dev/rmt/0mn ibs=&blksize cbs=&lrecl conv=ascii If a header 1 record is found (the record begins with the of=&dsname..&vol..&volseq..raw characters, “HDR1”), the information needed are read. 2>>&log"; if hr = 'HDR1' then do; If the data contains binary information, the ASCII conver- input @5 dsn $17. sion option should be removed and SAS informats used to @22 volser $6. convert selected fields as appropriate. The dd command @28 volseq $4. should then look like this: ; x "dd if=/dev/rmt/0mn bs=&blksize Now the values read are stored in SAS macro variables. of=&dsname..&vol..raw 2>>&log"; call symput ('dsname', The following data step reads the trailer record and ap- trim(left(dsname)) ); pends the trailer (EOF) records to the label file for docu- call symput ('vol', mentation purposes. trim(left(volser)) || trim(left(volseq)) ); filename eof pipe "dd end; if=/dev/rmt/0m cbs=80 ibs=80 conv=ascii 2>>&log"; If a header 2 record is found, the information from this record is read, data _null_; infile eof lrecl=80 pad; else if hr='HDR2' input; then do; file "&lbl" mod; put _infile_; Page 2 NESUG 16 Posters run; REFERENCES A message is then written to the UNIX console. Figure 1 is adapted from Gary DeWard Brown, System x "echo Finished tape &i"; 390 JCL, Fourth Edition, New York: Wiley, 1998. In our environment, the 10-cartridge auto-loader can be The use of pipes under UNIX in the filename statement is instructed to unload the cartridge and load the subsequent documented in SAS Companion for UNIX Environments: cartridge, with the following UNIX command: Language. x "mt -t /dev/rmt/0m offl"; ACKNOWLEDGEMENTS The do loop is now ended, and the macro is complete. SAS and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS %end; Institute in the USA and other countries. ® indicates USA registration. %mend; IBM is a registered trademark of the International Busi- With a 10-cartridge auto loader, this macro (with 10 as an ness Machines Corporation of Armonk, New York. argument) can read 10 tapes without operator interven- tion, except for the loading and unloading of the tape CONTACT INFORMATION magazine and the initial load of the first tape. %readtape(10); Comments and questions are welcomed, at: Hugh Kawabata CONCLUSION Pharmaceutical Research Institute Bristol-Myers Squibb This SAS program illustrates the flexibility of the SAS P.O. Box 4500 system in interacting with the computer operating system. Princeton, NJ 08543 We were able to process batches of cartridges from IBM 609-897-3695 (voice) facilities with significantly less labor. Using the same [email protected] techniques illustrated in this example, the data on the tapes could be read directly into SAS datasets. Page 3 NESUG 16 Posters Figure 1: Tape layouts for IBM standard labeled and unlabeled tapes IBM STANDARD LABELS HDR1/ EOF1/ VOL HDR2 DATA EOF2 LOAD TAPE MARKS POINT NO LABELS DATA Page 4.
Load more

Recommended publications
  • Georgia Department of Revenue
    Form MV-9W (Rev. 6-2015) Web and MV Manual Georgia Department of Revenue - Motor Vehicle Division Request for Manufacture of a Special Veteran License Plate ______________________________________________________________________________________ Purpose of this Form: This form is to be used to apply for a military license plate/tag. This form should not be used to record a change of ownership, change of address, or change of license plate classification. Required documentation: You must provide a legible copy of your service discharge (DD-214, DD-215, or for World War II veterans, a WD form) indicating your branch and term of service. If you are an active duty member, a copy of the approved documentation supporting your current membership in the respective reserve or National Guard unit is required. In the case of a retired reserve member from that unit, you must furnish approved documentation supporting the current retired membership status from that reserve unit. OWNER INFORMATION First Name Middle Initial Last Name Suffix Owners’ Full Legal Name: Mailing Address: City: State: Zip: Telephone Number: Owner(s)’ Full Legal Name: First Name Middle Initial Last Name Suffix If secondary Owner(s) are listed Mailing Address: City: State: Zip: Telephone Number: VEHICLE INFORMATION Passenger Vehicle Motorcycle Private Truck Vehicle Identification Number (VIN): Year: Make: Model: CAMPAIGN/TOUR of DUTY Branch of Service: SERVICE AWARD Branch of Service: LICENSE PLATES ______________________ LICENSE PLATES ______________________ World War I World
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
    [Show full text]
  • Unix (And Linux)
    AWK....................................................................................................................................4 BC .....................................................................................................................................11 CHGRP .............................................................................................................................16 CHMOD.............................................................................................................................19 CHOWN ............................................................................................................................26 CP .....................................................................................................................................29 CRON................................................................................................................................34 CSH...................................................................................................................................36 CUT...................................................................................................................................71 DATE ................................................................................................................................75 DF .....................................................................................................................................79 DIFF ..................................................................................................................................84
    [Show full text]
  • 5 Command Line Functions by Barbara C
    ADAPS: Chapter 5. Command Line Functions 5 Command Line Functions by Barbara C. Hoopes and James F. Cornwall This chapter describes ADAPS command line functions. These are functions that are executed from the UNIX command line instead of from ADAPS menus, and that may be run manually or by automated means such as “cron” jobs. Most of these functions are NOT accessible from the ADAPS menus. These command line functions are described in detail below. 5.1 Hydra Although Hydra is available from ADAPS at the PR sub-menu, Edit Time Series Data using Hydra (TS_EDIT), it can also be started from the command line. However, to start Hydra outside of ADAPS, a DV or UV RDB file needs to be available to edit. The command is “hydra rdb_file_name.” For a complete description of using Hydra, refer to Section 4.5.2 Edit Time-Series Data using Hydra (TS_EDIT). 5.2 nwrt2rdb This command is used to output rating information in RDB format. It writes RDB files with a table containing the rating equation parameters or the rating point pairs, with all other information contained in the RDB comments. The following arguments can be used with this command: nwrt2rdb -ooutfile -zdbnum -aagency -nstation -dddid -trating_type -irating_id -e (indicates to output ratings in expanded form; it is ignored for equation ratings.) -l loctzcd (time zone code or local time code "LOC") -m (indicates multiple output files.) -r (rounding suppression) Rules • If -o is omitted, nwrt2rdb writes to stdout; AND arguments -n, -d, -t, and -i must be present. • If -o is present, no other arguments are required, and the program will use ADAPS routines to prompt for them.
    [Show full text]
  • Student Batch File Layout – Version 1.0
    Student Batch File Layout – Version 1.0 This document shall set forth the layout of the Student Batch File that will be used for feeding student records into the Uniq-ID System for id assignment and/or student information updates. The Student Batch File should contain three different types of records. The three types of records are: (1) Header record (2) Detail Record (3) Trailer Record. The Header and Trailer record should be delimited by a single tab or space character. The Detail records can be either tab or comma delimited and the Header record should identify which type is being used (in the delimiter field). All records should be delimited from each by the source operating system’s end of line character or character sequence. In the Uniq-ID System, errors in the Student Batch File will be handled in two different ways. One way is to flag the particular record and allow the user to repair it in the “Fix Errors” stage. The other way is to reject the entire Student Batch File and require that the user resubmit it. Rejection of a Student Batch File will occur if: 1. One or more record types are missing. 2. One or more fields have been omitted from a record. 3. The “Number of Records” field in the trailer record is incorrect. 4. The “Transmission ID” fields in the header and trailer records do not match. 5. The maximum allowable number of detail record errors has been exceeded. 6. The maximum allowable number of records in the entire file has been exceeded.
    [Show full text]
  • EHR: Electronic Health Record (EHR) Data Processing and Analysis Tool
    Package ‘EHR’ June 9, 2021 Version 0.4-1 Date 2021-06-07 Title Electronic Health Record (EHR) Data Processing and Analysis Tool Maintainer Leena Choi <[email protected]> Description Process and analyze electronic health record (EHR) data. The 'EHR' package provides modules to perform diverse medication-related studies using data from EHR databases. Especially, the package includes modules to perform pharmacokinetic/pharmacodynamic (PK/PD) analyses using EHRs, as outlined in Choi, Beck, McNeer, Weeks, Williams, James, Niu, Abou-Khalil, Birdwell, Roden, Stein, Bejan, Denny, and Van Driest (2020) <doi:10.1002/cpt.1787>. Additional modules will be added in future. In addition, this package provides various functions useful to perform Phenome Wide Association Study (PheWAS) to explore associations between drug exposure and phenotypes obtained from EHR data, as outlined in Choi, Carroll, Beck, Mosley, Roden, Denny, and Van Driest (2018) <doi:10.1093/bioinformatics/bty306>. Depends R (>= 2.10) License GPL (>= 3) Imports stats, utils, data.table, methods, lubridate, pkdata Suggests glmnet, logistf, medExtractR, knitr, rmarkdown, ggplot2, markdown NeedsCompilation no RoxygenNote 7.1.1 VignetteBuilder knitr Author Leena Choi [aut, cre] (<https://orcid.org/0000-0002-2544-7090>), Cole Beck [aut] (<https://orcid.org/0000-0002-6849-6255>), Hannah Weeks [aut] (<https://orcid.org/0000-0002-0262-6790>), Elizabeth McNeer [aut], Nathan James [aut] (<https://orcid.org/0000-0001-7079-9151>), Michael Williams [aut] Repository CRAN Date/Publication 2021-06-09 07:20:08 UTC 1 2 R topics documented: R topics documented: EHR-package . .3 addLastDose . .4 analysisPheWAS . .5 buildDose . .6 collapseDose . .8 dataTransformation . .9 dd.............................................. 10 dd.baseline .
    [Show full text]
  • UNIX (Solaris/Linux) Quick Reference Card Logging in Directory Commands at the Login: Prompt, Enter Your Username
    UNIX (Solaris/Linux) QUICK REFERENCE CARD Logging In Directory Commands At the Login: prompt, enter your username. At the Password: prompt, enter ls Lists files in current directory your system password. Linux is case-sensitive, so enter upper and lower case ls -l Long listing of files letters as required for your username, password and commands. ls -a List all files, including hidden files ls -lat Long listing of all files sorted by last Exiting or Logging Out modification time. ls wcp List all files matching the wildcard Enter logout and press <Enter> or type <Ctrl>-D. pattern Changing your Password ls dn List files in the directory dn tree List files in tree format Type passwd at the command prompt. Type in your old password, then your new cd dn Change current directory to dn password, then re-enter your new password for verification. If the new password cd pub Changes to subdirectory “pub” is verified, your password will be changed. Many systems age passwords; this cd .. Changes to next higher level directory forces users to change their passwords at predetermined intervals. (previous directory) cd / Changes to the root directory Changing your MS Network Password cd Changes to the users home directory cd /usr/xx Changes to the subdirectory “xx” in the Some servers maintain a second password exclusively for use with Microsoft windows directory “usr” networking, allowing you to mount your home directory as a Network Drive. mkdir dn Makes a new directory named dn Type smbpasswd at the command prompt. Type in your old SMB passwword, rmdir dn Removes the directory dn (the then your new password, then re-enter your new password for verification.
    [Show full text]
  • Oracle Database Administrator's Reference for UNIX-Based Operating Systems
    Oracle® Database Administrator’s Reference 10g Release 2 (10.2) for UNIX-Based Operating Systems B15658-06 March 2009 Oracle Database Administrator's Reference, 10g Release 2 (10.2) for UNIX-Based Operating Systems B15658-06 Copyright © 2006, 2009, Oracle and/or its affiliates. All rights reserved. Primary Author: Brintha Bennet Contributing Authors: Kevin Flood, Pat Huey, Clara Jaeckel, Emily Murphy, Terri Winters, Ashmita Bose Contributors: David Austin, Subhranshu Banerjee, Mark Bauer, Robert Chang, Jonathan Creighton, Sudip Datta, Padmanabhan Ganapathy, Thirumaleshwara Hasandka, Joel Kallman, George Kotsovolos, Richard Long, Rolly Lv, Padmanabhan Manavazhi, Matthew Mckerley, Sreejith Minnanghat, Krishna Mohan, Rajendra Pingte, Hanlin Qian, Janelle Simmons, Roy Swonger, Lyju Vadassery, Douglas Williams This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S.
    [Show full text]
  • VUHDDS Reporting Manual STATE of VERMONT GREEN MOUNTAIN CARE BOARD NECESSARY DATA
    144 State Street Montpelier, VT 05602 802-828-2177 ______________________________________________________________________________________________________ Reporting Manual for Vermont Uniform Hospital Discharge Data System (VUHDDS) Necessary Data and Reporting Schedule STATE OF VERMONT GREEN MOUNTAIN CARE BOARD The Green Mountain Care Board is the steward of the Vermont Uniform Hospital Discharge Data System (“VUHDDS”) which contains information related to health care provided to patients at health care facilities in Vermont and health care provided to Vermont residents at health care facilities in other states. Under the statutory authority to collect these data (18 V.S.A. § 94101, 18 V.S.A. § 94562, and 18 V.S.A. § 94573), the Vermont Green Mountain Care Board (GMCB) administers the program. This reporting manual, as a companion to Green Mountain Care Board Rule 8.000, specifies data submission requirements for the VUHDDS data set, including the required data submission schedule, required fields, file layouts, file components, edit specifications, instructions, and other technical information. 1 https://legislature.vermont.gov/statutes/section/18/221/09410 2 https://legislature.vermont.gov/statutes/section/18/221/09456 3 https://legislature.vermont.gov/statutes/section/18/221/09457 2 VUHDDS Reporting Manual STATE OF VERMONT GREEN MOUNTAIN CARE BOARD NECESSARY DATA Emergency Outpatient Department Field Name Field Description Inpatient Discharges Discharges Discharges** Special Notes UPI Unique Person ID NPI National Provider ID
    [Show full text]
  • Standard TECO (Text Editor and Corrector)
    Standard TECO TextEditor and Corrector for the VAX, PDP-11, PDP-10, and PDP-8 May 1990 This manual was updated for the online version only in May 1990. User’s Guide and Language Reference Manual TECO-32 Version 40 TECO-11 Version 40 TECO-10 Version 3 TECO-8 Version 7 This manual describes the TECO Text Editor and COrrector. It includes a description for the novice user and an in-depth discussion of all available commands for more advanced users. General permission to copy or modify, but not for profit, is hereby granted, provided that the copyright notice is included and reference made to the fact that reproduction privileges were granted by the TECO SIG. © Digital Equipment Corporation 1979, 1985, 1990 TECO SIG. All Rights Reserved. This document was prepared using DECdocument, Version 3.3-1b. Contents Preface ............................................................ xvii Introduction ........................................................ xix Preface to the May 1985 edition ...................................... xxiii Preface to the May 1990 edition ...................................... xxv 1 Basics of TECO 1.1 Using TECO ................................................ 1–1 1.2 Data Structure Fundamentals . ................................ 1–2 1.3 File Selection Commands ...................................... 1–3 1.3.1 Simplified File Selection .................................... 1–3 1.3.2 Input File Specification (ER command) . ....................... 1–4 1.3.3 Output File Specification (EW command) ...................... 1–4 1.3.4 Closing Files (EX command) ................................ 1–5 1.4 Input and Output Commands . ................................ 1–5 1.5 Pointer Positioning Commands . ................................ 1–5 1.6 Type-Out Commands . ........................................ 1–6 1.6.1 Immediate Inspection Commands [not in TECO-10] .............. 1–7 1.7 Text Modification Commands . ................................ 1–7 1.8 Search Commands .
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Second Internet Edition William E. Shotts, Jr. A LinuxCommand.org Book Copyright ©2008-2013, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, 171 Second Street, Suite 300, San Fran- cisco, California, 94105, USA. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. This book is also available in printed form, published by No Starch Press and may be purchased wherever fine books are sold. No Starch Press also offers this book in elec- tronic formats for most popular e-readers: http://nostarch.com/tlcl.htm Release History Version Date Description 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. 09.11 November 19, 2009 Fourth draft with almost all reviewer feedback incorporated and edited through chapter 37. 09.10 October 3, 2009 Third draft with revised table formatting, partial application of reviewers feedback and edited through chapter 18. 09.08 August 12, 2009 Second draft incorporating the first editing pass. 09.07 July 18, 2009 Completed first draft. Table of Contents Introduction....................................................................................................xvi
    [Show full text]
  • Unix Commands (09/04/2014)
    Unix Commands (09/04/2014) • Access control – login <login_name> – exit – passwd <login_name> – yppassswd <loginname> – su – • Login as Super user – su <login> • Login as user <login> • Root Prompt – [root@localhost ~] # • User Prompt – [bms@raxama ~] $ On Line Documentation – man <command/topic> – info <command/topic> • Working with directories – mkdir –p <subdir> ... {-p create all directories in path if not present} mkdir –p /2015/Jan/21/14 will create /2015, Jan, 21 & 14 in case any of these is absent – cd <dir> – rm -r <subdir> ... Man Pages • 1 Executable programs or shell commands • 2 System calls (functions provided by the kernel) • 3 Library calls (functions within program libraries) • 4 Special files (usually found in /dev) • 5 File formats and conventions eg /etc/passwd • 6 Games • 7 Miscellaneous (including macro packages and conventions), e.g. man(7), groff(7) • 8 System administration commands (usually only for root) • 9 Kernel routines [Non standard] – man grep, {awk,sed,find,cut,sort} – man –k mysql, man –k dhcp – man crontab ,man 5 crontab – man printf, man 3 printf – man read, man 2 read – man info Runlevels used by Fedora/RHS Refer /etc/inittab • 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 multi user mode w/o X • 4 - unused • 5 - X11 • 6 - reboot (Do NOT set init default to this) – init 6 {Reboot System} – init 0 {Halt the System} – reboot {Requires Super User} – <ctrl> <alt> <del> • in tty[2-7] mode – tty switching • <ctrl> <alt> <F1-7> • In Fedora 10 tty1 is X.
    [Show full text]