DOCSLIB.ORG

Why Use the Integrated File System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Why Use the Integrated File System IBM IBM i Files and file systems Integrated file system 7.1 IBM IBM i Files and file systems Integrated file system 7.1 Note Before using this information and the product it supports, read the information in “Notices,” on page 147. This edition applies to IBM i 7.1 (product number 5770-SS1) and to all subsequent releases and modifications until otherwise indicated in new editions. This version does not run on all reduced instruction set computer (RISC) models nor does it run on CICS models. © Copyright IBM Corporation 1999, 2010. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Integrated file system ......... 1 Case sensitivity in an integrated file system What's new for IBM i 7.1 .......... 1 user-defined file system ........ 35 PDF file for Integrated file system ....... 2 Path names in an integrated file system Overview of the integrated file system...... 2 user-defined file system ........ 35 What the integrated file system is ...... 2 Links in an integrated file system user-defined Why use the integrated file system ...... 3 file system............. 36 Integrated file system concepts ........ 4 Use of integrated file system commands in a Directory .............. 4 user-defined file system ........ 36 Current directory ........... 7 Use of integrated file system APIs in a Home directory ........... 7 user-defined file system ........ 37 Provided directories .......... 7 Graphical user interface for a user-defined file *TYPE2 directories .......... 10 system .............. 37 Link ................ 11 Creating an integrated file system Hard link ............. 12 user-defined file system ........ 38 Symbolic link............ 13 Deleting an integrated file system user-defined Path name.............. 14 file system............. 38 Stream file.............. 15 Displaying an integrated file system Name continuity............ 17 user-defined file system ........ 38 Extended attributes ........... 18 Mounting an integrated file system Scanning support ........... 18 user-defined file system ........ 38 Examples: Scanning for viruses and files being Unmounting an integrated file system opened .............. 19 user-defined file system ........ 39 Related system values ......... 20 Saving and restoring an integrated file system Scanning occurrences ......... 21 user-defined file system ........ 39 Object change .......... 21 Object changes journaling in a user-defined Signature change ......... 21 file system............. 39 Different CCSID .......... 23 User-defined file system and independent During save operation ........ 23 auxiliary storage pools......... 40 Object integrity check ........ 23 Library file system (QSYS.LIB) ....... 40 File systems .............. 23 QPWFSERVER authorization list in the File system comparison ......... 25 QSYS.LIB file system ......... 41 "root" (/) file system .......... 28 File-handling restrictions in the QSYS.LIB file Case-sensitivity in the "root" (/) file system.. 29 system .............. 41 Path names in the "root" (/) file system ... 29 Support for user spaces in the QSYS.LIB file Links in the "root" (/) file system ..... 29 system .............. 41 Use of integrated file system commands in the Support for save files in the QSYS.LIB file "root" (/) file system ......... 29 system .............. 41 Use of integrated file system APIs in the "root" Case-sensitivity in the QSYS.LIB file system 42 (/) file system ........... 30 Path names in the QSYS.LIB file system ... 42 Object changes journaling in the "root" (/) file Links in the QSYS.LIB file system ..... 42 system .............. 30 Use of integrated file system commands and UDP and TCP devices in the "root" (/) file displays in the QSYS.LIB file system .... 42 system .............. 30 Use of integrated file system APIs in the Open systems file system (QOpenSys) .... 31 QSYS.LIB file system ......... 43 Case sensitivity in the QOpenSys file system 31 Independent ASP QSYS.LIB ........ 43 Path names in the QOpenSys file system .. 31 QPWFSERVER authorization list in the Links in the QOpenSys file system .... 32 independent ASP QSYS.LIB file system ... 43 Use of integrated file system commands and File handling restrictions in the independent displays in the QOpenSys file system.... 32 ASP QSYS.LIB file system ....... 44 Use of integrated file system APIs in the Support for user spaces in the independent QOpenSys file system ......... 32 ASP QSYS.LIB file system ....... 44 Object changes journaling in the QOpenSys Support for save files in the independent ASP file system............. 32 QSYS.LIB file system ......... 44 User-defined file systems (UDFSs) ...... 32 Case-sensitivity in the independent ASP | Temporary user-defined file systems .... 34 QSYS.LIB file system ......... 44 © Copyright IBM Corp. 1999, 2010 iii Path names in the independent ASP QSYS.LIB Variations of servers and clients in the file system............. 44 Network File System ......... 60 Links in the independent ASP QSYS.LIB file Links in the Network File System ..... 60 system .............. 45 Use of integrated file system commands in the Use of integrated file system commands and Network File System ......... 61 displays in the independent ASP QSYS.LIB file Use of integrated file system APIs in the system .............. 45 Network File System ......... 62 Use of integrated file system APIs in the | Comparison of Network File System version 4 independent ASP QSYS.LIB file system ... 46 | to Prior Versions........... 62 Document library services file system (QDLS) .. 46 | Setting up a network for RPCSEC-GSS ... 63 Integrated file system and HFS in the QDLS | Identity mapping .......... 64 file system............. 46 Accessing the integrated file system ...... 65 User enrollment in the QDLS file system .. 47 Accessing using menus and displays ..... 66 Case sensitivity in the QDLS file system ... 47 Accessing using CL commands ....... 67 Path names in the QDLS file system .... 47 Path name rules for CL commands and Links in the QDLS file system ...... 47 displays ............. 69 Use of integrated file system commands and Working with output of the RTVDIRINF and displays in the QDLS file system ..... 47 PRTDIRINF commands ......... 71 Use of integrated file system APIs in the Accessing the data of RTVDIRINF .... 84 QDLS file system .......... 48 Using the data of RTVDIRINF ...... 84 Optical file system (QOPT) ........ 48 Collecting and analyzing folder attributes Integrated file system and HFS in the QOPT with Navigator for i ........ 85 file system............. 49 Accessing using APIs .......... 86 Case-sensitivity in the QOPT file system... 49 Accessing using a PC .......... 86 Path names in the QOPT file system .... 49 Accessing using System i Navigator ..... 87 Links in the QOPT file system ...... 50 Accessing using IBM i NetServer ...... 87 Use of integrated file system commands and Accessing using File Transfer Protocol .... 88 displays in the QOPT file system ..... 50 Integrated file system conversion ....... 89 Use of integrated file system APIs in the Converting directories from *TYPE1 to *TYPE2 89 QOPT file system .......... 50 Overview of *TYPE1 to *TYPE2 conversion .. 89 IBM i NetClient file system (QNTC) ..... 51 Directory conversion considerations .... 90 Authorities and ownership in the QNTC file Conversion status determination .... 90 system .............. 51 User profiles creation ........ 91 Case sensitivity in the QNTC file system .. 51 Objects renamed.......... 91 Path names in the QNTC file system .... 51 User profile considerations ...... 92 Links in the QNTC file system ...... 52 Auxiliary storage requirements ..... 92 Use of integrated file system commands and Tips: Symbolic link ......... 93 displays in the QNTC file system ..... 52 Tips: Independent ASP ....... 93 Use of integrated file system APIs in the Tips: Saving and restoring ...... 93 QNTC file system .......... 53 Tips: Reclaiming integrated file system QNTC environment variables ...... 53 objects ............. 93 Creating directories in the QNTC file system 54 Integrated file system scanning ..... 94 Use of integrated file system APIs in the Converting names to support additional Network File System ........ 54 characters .............. 94 Enabling QNTC file system for Network Overview of automatic name conversion .. 94 Authentication Service......... 55 Name conversion considerations ..... 95 IBM i file server file system (QFileSvr.400) ... 55 Conversion status determination .... 95 Case-sensitivity in the QFileSvr.400 file system 56 Objects renamed.......... 95 Path names in the QFileSvr.400 file system .. 56 User profile considerations ...... 96 Communications in the QFileSvr.400 file Tips: Symbolic link ......... 96 system .............. 57 Tips: Independent ASP ....... 96 Security and object authority in the Tips: Saving and restoring ...... 96 QFileSvr.400 file system ........ 58 Tips: Reclaiming integrated file system Links in the QFileSvr.400 file system .... 58 objects ............. 96 Use of integrated file system commands and Journaling objects ............ 97 displays in the QFileSvr.400 file system ... 58 Journaling overview .......... 97 Use of integrated file system APIs in the Journal management ......... 97 QFileSvr.400 file system ........ 59 Objects you should journal ....... 97 Network File System (NFS) ........ 59 Journaled integrated file system objects ... 98 Characteristics of the Network File System .. 60 Journaled operations ......... 99 Special considerations for journal
Load more

