DOCSLIB.ORG

EIS CD Install Solaris Patch(Vmware Lab)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
EIS CD Install Solaris Patch(Vmware Lab) EIS CD Install Solaris Patch(Vmware Lab) # ls -al total 4 drwxr-xr-x 2 root nobody 512 Jan 4 11:44 . drwxr-xr-x 5 root root 512 Jan 18 18:39 .. # cd /cdrom # ls 20040114_000414 cdrom0 eis-cd sol_9_905_x86_2 # cd eis* # # # ls -al total 293 dr-xr-xr-x 2 root sys 2048 Dec 1 18:09 . drwxr-xr-x 5 root root 512 Jan 18 18:39 .. -r--r--r-- 1 root root 43098 Dec 1 18:09 .eis-cd1.md5 dr-xr-xr-x 2 root root 2048 Nov 25 22:54 .verify -r--r--r-- 1 root root 2550 Nov 29 00:53 CONTENTS.txt -r--r--r-- 1 root root 2674 Jul 13 2000 COPYRIGHT -r--r--r-- 1 root root 1417 Jul 27 2001 DISCLAIMER.txt -r--r--r-- 1 root root 2476 Dec 1 02:08 README-29NOV05 -r--r--r-- 1 root root 89296 Dec 1 01:10 history.txt dr-xr-xr-x 6 root root 2048 Sep 25 03:27 sun # ls -F CONTENTS.txt DISCLAIMER.txt history.txt COPYRIGHT README-29NOV05 sun/ # cd sun # ls install patch progs tools # cd install # ls bin local-bin profile-EIS copy-cd2sun.sh local-bin_x86 profile-root copy-dvd2sun.sh make-cd-images setup-standard.sh # ls -F bin/ local-bin/ profile-EIS copy-cd2sun.sh* local-bin_x86/ profile-root copy-dvd2sun.sh* make-cd-images* setup-standard.sh* # ./setup* Running setup-standard with EIS-CD Vn 29-NOV-05 =============================================== Creating /var/sun for scripts, log files etc... Loading /opt/sun/bin... Setting up /.profile-EIS... BEWARE: /.profile does NOT source /.profile-EIS PLEASE: examine why this is not sourced! Is the power saving daemon to be disabled? [y/n]: y /etc/power.conf has been modified. Sun keyboard Power button to be disabled? [y/n]: y /usr/openwin/lib/speckeysd.map has been modified. The buttons & dials have probably already been disabled.... Remote ROOT logins probably enabled: See /etc/default/login... One or more SAN Foundation Suite Packages are not installed. Installation of SAN Foundation Suite prevented via option! *********************************************************** * There is a risk that the system will halt and enter * * the debugger (thus stopping operation) if a break * * signal is seen on the serial port and the system had * * been booted with kadb. * * This can happen when the device attached to the serial * * port (e.g. workstation or terminal) is powered on. * * This behaviour can be prevented by setting the * * Alternate Break Sequence in /etc/default/kbd. * *********************************************************** Do you wish to ENABLE the alternate break sequence? [E/n]: E Please note that the new break sequence is: <cr> ~ ^B (no spaces) (i.e. Carriage return, tilde, control-B) Automated Core File Analysis Tool (ACT)..... ACT Package is not installed - Version 8.10 available.... Do you want to install the ACT package? [y/n]: y Processing package instance <CTEactx> from </tmp/act> CS CTE Automated Crash Analysis tool (http://cpre-emea.uk/tools/act.html) (i386) 8.10 ACT Copyright 2005 Sun Microsystems, Inc. All rights reserved. enter base directory for install (Default /opt/CTEactx) [?,q] Do you wish to enable the email of panic facility [y] [y,n,?] n The selected base directory </opt/CTEactx> must exist before installation is attempted. Do you want this directory created now [y,n,?,q] y Using </opt/CTEactx> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <CTEactx> [y,n,?] y Installing CS CTE Automated Crash Analysis tool (http://cpre-emea.uk/tools/act.html) as <CTEact x> ## Installing part 1 of 1. /opt/CTEactx/man/man1/act.1 /opt/CTEactx/scripts/ACT_dumpscript [ verifying class <none> ] /opt/CTEactx/bin/5.9/act [ verifying class <59> ] ## Executing postinstall script. Creating symbolic link for ACT Installing ACT_dumpscript in /etc/init.d Installing Link in /etc/rc2.d Please Modify your PATH environment variable to include /opt/CTEactx/bin Please Modify your MANPATH environment variable to include /opt/CTEactx/man Installation of <CTEactx> was successful. Explorer Package not present - will install Version 5.2,REV=2005.08.31.01.48... Processing package instance <SUNWexplo> from </tmp/explorer> Sun(TM) Explorer Data Collector (all) 5.2,REV=2005.08.31.01.48 Copyright 1996-2005 Sun Microsystems, Inc. All rights reserved. ## Executing checkinstall script. Using </opt> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <SUNWexplo> [y,n,?] Installing Sun(TM) Explorer Data Collector as <SUNWexplo> ## Executing preinstall script. ## Installing part 1 of 1. /opt/SUNWexplo/LICENSEREADME/LICENSE.txt /opt/SUNWexplo/LICENSEREADME/THIRDPARTYLICENSEREADME.txt /opt/SUNWexplo/LICENSEREADME/gzip-1.2.4a.tar.gz /opt/SUNWexplo/LICENSEREADME/wget-1.9.tar.gz /opt/SUNWexplo/bin/capture.sparc /opt/SUNWexplo/bin/core_check.sh /opt/SUNWexplo/bin/diskinfo.i386 /opt/SUNWexplo/bin/diskinfo.sparc /opt/SUNWexplo/bin/exp_defaults /opt/SUNWexplo/bin/explorer /opt/SUNWexplo/bin/explorer_notify_update /opt/SUNWexplo/bin/instinfo_config /opt/SUNWexplo/bin/j2se_config /opt/SUNWexplo/bin/mktime.i386 /opt/SUNWexplo/bin/mktime.sparc /opt/SUNWexplo/bin/rprtfru.sparc /opt/SUNWexplo/bin/se3kxtr.ksh /opt/SUNWexplo/bin/snapshot /opt/SUNWexplo/bin/st_diag.i386 /opt/SUNWexplo/bin/st_diag.sparc /opt/SUNWexplo/bin/sunone_config /opt/SUNWexplo/bin/sunone_ps /opt/SUNWexplo/bin/wget.i386 /opt/SUNWexplo/bin/wget.sparc /opt/SUNWexplo/doc/CHANGES /opt/SUNWexplo/doc/README /opt/SUNWexplo/doc/README.j2se_config /opt/SUNWexplo/doc/README.man /opt/SUNWexplo/doc/README.sunone_config /opt/SUNWexplo/java/fruid-scappclient.jar /opt/SUNWexplo/java/libfru.jar /opt/SUNWexplo/lib/AMERICAS_countries.1 /opt/SUNWexplo/lib/AMERICAS_countries.2 /opt/SUNWexplo/lib/AMERICAS_countries.3 /opt/SUNWexplo/lib/AMERICAS_countries_codes /opt/SUNWexplo/lib/APAC_countries.1 /opt/SUNWexplo/lib/APAC_countries.2 /opt/SUNWexplo/lib/APAC_countries.3 /opt/SUNWexplo/lib/APAC_countries.4 /opt/SUNWexplo/lib/APAC_countries_codes /opt/SUNWexplo/lib/EMEA_countries.1 /opt/SUNWexplo/lib/EMEA_countries.2 /opt/SUNWexplo/lib/EMEA_countries.3 /opt/SUNWexplo/lib/EMEA_countries.4 /opt/SUNWexplo/lib/EMEA_countries.5 /opt/SUNWexplo/lib/EMEA_countries.6 /opt/SUNWexplo/lib/EMEA_countries.7 /opt/SUNWexplo/lib/EMEA_countries.8 /opt/SUNWexplo/lib/EMEA_countries_codes /opt/SUNWexplo/lib/cmd.txt /opt/SUNWexplo/lib/cmd_ssh.txt /opt/SUNWexplo/lib/crontab.txt /opt/SUNWexplo/lib/exp_check /opt/SUNWexplo/lib/exp_common /opt/SUNWexplo/lib/exp_file /opt/SUNWexplo/lib/exp_ftp /opt/SUNWexplo/lib/exp_j2se /opt/SUNWexplo/lib/exp_mail /opt/SUNWexplo/lib/exp_main /opt/SUNWexplo/lib/exp_postproc /opt/SUNWexplo/lib/exp_sunone /opt/SUNWexplo/lib/exp_tools /opt/SUNWexplo/lib/exp_transport /opt/SUNWexplo/lib/libfru.so <symbolic link> /opt/SUNWexplo/lib/libfru.so.1 /opt/SUNWexplo/lib/libfrujni.so <symbolic link> /opt/SUNWexplo/lib/libfrujni.so.1 /opt/SUNWexplo/lib/libfrureg.so <symbolic link> /opt/SUNWexplo/lib/libfrureg.so.1 /opt/SUNWexplo/lib/libfrurmi.so <symbolic link> /opt/SUNWexplo/lib/libfrurmi.so.1 /opt/SUNWexplo/lib/libfruutils.so <symbolic link> /opt/SUNWexplo/lib/libfruutils.so.1 /opt/SUNWexplo/lib/locale/C/LC_MESSAGES/explorer.mo /opt/SUNWexplo/lib/locale/C/LC_MESSAGES/explorer.po /opt/SUNWexplo/lib/uu2b64 /opt/SUNWexplo/man/man1m/explorer.1m /opt/SUNWexplo/man/man4/explorer.4 /opt/SUNWexplo/man/man5/explorer.5 /opt/SUNWexplo/tools/1280extended /opt/SUNWexplo/tools/Tx000 /opt/SUNWexplo/tools/alomextended /opt/SUNWexplo/tools/b1600extended /opt/SUNWexplo/tools/b1600switch /opt/SUNWexplo/tools/cluster /opt/SUNWexplo/tools/cmdline /opt/SUNWexplo/tools/cst /opt/SUNWexplo/tools/disks /opt/SUNWexplo/tools/emc /opt/SUNWexplo/tools/etc /opt/SUNWexplo/tools/fcal /opt/SUNWexplo/tools/firelink /opt/SUNWexplo/tools/fma /opt/SUNWexplo/tools/fru /opt/SUNWexplo/tools/hds /opt/SUNWexplo/tools/init /opt/SUNWexplo/tools/instinfo /opt/SUNWexplo/tools/iplanet <symbolic link> /opt/SUNWexplo/tools/j2se /opt/SUNWexplo/tools/ldap /opt/SUNWexplo/tools/lic /opt/SUNWexplo/tools/lp /opt/SUNWexplo/tools/lvm /opt/SUNWexplo/tools/messages /opt/SUNWexplo/tools/nbu /opt/SUNWexplo/tools/nbu_extended /opt/SUNWexplo/tools/ndd /opt/SUNWexplo/tools/netinfo /opt/SUNWexplo/tools/nhas /opt/SUNWexplo/tools/patch /opt/SUNWexplo/tools/photon /opt/SUNWexplo/tools/pkg /opt/SUNWexplo/tools/proc /opt/SUNWexplo/tools/samfs /opt/SUNWexplo/tools/sanextended /opt/SUNWexplo/tools/sap /opt/SUNWexplo/tools/sbu /opt/SUNWexplo/tools/scextended /opt/SUNWexplo/tools/se3k /opt/SUNWexplo/tools/se6130 /opt/SUNWexplo/tools/se6320 /opt/SUNWexplo/tools/se6920 /opt/SUNWexplo/tools/sf15k_ndd /opt/SUNWexplo/tools/sf15k_sc /opt/SUNWexplo/tools/smfextended /opt/SUNWexplo/tools/sonoma /opt/SUNWexplo/tools/srscextended /opt/SUNWexplo/tools/ssa /opt/SUNWexplo/tools/ssp /opt/SUNWexplo/tools/storade /opt/SUNWexplo/tools/storedge /opt/SUNWexplo/tools/stortools /opt/SUNWexplo/tools/sunone /opt/SUNWexplo/tools/sunray /opt/SUNWexplo/tools/sysconfig /opt/SUNWexplo/tools/t3 /opt/SUNWexplo/tools/t3extended /opt/SUNWexplo/tools/tape /opt/SUNWexplo/tools/test /opt/SUNWexplo/tools/u4ft
Load more

