DOCSLIB.ORG

An Introduction to Computing at MSI

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
An Introduction to Computing at MSI An Introduction to Computing at MSI University of Minnesota Supercomputing Institute for Advanced Computational Research June 8, 2010 1 Contents 1 Setting up your account 3 2 UNIX Tutorial 3 2.1 Basic Commands, Paths and Directories . 3 2.1.1 Basic Commands . 3 2.1.2 Paths . 5 2.2 Files . 6 2.2.1 Copying, moving, removing, and renaming . 6 2.2.2 Displaying and searching . 6 2.2.3 Permissions . 6 2.3 Redirection and Pipes . 7 2.3.1 Input and Output Redirection . 7 2.3.2 Pipes . 8 2.4 Regular Expressions . 8 2.5 MSI Software . 9 2.6 Writing and Compiling Code . 10 3 Remote Computing and other FAQs 11 3.1 Access an MSI *nix machine from a Windows machine. 11 3.2 Access an MSI *nix machine from another *nix machine . 11 3.3 Access an MSI *nix machine from a Mac . 11 3.4 Access an MSI Windows server . 11 3.5 Upload files from to MSI computers . 12 3.6 Resetting your password . 12 3.7 Check the status of machine or resource . 12 3.8 Getting help . 12 2 This document contains command blocks, the monospaced typewriter fonts within a bounding box. They are an indication that the commands should be typed directly into the shell, or are the resulting screen output of such commands. The \#" char- acter represents a comment. If typed into the console or included in a script they are ignored by the shell. When commands are included inline they are presented in a bold font. 1 Setting up your account 1. Information pertaining to getting an account, access to laboratories, and/or su- percomputer resource allocations can be found at http://www.msi.umn.edu/ help/resource.html. If you do not have an MSI account you may request a temporary account from one of the instructors. 2. Type your username and password into the prompt. 3. Open a Unix terminal by right clicking the desktop and selecting \open new terminal." 4. Type passwd at the terminal prompt and follow the instructions to change your password. 5. Open your favorite text editor and create a .forward file in your home directory. If you do not have a favorite text editor use nedit or gedit. These text editors function similarly to Notepad on Microsoft Windows. cd nedit .forward Your mail will now be forwarded to the address you entered. 2 UNIX Tutorial 2.1 Basic Commands, Paths and Directories 2.1.1 Basic Commands • Open a shell. The exact procedure varies from machine to machine depending on the version and revision of the operating system running, but is usually 3 available by right clicking in the open desktop area and selecting an option such as \New Terminal." • Try a few commands out. Some basics are pwd (list the full path of your current location), ls (list the contents of the directory), date (print the current date and time), and whoami (prints your username). pwd /home/msi/nlabello date Fri Oct 31 11:39:14 CDT 2008 whoami nlabello Listing 1: A few basic commands. • Most commands can be customized by passing options, and these options and general instructions for using the command are included in a built in manual, known as the man page. Examine the man page for the commands above by entering man pwd, for example. Exit the man page by entering \:q" into the terminal. • Create the directory structure demonstrated in Figure 1. mkdir will create a new directory. cd will allow you to change into a directory. rmdir will remove an empty directory. Figure 1: An example directory structure. The tilda represents your home directory. • From your home directory use the ls command. Pass ls a few options to customize its behavior. cd # changes directly to your home dir ls # plain old listing of files ls -l # a "long" listing of the files ls -a # also list "hidden" files. # Any file can be hidden by starting # the file name with a "." ls -lrth # listing of files reverse sorted by # date of last modification Listing 2: ls 4 • Write a script to automate a few commands. Open a text editor and include create a file with contents similar to the box below. Save the file as \myscript." It is not necessary to include the comments in your script. #/ bin / bash # Tell the operating system this is a bash script. # The first line includes a '#' but IS NOT a comment. echo "This script will report the date and run a few" echo "simple commands." # Back ticks, (the key under ESC), # allow nested commands. # The output of the nested command is # included in the parent command. # For example, date # This way works fine. # But this way is fancier. echo "Script run time is `date`." # list files in the directory # direct the output to a new file ls -lrth > current_file_listing.txt Listing 3: A simple bash script. • Run the script as follows: ./myscript # That didn't work! OK, let's try chmod +x myscript ./myscript # It works now! Listing 4: Running a script. 2.1.2 Paths The UNIX environment supports explicit as well as relative paths. Explicit paths spell out the exact location on the file system. Relative paths use symbols to describe the location relative to the current working directory. ls . # indicates the current working directory ls .. # references the parent directory ls ~ # references your home directory cp ~/file1 . # copies a file1 from your home directory to your # present working directory cp ../file1 . # copies file1 from the directory above to your # present working directory 5 pwd # prints the present working directory Listing 5: Path examples. 2.2 Files 2.2.1 Copying, moving, removing, and renaming Files are copied using cp command. Directories are copied by passing the -r option. Files are removed with rm command, and directories are likewise removed with rm -r. Files and directories are moved and renamed with the mv command. Move, copy, rename, and remove the sample directories and files you have created until you are comfortable manipulating the file system. cp file1 file2 # copy file1 to file2 in the same directory cp file1 .. # copy file1 to the directory one up in the file hierarchy mv file1 supercool # rename file1 to supercool cp -r directory1 directory2 # make a copy of directory1 and all of its # contents in directory2 rm -r directory1 file1 file2 # remove the directory and files Listing 6: Moving, copying, and renaming files. 2.2.2 Displaying and searching Files can be read with the less command. Files can be searched with grep. head will display the first N lines of a file and tail will display the last N lines. cat dumps the entire file to the screen. less file1 # display file1 inareader tail file1 # print the last 10 lines of file1 to the screen tail -n 5 file1 # print the last 5 lines of file1 to the screen tail -n 100 file1 # print the last 100 lines of file1 to the screen head file1 # print the first 10 lines of file1 to the screen head -n 5 file1 # print the first 5 lines of file1 to the screen cat file1 # print allof file1 tothe screen grep "SCF ENERGY" file1 # print all lines in the file that contain "SCF ENERGY" Listing 7: Displaying and searching files. 2.2.3 Permissions Why was the chmod +x step necessary in the previous section? Every item in the UNIX file system is described by three sets of permissions. 6 1. Owner Permissions 2. Group Permissions 3. Other Permissions The permissions for a set may include read, write, or executable privileges, or any combination. By default the file we created did not have executable permission enabled for its owner (you). We added the appropriate permission, execution rights, with the chmod +x command. Consider the following examples. ls -lrth drwx------ 4 nlabello support 4.0K 2008-10-09 13:22 sandbox -rw------- 1 nlabello support 128 2008-10-31 13:07 forme.txt -rwxrwxrwx 1 nlabello support 132 2008-10-31 13:07 foreveryone.txt Listing 8: File permissions. The sandbox file is a directory, indicated by a d in the first column. The directory is readable, writeable/changeable, and executable by its owner. Note "exe- cutable" has a different meaning for directories than for files. Executable permission is required in addition to read permissions to access a directory. • Apply the following command to a file: chmod 755 file. Examine the permis- sions with ls -l. What did you do? The three numbers (7, 5, and 5) indicate permissions for the three sets described above - owner, group, and other. Read permissions have a value of 4, write permissions a value of 2, and executable permissions a value of 1 (r = 4, w = 2, x = 1). The sum of all three is 7, the highest access someone can have to a file. You gave the file owner all permis- sions (7), and anyone else only w and x access (5). While the other users who share your computer can read and/or run your scripts and code they will not be able to write or change the files in your directory. 2.3 Redirection and Pipes 2.3.1 Input and Output Redirection Input and output can be redirected away from the screen and into other commands. For example, cat as used thus far prints the contents of a file to the screen. The output from cat can be redirected. Input redirection is used more rarely, but some programs do not take command line arguments and instead require that you feed the data with redirects.
Load more