Recommended publications
  • Better Performance Through a Disk/Persistent-RAM Hybrid Design
    The Conquest File System: Better Performance Through a Disk/Persistent-RAM Hybrid Design AN-I ANDY WANG Florida State University GEOFF KUENNING Harvey Mudd College PETER REIHER, GERALD POPEK University of California, Los Angeles ________________________________________________________________________ Modern file systems assume the use of disk, a system-wide performance bottleneck for over a decade. Current disk caching and RAM file systems either impose high overhead to access memory content or fail to provide mechanisms to achieve data persistence across reboots. The Conquest file system is based on the observation that memory is becoming inexpensive, which enables all file system services to be delivered from memory, except providing large storage capacity. Unlike caching, Conquest uses memory with battery backup as persistent storage, and provides specialized and separate data paths to memory and disk. Therefore, the memory data path contains no disk-related complexity. The disk data path consists of only optimizations for the specialized disk usage pattern. Compared to a memory-based file system, Conquest incurs little performance overhead. Compared to several disk-based file systems, Conquest achieves 1.3x to 19x faster memory performance, and 1.4x to 2.0x faster performance when exercising both memory and disk. Conquest realizes most of the benefits of persistent RAM at a fraction of the cost of a RAM-only solution. Conquest also demonstrates that disk-related optimizations impose high overheads for accessing memory content in a memory-rich environment. Categories and Subject Descriptors: D.4.2 [Operating Systems]: Storage Management—Storage Hierarchies; D.4.3 [Operating Systems]: File System Management—Access Methods and Directory Structures; D.4.8 [Operating Systems]: Performance—Measurements General Terms: Design, Experimentation, Measurement, and Performance Additional Key Words and Phrases: Persistent RAM, File Systems, Storage Management, and Performance Measurement ________________________________________________________________________ 1.
    [Show full text]
  • Configuring UNIX-Specific Settings: Creating Symbolic Links : Snap
    Configuring UNIX-specific settings: Creating symbolic links Snap Creator Framework NetApp September 23, 2021 This PDF was generated from https://docs.netapp.com/us-en/snap-creator- framework/installation/task_creating_symbolic_links_for_domino_plug_in_on_linux_and_solaris_hosts.ht ml on September 23, 2021. Always check docs.netapp.com for the latest. Table of Contents Configuring UNIX-specific settings: Creating symbolic links . 1 Creating symbolic links for the Domino plug-in on Linux and Solaris hosts. 1 Creating symbolic links for the Domino plug-in on AIX hosts. 2 Configuring UNIX-specific settings: Creating symbolic links If you are going to install the Snap Creator Agent on a UNIX operating system (AIX, Linux, and Solaris), for the IBM Domino plug-in to work properly, three symbolic links (symlinks) must be created to link to Domino’s shared object files. Installation procedures vary slightly depending on the operating system. Refer to the appropriate procedure for your operating system. Domino does not support the HP-UX operating system. Creating symbolic links for the Domino plug-in on Linux and Solaris hosts You need to perform this procedure if you want to create symbolic links for the Domino plug-in on Linux and Solaris hosts. You should not copy and paste commands directly from this document; errors (such as incorrectly transferred characters caused by line breaks and hard returns) might result. Copy and paste the commands into a text editor, verify the commands, and then enter them in the CLI console. The paths provided in the following steps refer to the 32-bit systems; 64-bit systems must create simlinks to /usr/lib64 instead of /usr/lib.
    [Show full text]
  • System Calls System Calls
    System calls We will investigate several issues related to system calls. Read chapter 12 of the book Linux system call categories file management process management error handling note that these categories are loosely defined and much is behind included, e.g. communication. Why? 1 System calls File management system call hierarchy you may not see some topics as part of “file management”, e.g., sockets 2 System calls Process management system call hierarchy 3 System calls Error handling hierarchy 4 Error Handling Anything can fail! System calls are no exception Try to read a file that does not exist! Error number: errno every process contains a global variable errno errno is set to 0 when process is created when error occurs errno is set to a specific code associated with the error cause trying to open file that does not exist sets errno to 2 5 Error Handling error constants are defined in errno.h here are the first few of errno.h on OS X 10.6.4 #define EPERM 1 /* Operation not permitted */ #define ENOENT 2 /* No such file or directory */ #define ESRCH 3 /* No such process */ #define EINTR 4 /* Interrupted system call */ #define EIO 5 /* Input/output error */ #define ENXIO 6 /* Device not configured */ #define E2BIG 7 /* Argument list too long */ #define ENOEXEC 8 /* Exec format error */ #define EBADF 9 /* Bad file descriptor */ #define ECHILD 10 /* No child processes */ #define EDEADLK 11 /* Resource deadlock avoided */ 6 Error Handling common mistake for displaying errno from Linux errno man page: 7 Error Handling Description of the perror () system call.
    [Show full text]
  • 1994 Hearings on Software Patents
    United States Patent and Trademark Office Public Hearing on Use of the Patent System to Protect Software-Related Inventions Transcript of Proceedings Wednesday, January 26, 1994 Thursday, January 27, 1994 9:00 a.m. to 5:00 p.m. Before Bruce A. Lehman Assistant Secretary of Commerce and Commissioner of Patents and Trademarks Location: San Jose Convention Center 408 Almaden Avenue San Jose, California UNITED STATES PATENT AND TRADEMARK OFFICE Public Hearing on Patent Protection for Software-Related Inventions San Jose, California -- January 26-27, 1994 Table of Participants Before: Bruce A. Lehman Assistant Secretary of Commerce and Commissioner of Patents and Trademarks United States Patent and Trademark Office The Panel: Ginger Lew General Counsel-Designate United States Department of Commerce Lawrence Goffney Assistant Commissioner for Patents-Designate United States Patent and Trademark Office Micheal K. Kirk Assistant Commissioner for External Affairs United States Patent and Trademark Office Jeffrey P. Kushan Attorney-Advisor United States Patent and Trademark Office Recording Technicians: Karl Henderscheid Support Office Services 52 Second Street, Third Floor San Francisco, CA 94104 (415) 391-4578 Trascriber: Milton Hare Rogershare Transcribers 541 Maud Avenue San Leandro, CA 94577 (510) 357-8220 - ii - UNITED STATES PATENT AND TRADEMARK OFFICE Public Hearing on Patent Protection for Software-Related Inventions San Jose, California -- January 26-27, 1994 Witnesses January 26, 1994 January 27, 1994 Mr. Clark Mr. Fiddler VideoDiscovery Wind River Systems Mr. Poppa Mr. Warren StorageTek Autodesk, Inc. Mr. Ryan Ms. O'Hare Intellectual Property Owners, Inc. Mr. Glenn Mr. LeFaivre Intellectual Property Section of the State Bar of California Apple Computer Mr.
    [Show full text]
  • System Calls and I/O
    System Calls and I/O CS 241 January 27, 2012 Copyright ©: University of Illinois CS 241 Staff 1 This lecture Goals Get you familiar with necessary basic system & I/O calls to do programming Things covered in this lecture Basic file system calls I/O calls Signals Note: we will come back later to discuss the above things at the concept level Copyright ©: University of Illinois CS 241 Staff 2 System Calls versus Function Calls? Copyright ©: University of Illinois CS 241 Staff 3 System Calls versus Function Calls Function Call Process fnCall() Caller and callee are in the same Process - Same user - Same “domain of trust” Copyright ©: University of Illinois CS 241 Staff 4 System Calls versus Function Calls Function Call System Call Process Process fnCall() sysCall() OS Caller and callee are in the same Process - Same user - OS is trusted; user is not. - Same “domain of trust” - OS has super-privileges; user does not - Must take measures to prevent abuse Copyright ©: University of Illinois CS 241 Staff 5 System Calls System Calls A request to the operating system to perform some activity System calls are expensive The system needs to perform many things before executing a system call The computer (hardware) saves its state The OS code takes control of the CPU, privileges are updated. The OS examines the call parameters The OS performs the requested function The OS saves its state (and call results) The OS returns control of the CPU to the caller Copyright ©: University of Illinois CS 241 Staff 6 Steps for Making a System Call
    [Show full text]
  • File Formats
    man pages section 4: File Formats Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 817–3945–10 September 2004 Copyright 2004 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, docs.sun.com, AnswerBook, AnswerBook2, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • Mac Keyboard Shortcuts Cut, Copy, Paste, and Other Common Shortcuts
    Mac keyboard shortcuts By pressing a combination of keys, you can do things that normally need a mouse, trackpad, or other input device. To use a keyboard shortcut, hold down one or more modifier keys while pressing the last key of the shortcut. For example, to use the shortcut Command-C (copy), hold down Command, press C, then release both keys. Mac menus and keyboards often use symbols for certain keys, including the modifier keys: Command ⌘ Option ⌥ Caps Lock ⇪ Shift ⇧ Control ⌃ Fn If you're using a keyboard made for Windows PCs, use the Alt key instead of Option, and the Windows logo key instead of Command. Some Mac keyboards and shortcuts use special keys in the top row, which include icons for volume, display brightness, and other functions. Press the icon key to perform that function, or combine it with the Fn key to use it as an F1, F2, F3, or other standard function key. To learn more shortcuts, check the menus of the app you're using. Every app can have its own shortcuts, and shortcuts that work in one app may not work in another. Cut, copy, paste, and other common shortcuts Shortcut Description Command-X Cut: Remove the selected item and copy it to the Clipboard. Command-C Copy the selected item to the Clipboard. This also works for files in the Finder. Command-V Paste the contents of the Clipboard into the current document or app. This also works for files in the Finder. Command-Z Undo the previous command. You can then press Command-Shift-Z to Redo, reversing the undo command.
    [Show full text]
  • Alias Manager 4
    CHAPTER 4 Alias Manager 4 This chapter describes how your application can use the Alias Manager to establish and resolve alias records, which are data structures that describe file system objects (that is, files, directories, and volumes). You create an alias record to take a “fingerprint” of a file system object, usually a file, that you might need to locate again later. You can store the alias record, instead of a file system specification, and then let the Alias Manager find the file again when it’s needed. The Alias Manager contains algorithms for locating files that have been moved, renamed, copied, or restored from backup. Note The Alias Manager lets you manage alias records. It does not directly manipulate Finder aliases, which the user creates and manages through the Finder. The chapter “Finder Interface” in Inside Macintosh: Macintosh Toolbox Essentials describes Finder aliases and ways to accommodate them in your application. ◆ The Alias Manager is available only in system software version 7.0 or later. Use the Gestalt function, described in the chapter “Gestalt Manager” of Inside Macintosh: Operating System Utilities, to determine whether the Alias Manager is present. Read this chapter if you want your application to create and resolve alias records. You might store an alias record, for example, to identify a customized dictionary from within a word-processing document. When the user runs a spelling checker on the document, your application can ask the Alias Manager to resolve the record to find the correct dictionary. 4 To use this chapter, you should be familiar with the File Manager’s conventions for Alias Manager identifying files, directories, and volumes, as described in the chapter “Introduction to File Management” in this book.
    [Show full text]
  • Answers to Even- Numbered Exercises 5
    Answers to Even- Numbered Exercises 5 from page 163 1. What does the shell ordinarily do while a command is executing? What should you do if you do not want to wait for a command to finish before running another command? 2. Using sort as a filter, rewrite the following sequence of commands: $ sort list > temp $ lpr temp $ rm temp $ cat list | sort | lpr 3. What is a PID number? Why are they useful when you run processes in the background? 4. Assume that the following files are in the working directory: $ ls intro notesb ref2 section1 section3 section4b notesa ref1 ref3 section2 section4a sentrev Give commands for each of the following, using wildcards to express filenames with as few characters as possible. 1 2 Chapter 5 Answers to Exercises a. List all files that begin with section. $ ls section* b. List the section1, section2, and section3 files only. $ ls section[1-3] c. List the intro file only. $ ls i* d. List the section1, section3, ref1, and ref3 files. $ ls *[13] 5. Refer to the documentation of utilities in Part III or the man pages to determine what commands will a. Output the number of lines in the standard input that contain the word a or A. b. Output only the names of the files in the working directory that contain the pattern $(. c. List the files in the working directory in their reverse alphabetical order. d. Send a list of files in the working directory to the printer, sorted by size. 6. Give a command to a. Redirect the standard output from a sort command into a file named phone_list.
    [Show full text]
  • Efficient Metadata Management in Cloud Computing
    Send Orders for Reprints to [email protected] The Open Cybernetics & Systemics Journal, 2015, 9, 1485-1489 1485 Open Access Efficient Metadata Management in Cloud Computing Yu Shuchun1,* and Huang Bin2 1Deptment of Computer Engineering, Huaihua University, Huaihua, Hunan, 418008, P.R. China; 2School of Mathmatic and Computer Science, Guizhou Normal University, Guiyang, Guizhou, 550001, P.R. China Abstract: Existing metadata management methods bring about lower access efficiency in solving the problem of renam- ing directory. This paper proposes a metadata management method based on directory path redirection (named as DPRD) which includes the data distribution method based on directory path and the directory renaming method based on directory path redirection. Experiments show that DPRD effectively solves the lower access efficiency caused by the renaming di- rectory. Keywords: Cloud computing, directory path, redirection, metadata. 1. INTRODUCTION renaming a directory. The directory path fixed numbering (marked as DPFN) [10, 11] endows the globally unique ID With the prevalence of Internet application and data- (DPID) for each directory path, and DPID remains un- intensive computing, there are many new application sys- changed in the life cycle of the directory path, and the meta- tems in cloud computing environment. These systems are data of all files (or sub-directories) in the directory path will mainly characterized by [1-3]: (1) The enormous files stored be placed and achieved according to its hash value of DPID. in the system, some even reach trillions level, and it still in- It can solve the metadata migration issue caused by directory crease rapidly; (2) The user number and daily access are renaming, but it uses a directory path index server to manage quire enormous, reaching billions level.
    [Show full text]
  • Openvms: an Introduction
    The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme VMS Table of Contents Chapter 7 OpenVMS: An Introduction.............................................................................. 7.1 History..........................................................................................................................2 7.1.1 Today........................................................................................................................3 7.1.1.1 Popular VMS Software..........................................................................................4 7.1.2 VMS, DCL................................................................................................................4 Chapter 8 Getting Started with OpenVMS........................................................................ 8.1 Starting Up...................................................................................................................7 8.1.1 Finishing Your VMS Session...................................................................................7 8.1.1.1 Reconnecting..........................................................................................................7 8.1.2 Entering Commands..................................................................................................8 8.1.2.1 Retrieving Previous Commands............................................................................9 8.1.2.2 Aborting Screen Output.........................................................................................9
    [Show full text]
  • 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.
    [Show full text]