DOCSLIB.ORG

OS/2 Workplace Shell Configuration Techniques

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
OS/2 Workplace Shell Configuration Techniques OS/2 Workplace Shell Configuration Techniques Document Number GG24-4201-00 August 1994 International Technical Support Organization Boca Raton Center Take Note! Before using this information and the product it supports, be sure to read the general information under “Special Notices” on page xvii. First Edition (August 1994) This edition applies to OS/2 Version 2.1. Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below. An ITSO Technical Bulletin Evaluation Form for reader′s feedback appears facing Chapter 1. If the form has been removed, comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. 91J, Building 235-2 Internal Zip 4423 901 NW 51st Street Boca Raton, Florida 33431-1328 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. Copyright International Business Machines Corporation 1994. All rights reserved. Note to U.S. Government Users — Documentation related to restricted rights — Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Abstract This document describes interfaces to the Workplace Shell of OS/2 Version 2.1. It provides a discussion and examples of using the CONFIG.SYS, .RC files, .INI files and programs to install, customize and distribute the OS/2 Workplace Shell in a stand-alone and distributed environment. This document was written for IBM Technical Professionals. Some knowledge of OS/2 is assumed. (290 pages) Copyright IBM Corp. 1994 iii iv OS/2 Workplace Shell Configuration Techniques Contents Abstract . iii Figures . ix Tables . xv Special Notices . xvii Preface . xix How This Document is Organized ....................... xix Related Publications . xx International Technical Support Organization Publications ......... xx Acknowledgments . xxi Chapter 1. Introduction . 1 Chapter 2. Changing the Desktop via the CONFIG.SYS ............ 5 2.1 Desktop Loading Statements ......................... 7 2.1.1 Restarting Applications .......................... 7 2.1.2 Shutdown Alternatives . 8 2.1.3 PROTSHELL= . 8 2.1.4 SET RUNWORKPLACE= . 9 2.2 Single Application Access .......................... 9 2.2.1 Using AmiPro for OS/2 as a Desktop ................ 11 2.2.2 Using DeScribe as a Desktop ..................... 11 2.2.3 Using CorelDRAW! as a Desktop ................... 11 2.2.4 Using Aldus PageMaker for Windows as a Desktop ........ 13 2.3 Multiple Application Access via File Managers ............. 13 2.3.1 Using the WIN-OS/2 File Manager as a Desktop .......... 13 2.3.2 Using Norton Commander as a Desktop .............. 14 2.4 Application Access via CMD.EXE ..................... 14 2.4.1 OS/2 Full Screen Interface ....................... 14 2.4.2 OS/2 Window Interface ......................... 15 2.5 Multiple Application Access via .CMD Files ............... 15 2.5.1 Multiple Application Access Using STARTUP.CMD ........ 16 2.5.2 SET RUNWORKPLACE=user.CMD . 17 2.6 WIN-OS/2 as Your Desktop ......................... 18 Chapter 3. Using the Resource Files to Change the Desktop ....... 19 3.1 The Default .INI Files ............................. 20 Copyright IBM Corp. 1994 v 3.2 The Default .RC Files ............................ 20 3.3 The MAKEINI Compiler ........................... 21 3.3.1 Making a New .INI File ......................... 22 3.3.2 Changing an Existing .INI File ..................... 24 3.3.3 The LOCK.RC File ............................ 25 3.4 The Structure of .RC File Commands ................... 26 3.5 The User .RC File Structure ......................... 28 3.5.1 RC File Header ............................. 29 3.5.2 System Information . 30 3.5.3 The International Information ..................... 40 3.5.4 Desktop Settings . 42 3.5.5 Object Definitions . 44 3.5.6 Color and Display Settings ...................... 84 3.6 The System.RC File Structure ....................... 86 3.7 Examples of RC Files ............................ 87 3.7.1 Creating a New Desktop ........................ 87 3.7.2 Using an Existing Desktop ....................... 109 Chapter 4. Using .INI files to Change the Desktop .............. 119 4.1 The Structure of a .INI File ......................... 120 4.1.1 The Difference Between OS2.INI and OS2SYS.INI ......... 120 4.2 Reading and Writing Data to the .INI Files ................ 120 4.2.1 Retrieving All Keys for a Single Application ............ 122 4.2.2 Retrieving a Single Key Value .................... 125 4.2.3 Setting a Single Key Value ...................... 126 4.3 Changing the Desktop Settings ...................... 127 4.3.1 System Settings . 127 4.3.2 Changing Country Settings ...................... 148 4.3.3 Changing Your Colors ......................... 166 4.3.4 Changing the System Fonts ...................... 172 4.3.5 Changing Your Mouse Mappings ................... 178 4.3.6 Changing Other Mouse Settings ................... 182 4.3.7 Changing Your Keyboard Mappings ................. 185 4.3.8 Workplace Shell Setup for Users with Special Needs ....... 189 4.3.9 Installing Your Own Fonts ....................... 196 4.4 Binary Data in the .INI Files ......................... 197 Chapter 5. CID and The WorkPlace Shell ................... 201 5.1 CONFIG.SYS . 201 5.1.1 ConfigSysLine . 202 5.1.2 UserExit and CMD File ......................... 202 5.2 RC Files . 203 5.3 Customization of INI ............................. 205 vi OS/2 Workplace Shell Configuration Techniques 5.3.1 REXX the INI Files ............................ 205 5.4 REXX from the LCU Command File .................... 208 5.4.1 OS2IniData Keyword . 213 5.5 Combined Scenario . 215 5.6 CID Conclusions . 216 Appendix A. ITSO DESKTOPS Utilities .................... 217 A.1 Using PrfReset . 218 A.2 Deleting Desktops . 222 A.3 Managing Multiple Desktops on One Machine ............. 223 A.3.1 Installing the DLL ............................ 224 A.3.2 Creating a New Desktop ........................ 224 A.3.3 Switching Desktops . 226 A.4 Moving Desktops from One Machine to Another ............ 229 A.4.1 Exporting a Desktop Using the Desktops Program ........ 229 A.4.2 Importing a Desktop Using the Desktops Program ........ 230 A.4.3 From the Command Line ....................... 230 A.5 Recovering From a Corrupted Desktop ................. 232 Appendix B. Associating Your Data Files ................... 235 B.1 What is An Association? .......................... 235 B.2 Associating a Single File .......................... 235 B.3 Associating Groups of Files ........................ 239 B.3.1 Creating Group Associations ..................... 239 B.3.2 Default Group Associations ...................... 242 B.4 Template Associations . 242 B.4.1 Changing an Existing Template ................... 243 B.4.2 Creating a New Template ....................... 244 B.5 Using Associations .............................. 245 B.5.1 Project Based Organization ...................... 245 B.5.2 Type Based Organization ....................... 246 B.6 Work Area Folders and Associations ................... 247 B.6.1 Setting Up a Work Area Folder .................... 248 Appendix C. RC Syntax Diagrams ....................... 251 C.1 Keyword Instructions . 253 C.2 PM_InstallObject Keyword Instructions .................. 253 Appendix D. Deskman/2 ............................. 255 D.1 DeskMan/2 . 255 D.2 DM/2 Image . 261 D.3 VUEMan/2 . 262 D.4 DeskMan/2 User′s Guide .......................... 267 Contents vii D.5 DM/2 Command Line Interface ...................... 268 D.5.1 Installation and Configuration Command Files .......... 268 D.5.2 Operation Command Files. ...................... 268 D.5.3 Object Creation Command Files ................... 269 Appendix E. Alternate Shells . 271 E.1 Why Use a Different Shell? ......................... 271 E.2 TShell . 272 E.2.1 Programming the Start Group .................... 273 E.2.2 Available REXX Functions ....................... 275 E.3 MShell . 276 Appendix F. GG24-4201 Diskette Contents .................. 279 Index . 281 viii OS/2 Workplace Shell Configuration Techniques Figures 1. A User′s Desktop . 3 2. An Administrator′s Desktop ......................... 3 3. CONFIG.SYS Modification for Single Application Environment . 10 4. Structure of STARTUP.CMD for Single Application Environment . 10 5. STARTUP.CMD to Load AmiPro for OS/2 . 11 6. STARTUP.CMD to Load DeScribe . 11 7. STARTUP.CMD to Load CorelDRAW! . 12 8. STARTUP.CMD to Load Aldus Pagemaker for Windows . 13 9. STARTUP.CMD to Load WIN-OS/2 File Manager . 13 10. STARTUP.CMD to Load Norton Commander′s File Manager .... 14 11. CONFIG.SYS to Load an OS/2 Full Screen as the Desktop ..... 14 12. CONFIG.SYS to Load an OS/2 Window as the Desktop ........ 15 13. STARTUP.CMD to Load Multiple Applications ............. 16 14. STARTUP.CMD to Load Multiple Applications and Communications 16 15. STARTUP.CMD to Load WIN-OS/2 as the Desktop .......... 18 16. Workplace Shell INI Error ......................... 23 17. A Comment Line in an .RC File ...................... 28 18. Using ? as a Drive Letter ......................... 28 19. RC File Header ............................... 29 20. Default .RC File Border Width Setting .................. 30 21. Desktop With a Border Width of 50 ................... 31 22. The Confirmations Page in the System Setting Notebook ...... 31 23. Examples of PM_DefaultSetup .....................
Load more

