DOCSLIB.ORG

Selected IRIX™ Site Administration Reference Pages

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Selected IRIX™ Site Administration Reference Pages Document Number 007-2159-004 © Copyright 1993, 1994, Silicon Graphics, Inc.— All Rights Reserved This document contains proprietary and confidential information of Silicon Graphics, Inc. The contents of this document may not be disclosed to third parties, copied, or duplicated in any form, in whole or in part, without the prior written permission of Silicon Graphics, Inc. Restricted Rights Legend Use, duplication, or disclosure of the technical data contained in this document by the Government is subject to restrictions as set forth in subdivision (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.227-7013 and/or in similar or successor clauses in the FAR, or in the DOD or NASA FAR Supplement. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 2011 N. Shoreline Blvd., Mountain View, CA 94039-7311. Selected IRIX Site Administration Reference Pages Document Number 007-2159-004 Silicon Graphics, Inc. Mountain View, California IRIX is a trademark of Silicon Graphics, Inc. UNIX is a trademark of AT&T, Inc. Introduction This volume contains selected IRIX Site Administration Man Pages. The table below lists the Man Pages and summarizes their functions. Man Page Function Add_disk(1) add an optional disk to the system autoconfig(1m) configure kernel Backup(1) backup the specified file or directory bootp(1m) server for Internet Bootstrap Protocol brc(1m) system initialization procedures chkconfig(1m) configuration state checker chroot(1m) change root directory for a command core(4) format of core image file cshrc(4) system-wide csh initialization command file devnm(1m) device name distcp(1m) copy or compare software distributions dvhtool(1m) modify and obtain disk volume header information ecc(1) dump memory ecc log ed(1) text editor find(1) find files Selected IRIX Site Administration Reference Pages iii Man Page Function fs(4) layout of the Extent file system fsck, dfsck(1m) check and repair file systems fsdb(1m) file system debugger fsstat(1m) report file system status fstab(4) static information about filesystems ftp(1c) Internet file transfer program fx(1m) disk utility gettydefs(4) speed and terminal settings used by getty growfs(1m) expand a filesystem hinv(1m) hardware inventory command hosts(4) host name-address database init(1m) process control initialization inittab(4) script for the init process inode(4) format of an Extent File System inode inst(1m) software installation tool killall(1m) kill named processes lboot(1m) configure bootable kernel login(1) sign on lvck(1m) check and restore consistency of logical volumes lvinfo(1m) print information about active logical volumes lvinit(1m) initialize logical volume devices lvtab(4) information about logical volumes MAKEDEV(1m) Create device special files master(4) master configuration database mkboottape(1m) make a boot tape Selected IRIX Site Administration Reference Pages (continued) iv Man Page Function mkfs(1m) construct a file system mklv(1m) construct or extend a logical volume mload(4) dynamically loadable kernel modules mount, umount(1m) mount and dismount file systems mtune(4) default system tunable parameters nvram(1m) get or set non-volatile RAM variable(s) passwd(4) password file profile(4) setting up an environment at login time prom(1m) PROM monitor prtvtoc(1m) print disk volume header information. ps(1) report process status pwck(1m) password file checker pwconv(1m) install and update /etc/shadow with information from /etc/passwd rcp(1c) remote file copy Restore(1) restore the specified file or directory from tape restore(1m) incremental file system restore rlogin(1c) remote login savecore(1m) save a crash vmcore dump of the operating system setmnt(1m) establish mount table sh(1) shell, the standard command programming language shadow(4) shadow password file statd(1m) network status monitor daemon stune(4) local settings for system tunable parameters su(1m) become super-user or another user Selected IRIX Site Administration Reference Pages (continued) v Man Page Function symmon(1m) kernel symbolic debugger syslogd(1m) log systems messages system(4) system configuration information directory systune(1m) display and set tunable parameters sys_id(4) system identification (hostname) file telnet(1c) User interface to the TELNET protocol ttytype(4) data base of terminal types by port versions(1m) software versions tool Selected IRIX Site Administration Reference Pages (continued) vi hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhADD_DISK(1) ADD_DISK(1) NAME Add_disk − add an optional disk to the system SYNOPSIS Add_disk [ controller number ][disk number ] DESCRIPTION The Add_disk command allows the user to add an extra SCSI disk to the system on integral SCSI controll- ers only (i.e., it many not be used for disks attached to the VME SCSI controllers). The disk number option must be specified if not adding the default ID of 2; similarly the controller must be specified if other than 0. The Add_disk command creates the required directory, makes the appropriate device file links, makes a new filesystem, does the required mount operation, and adds the appropriate entry to /etc/fstab. Appropriate checks are made for filesystems already existing on the common partitions (0, 6, and 7), and if they are present, the user is asked if they want to proceed, before a filesystem is made. If the answer is no, Add_disk exits. NOTE Older versions of this script worked only with controller 0, and used a default mount point of /disk#, where # was the SCSI ID. This version uses /disk##, where the first # is the controller, and the second is the SCSI ID. Add_disk is a shell script, and can be used as a template to determine what is necessary. The volume header on the disk must already have been initialized with the fx(1m) program. SEE ALSO mkfs(1m), fx(1m), fstab(4) 1 hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhAUTOCONFIG(1M) AUTOCONFIG(1M) NAME autoconfig − configure kernel SYNOPSIS /etc/autoconfig [−vf][−p toolroot] [−d /var/sysgen] [−o lbootopts] [start|| stop] DESCRIPTION The autoconfig command is used invoke lboot and other commands to generate a UNIX kernel. The autoconfig command is also a start-up script in /etc/init.d. The options are as follows: −v Requests verbose output from lboot and other commands. −f Generates a new kernel even if it appears that no hardware or software changes have been made. −p toolroot Specifies the directory tree containing the compiler and other tools needed to generate the kernel. −d /var/sysgen Specifies the directory tree containing the system configuration modules and binaries. −n Performs a dry run of lboot and reports whether a new kernel would be created or not. start Used by rc2 when the system is starting. stop Used by rc0 when the system is stopping. The autoconfig command also uses the /var/config/autoconfig.options file to tell lboot to configure a new ker- nel automatically or to prompt for permission before configuring a new kernel. The /var/config/autoconfig.options file contains a -T by default which indicates to lboot to configure the kernel automatically if necessary. This option can be changed to a -t to force lboot to prompt for permission before configuring a new kernel. SEE ALSO lboot(1m), setsym(1m), rc0(1m), rc2(1m) 1 hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhBACKUP(1) BACKUP(1) NAME Backup − backup the specified file or directory SYNOPSIS Backup [ −h hostname ][−t tapedevice ][−i ][directory name | file name ] DESCRIPTION The Backup command archives the named file or directory ("." if none specified) to the local or remote tape device. It can be used to make a full system backup by specifying the directory name as /. In case of a full backup this command makes a list of the files in the disk volume header and saves this information in a file which is then stored on tape. This file is used during crash recovery to restore a dam- aged volume header. The current date is saved in the file /etc/lastbackup. If a tape drive attached to a remote host is used for backup, the name of the remote host needs to be specified with the −h hostname option on the command line. For remote backup to successfully work, the user should have a TCP/IP network connection to the remote host and also have "guest" login privileges on that host. If the local or remote tape device is pointed to by a device file other than /dev/tape, the device should be specified by the −t tapedevice option. If a backup of all files modified since the date specified in the /etc/lastbackup file is desired, the −i option should be specified. This option is only valid when doing a complete backup. The Backup command uses bru to perform the backup function. FILES /tmp/volhdrlist − contains the list of the root volume header files /etc/lastbackup − contains the date of last full backup SEE ALSO Restore(1), List_tape(1), bru(1). 1 hhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhBOOTP(1M) BOOTP(1M) NAME bootp − server for Internet Bootstrap Protocol SYNOPSIS /usr/etc/bootp [ −d][−f] DESCRIPTION Bootp is a server that supports the Internet Bootstrap Protocol (BOOTP). This protocol is designed to allow a (possibly diskless) client machine to determine its own Internet address, the address of a boot server and the name of an appropriate boot file to be loaded and executed. BOOTP does not provide the actual transfer of the boot file, which is typically done with a simple file transfer protocol such as TFTP. A detailed protocol specification for BOOTP is contained in RFC 951, which is available from the Network Information Center. The BOOTP protocol uses UDP/IP as its transport mechanism. The BOOTP server receives service requests at the UDP port indicated in the ‘‘bootp’’ service description contained in the file /etc/services (see services(4)).
Recommended publications
  • Beyond BIOS Developing with the Unified Extensible Firmware Interface

    Beyond BIOS Developing with the Unified Extensible Firmware Interface

    Digital Edition Digital Editions of selected Intel Press books are in addition to and complement the printed books. Click the icon to access information on other essential books for Developers and IT Professionals Visit our website at www.intel.com/intelpress Beyond BIOS Developing with the Unified Extensible Firmware Interface Second Edition Vincent Zimmer Michael Rothman Suresh Marisetty Copyright © 2010 Intel Corporation. All rights reserved. ISBN 13 978-1-934053-29-4 This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold with the understanding that the publisher is not engaged in professional services. If professional advice or other expert assistance is required, the services of a competent professional person should be sought. Intel Corporation may have patents or pending patent applications, trademarks, copyrights, or other intellectual property rights that relate to the presented subject matter. The furnishing of documents and other materials and information does not provide any license, express or implied, by estoppel or otherwise, to any such patents, trademarks, copyrights, or other intellectual property rights. Intel may make changes to specifications, product descriptions, and plans at any time, without notice. Fictitious names of companies, products, people, characters, and/or data mentioned herein are not intended to represent any real individual, company, product, or event. Intel products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications. Intel, the Intel logo, Celeron, Intel Centrino, Intel NetBurst, Intel Xeon, Itanium, Pentium, MMX, and VTune are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
  • Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT

    Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT

    LPI 117-101 117-101 LPI 101 General Linux, Part I Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT You suspect that a new ethernet card might be conflicting with another device. Which file should you check within the /proc tree to learn which IRQs are being used by which kernel drives? Answer: interrupts QUESTION NO: 2 How many SCSI ids for peripherals can SCSI-1 support? A. 5 B. 6 C. 7 D. 8 Answer: C Explanation: SCSI-1 support total 7 peripherals. There are several different types of SCSI devices. The original SCSI specification is commonly referred to as SCSI-1. The newer specification, SCSI-2, offers increased speed and performance, as well as new commands. Fast SCSI increases throughput to more than 10MB per second. Fast-Wide SCSI provides a wider data path and throughput of up to 40MB per second and up to 15 devices. There there are Ultra-SCSI and Ultra-Wide-SCSI QUESTION NO: 3 You need to install a fax server. Which type of fax/modem should you install to insure Linux compatibility? Test-King.com A. External Serial Fax/modem B. External USB Fax/modem C. Internal ISA Fax/modem D. Internal PCI Fax/modem Answer: A QUESTION NO: 4 You are running Linux 2.0.36 and you need to add a USB mouse to your system. Which of the following statements is true? "Welcome to Certification's Main Event" - www.test-king.com 2 LPI 117-101: Practice Exam A. You need to rebuild the kernel.
  • Plw Sc/Nt/Ntr/Ls

    Plw Sc/Nt/Ntr/Ls

    K Service Source PLW SC/NT/NTR/LS Personal LaserWriter SC, Personal LaserWriter NT, Personal LaserWriter NTR, Personal LaserWriter LS, Personal LaserWriter LS/L K Service Source Basics PLW SC/NT/NTR/LS Basics Product Information - 1 Product Information The printers covered in this manual are • Personal LaserWriter SC • Personal LaserWriter NT • Personal LaserWriter NTR • Personal LaserWriter LS • Personal LaserWriter LS/L Compatibility Not all parts are compatible among the five models. Refer to Illustrated Parts for compatibility cross references. The cassette feeder tray and its associated parts are optional on the LS, LS/L, and NTR models. Basics Paper Paths - 2 Paper Paths There are four paper paths in the Personal LaserWriter. Paper is fed from the cassette or multipurpose tray and delivered to the face-down or face-up delivery trays. Note: Face signifies image side. Default delivery is face- down at the top of the printer. Basics LS–LS/L Identification - 3 LS–LS/L Identification I/O Board Bracket The LS/L is a cost-reduced version of the LS but is sold and packaged under the same LS name. Parts are not necessarily interchangeable between the two models. Power Switch External distinguishing characteristics: • LS: The power switch is on the left rear of printer; the rear cover has an opening for an I/O board bracket and Personal LaserWriter LS displays the family number M2000. • LS/L: The power switch is on the right rear of printer; Solid Rear Cover the rear cover is solid plastic and displays the family number M2002. Power Switch Personal LaserWriter LS/L Basics Sensing System Theory - 4 Sensing System Theory There are six sensors in the PS11 Personal LaserWriter: four PS12 paper sensors and two printer-open sensors.
  • Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D

    Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D

    Article pubs.acs.org/JPCC Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D. Tuttle, Lingyang Zhu, Deborah A. Berthold, Petr Kral,́, † ‡ # † Chad M. Rienstra,*, , , and Catherine J. Murphy*, † ‡ Department of Chemistry and Department of Biochemistry, University of Illinois at Urbana−Champaign, 600 South Matthews Avenue, Urbana, Illinois 61801, United States § School of Chemical Sciences, University of Illinois at Urbana−Champaign, 505 South Matthews Avenue, Urbana, Illinois 61801, United States ∥ ⊥ Department of Chemistry and Department of Physics, University of Illinois at Chicago, 845 West Taylor Street, Chicago, Illinois 60607, United States # Center for Biophysics and Computational Biology, University of Illinois at Urbana−Champaign, 607 South Matthews Avenue, Urbana, Illinois 61801, United States *S Supporting Information ABSTRACT: Gold nanoparticles (Au NPs) have attracted much attention due to their potential applications in nanomedicine. While numerous studies have quantified biomolecular adsorption to Au NPs in terms of equilibrium binding constants, far less is known about biomolecular orientation on nanoparticle surfaces. In this study, the binding of the protein α-synuclein to citrate and (16- mercaptohexadecyl)trimethylammonium bromide (MTAB)-coated 12 nm Au NPs is examined by heteronuclear single quantum coherence NMR spectroscopy to provide site-specific measurements of protein−nanoparticle binding. Molecular dynamics simulations support the orientation assignments, which
  • File System, Files, and *Tab /Etc/Fstab

    File System, Files, and *Tab /Etc/Fstab

    File system, files, and *tab File system files directories volumes, file systems mounting points local versus networked file systems 1 /etc/fstab Specifies what is to be mounted where and how fs_spec: describes block special device for remote filesystem to be mounted fs_file: describes the mount point fs_vfstype: describes the type of file system fs_mntops: describes the mount options associated with the filesystem 2 /etc/fstab cont. fs_freq: used by the dump command fs_passno: used by fsck to determine the order in which checks are done at boot time. Root file systems should be specified as 1, others should be 2. Value 0 means that file system does not need to be checked 3 /etc/fstab 4 from blocks to mounting points metadata inodes directories superblocks 5 mounting file systems mounting e.g., mount -a unmounting manually or during shutdown umount 6 /etc/mtab see what is mounted 7 Network File System Access file system (FS) over a network looks like a local file system to user e.g. mount user FS rather than duplicating it (which would be a disaster) Developed by Sun Microsystems (mid 80s) history for NFS: NFS, NFSv2, NFSv3, NFSv4 RFC 3530 (from 2003) take a look to see what these RFCs are like!) 8 Network File System How does this actually work? server needs to export the system client needs to mount the system server: /etc/exports file client: /etc/fstab file 9 Network File System Security concerns UID GID What problems could arise? 10 Network File System example from our raid system (what is a RAID again?) Example of exports file from
  • Software Engineering a Abnormal End: Abend Abnormaal Einde De Beëindiging Van Een Proces Voordat Dat Proces Geheel Is Afgewerkt

    Software Engineering a Abnormal End: Abend Abnormaal Einde De Beëindiging Van Een Proces Voordat Dat Proces Geheel Is Afgewerkt

    1 Verklarende terminologielijst voor de Software Engineering A abnormal end: abend abnormaal einde De beëindiging van een proces voordat dat proces geheel is afgewerkt. abort (to) afbreken Een proces afbreken voordat het volledig is afgewerkt. absolute address absoluut adres Een adres dat permanent aan een eenheid of geheugenplaats is toegewezen en dat de eenheid of de geheugenplaats identificeert zonder dat daarvoor een vertaling of berekening nodig is. absolute assembler absoluut assembleerprogramma Een assembleerprogramma dat uitsluitend absolute code genereert. absolute code absolute code Code waarin alle adressen absoluut zijn. absolute coding absolute codering Een coderingsmethode waarin gebruik wordt gemaakt van instructies die absolute adressen bevatten. absolute expression absolute uitdrukking Een uitdrukking voorafgaande aan het moment waarop het assembleren van een programma plaatsvindt. Dit moment wordt niet beïnvloed door het verplaatsen van het programma. Een absolute uitdrukking kan een absoluut adres in een assembleertaal weergeven. absolute instruction absolute instructie 1. Een instructie in de definitieve uitvoerbare vorm. 2. Een computerinstructie waarin alle adressen uit absolute adressen bestaan. absolute loader absoluut laadprogramma Een programma dat een ander programma in het hoofdgeheugen kan plaatsen. Dit begint bij het initiële adres dat aan de code door het assembleerprogramma of de compiler is toegewezen en dat de adressen in de code niet verder wijzigt of aanpast. absolute load module absolute laadmodule 2 Een combinatie van werkmodules die op een gespecificeerd adres in het werkgeheugen wordt uitgevoerd. absolute machine code absolute machinecode Machinecode die steeds in vaste geheugenplaatsen moet worden geladen en niet mag worden verplaatst. Dit in tegenstelling tot verplaatsbare machinecode. absolute pathname absolute padnaam Een padnaam die de informatie bevat over de wijze waarop een bestand kan worden gevonden.
  • Filesystem Hierarchy Standard

    Filesystem Hierarchy Standard

    Filesystem Hierarchy Standard LSB Workgroup, The Linux Foundation Filesystem Hierarchy Standard LSB Workgroup, The Linux Foundation Version 3.0 Publication date March 19, 2015 Copyright © 2015 The Linux Foundation Copyright © 1994-2004 Daniel Quinlan Copyright © 2001-2004 Paul 'Rusty' Russell Copyright © 2003-2004 Christopher Yeoh Abstract This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems. All trademarks and copyrights are owned by their owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Permission is granted to make and distribute verbatim copies of this standard provided the copyright and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this standard under the conditions for verbatim copying, provided also that the title page is labeled as modified including a reference to the original standard, provided that information on retrieving the original standard is included, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this standard into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the copyright holder. Dedication This release is dedicated to the memory of Christopher Yeoh, a long-time friend and colleague, and one of the original editors of the FHS.
  • Advanced Bash-Scripting Guide

    Advanced Bash-Scripting Guide

    Advanced Bash−Scripting Guide An in−depth exploration of the art of shell scripting Mendel Cooper <[email protected]> 2.2 31 October 2003 Revision History Revision 0.1 14 June 2000 Revised by: mc Initial release. Revision 0.2 30 October 2000 Revised by: mc Bugs fixed, plus much additional material and more example scripts. Revision 0.3 12 February 2001 Revised by: mc Another major update. Revision 0.4 08 July 2001 Revised by: mc More bugfixes, much more material, more scripts − a complete revision and expansion of the book. Revision 0.5 03 September 2001 Revised by: mc Major update. Bugfixes, material added, chapters and sections reorganized. Revision 1.0 14 October 2001 Revised by: mc Bugfixes, reorganization, material added. Stable release. Revision 1.1 06 January 2002 Revised by: mc Bugfixes, material and scripts added. Revision 1.2 31 March 2002 Revised by: mc Bugfixes, material and scripts added. Revision 1.3 02 June 2002 Revised by: mc 'TANGERINE' release: A few bugfixes, much more material and scripts added. Revision 1.4 16 June 2002 Revised by: mc 'MANGO' release: Quite a number of typos fixed, more material and scripts added. Revision 1.5 13 July 2002 Revised by: mc 'PAPAYA' release: A few bugfixes, much more material and scripts added. Revision 1.6 29 September 2002 Revised by: mc 'POMEGRANATE' release: some bugfixes, more material, one more script added. Revision 1.7 05 January 2003 Revised by: mc 'COCONUT' release: a couple of bugfixes, more material, one more script. Revision 1.8 10 May 2003 Revised by: mc 'BREADFRUIT' release: a number of bugfixes, more scripts and material.
  • Evaluating UNIX Security Previous Screen Allen B

    Evaluating UNIX Security Previous Screen Allen B

    84-01-15.1 Evaluating UNIX Security Previous screen Allen B. Lum Payoff The UNIX operating system's basic security features include password protection, access permission, user profiles, shell scripts, and file ownership. Because new and enhanced UNIX security features are continually being added to these features in response to the demands of an increasingly competitive user community, information security professionals must begin with an understanding of the basic UNIX security environment. This article covers the fundamental security features that can be found in most of the currently available versions of the UNIX operating system. Several checklists are included at the end of the article to assist administrators in ensuring the security of UNIX systems. Problems Addressed The UNIX operating system was originally developed for use by programmers within an open systems environment. The adoption of UNIX as a common operating system across several different platforms has increased the need for security beyond its original purpose. As a result, many UNIX installations have less than optimal security. In addition, there are several versions of UNIX on the market today with differing security features. This article discusses basic access controls (e.g., passwords) and directory and file permissions within the UNIX system. The concepts discussed are applicable to all versions of UNIX unless specifically noted otherwise. UNIX History As the majority of UNIX users know, UNIX was developed at AT Bell Laboratories in the late 1960s by Thompson and Ritchie; the name UNIXis a contraction of uni and multics. The original UNIX system software was written in the assembler language to run on the digital PDP-7 computer.
  • Chapter 3 Unix Overview

    Chapter 3 Unix Overview

    Chapter 3 Unix Overview Figure 3.1 Unix file system Directory Purpose / The root directory /bin or /sbin Critical executables needed to boot the system /dev Device drivers /etc System configuration files such as passwords, network addresses and names,system startup scripts /home User home directories /lib Shared libraries used by programs /mnt Temporary mount point for file systems /proc Images of currently executing processes on the system /tmp Temporary files /usr A variety of critical system files, including system utilities (/usr/bin), and administration executables (/usr/sbin) /var Stores varying files such as /var/log, /var/mail Table 3.1 Important Directories in the Unix file system Figure 3.2 Unix Architecture Figure 3.3 Relationship between init, inetd, and various network services Sample /etc/inetd.conf file containing services spawned by inetd /etc/inetd.conf file format • Service name (port # defined in /etc/services) • Socket type (stream or dgram) • Protocol (tcp, udp, rpc/tcp, or rpc/udp) • Wait status (wait or nowait) • Username (service run as) • Server program • Server program arguments Use of inetd.conf to create backdoor listeners and attack relays Common Unix Administration Tasks ♦ Vulnerability of using “.” in your search path $PATH ♦ Showing all running processes ps –aux ps –aef ♦ Killing/restarting processes kill –HUP pid killall –HUP inetd ♦ /etc/passwd file ♦ Unix permissions rwxrwxrwx chmod command Common Unix Administration Tasks (cont.) ♦ SetUID programs – Executes with permissions of its owner, not of its
  • Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO

    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO

    Filesystems HOWTO Filesystems HOWTO Table of Contents Filesystems HOWTO..........................................................................................................................................1 Martin Hinner < [email protected]>, http://martin.hinner.info............................................................1 1. Introduction..........................................................................................................................................1 2. Volumes...............................................................................................................................................1 3. DOS FAT 12/16/32, VFAT.................................................................................................................2 4. High Performance FileSystem (HPFS)................................................................................................2 5. New Technology FileSystem (NTFS).................................................................................................2 6. Extended filesystems (Ext, Ext2, Ext3)...............................................................................................2 7. Macintosh Hierarchical Filesystem − HFS..........................................................................................3 8. ISO 9660 − CD−ROM filesystem.......................................................................................................3 9. Other filesystems.................................................................................................................................3
  • The Complete Freebsd

    The Complete Freebsd

    The Complete FreeBSD® If you find errors in this book, please report them to Greg Lehey <grog@Free- BSD.org> for inclusion in the errata list. The Complete FreeBSD® Fourth Edition Tenth anniversary version, 24 February 2006 Greg Lehey The Complete FreeBSD® by Greg Lehey <[email protected]> Copyright © 1996, 1997, 1999, 2002, 2003, 2006 by Greg Lehey. This book is licensed under the Creative Commons “Attribution-NonCommercial-ShareAlike 2.5” license. The full text is located at http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode. You are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. • Noncommercial. You may not use this work for commercial purposes. This clause is modified from the original by the provision: You may use this book for commercial purposes if you pay me the sum of USD 20 per copy printed (whether sold or not). You must also agree to allow inspection of printing records and other material necessary to confirm the royalty sums. The purpose of this clause is to make it attractive to negotiate sensible royalties before printing. • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. • For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.