DOCSLIB.ORG

Solaris Common Messages and Troubleshooting Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Solaris Common Messages and Troubleshooting Guide Solaris Common Messages and Troubleshooting Guide Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303-4900 U.S.A. Part Number 806-1075–10 February 2000 Copyright 2000 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 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, SunOS, SunPC, Java, Java Workshop, NFS, and Solaris are trademarks, registered trademarks, or service marks 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. OpenGL is a registered trademark of Silicon Graphics, Inc. The OPEN LOOK and SunTM 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. RESTRICTED RIGHTS: Use, duplication, or disclosure by the U.S. Government is subject to restrictions of FAR 52.227–14(g)(2)(6/87) and FAR 52.227–19(6/87), or DFAR 252.227–7015(b)(6/95) and DFAR 227.7202–3(a). DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Copyright 2000 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, Californie 94303-4900 Etats-Unis. Tous droits réservés. Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y en a. Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun. Des parties de ce produit pourront être dérivées du système Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, docs.sun.com, AnswerBook, AnswerBook2, SunOS, SunPC, Java, Java Workshop, NFS, et Solaris sont des marques de fabrique ou des marques déposées, ou marques de service, de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays. Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.OpenGL est une marque dpose de Silicon Graphics, Inc. L’interface d’utilisation graphique OPEN LOOK et SunTM a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une licence non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciés de Sun qui mettent en place l’interface d’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun. CETTE PUBLICATION EST FOURNIE “EN L’ETAT” ET AUCUNE GARANTIE, EXPRESSE OU IMPLICITE, N’EST ACCORDEE, Y COMPRIS DES GARANTIES CONCERNANT LA VALEUR MARCHANDE, L’APTITUDE DE LA PUBLICATION A REPONDRE A UNE UTILISATION PARTICULIERE, OU LE FAIT QU’ELLE NE SOIT PAS CONTREFAISANTE DE PRODUIT DE TIERS. CE DENI DE GARANTIE NE S’APPLIQUERAIT PAS, DANS LA MESURE OU IL SERAIT TENU JURIDIQUEMENT NUL ET NON AVENU. Please Recycle Contents Preface 1. About Error Messages 27 Searching for Messages 27 Choosing What to Look For 27 In the Printed Book 28 In the AnswerBook Navigator 28 Combining Search Techniques 30 Understanding the Message Explanations 30 2. Alphabetical Message Listing 33 Numbers and Symbols 33 ***** FILE SYSTEM WAS MODIFIED ***** 33 ** Phase 1– Check Blocks and Sizes 34 ** Phase 1b– Rescan For More DUPS 34 ** Phase 2– Check Pathnames 35 ** Phase 3– Check Connectivity 35 ** Phase 4– Check Reference Counts 36 ** Phase 5– Check Cyl groups 36 @@ 37 29a00 illegal instruction 38 3 451 timeout waiting for input during source 38 501 MAIL FROM: unrecognized address: @@hostname 39 550 hostname... Host unknown 40 550 Security server failed to perform requested command 41 550 username... User unknown 42 554 hostname... Local configuration error 42 "A" 43 A command window has exited because its child exited. 43 access violation unknown host IP address 43 Accessing a corrupted shared library 44 Address already in use 44 Address family not supported by protocol family 44 admintool: Received communication service error 4 45 Advertise error 45 answerbook: XView error: NULL pointer passed to xv_set 46 apdb: Resource temporarily unavailable 46 Arg list too long 47 Argument out of domain 48 Arguments too long 48 assertion failed: string, file name, line int 49 Attempting to link in more shared libraries than system limit 49 automount[int]: name: Not a directory 49 automountd[int]: server hostname responding 50 "B" 50 Bad address 50 BAD/DUP FILE I=i OWNER=o MODE=m SIZE=s MTIME=t CLEAR? 51 Bad file number 51 4 Solaris Common Messages and Troubleshooting Guide ♦ February 2000 block no. BAD I=inode no. 52 BAD_MESSAGE (error code 100) from X.400 52 bad module/chip at: position 53 Bad request descriptor 53 BAD SUPER BLOCK: string 53 BAD TRAP 55 /bin/sh: file: too big 55 Block device required 56 Boot device: /iommu/sbus/directory/directory/sd@3,0 56 Broadcast Message from root (pts/int) on server [date] 57 Broken pipe 57 Bus Error 58 "C" 58 Cannot access a needed shared library 58 Cannot allocate colormap entry for "string"59 Cannot assign requested address 59 Cannot bind to domain domainname: can’t communicate with ypbind 59 Cannot boot after install, error that points to an .rc file 60 cannot change passwd, not correct passwd 61 cannot establish nfs service over /dev/tcp: transport setup problem 61 Cannot exec a shared library directly 62 Cannot find SERVER hostname in network database 62 cannot install bootblock 63 Cannot open FCC file 64 Cannot send after transport endpoint shutdown 64 can’t communicate with ypbind 65 Can’t create public message device (Device busy) 65 Can’t invoke /etc/init, error int 66 Contents 5 can’t open /dev/rdsk/string: (null): UNEXPECTED INCONSISTENCY 67 can’t synchronize with hayes 67 cd: Too many arguments 68 Channel number out of range 68 chmod: ERROR: invalid mode 68 Command not found 69 Communication error on send 70 config error: mail loops back to myself. 70 connect from hostIP to callit(ypserv): request from non-local host 71 connect from hostIP to callit(ypserv): request from unauthorized host 71 connect from hostIP to callit(ypserv): request from unprivileged port 72 connect from hostIP to callit(ypserv): request not forwarded 72 Connection closed. 72 Connection closed by foreign host. 73 [Connection closed. Exiting] 73 Connection refused 73 Connection reset by peer 74 Connection timed out 74 console login: ^J^M^Q^K^K^P 75 core dumped 76 corrupt label - wrong magic number or corrupt label or corrupt label - label checksum failed 77 could not grant slave pty 78 Could not initialize tooltalk (tt_open): TT_ERR_NOMP 78 Could not open ToolTalk Channel 79 Could not start new viewer 80 Could not start NFS service for any protocol. Exiting 80 cpio: Bad magic number/header. 81 6 Solaris Common Messages and Troubleshooting Guide ♦ February 2000 cpio : can’t read input : end of file encountered prior to expected end of archive. 81 Cross-device link 82 "D" 82 data access exception 82 Data fault 83 Deadlock situation detected/avoided 83 Destination address required 84 destination component full 84 /dev/fd/int: /dev/fd/int: cannot open 84 /dev/rdsk/c0t6d0s2: No such file or directory 85 Device busy 86 device busy 86 /dev/rdsk/string: CAN’T CHECK FILE SYSTEM. 88 /dev/rdsk/string: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. 88 Directory not empty 89 Disc quota exceeded 89 disk does not appear to be prepared for encapsulation 90 diskN not unique 90 dlopen (libxfn.so) failed 91 driver is already installed 91 dtmail: cannot open mailfile on 2.5.1 /var/mail server 92 DUMP:
Load more