Recommended publications
  • 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]
  • UKUI: a Lightweight Desktop Environment Based on Pluggable
    2016 International Conference on Artificial Intelligence and Computer Science (AICS 2016) ISBN: 978-1-60595-411-0 UKUI: A Lightweight Desktop Environment Based on Pluggable Framework for Linux Distribution Jie YU1, Lu SI1,*, Jun MA1, Lei LUO1, Xiao-dong LIU1, Ya-ting KUANG2, Huan PENG2, Rui LI1, Jin-zhu KONG2 and Qing-bo WU1 1College of Computer, National University of Defense Technology, Changsha, China 2Tianjin KYLIN Information Technology Co., Ltd, Tianjin, China *[email protected] *Corresponding author Keywords: Desktop environment, Ubuntu, User interface. Abstract. Ubuntu is an operating system with Linux kernel based on Debian and distributed as free and open-source software. It uses Unity as its default desktop environment, which results in more difficulties of usage for Microsoft Windows users. In this paper, we present a lightweight desktop environment named UKUI based on UbuntuKylin, the official Chinese version of Ubuntu, for Linux distribution. It is designed as a pluggable framework and provides better user experience during human-computer interaction. In order to evaluate the performance of UKUI, a set of testing bench suits were performed on a personal computer. Overall, the results showed that UKUI has better performance compared with Unity. Introduction Linux is a freely available operating system (OS) originated by Linux Torvalds and further developed by thousands of others. Typically, Linux is packaged in a form known as a Linux distribution for both desktop and server use. Some of the most popular mainstream Linux distributions are Red Hat [1], Ubuntu [2], Arch [3], openSUSY [4], Gentoo [5], etc. There are several desktop environments available for nowadays modern Linux distributions, such as XFCE [6], GNOME [7], KDE [8] and LXDE [9].
    [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]
  • Powershell Integration with Vmware View 5.0
    PowerShell Integration with VMware® View™ 5.0 TECHNICAL WHITE PAPER PowerShell Integration with VMware View 5.0 Table of Contents Introduction . 3 VMware View. 3 Windows PowerShell . 3 Architecture . 4 Cmdlet dll. 4 Communication with Broker . 4 VMware View PowerCLI Integration . 5 VMware View PowerCLI Prerequisites . 5 Using VMware View PowerCLI . 5 VMware View PowerCLI cmdlets . 6 vSphere PowerCLI Integration . 7 Examples of VMware View PowerCLI and VMware vSphere PowerCLI Integration . 7 Passing VMs from Get-VM to VMware View PowerCLI cmdlets . 7 Registering a vCenter Server . .. 7 Using Other VMware vSphere Objects . 7 Advanced Usage . 7 Integrating VMware View PowerCLI into Your Own Scripts . 8 Scheduling PowerShell Scripts . 8 Workflow with VMware View PowerCLI and VMware vSphere PowerCLI . 9 Sample Scripts . 10 Add or Remove Datastores in Automatic Pools . 10 Add or Remove Virtual Machines . 11 Inventory Path Manipulation . 15 Poll Pool Usage . 16 Basic Troubleshooting . 18 About the Authors . 18 TECHNICAL WHITE PAPER / 2 PowerShell Integration with VMware View 5.0 Introduction VMware View VMware® View™ is a best-in-class enterprise desktop virtualization platform. VMware View separates the personal desktop environment from the physical system by moving desktops to a datacenter, where users can access them using a client-server computing model. VMware View delivers a rich set of features required for any enterprise deployment by providing a robust platform for hosting virtual desktops from VMware vSphere™. Windows PowerShell Windows PowerShell is Microsoft’s command line shell and scripting language. PowerShell is built on the Microsoft .NET Framework and helps in system administration. By providing full access to COM (Component Object Model) and WMI (Windows Management Instrumentation), PowerShell enables administrators to perform administrative tasks on both local and remote Windows systems.
    [Show full text]
  • Managing Files with Sterling Connect:Direct File Agent 1.4.0.1
    Managing Files with Sterling Connect:Direct File Agent 1.4.0.1 IBM Contents Managing Files with Sterling Connect:Direct File Agent.......................................... 1 Sterling Connect:Direct File Agent Overview.............................................................................................. 1 How to Run Sterling Connect:Direct File Agent.......................................................................................... 2 Sterling Connect:Direct File Agent Logging.................................................................................................3 Sterling Connect:Direct File Agent Configuration Planning........................................................................ 3 Sterling Connect:Direct File Agent Worksheet ...........................................................................................4 Considerations for a Large Number of Watch Directories.......................................................................... 6 Modifying MaxFileSize............................................................................................................................ 6 Modifying MaxBackupIndex...................................................................................................................6 Considerations for a Large Number of Files in a Watch Directory..............................................................7 Sterling Connect:Direct File Agent Configuration Scenarios...................................................................... 7 Scenario:Detecting
    [Show full text]
  • Shell Script & Advance Features of Shell Programming
    Kirti Kaushik et al, International Journal of Computer Science and Mobile Computing, Vol.4 Issue.4, April- 2015, pg. 458-462 Available Online at www.ijcsmc.com International Journal of Computer Science and Mobile Computing A Monthly Journal of Computer Science and Information Technology ISSN 2320–088X IJCSMC, Vol. 4, Issue. 4, April 2015, pg.458 – 462 RESEARCH ARTICLE Shell Script & Advance Features of Shell Programming Kirti Kaushik* Roll No.15903, CS, Department of Computer science, Dronacharya College of Engineering, Gurgaon-123506, India Email: [email protected] Jyoti Yadav Roll No. 15040, CS, Department of Applied Computer science, Dronacharya College of Engineering, Gurgaon-123506, India Email: [email protected] Kriti Bhatia Roll No. 15048, CS, Department of Applied Computer science, Dronacharya College of Engineering, Gurgaon-123506, India Email: [email protected] Abstract-- In this research paper, the idea of shell scripting and writing computer programs is examined and different parts of shell programming are likewise contemplated. A shell script is a PC system intended to be controlled by the UNIX shell which is a charge line translator. The different tongues of shell scripts are thought to be scripting dialects. Regular operations performed by shell scripts incorporate document control, program execution, and printing content. A shell script can give an advantageous variety ofa framework order where unique environment settings, charge alternatives, or post-transforming apply naturally, yet in a manner that permits the new script to still go about as a completely typical UNIX summon. The real ideas like Programming in the Borne and C-shell, in which it would be clarified that how shell programming could be possible in Borne and C-shell.
    [Show full text]
  • Where Do You Want to Go Today? Escalating
    Where Do You Want to Go Today? ∗ Escalating Privileges by Pathname Manipulation Suresh Chari Shai Halevi Wietse Venema IBM T.J. Watson Research Center, Hawthorne, New York, USA Abstract 1. Introduction We analyze filename-based privilege escalation attacks, In this work we take another look at the problem of where an attacker creates filesystem links, thereby “trick- privilege escalation via manipulation of filesystem names. ing” a victim program into opening unintended files. Historically, attention has focused on attacks against priv- We develop primitives for a POSIX environment, provid- ileged processes that open files in directories that are ing assurance that files in “safe directories” (such as writable by an attacker. One classical example is email /etc/passwd) cannot be opened by looking up a file by delivery in the UNIX environment (e.g., [9]). Here, an “unsafe pathname” (such as a pathname that resolves the mail-delivery directory (e.g., /var/mail) is often through a symbolic link in a world-writable directory). In group or world writable. An adversarial user may use today's UNIX systems, solutions to this problem are typ- its write permission to create a hard link or symlink at ically built into (some) applications and use application- /var/mail/root that resolves to /etc/passwd. A specific knowledge about (un)safety of certain directories. simple-minded mail-delivery program that appends mail to In contrast, we seek solutions that can be implemented in the file /var/mail/root can have disastrous implica- the filesystem itself (or a library on top of it), thus providing tions for system security.
    [Show full text]
  • An Overview of the Jumplist Configuration File in Windows 7
    Journal of Digital Forensics, Security and Law Volume 7 Number 1 Article 2 2012 An Overview of the Jumplist Configuration File in Windows 7 Harjinder S. Lallie University of Warwick, Coventry Parmjit S. Bains University of Derby, School of Computing and Mathematics Follow this and additional works at: https://commons.erau.edu/jdfsl Part of the Computer Engineering Commons, Computer Law Commons, Electrical and Computer Engineering Commons, Forensic Science and Technology Commons, and the Information Security Commons Recommended Citation Lallie, Harjinder S. and Bains, Parmjit S. (2012) "An Overview of the Jumplist Configuration File in Windows 7," Journal of Digital Forensics, Security and Law: Vol. 7 : No. 1 , Article 2. DOI: https://doi.org/10.15394/jdfsl.2012.1110 Available at: https://commons.erau.edu/jdfsl/vol7/iss1/2 This Article is brought to you for free and open access by the Journals at Scholarly Commons. It has been accepted for inclusion in Journal of Digital Forensics, Security and Law by an authorized administrator of (c)ADFSL Scholarly Commons. For more information, please contact [email protected]. Journal of Digital Forensics, Security and Law, Vol. 7(1) An Overview of the Jumplist Configuration File in Windows 7 Harjinder Singh Lalli University of Warwick, International Digital Laboratory (WMG), University of Warwick, Coventry, CV4 7AL, UK; [email protected] Parmjit Singh Bains University of Derby, School of Computing and Mathematics, Kedleston Road, Derby, DE22 1GB, UK; [email protected] ABSTRACT The introduction of Jumplists in Windows 7 was an important feature from a forensic examiners viewpoint. Jumplist configuration files can provide the examiner with a wealth of information relating to file access and in particular: dates/times, Volume GUIDs and unique file object IDs relating to those files.
    [Show full text]
  • Openvms Security
    OpenVMS Security Presented by Paul Williams PARSEC Group 999 18th Street, Suite 1725 Denver, CO 80202 www.parsec.com | 888-4-PARSEC To Download this Presentation, please visit: http://www.parsec.com/public/openvmssecurity.pdf To E-mail Paul [email protected] www.parsec.com | 888-4-PARSEC Outline • OpenVMS Security Design • Physical Security • Object Security • UIC/ACL Security • User Access • Break-in Detection • Network and Internet Considerations • Encrypted Network Communication • Kerberos • Secure Socket Layer (SSL) Goals • Discuss the important points and consideration of OpenVMS Security • Concentrate on the mechanics and mechanisms of OpenVMS features. • Show how OpenVMS is one of the most secure operating systems on the market. OpenVMS Security Design • Security was designed into OpenVMS since V1.0 • Many different levels of security in OpenVMS Physical Security Object Security User Management Network Security • Has never had a virus Physical Security • System • System Console • Storage devices and media System Disk Data and Database Volumes Backups • Network devices and media Physical Security: System • Increase system reliability through restricted access Prevent intentional tampering and outage Prevent outage due to accidents • Prevent Front Panel Access Halts Reset/initializations Power switch/source Power on action settings (VAX) switch Physical Security: Console • Can be a big security hole for OpenVMS Anyone with physical access to the console can break into OpenVMS buy getting into the SYSBOOT utility. Then OpenVMS can be broken into: Buy redirecting startup Buy changing system parameters Physical Security: Getting to SYSBOOT on the Integrity Console Example • On the Integrity shutdown to the EFI Boot Manager and select the EFI Shell and create a alias.
    [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]
  • What Is the Shell? • the Login Shell
    03 0672324903 Ch03 2/3/03 1:41 PM Page 41 3 IN THIS CHAPTER • The Kernel and the Utilities What Is the Shell? • The Login Shell • Typing Commands to the Shell In this chapter you’ll learn what the shell is and what it does. • The Shell’s Responsibilities The Kernel and the Utilities The Unix system is itself logically divided into two pieces: the kernel and the utilities (see Figure 3.1). Unix system Utilities kernel disks Memory FIGURE 3.1 The Unix system. The kernel is the heart of the Unix system and resides in the computer’s memory from the time the computer is turned on and booted until the time it is shut down. The utilities, on the other hand, reside on the computer’s disk and are only brought into memory as requested. Virtually every command you know under the Unix system is classified as a utility; therefore, the program resides on the disk and is brought into memory only when you request that the command be executed. So, for example, when you execute the date command, the Unix system loads the program called date from the computer’s disk into memory and initiates its execution. The shell, too, is a utility program. It is loaded into memory for execution whenever you log in to the system. 03 0672324903 Ch03 2/3/03 1:41 PM Page 42 42 CHAPTER 3 What Is the Shell? In fact, it’s worth learning the precise sequence of events that occurs when the first shell on a terminal or window starts up.
    [Show full text]
  • Mac OS X: an Introduction for Support Providers
    Mac OS X: An Introduction for Support Providers Course Information Purpose of Course Mac OS X is the next-generation Macintosh operating system, utilizing a highly robust UNIX core with a brand new simplified user experience. It is the first successful attempt to provide a fully-functional graphical user experience in such an implementation without requiring the user to know or understand UNIX. This course is designed to provide a theoretical foundation for support providers seeking to provide user support for Mac OS X. It assumes the student has performed this role for Mac OS 9, and seeks to ground the student in Mac OS X using Mac OS 9 terms and concepts. Author: Robert Dorsett, manager, AppleCare Product Training & Readiness. Module Length: 2 hours Audience: Phone support, Apple Solutions Experts, Service Providers. Prerequisites: Experience supporting Mac OS 9 Course map: Operating Systems 101 Mac OS 9 and Cooperative Multitasking Mac OS X: Pre-emptive Multitasking and Protected Memory. Mac OS X: Symmetric Multiprocessing Components of Mac OS X The Layered Approach Darwin Core Services Graphics Services Application Environments Aqua Useful Mac OS X Jargon Bundles Frameworks Umbrella Frameworks Mac OS X Installation Initialization Options Installation Options Version 1.0 Copyright © 2001 by Apple Computer, Inc. All Rights Reserved. 1 Startup Keys Mac OS X Setup Assistant Mac OS 9 and Classic Standard Directory Names Quick Answers: Where do my __________ go? More Directory Names A Word on Paths Security UNIX and security Multiple user implementation Root Old Stuff in New Terms INITs in Mac OS X Fonts FKEYs Printing from Mac OS X Disk First Aid and Drive Setup Startup Items Mac OS 9 Control Panels and Functionality mapped to Mac OS X New Stuff to Check Out Review Questions Review Answers Further Reading Change history: 3/19/01: Removed comment about UFS volumes not being selectable by Startup Disk.
    [Show full text]