Recommended publications
  • Debugging with DDD
    Debugging with DDD User’s Guide and Reference Manual First Edition, for DDD Version 3.2 Last updated 2000-01-03 Andreas Zeller Debugging with DDD User’s Guide and Reference Manual Copyright c 2000 Universität Passau Lehrstuhl für Software-Systeme Innstraße 33 D-94032 Passau GERMANY Distributed by Free Software Foundation, Inc. 59 Temple Place – Suite 330 Boston, MA 02111-1307 USA ddd and this manual are available via the ddd www page. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the sections entitled “Copying” and “GNU General Public License” (see Appendix G [License], page 181) are included exactly as in the original, 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 manual into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Send questions, comments, suggestions, etc. to [email protected]. Send bug reports to [email protected]. i Short Contents Summary of DDD .............................................. 1 1 A Sample DDD Session ...................................... 5 2 Getting In and Out of DDD ................................... 15 3 The DDD Windows ........................................ 39 4 Navigating through the Code .................................. 71 5 Stopping the Program ....................................... 79 6 Running the Program ....................................... 89 7 Examining Data .........................................
    [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]
  • Your Performance Task Summary Explanation
    Lab Report: 11.2.5 Manage Files Your Performance Your Score: 0 of 3 (0%) Pass Status: Not Passed Elapsed Time: 6 seconds Required Score: 100% Task Summary Actions you were required to perform: In Compress the D:\Graphics folderHide Details Set the Compressed attribute Apply the changes to all folders and files In Hide the D:\Finances folder In Set Read-only on filesHide Details Set read-only on 2017report.xlsx Set read-only on 2018report.xlsx Do not set read-only for the 2019report.xlsx file Explanation In this lab, your task is to complete the following: Compress the D:\Graphics folder and all of its contents. Hide the D:\Finances folder. Make the following files Read-only: D:\Finances\2017report.xlsx D:\Finances\2018report.xlsx Complete this lab as follows: 1. Compress a folder as follows: a. From the taskbar, open File Explorer. b. Maximize the window for easier viewing. c. In the left pane, expand This PC. d. Select Data (D:). e. Right-click Graphics and select Properties. f. On the General tab, select Advanced. g. Select Compress contents to save disk space. h. Click OK. i. Click OK. j. Make sure Apply changes to this folder, subfolders and files is selected. k. Click OK. 2. Hide a folder as follows: a. Right-click Finances and select Properties. b. Select Hidden. c. Click OK. 3. Set files to Read-only as follows: a. Double-click Finances to view its contents. b. Right-click 2017report.xlsx and select Properties. c. Select Read-only. d. Click OK. e.
    [Show full text]
  • The Linux Command Line
    The Linux Command Line Fifth Internet Edition William Shotts A LinuxCommand.org Book Copyright ©2008-2019, William E. Shotts, Jr. This work is licensed under the Creative Commons Attribution-Noncommercial-No De- rivative Works 3.0 United States License. To view a copy of this license, visit the link above or send a letter to Creative Commons, PO Box 1866, Mountain View, CA 94042. A version of this book is also available in printed form, published by No Starch Press. Copies may be purchased wherever fine books are sold. No Starch Press also offers elec- tronic formats for popular e-readers. They can be reached at: https://www.nostarch.com. Linux® is the registered trademark of Linus Torvalds. All other trademarks belong to their respective owners. This book is part of the LinuxCommand.org project, a site for Linux education and advo- cacy devoted to helping users of legacy operating systems migrate into the future. You may contact the LinuxCommand.org project at http://linuxcommand.org. Release History Version Date Description 19.01A January 28, 2019 Fifth Internet Edition (Corrected TOC) 19.01 January 17, 2019 Fifth Internet Edition. 17.10 October 19, 2017 Fourth Internet Edition. 16.07 July 28, 2016 Third Internet Edition. 13.07 July 6, 2013 Second Internet Edition. 09.12 December 14, 2009 First Internet Edition. Table of Contents Introduction....................................................................................................xvi Why Use the Command Line?......................................................................................xvi
    [Show full text]
  • 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]
  • The Focus - Issue 36
    Contents The Focus - Issue 36 A Publication for ANSYS Users Contents Feature Articles ● Linux & ANSYS: Lessons Learned ● Backup Tool ● Design Modeler FAQ On the Web ● APDL Customization course notes now available for purchase ● ANSYS and MathCAD ● ANSYS Acquires Century Dynamics Resources ● PADT Support: How can we help? ● Upcoming Training at PADT ● About The Focus ❍ The Focus Library ❍ Contributor Information ❍ Subscribe / Unsubscribe ❍ Legal Disclaimer http://www.padtinc.com/epubs/focus/common/contents.asp [3/28/2005 9:06:12 AM] Linux & ANSYS: Lessons Learned The Focus - Issue 36 A Publication for ANSYS Users Linux & ANSYS: Lessons Learned by Eric Miller, PADT Every couple of years, the computing picture for analysts gets turned upside down. For a long time now the industry has been moving from Unix workstations to Windows/Intel desktop machines. The wintel price/performance has been fantastic, the IT guys are happier, and all of that productivity software that you spend so much time with runs in the same spot. We have been happy with a stable and known environment. However, accepting the fact that unless you work for a big company that can buy some Unix servers, you just don’t have an easy way to get some extra horsepower other then getting a new box. Then along comes this Finnish guy that may or may not have been named after Lucy’s little brother. With not much of a life and a very large brain, he popped out the majority of a complete and free version of Unix that anyone can use, breaking the stranglehold of (expensive) proprietary Unix OS’s that ran on (expensive) proprietary hardware.
    [Show full text]
  • File Systems
    File Systems Profs. Bracy and Van Renesse based on slides by Prof. Sirer Storing Information • Applications could store information in the process address space • Why is this a bad idea? – Size is limited to size of virtual address space – The data is lost when the application terminates • Even when computer doesn’t crash! – Multiple process might want to access the same data File Systems • 3 criteria for long-term information storage: 1. Able to store very large amount of information 2. Information must survive the processes using it 3. Provide concurrent access to multiple processes • Solution: – Store information on disks in units called files – Files are persistent, only owner can delete it – Files are managed by the OS File Systems: How the OS manages files! File Naming • Motivation: Files abstract information stored on disk – You do not need to remember block, sector, … – We have human readable names • How does it work? – Process creates a file, and gives it a name • Other processes can access the file by that name – Naming conventions are OS dependent • Usually names as long as 255 characters is allowed • Windows names not case sensitive, UNIX family is File Extensions • Name divided into 2 parts: Name+Extension • On UNIX, extensions are not enforced by OS – Some applications might insist upon them • Think: .c, .h, .o, .s, etc. for C compiler • Windows attaches meaning to extensions – Tries to associate applications to file extensions File Access • Sequential access – read all bytes/records from the beginning – particularly convenient for magnetic tape • Random access – bytes/records read in any order – essential for database systems File Attributes • File-specific info maintained by the OS – File size, modification date, creation time, etc.
    [Show full text]
  • Filesystem Hierarchy Standard
    Filesystem Hierarchy Standard Filesystem Hierarchy Standard Group Edited by Rusty Russell Daniel Quinlan Filesystem Hierarchy Standard by Filesystem Hierarchy Standard Group Edited by Rusty Russell and Daniel Quinlan Published November 4 2003 Copyright © 1994-2003 Daniel Quinlan Copyright © 2001-2003 Paul ’Rusty’ Russell Copyright © 2003 Christopher Yeoh 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. Table of Contents 1. Introduction........................................................................................................................................................1 1.1.
    [Show full text]
  • File Systems
    “runall” 2002/9/24 page 305 CHAPTER 10 File Systems 10.1 BASIC FUNCTIONS OF FILE MANAGEMENT 10.2 HIERARCHICAL MODEL OF A FILE SYSTEM 10.3 THE USER’S VIEW OF FILES 10.4 FILE DIRECTORIES 10.5 BASIC FILE SYSTEM 10.6 DEVICE ORGANIZATION METHODS 10.7 PRINCIPLES OF DISTRIBUTED FILE SYSTEMS 10.8 IMPLEMENTING DISTRIBUTED FILE SYSTEM Given that main memory is volatile, i.e., does not retain information when power is turned off, and is also limited in size, any computer system must be equipped with secondary memory on which the user and the system may keep information for indefinite periods of time. By far the most popular secondary memory devices are disks for random access purposes and magnetic tapes for sequential, archival storage. Since these devices are very complex to interact with, and, in multiuser systems are shared among different users, operating systems (OS) provide extensive services for managing data on secondary memory. These data are organized into files, which are collections of data elements grouped together for the purposes of access control, retrieval, and modification. A file system is the part of the operating system that is responsible for managing files and the resources on which these reside. Without a file system, efficient computing would essentially be impossible. This chapter discusses the organization of file systems and the tasks performed by the different components. The first part is concerned with general user and implementation aspects of file management emphasizing centralized systems; the last sections consider extensions and methods for distributed systems. 10.1 BASIC FUNCTIONS OF FILE MANAGEMENT The file system, in collaboration with the I/O system, has the following three basic functions: 1.
    [Show full text]
  • A Brief Technical Introduction
    Mac OS X A Brief Technical Introduction Leon Towns-von Stauber, Occam's Razor LISA Hit the Ground Running, December 2005 http://www.occam.com/osx/ X Contents Opening Remarks..............................3 What is Mac OS X?.............................5 A New Kind of UNIX.........................12 A Diferent Kind of UNIX..................15 Resources........................................39 X Opening Remarks 3 This is a technical introduction to Mac OS X, mainly targeted to experienced UNIX users for whom OS X is at least relatively new This presentation covers primarily Mac OS X 10.4.3 (Darwin 8.3), aka Tiger X Legal Notices 4 This presentation Copyright © 2003-2005 Leon Towns-von Stauber. All rights reserved. Trademark notices Apple®, Mac®, Macintosh®, Mac OS®, Finder™, Quartz™, Cocoa®, Carbon®, AppleScript®, Bonjour™, Panther™, Tiger™, and other terms are trademarks of Apple Computer. See <http://www.apple.com/legal/ appletmlist.html>. NeXT®, NeXTstep®, OpenStep®, and NetInfo® are trademarks of NeXT Software. See <http://www.apple.com/legal/nexttmlist.html>. Other trademarks are the property of their respective owners. X What Is It? 5 Answers Ancestry Operating System Products The Structure of Mac OS X X What Is It? Answers 6 It's an elephant I mean, it's like the elephant in the Chinese/Indian parable of the blind men, perceived as diferent things depending on the approach X What Is It? Answers 7 Inheritor of the Mac OS legacy Evolved GUI, Carbon (from Mac Toolbox), AppleScript, QuickTime, etc. The latest version of NeXTstep Mach, Quartz (from Display PostScript), Cocoa (from OpenStep), NetInfo, apps (Mail, Terminal, TextEdit, Preview, Interface Builder, Project Builder, etc.), bundles, faxing from Print panel, NetBoot, etc.
    [Show full text]