Recommended publications
  • Administration and Reference Guide
    Oracle® Database Appliance Administration and Reference Guide Release 12.2.1.4.0 for Linux x86-64 E97563-01 June 2018 Oracle Database Appliance Administration and Reference Guide, Release 12.2.1.4.0 for Linux x86-64 E97563-01 Copyright © 2014, 2018, 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, then 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 any operating 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.
    [Show full text]
  • Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT
    LPI 117-101 117-101 LPI 101 General Linux, Part I Practice Test Version 1.8 LPI 117-101: Practice Exam QUESTION NO: 1 CORRECT TEXT You suspect that a new ethernet card might be conflicting with another device. Which file should you check within the /proc tree to learn which IRQs are being used by which kernel drives? Answer: interrupts QUESTION NO: 2 How many SCSI ids for peripherals can SCSI-1 support? A. 5 B. 6 C. 7 D. 8 Answer: C Explanation: SCSI-1 support total 7 peripherals. There are several different types of SCSI devices. The original SCSI specification is commonly referred to as SCSI-1. The newer specification, SCSI-2, offers increased speed and performance, as well as new commands. Fast SCSI increases throughput to more than 10MB per second. Fast-Wide SCSI provides a wider data path and throughput of up to 40MB per second and up to 15 devices. There there are Ultra-SCSI and Ultra-Wide-SCSI QUESTION NO: 3 You need to install a fax server. Which type of fax/modem should you install to insure Linux compatibility? Test-King.com A. External Serial Fax/modem B. External USB Fax/modem C. Internal ISA Fax/modem D. Internal PCI Fax/modem Answer: A QUESTION NO: 4 You are running Linux 2.0.36 and you need to add a USB mouse to your system. Which of the following statements is true? "Welcome to Certification's Main Event" - www.test-king.com 2 LPI 117-101: Practice Exam A. You need to rebuild the kernel.
    [Show full text]
  • Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D
    Article pubs.acs.org/JPCC Control of Protein Orientation on Gold Nanoparticles † ∥ † § † ∥ ⊥ Wayne Lin, Thomas Insley, Marcus D. Tuttle, Lingyang Zhu, Deborah A. Berthold, Petr Kral,́, † ‡ # † Chad M. Rienstra,*, , , and Catherine J. Murphy*, † ‡ Department of Chemistry and Department of Biochemistry, University of Illinois at Urbana−Champaign, 600 South Matthews Avenue, Urbana, Illinois 61801, United States § School of Chemical Sciences, University of Illinois at Urbana−Champaign, 505 South Matthews Avenue, Urbana, Illinois 61801, United States ∥ ⊥ Department of Chemistry and Department of Physics, University of Illinois at Chicago, 845 West Taylor Street, Chicago, Illinois 60607, United States # Center for Biophysics and Computational Biology, University of Illinois at Urbana−Champaign, 607 South Matthews Avenue, Urbana, Illinois 61801, United States *S Supporting Information ABSTRACT: Gold nanoparticles (Au NPs) have attracted much attention due to their potential applications in nanomedicine. While numerous studies have quantified biomolecular adsorption to Au NPs in terms of equilibrium binding constants, far less is known about biomolecular orientation on nanoparticle surfaces. In this study, the binding of the protein α-synuclein to citrate and (16- mercaptohexadecyl)trimethylammonium bromide (MTAB)-coated 12 nm Au NPs is examined by heteronuclear single quantum coherence NMR spectroscopy to provide site-specific measurements of protein−nanoparticle binding. Molecular dynamics simulations support the orientation assignments, which
    [Show full text]
  • File System, Files, and *Tab /Etc/Fstab
    File system, files, and *tab File system files directories volumes, file systems mounting points local versus networked file systems 1 /etc/fstab Specifies what is to be mounted where and how fs_spec: describes block special device for remote filesystem to be mounted fs_file: describes the mount point fs_vfstype: describes the type of file system fs_mntops: describes the mount options associated with the filesystem 2 /etc/fstab cont. fs_freq: used by the dump command fs_passno: used by fsck to determine the order in which checks are done at boot time. Root file systems should be specified as 1, others should be 2. Value 0 means that file system does not need to be checked 3 /etc/fstab 4 from blocks to mounting points metadata inodes directories superblocks 5 mounting file systems mounting e.g., mount -a unmounting manually or during shutdown umount 6 /etc/mtab see what is mounted 7 Network File System Access file system (FS) over a network looks like a local file system to user e.g. mount user FS rather than duplicating it (which would be a disaster) Developed by Sun Microsystems (mid 80s) history for NFS: NFS, NFSv2, NFSv3, NFSv4 RFC 3530 (from 2003) take a look to see what these RFCs are like!) 8 Network File System How does this actually work? server needs to export the system client needs to mount the system server: /etc/exports file client: /etc/fstab file 9 Network File System Security concerns UID GID What problems could arise? 10 Network File System example from our raid system (what is a RAID again?) Example of exports file from
    [Show full text]
  • MINCS - the Container in the Shell (Script)
    MINCS - The Container in the Shell (script) - Masami Hiramatsu <[email protected]> Tech Lead, Linaro Ltd. Open Source Summit Japan 2017 LEADING COLLABORATION IN THE ARM ECOSYSTEM Who am I... Masami Hiramatsu - Linux kernel kprobes maintainer - Working for Linaro as a Tech Lead LEADING COLLABORATION IN THE ARM ECOSYSTEM Demo # minc top # minc -r /opt/debian/x86_64 # minc -r /opt/debian/arm64 --arch arm64 LEADING COLLABORATION IN THE ARM ECOSYSTEM What Is MINCS? My Personal Fun Project to learn how linux containers work :-) LEADING COLLABORATION IN THE ARM ECOSYSTEM What Is MINCS? Mini Container Shell Scripts (pronounced ‘minks’) - Container engine implementation using POSIX shell scripts - It is small (~60KB, ~2KLOC) (~20KB in minimum) - It can run on busybox - No architecture dependency (* except for qemu/um mode) - No need for special binaries (* except for libcap, just for capsh --exec) - Main Features - Namespaces (Mount, PID, User, UTS, Net*) - Cgroups (CPU, Memory) - Capabilities - Overlay filesystem - Qemu cross-arch/system emulation - User-mode-linux - Image importing from dockerhub And all are done by CLI commands :-) LEADING COLLABORATION IN THE ARM ECOSYSTEM Why Shell Script? That is my favorite language :-) - Easy to understand for *nix administrators - Just a bunch of commands - Easy to modify - Good for prototyping - Easy to deploy - No architecture dependencies - Very small - Able to run on busybox (+ libcap is perfect) LEADING COLLABORATION IN THE ARM ECOSYSTEM MINCS Use-Cases For Learning - Understand how containers work For Development - Prepare isolated (cross-)build environment For Testing - Test new applications in isolated environment - Test new kernel features on qemu using local tools For products? - Maybe good for embedded devices which has small resources LEADING COLLABORATION IN THE ARM ECOSYSTEM What Is A Linux Container? There are many linux container engines - Docker, LXC, rkt, runc, ..
    [Show full text]
  • Hardening Linux
    eBooks-IT.org 4444_FM_final.qxd 1/5/05 12:39 AM Page i eBooks-IT.org Hardening Linux JAMES TURNBULL 4444_FM_final.qxd 1/5/05 12:39 AM Page ii eBooks-IT.org Hardening Linux Copyright © 2005 by James Turnbull All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN (pbk): 1-59059-444-4 Printed and bound in the United States of America 987654321 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Jim Sumser Technical Reviewer: Judith Myerson Editorial Board: Steve Anglin, Dan Appleman, Ewan Buckingham, Gary Cornell, Tony Davis, Jason Gilmore, Chris Mills, Dominic Shakeshaft, Jim Sumser Project Manager: Kylie Johnston Copy Edit Manager: Nicole LeClerc Copy Editor: Kim Wimpsett Production Manager: Kari Brooks-Copony Production Editor: Kelly Winquist Compositor: Linda Weidemann Proofreader: Lori Bring Indexer: Kevin Broccoli Artist: Kinetic Publishing Services, LLC Cover Designer: Kurt Krames Manufacturing Manager: Tom Debolski Distributed to the book trade in the United States by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013, and outside the United States by Springer-Verlag GmbH & Co. KG, Tiergartenstr. 17, 69112 Heidelberg, Germany. In the United States: phone 1-800-SPRINGER, fax 201-348-4505, e-mail [email protected], or visit http://www.springer-ny.com.
    [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]
  • Advanced Bash-Scripting Guide
    Advanced Bash−Scripting Guide An in−depth exploration of the art of shell scripting Mendel Cooper <[email protected]> 2.2 31 October 2003 Revision History Revision 0.1 14 June 2000 Revised by: mc Initial release. Revision 0.2 30 October 2000 Revised by: mc Bugs fixed, plus much additional material and more example scripts. Revision 0.3 12 February 2001 Revised by: mc Another major update. Revision 0.4 08 July 2001 Revised by: mc More bugfixes, much more material, more scripts − a complete revision and expansion of the book. Revision 0.5 03 September 2001 Revised by: mc Major update. Bugfixes, material added, chapters and sections reorganized. Revision 1.0 14 October 2001 Revised by: mc Bugfixes, reorganization, material added. Stable release. Revision 1.1 06 January 2002 Revised by: mc Bugfixes, material and scripts added. Revision 1.2 31 March 2002 Revised by: mc Bugfixes, material and scripts added. Revision 1.3 02 June 2002 Revised by: mc 'TANGERINE' release: A few bugfixes, much more material and scripts added. Revision 1.4 16 June 2002 Revised by: mc 'MANGO' release: Quite a number of typos fixed, more material and scripts added. Revision 1.5 13 July 2002 Revised by: mc 'PAPAYA' release: A few bugfixes, much more material and scripts added. Revision 1.6 29 September 2002 Revised by: mc 'POMEGRANATE' release: some bugfixes, more material, one more script added. Revision 1.7 05 January 2003 Revised by: mc 'COCONUT' release: a couple of bugfixes, more material, one more script. Revision 1.8 10 May 2003 Revised by: mc 'BREADFRUIT' release: a number of bugfixes, more scripts and material.
    [Show full text]
  • MC-1200 Series Linux Software User's Manual
    MC-1200 Series Linux Software User’s Manual Version 1.0, November 2020 www.moxa.com/product © 2020 Moxa Inc. All rights reserved. MC-1200 Series Linux Software User’s Manual The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement. Copyright Notice © 2020 Moxa Inc. All rights reserved. Trademarks The MOXA logo is a registered trademark of Moxa Inc. All other trademarks or registered marks in this manual belong to their respective manufacturers. Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa. Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time. Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use. This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication. Technical Support Contact Information www.moxa.com/support Moxa Americas Moxa China (Shanghai office) Toll-free: 1-888-669-2872 Toll-free: 800-820-5036 Tel: +1-714-528-6777 Tel: +86-21-5258-9955 Fax: +1-714-528-6778 Fax: +86-21-5258-5505 Moxa Europe Moxa Asia-Pacific Tel: +49-89-3 70 03 99-0 Tel: +886-2-8919-1230 Fax: +49-89-3 70 03 99-99 Fax: +886-2-8919-1231 Moxa India Tel: +91-80-4172-9088 Fax: +91-80-4132-1045 Table of Contents 1.
    [Show full text]
  • The Linux Device File-System
    The Linux Device File-System Richard Gooch EMC Corporation [email protected] Abstract 1 Introduction All Unix systems provide access to hardware via de- vice drivers. These drivers need to provide entry points for user-space applications and system tools to access the hardware. Following the \everything is a file” philosophy of Unix, these entry points are ex- posed in the file name-space, and are called \device The Device File-System (devfs) provides a power- special files” or \device nodes". ful new device management mechanism for Linux. Unlike other existing and proposed device manage- This paper discusses how these device nodes are cre- ment schemes, it is powerful, flexible, scalable and ated and managed in conventional Unix systems and efficient. the limitations this scheme imposes. An alternative mechanism is then presented. It is an alternative to conventional disc-based char- acter and block special devices. Kernel device drivers can register devices by name rather than de- vice numbers, and these device entries will appear in the file-system automatically. 1.1 Device numbers Devfs provides an immediate benefit to system ad- ministrators, as it implements a device naming scheme which is more convenient for large systems Conventional Unix systems have the concept of a (providing a topology-based name-space) and small \device number". Each instance of a driver and systems (via a device-class based name-space) alike. hardware component is assigned a unique device number. Within the kernel, this device number is Device driver authors can benefit from devfs by used to refer to the hardware and driver instance.
    [Show full text]
  • Singularityce User Guide Release 3.8
    SingularityCE User Guide Release 3.8 SingularityCE Project Contributors Aug 16, 2021 CONTENTS 1 Getting Started & Background Information3 1.1 Introduction to SingularityCE......................................3 1.2 Quick Start................................................5 1.3 Security in SingularityCE........................................ 15 2 Building Containers 19 2.1 Build a Container............................................. 19 2.2 Definition Files.............................................. 24 2.3 Build Environment............................................ 35 2.4 Support for Docker and OCI....................................... 39 2.5 Fakeroot feature............................................. 79 3 Signing & Encryption 83 3.1 Signing and Verifying Containers.................................... 83 3.2 Key commands.............................................. 88 3.3 Encrypted Containers.......................................... 90 4 Sharing & Online Services 95 4.1 Remote Endpoints............................................ 95 4.2 Cloud Library.............................................. 103 5 Advanced Usage 109 5.1 Bind Paths and Mounts.......................................... 109 5.2 Persistent Overlays............................................ 115 5.3 Running Services............................................. 118 5.4 Environment and Metadata........................................ 129 5.5 OCI Runtime Support.......................................... 140 5.6 Plugins.................................................
    [Show full text]
  • Oracle® Linux 7 Managing File Systems
    Oracle® Linux 7 Managing File Systems F32760-07 August 2021 Oracle Legal Notices Copyright © 2020, 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]