Recommended publications
  • Virtual Memory
    Chapter 4 Virtual Memory Linux processes execute in a virtual environment that makes it appear as if each process had the entire address space of the CPU available to itself. This virtual address space extends from address 0 all the way to the maximum address. On a 32-bit platform, such as IA-32, the maximum address is 232 − 1or0xffffffff. On a 64-bit platform, such as IA-64, this is 264 − 1or0xffffffffffffffff. While it is obviously convenient for a process to be able to access such a huge ad- dress space, there are really three distinct, but equally important, reasons for using virtual memory. 1. Resource virtualization. On a system with virtual memory, a process does not have to concern itself with the details of how much physical memory is available or which physical memory locations are already in use by some other process. In other words, virtual memory takes a limited physical resource (physical memory) and turns it into an infinite, or at least an abundant, resource (virtual memory). 2. Information isolation. Because each process runs in its own address space, it is not possible for one process to read data that belongs to another process. This improves security because it reduces the risk of one process being able to spy on another pro- cess and, e.g., steal a password. 3. Fault isolation. Processes with their own virtual address spaces cannot overwrite each other’s memory. This greatly reduces the risk of a failure in one process trig- gering a failure in another process. That is, when a process crashes, the problem is generally limited to that process alone and does not cause the entire machine to go down.
    [Show full text]
  • Linux Physical Memory Analysis
    Linux Physical Memory Analysis Paul Movall International Business Machines Corporation 3605 Highway 52N, Rochester, MN Ward Nelson International Business Machines Corporation 3605 Highway 52N, Rochester, MN Shaun Wetzstein International Business Machines Corporation 3605 Highway 52N, Rochester, MN Abstract A significant amount of this information can alo be found in the /proc filesystem provided by the kernel. We present a tool suite for analysis of physical memory These /proc entries can be used to obtain many statis- usage within the Linux kernel environment. This tool tics including several related to memory usage. For ex- suite can be used to collect and analyze how the physi- ample, /proc/<pid>/maps can be used to display a pro- cal memory within a Linuxenvironment is being used. cess' virtual memory map. Likewise, the contents of / proc/<pid>/status can be used to retreive statistics about virtual memory usage as well as the Resident Set Size (RSS). Embedded subsystems are common in today's computer In most cases, this process level detail is sufficient to systems. These embedded subsystems range from the analyze memory usage. In systems that do not have very simple to the very complex. In such embedded sys- backing store, more details are often needed to analyze tems, memory is scarce and swap is non-existent. When memory usage. For example, it's useful to know which adapting Linux for use in this environment, we needed pages in a process' address map are resident, not just to keep a close eye on physical memory usage. how many. This information can be used to get some clues on the usage of a shared library.
    [Show full text]
  • Oracle Solaris Administration Basic Administration
    Oracle® Solaris Administration: Basic Administration Part No: E29492–03 June 2013 Copyright © 1998, 2013, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including anyoperating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications.
    [Show full text]
  • Downloading a Package
    man pages section 4: File Formats Part No: E29042 October 2012 Copyright © 2012, 2013, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable: U.S. GOVERNMENT END USERS. Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including anyoperating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications.
    [Show full text]
  • Solid Truss to Shell Numerical Homogenization of Prefabricated Composite Slabs
    materials Article Solid Truss to Shell Numerical Homogenization of Prefabricated Composite Slabs Natalia Staszak 1, Tomasz Garbowski 2 and Anna Szymczak-Graczyk 3,* 1 Research and Development Department, FEMat Sp. z o. o., Romana Maya 1, 61-371 Pozna´n,Poland; [email protected] 2 Department of Biosystems Engineering, Poznan University of Life Sciences, Wojska Polskiego 50, 60-627 Pozna´n,Poland; [email protected] 3 Department of Construction and Geoengineering, Poznan University of Life Sciences, Pi ˛atkowska94 E, 60-649 Pozna´n,Poland * Correspondence: [email protected] Abstract: The need for quick and easy deflection calculations of various prefabricated slabs causes simplified procedures and numerical tools to be used more often. Modelling of full 3D finite element (FE) geometry of such plates is not only uneconomical but often requires the use of complex software and advanced numerical knowledge. Therefore, numerical homogenization is an excellent tool, which can be easily employed to simplify a model, especially when accurate modelling is not necessary. Homogenization allows for simplifying a computational model and replacing a complicated composite structure with a homogeneous plate. Here, a numerical homogenization method based on strain energy equivalence is derived. Based on the method proposed, the structure of the prefabricated concrete slabs reinforced with steel spatial trusses is homogenized to a single plate element with an effective stiffness. There is a complete equivalence between the full 3D FE model built with solid elements combined with truss structural elements and the simplified Citation: Staszak, N.; Garbowski, T.; Szymczak-Graczyk, A. Solid Truss to homogenized plate FE model.
    [Show full text]
  • Solaris Advanced User's Guide
    Solaris Advanced User’s Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part No: 806–7612–10 May 2002 Copyright 2002 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, SunOS, and Solaris are trademarks, registered trademarks, or service marks 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]
  • Solaris 10 End of Life
    Solaris 10 end of life Continue Oracle Solaris 10 has had an amazing OS update, including ground features such as zones (Solaris containers), FSS, Services, Dynamic Tracking (against live production operating systems without impact), and logical domains. These features have been imitated in the market (imitation is the best form of flattery!) like all good things, they have to come to an end. Sun Microsystems was acquired by Oracle and eventually, the largest OS known to the industry, needs to be updated. Oracle has set a retirement date of January 2021. Oracle indicated that Solaris 10 systems would need to raise support costs. Oracle has never provided migratory tools to facilitate migration from Solaris 10 to Solaris 11, so migration to Solaris has been slow. In September 2019, Oracle decided that extended support for Solaris 10 without an additional financial penalty would be delayed until 2024! Well its March 1 is just a reminder that Oracle Solaris 10 is getting the end of life regarding support if you accept extended support from Oracle. Combined with the fact gdpR should take effect on May 25, 2018 you want to make sure that you are either upgraded to Solaris 11.3 or have taken extended support to obtain any patches for security issues. For more information on tanningix releases and support dates of old and new follow this link ×Sestive to abort the Unix Error Operating System originally developed by Sun Microsystems SolarisDeveloperSun Microsystems (acquired by Oracle Corporation in 2009)Written inC, C'OSUnixWorking StateCurrentSource ModelMixedInitial release1992; 28 years ago (1992-06)Last release11.4 / August 28, 2018; 2 years ago (2018-08-28)Marketing targetServer, PlatformsCurrent: SPARC, x86-64 Former: IA-32, PowerPCKernel typeMonolithic with dynamically downloadable modulesDefault user interface GNOME-2-LicenseVariousOfficial websitewww.oracle.com/solaris Solaris is the own operating system Of Unix, originally developed by Sunsystems.
    [Show full text]
  • Introduction to UNIX What Is UNIX? Why UNIX? Brief History of UNIX Early UNIX History UNIX Variants
    What is UNIX? A modern computer operating system Introduction to UNIX Operating system: “a program that acts as an intermediary between a user of the computer and the computer hardware” CS 2204 Software that manages your computer’s resources (files, programs, disks, network, …) Class meeting 1 e.g. Windows, MacOS Modern: features for stability, flexibility, multiple users and programs, configurability, etc. *Notes by Doug Bowman and other members of the CS faculty at Virginia Tech. Copyright 2001-2003. (C) Doug Bowman, Virginia Tech, 2001- 2 Why UNIX? Brief history of UNIX Used in many scientific and industrial settings Ken Thompson & Dennis Richie Huge number of free and well-written originally developed the earliest software programs versions of UNIX at Bell Labs for Open-source OS internal use in 1970s Internet servers and services run on UNIX Borrowed best ideas from other Oss Largely hardware-independent Meant for programmers and computer Based on standards experts Meant to run on “mini computers” (C) Doug Bowman, Virginia Tech, 2001- 3 (C) Doug Bowman, Virginia Tech, 2001- 4 Early UNIX History UNIX variants Thompson also rewrote the operating system Two main threads of development: in high level language of his own design Berkeley software distribution (BSD) which he called B. Unix System Laboratories System V Sun: SunOS, Solaris The B language lacked many features and Ritchie decided to design a successor to B GNU: Linux (many flavors) which he called C. SGI: Irix They then rewrote UNIX in the C FreeBSD programming language to aid in portability. Hewlett-Packard: HP-UX Apple: OS X (Darwin) … (C) Doug Bowman, Virginia Tech, 2001- 5 (C) Doug Bowman, Virginia Tech, 2001- 6 1 Layers in the UNIX System UNIX Structure User Interface The kernel is the core of the UNIX Library Interface Users system, controlling the system Standard Utility Programs hardware and performing various low- (shell, editors, compilers, etc.) System Interface calls User Mode level functions.
    [Show full text]
  • Bridge Types in NSW Historical Overviews 2006
    Timber Truss Bridges Study of Relative Heritage Significance of All Timber Truss Road Bridges in NSW 1998 25 Historical Overview of Bridge Types in NSW: Extract from the Study of Relative Heritage Significance of all Timber Truss Road Bridges in NSW HISTORY OF TIMBER TRUSS BRIDGES IN NSW 1.1 GENERAL During the first fifty years of the colony of New South Wales, 1788 - 1838, settlement was confined to the narrow coastal strip between the Pacific Ocean and the Great Dividing Range. The scattered communities were well served by ships plying the east coast and its many navigable rivers. Figure 1.1a: Settlement of early colonial NSW. Shaded areas are settled. In Governor Macquarie's time between 1810-1822, a number of good roads were built, but despite his efforts and those of the subsequent Governors Darling and Bourke, and of road builders George Evans, William Cox and Thomas Mitchell, the road system and its associated bridges could only be described as primitive. Many roads and bridges were financed through public subscriptions or as private ventures, particularly where tolls could be levied. The first significant improvement to this situation occurred in late 1832 when Surveyor- General Mitchell observed a competent stone mason working on a wall in front of the Legislative Council Chambers in Macquarie Street. It was David LennoxR3. He was appointed Sub-Inspector of Roads on October 1, 1832 then Superintendent of Bridges on June 6, 1833. His first project was to span a gully for the newly formed Mitchell's Pass on the eastern side of the Blue Mountains.
    [Show full text]
  • Learning the Methods of Engineering Analysis Using Case Studies, Excel and VBA - Course Design
    Computers in Education, Session 1520 Learning the Methods of Engineering Analysis Using Case Studies, Excel and VBA - Course Design Michael A. Collura, Bouzid Aliane, Samuel Daniels, Jean Nocito-Gobel School of Engineering & Applied Science, University of New Haven Abstract Methods of Engineering Analysis, EAS 112, is a first year course in which engineering and applied science students learn how to apply a variety of computer analysis methods. The course uses a “problem-driven” approach in which case studies of typical engineering and science problems become the arena in which these analytical methods must be applied. A common spreadsheet program, such as Microsoft Excel, is the starting point to teach such topics as descriptive statistics, regression, interpolation, integration and solving sets of algebraic, differential and finite difference equations. Students are also introduced to programming fundamentals in the Visual Basic for Applications environment as they create the algorithms needed for the analysis. In this programming environment students gain an understanding of basic programming concepts, such as data types, assignment and conditional statements, logical and numerical functions, program flow control, passing parameters/returning values with functions and working with arrays. EAS 112 is a stop along the Multidisciplinary Engineering Foundation Spiral1 in the engineering programs at the University of New Haven. A typical student will take the course in the second semester of the first year. Certain engineering foundation topics will appear in the assigned problems and case studies, contributing to students’ understanding of areas such as electrical circuits, mass balances, and structural mechanics. At this point along the spiral curriculum students are given most of the equations needed to analyze the case study problems, but they are responsible for development of the algorithms and implementing these in the spreadsheet and/or programming environment.
    [Show full text]
  • Managing Network File Systems in Oracle® Solaris 11.4
    Managing Network File Systems in ® Oracle Solaris 11.4 Part No: E61004 August 2021 Managing Network File Systems in Oracle Solaris 11.4 Part No: E61004 Copyright © 2002, 2021, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Solaris Powerpc Edition: Installing Solaris Software—May 1996 What Is a Profile
    SolarisPowerPC Edition: Installing Solaris Software 2550 Garcia Avenue Mountain View, CA 94043 U.S.A. A Sun Microsystems, Inc. Business Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Avenue, Mountain View, California 94043-1100 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. Portions of this product may be derived from the UNIX® system, licensed from Novell, Inc., and from the Berkeley 4.3 BSD system, licensed from the University of California. UNIX is a registered trademark in the United States and other countries and is exclusively licensed by X/Open Company Ltd. Third-party software, including font technology in this product, is protected by copyright and licensed from Sun’s suppliers. RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR 52.227-19. Sun, Sun Microsystems, the Sun logo, Solaris, Solstice, SunOS, OpenWindows, ONC, NFS, DeskSet are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.
    [Show full text]