DOCSLIB.ORG

GNU Findutils Finding Files Version 4.8.0, 7 January 2021

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
GNU Findutils Finding Files Version 4.8.0, 7 January 2021 GNU Findutils Finding files version 4.8.0, 7 January 2021 by David MacKenzie and James Youngman This manual documents version 4.8.0 of the GNU utilities for finding files that match certain criteria and performing various operations on them. Copyright c 1994{2021 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents 1 Introduction ::::::::::::::::::::::::::::::::::::: 1 1.1 Scope :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.2 Overview ::::::::::::::::::::::::::::::::::::::::::::::::::::::: 2 2 Finding Files ::::::::::::::::::::::::::::::::::::: 4 2.1 find Expressions ::::::::::::::::::::::::::::::::::::::::::::::: 4 2.2 Name :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2.2.1 Base Name Patterns ::::::::::::::::::::::::::::::::::::::: 5 2.2.2 Full Name Patterns :::::::::::::::::::::::::::::::::::::::: 5 2.2.3 Fast Full Name Search ::::::::::::::::::::::::::::::::::::: 7 2.2.4 Shell Pattern Matching :::::::::::::::::::::::::::::::::::: 8 2.3 Links ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.3.1 Symbolic Links :::::::::::::::::::::::::::::::::::::::::::: 8 2.3.2 Hard Links ::::::::::::::::::::::::::::::::::::::::::::::: 10 2.4 Time :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 11 2.4.1 Age Ranges::::::::::::::::::::::::::::::::::::::::::::::: 11 2.4.2 Comparing Timestamps :::::::::::::::::::::::::::::::::: 12 2.5 Size ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 13 2.6 Type :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 14 2.7 Owner :::::::::::::::::::::::::::::::::::::::::::::::::::::::: 15 2.8 File Mode Bits :::::::::::::::::::::::::::::::::::::::::::::::: 15 2.9 Contents :::::::::::::::::::::::::::::::::::::::::::::::::::::: 18 2.10 Directories ::::::::::::::::::::::::::::::::::::::::::::::::::: 18 2.11 Filesystems::::::::::::::::::::::::::::::::::::::::::::::::::: 20 2.12 Combining Primaries With Operators::::::::::::::::::::::::: 21 3 Actions:::::::::::::::::::::::::::::::::::::::::: 22 3.1 Print File Name ::::::::::::::::::::::::::::::::::::::::::::::: 22 3.2 Print File Information ::::::::::::::::::::::::::::::::::::::::: 22 3.2.1 Escapes :::::::::::::::::::::::::::::::::::::::::::::::::: 23 3.2.2 Format Directives :::::::::::::::::::::::::::::::::::::::: 24 3.2.2.1 Name Directives ::::::::::::::::::::::::::::::::::::: 24 3.2.2.2 Ownership Directives :::::::::::::::::::::::::::::::: 25 3.2.2.3 Size Directives ::::::::::::::::::::::::::::::::::::::: 25 3.2.2.4 Location Directives :::::::::::::::::::::::::::::::::: 26 3.2.2.5 Time Directives:::::::::::::::::::::::::::::::::::::: 26 3.2.2.6 Other Directives ::::::::::::::::::::::::::::::::::::: 26 3.2.2.7 Reserved and Unknown Directives:::::::::::::::::::: 27 3.2.3 Time Formats :::::::::::::::::::::::::::::::::::::::::::: 27 3.2.3.1 Time Components ::::::::::::::::::::::::::::::::::: 27 3.2.3.2 Date Components:::::::::::::::::::::::::::::::::::: 27 3.2.3.3 Combined Time Formats::::::::::::::::::::::::::::: 28 ii 3.2.4 Formatting Flags ::::::::::::::::::::::::::::::::::::::::: 28 3.3 Run Commands ::::::::::::::::::::::::::::::::::::::::::::::: 28 3.3.1 Single File :::::::::::::::::::::::::::::::::::::::::::::::: 29 3.3.2 Multiple Files :::::::::::::::::::::::::::::::::::::::::::: 30 3.3.2.1 Unsafe File Name Handling :::::::::::::::::::::::::: 31 3.3.2.2 Safe File Name Handling::::::::::::::::::::::::::::: 32 3.3.2.3 Unusual Characters in File Names ::::::::::::::::::: 32 3.3.2.4 Limiting Command Size ::::::::::::::::::::::::::::: 34 3.3.2.5 Controlling Parallelism::::::::::::::::::::::::::::::: 34 3.3.2.6 Interspersing File Names ::::::::::::::::::::::::::::: 36 3.3.3 Querying ::::::::::::::::::::::::::::::::::::::::::::::::: 37 3.4 Delete Files ::::::::::::::::::::::::::::::::::::::::::::::::::: 38 3.5 Adding Tests :::::::::::::::::::::::::::::::::::::::::::::::::: 38 4 File Name Databases :::::::::::::::::::::::::: 40 4.1 Database Locations:::::::::::::::::::::::::::::::::::::::::::: 40 4.2 Database Formats ::::::::::::::::::::::::::::::::::::::::::::: 40 4.2.1 LOCATE02 Database Format::::::::::::::::::::::::::::: 41 4.2.2 Sample LOCATE02 Database::::::::::::::::::::::::::::: 41 4.2.3 slocate Database Format:::::::::::::::::::::::::::::::::: 42 4.2.4 Old Database Format ::::::::::::::::::::::::::::::::::::: 42 4.3 Newline Handling ::::::::::::::::::::::::::::::::::::::::::::: 43 5 File Permissions :::::::::::::::::::::::::::::::: 44 5.1 Structure of File Permissions :::::::::::::::::::::::::::::::::: 44 5.2 Symbolic Modes ::::::::::::::::::::::::::::::::::::::::::::::: 45 5.2.1 Setting Permissions ::::::::::::::::::::::::::::::::::::::: 45 5.2.2 Copying Existing Permissions ::::::::::::::::::::::::::::: 46 5.2.3 Changing Special Permissions ::::::::::::::::::::::::::::: 46 5.2.4 Conditional Executability ::::::::::::::::::::::::::::::::: 47 5.2.5 Making Multiple Changes::::::::::::::::::::::::::::::::: 47 5.2.6 The Umask and Protection ::::::::::::::::::::::::::::::: 48 5.3 Numeric Modes ::::::::::::::::::::::::::::::::::::::::::::::: 48 6 Date input formats::::::::::::::::::::::::::::: 50 6.1 General date syntax ::::::::::::::::::::::::::::::::::::::::::: 50 6.2 Calendar date items ::::::::::::::::::::::::::::::::::::::::::: 51 6.3 Time of day items ::::::::::::::::::::::::::::::::::::::::::::: 52 6.4 Time zone items::::::::::::::::::::::::::::::::::::::::::::::: 53 6.5 Combined date and time of day items:::::::::::::::::::::::::: 53 6.6 Day of week items ::::::::::::::::::::::::::::::::::::::::::::: 53 6.7 Relative items in date strings :::::::::::::::::::::::::::::::::: 54 6.8 Pure numbers in date strings :::::::::::::::::::::::::::::::::: 55 6.9 Seconds since the Epoch ::::::::::::::::::::::::::::::::::::::: 55 6.10 Specifying time zone rules :::::::::::::::::::::::::::::::::::: 55 6.11 Authors of parse_datetime :::::::::::::::::::::::::::::::::: 56 iii 7 Configuration ::::::::::::::::::::::::::::::::::: 57 7.1 Leaf Optimisation ::::::::::::::::::::::::::::::::::::::::::::: 57 7.2 d type Optimisation ::::::::::::::::::::::::::::::::::::::::::: 57 8 Reference ::::::::::::::::::::::::::::::::::::::: 58 8.1 Invoking find ::::::::::::::::::::::::::::::::::::::::::::::::: 58 8.1.1 Filesystem Traversal Options ::::::::::::::::::::::::::::: 58 8.1.2 Warning Messages :::::::::::::::::::::::::::::::::::::::: 59 8.1.3 Optimisation Options ::::::::::::::::::::::::::::::::::::: 59 8.1.4 Debug Options ::::::::::::::::::::::::::::::::::::::::::: 60 8.1.5 Find Expressions ::::::::::::::::::::::::::::::::::::::::: 60 8.2 Invoking locate::::::::::::::::::::::::::::::::::::::::::::::: 60 8.3 Invoking updatedb :::::::::::::::::::::::::::::::::::::::::::: 63 8.4 Invoking xargs :::::::::::::::::::::::::::::::::::::::::::::::: 64 8.4.1 xargs options ::::::::::::::::::::::::::::::::::::::::::::: 64 8.4.2 Conflicting options ::::::::::::::::::::::::::::::::::::::: 66 8.4.3 Invoking the shell from xargs ::::::::::::::::::::::::::::: 67 8.5 Regular Expressions ::::::::::::::::::::::::::::::::::::::::::: 68 8.5.1 `findutils-default' regular expression syntax ::::::::::: 68 8.5.2 `emacs' regular expression syntax ::::::::::::::::::::::::: 70 8.5.3 `gnu-awk' regular expression syntax ::::::::::::::::::::::: 71 8.5.4 `grep' regular expression syntax :::::::::::::::::::::::::: 72 8.5.5 `posix-awk' regular expression syntax::::::::::::::::::::: 73 8.5.6 `awk' regular expression syntax:::::::::::::::::::::::::::: 74 8.5.7 `posix-basic' regular expression syntax :::::::::::::::::: 74 8.5.8 `posix-egrep' regular expression syntax :::::::::::::::::: 75 8.5.9 `egrep' regular expression syntax ::::::::::::::::::::::::: 76 8.5.10 `posix-extended' regular expression syntax:::::::::::::: 76 8.6 Environment Variables :::::::::::::::::::::::::::::::::::::::: 77 9 Common Tasks ::::::::::::::::::::::::::::::::: 79 9.1 Viewing And Editing :::::::::::::::::::::::::::::::::::::::::: 79 9.2 Archiving ::::::::::::::::::::::::::::::::::::::::::::::::::::: 79 9.3 Cleaning Up::::::::::::::::::::::::::::::::::::::::::::::::::: 80 9.4 Strange File Names:::::::::::::::::::::::::::::::::::::::::::: 81 9.5 Fixing Permissions :::::::::::::::::::::::::::::::::::::::::::: 81 9.6 Classifying Files ::::::::::::::::::::::::::::::::::::::::::::::: 82 10 Worked Examples::::::::::::::::::::::::::::: 83 10.1 Deleting Files :::::::::::::::::::::::::::::::::::::::::::::::: 83 10.1.1 The Traditional Way :::::::::::::::::::::::::::::::::::: 83 10.1.2 Making Use of xargs :::::::::::::::::::::::::::::::::::: 84 10.1.3 Unusual characters in filenames :::::::::::::::::::::::::: 84 10.1.4 Going back to -exec :::::::::::::::::::::::::::::::::::: 84 10.1.5 A more secure version of -exec :::::::::::::::::::::::::: 85 10.1.6 Using the -delete action :::::::::::::::::::::::::::::::: 86 10.1.7 Improving things still further :::::::::::::::::::::::::::: 86 iv 10.1.8 Conclusion :::::::::::::::::::::::::::::::::::::::::::::: 87 10.2 Copying A Subset of Files :::::::::::::::::::::::::::::::::::: 87 10.3 Updating A Timestamp File :::::::::::::::::::::::::::::::::: 88 10.3.1 Updating the Timestamp The Wrong Way ::::::::::::::: 88 10.3.2 Using the test utility to compare timestamps::::::::::::: 88 10.3.3
Load more

Recommended publications
  • At—At, Batch—Execute Commands at a Later Time
    at—at, batch—execute commands at a later time at [–csm] [–f script] [–qqueue] time [date] [+ increment] at –l [ job...] at –r job... batch at and batch read commands from standard input to be executed at a later time. at allows you to specify when the commands should be executed, while jobs queued with batch will execute when system load level permits. Executes commands read from stdin or a file at some later time. Unless redirected, the output is mailed to the user. Example A.1 1 at 6:30am Dec 12 < program 2 at noon tomorrow < program 3 at 1945 pm August 9 < program 4 at now + 3 hours < program 5 at 8:30am Jan 4 < program 6 at -r 83883555320.a EXPLANATION 1. At 6:30 in the morning on December 12th, start the job. 2. At noon tomorrow start the job. 3. At 7:45 in the evening on August 9th, start the job. 4. In three hours start the job. 5. At 8:30 in the morning of January 4th, start the job. 6. Removes previously scheduled job 83883555320.a. awk—pattern scanning and processing language awk [ –fprogram–file ] [ –Fc ] [ prog ] [ parameters ] [ filename...] awk scans each input filename for lines that match any of a set of patterns specified in prog. Example A.2 1 awk '{print $1, $2}' file 2 awk '/John/{print $3, $4}' file 3 awk -F: '{print $3}' /etc/passwd 4 date | awk '{print $6}' EXPLANATION 1. Prints the first two fields of file where fields are separated by whitespace. 2. Prints fields 3 and 4 if the pattern John is found.
    [Show full text]
  • Unix Introduction
    Unix introduction Mikhail Dozmorov Summer 2018 Mikhail Dozmorov Unix introduction Summer 2018 1 / 37 What is Unix Unix is a family of operating systems and environments that exploits the power of linguistic abstractions to perform tasks Unix is not an acronym; it is a pun on “Multics”. Multics was a large multi-user operating system that was being developed at Bell Labs shortly before Unix was created in the early ’70s. Brian Kernighan is credited with the name. All computational genomics is done in Unix http://www.read.seas.harvard.edu/~kohler/class/aosref/ritchie84evolution.pdfMikhail Dozmorov Unix introduction Summer 2018 2 / 37 History of Unix Initial file system, command interpreter (shell), and process management started by Ken Thompson File system and further development from Dennis Ritchie, as well as Doug McIlroy and Joe Ossanna Vast array of simple, dependable tools that each do one simple task Ken Thompson (sitting) and Dennis Ritchie working together at a PDP-11 Mikhail Dozmorov Unix introduction Summer 2018 3 / 37 Philosophy of Unix Vast array of simple, dependable tools Each do one simple task, and do it really well By combining these tools, one can conduct rather sophisticated analyses The Linux help philosophy: “RTFM” (Read the Fine Manual) Mikhail Dozmorov Unix introduction Summer 2018 4 / 37 Know your Unix Unix users spend a lot of time at the command line In Unix, a word is worth a thousand mouse clicks Mikhail Dozmorov Unix introduction Summer 2018 5 / 37 Unix systems Three common types of laptop/desktop operating systems: Windows, Mac, Linux. Mac and Linux are both Unix-like! What that means for us: Unix-like operating systems are equipped with “shells”" that provide a command line user interface.
    [Show full text]
  • Fundamentals of UNIX Lab 5.4.6 – Listing Directory Information (Estimated Time: 30 Min.)
    Fundamentals of UNIX Lab 5.4.6 – Listing Directory Information (Estimated time: 30 min.) Objectives: • Learn to display directory and file information • Use the ls (list files) command with various options • Display hidden files • Display files and file types • Examine and interpret the results of a long file listing • List individual directories • List directories recursively Background: In this lab, the student will use the ls command, which is used to display the contents of a directory. This command will display a listing of all files and directories within the current directory or specified directory or directories. If no pathname is given as an argument, ls will display the contents of the current directory. The ls command will list any subdirectories and files that are in the current working directory if a pathname is specified. The ls command will also default to a wide listing and display only file and directory names. There are many options that can be used with the ls command, which makes this command one of the more flexible and useful UNIX commands. Command Format: ls [-option(s)] [pathname[s]] Tools / Preparation: a) Before starting this lab, the student should review Chapter 5, Section 4 – Listing Directory Contents b) The student will need the following: 1. A login user ID, for example user2, and a password assigned by their instructor. 2. A computer running the UNIX operating system with CDE. 3. Networked computers in classroom. Notes: 1 - 5 Fundamentals UNIX 2.0—-Lab 5.4.6 Copyright 2002, Cisco Systems, Inc. Use the diagram of the sample Class File system directory tree to assist with this lab.
    [Show full text]
  • Configuring UNIX-Specific Settings: Creating Symbolic Links : Snap
    Configuring UNIX-specific settings: Creating symbolic links Snap Creator Framework NetApp September 23, 2021 This PDF was generated from https://docs.netapp.com/us-en/snap-creator- framework/installation/task_creating_symbolic_links_for_domino_plug_in_on_linux_and_solaris_hosts.ht ml on September 23, 2021. Always check docs.netapp.com for the latest. Table of Contents Configuring UNIX-specific settings: Creating symbolic links . 1 Creating symbolic links for the Domino plug-in on Linux and Solaris hosts. 1 Creating symbolic links for the Domino plug-in on AIX hosts. 2 Configuring UNIX-specific settings: Creating symbolic links If you are going to install the Snap Creator Agent on a UNIX operating system (AIX, Linux, and Solaris), for the IBM Domino plug-in to work properly, three symbolic links (symlinks) must be created to link to Domino’s shared object files. Installation procedures vary slightly depending on the operating system. Refer to the appropriate procedure for your operating system. Domino does not support the HP-UX operating system. Creating symbolic links for the Domino plug-in on Linux and Solaris hosts You need to perform this procedure if you want to create symbolic links for the Domino plug-in on Linux and Solaris hosts. You should not copy and paste commands directly from this document; errors (such as incorrectly transferred characters caused by line breaks and hard returns) might result. Copy and paste the commands into a text editor, verify the commands, and then enter them in the CLI console. The paths provided in the following steps refer to the 32-bit systems; 64-bit systems must create simlinks to /usr/lib64 instead of /usr/lib.
    [Show full text]
  • Copy on Write Based File Systems Performance Analysis and Implementation
    Copy On Write Based File Systems Performance Analysis And Implementation Sakis Kasampalis Kongens Lyngby 2010 IMM-MSC-2010-63 Technical University of Denmark Department Of Informatics Building 321, DK-2800 Kongens Lyngby, Denmark Phone +45 45253351, Fax +45 45882673 [email protected] www.imm.dtu.dk Abstract In this work I am focusing on Copy On Write based file systems. Copy On Write is used on modern file systems for providing (1) metadata and data consistency using transactional semantics, (2) cheap and instant backups using snapshots and clones. This thesis is divided into two main parts. The first part focuses on the design and performance of Copy On Write based file systems. Recent efforts aiming at creating a Copy On Write based file system are ZFS, Btrfs, ext3cow, Hammer, and LLFS. My work focuses only on ZFS and Btrfs, since they support the most advanced features. The main goals of ZFS and Btrfs are to offer a scalable, fault tolerant, and easy to administrate file system. I evaluate the performance and scalability of ZFS and Btrfs. The evaluation includes studying their design and testing their performance and scalability against a set of recommended file system benchmarks. Most computers are already based on multi-core and multiple processor architec- tures. Because of that, the need for using concurrent programming models has increased. Transactions can be very helpful for supporting concurrent program- ming models, which ensure that system updates are consistent. Unfortunately, the majority of operating systems and file systems either do not support trans- actions at all, or they simply do not expose them to the users.
    [Show full text]
  • Administering Unidata on UNIX Platforms
    C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta UniData Administering UniData on UNIX Platforms UDT-720-ADMU-1 C:\Program Files\Adobe\FrameMaker8\UniData 7.2\7.2rebranded\ADMINUNIX\ADMINUNIXTITLE.fm March 5, 2010 1:34 pm Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Beta Notices Edition Publication date: July, 2008 Book number: UDT-720-ADMU-1 Product version: UniData 7.2 Copyright © Rocket Software, Inc. 1988-2010. All Rights Reserved. Trademarks The following trademarks appear in this publication: Trademark Trademark Owner Rocket Software™ Rocket Software, Inc. Dynamic Connect® Rocket Software, Inc. RedBack® Rocket Software, Inc. SystemBuilder™ Rocket Software, Inc. UniData® Rocket Software, Inc. UniVerse™ Rocket Software, Inc. U2™ Rocket Software, Inc. U2.NET™ Rocket Software, Inc. U2 Web Development Environment™ Rocket Software, Inc. wIntegrate® Rocket Software, Inc. Microsoft® .NET Microsoft Corporation Microsoft® Office Excel®, Outlook®, Word Microsoft Corporation Windows® Microsoft Corporation Windows® 7 Microsoft Corporation Windows Vista® Microsoft Corporation Java™ and all Java-based trademarks and logos Sun Microsystems, Inc. UNIX® X/Open Company Limited ii SB/XA Getting Started The above trademarks are property of the specified companies in the United States, other countries, or both. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names as designated by the companies who own or market them. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc., are furnished under license, and may be used and copied only in accordance with the terms of such license and with the inclusion of the copyright notice.
    [Show full text]
  • DC Console Using DC Console Application Design Software
    DC Console Using DC Console Application Design Software DC Console is easy-to-use, application design software developed specifically to work in conjunction with AML’s DC Suite. Create. Distribute. Collect. Every LDX10 handheld computer comes with DC Suite, which includes seven (7) pre-developed applications for common data collection tasks. Now LDX10 users can use DC Console to modify these applications, or create their own from scratch. AML 800.648.4452 Made in USA www.amltd.com Introduction This document briefly covers how to use DC Console and the features and settings. Be sure to read this document in its entirety before attempting to use AML’s DC Console with a DC Suite compatible device. What is the difference between an “App” and a “Suite”? “Apps” are single applications running on the device used to collect and store data. In most cases, multiple apps would be utilized to handle various operations. For example, the ‘Item_Quantity’ app is one of the most widely used apps and the most direct means to take a basic inventory count, it produces a data file showing what items are in stock, the relative quantities, and requires minimal input from the mobile worker(s). Other operations will require additional input, for example, if you also need to know the specific location for each item in inventory, the ‘Item_Lot_Quantity’ app would be a better fit. Apps can be used in a variety of ways and provide the LDX10 the flexibility to handle virtually any data collection operation. “Suite” files are simply collections of individual apps. Suite files allow you to easily manage and edit multiple apps from within a single ‘store-house’ file and provide an effortless means for device deployment.
    [Show full text]
  • Types and Programming Languages by Benjamin C
    < Free Open Study > . .Types and Programming Languages by Benjamin C. Pierce ISBN:0262162091 The MIT Press © 2002 (623 pages) This thorough type-systems reference examines theory, pragmatics, implementation, and more Table of Contents Types and Programming Languages Preface Chapter 1 - Introduction Chapter 2 - Mathematical Preliminaries Part I - Untyped Systems Chapter 3 - Untyped Arithmetic Expressions Chapter 4 - An ML Implementation of Arithmetic Expressions Chapter 5 - The Untyped Lambda-Calculus Chapter 6 - Nameless Representation of Terms Chapter 7 - An ML Implementation of the Lambda-Calculus Part II - Simple Types Chapter 8 - Typed Arithmetic Expressions Chapter 9 - Simply Typed Lambda-Calculus Chapter 10 - An ML Implementation of Simple Types Chapter 11 - Simple Extensions Chapter 12 - Normalization Chapter 13 - References Chapter 14 - Exceptions Part III - Subtyping Chapter 15 - Subtyping Chapter 16 - Metatheory of Subtyping Chapter 17 - An ML Implementation of Subtyping Chapter 18 - Case Study: Imperative Objects Chapter 19 - Case Study: Featherweight Java Part IV - Recursive Types Chapter 20 - Recursive Types Chapter 21 - Metatheory of Recursive Types Part V - Polymorphism Chapter 22 - Type Reconstruction Chapter 23 - Universal Types Chapter 24 - Existential Types Chapter 25 - An ML Implementation of System F Chapter 26 - Bounded Quantification Chapter 27 - Case Study: Imperative Objects, Redux Chapter 28 - Metatheory of Bounded Quantification Part VI - Higher-Order Systems Chapter 29 - Type Operators and Kinding Chapter 30 - Higher-Order Polymorphism Chapter 31 - Higher-Order Subtyping Chapter 32 - Case Study: Purely Functional Objects Part VII - Appendices Appendix A - Solutions to Selected Exercises Appendix B - Notational Conventions References Index List of Figures < Free Open Study > < Free Open Study > Back Cover A type system is a syntactic method for automatically checking the absence of certain erroneous behaviors by classifying program phrases according to the kinds of values they compute.
    [Show full text]
  • How to Find out the IP Address of an Omron
    Communications Middleware/Network Browser How to find an Omron Controller’s IP address Valin Corporation | www.valin.com Overview • Many Omron PLC’s have Ethernet ports or Ethernet port options • The IP address for a PLC is usually changed by the programmer • Most customers do not mark the controller with IP address (label etc.) • Very difficult to communicate to the PLC over Ethernet if the IP address is unknown. Valin Corporation | www.valin.com Simple Ethernet Network Basics IP address is up to 12 digits (4 octets) Ex:192.168.1.1 For MOST PLC programming applications, the first 3 octets are the network address and the last is the node address. In above example 192.168.1 is network address, 1 is node address. For devices to communicate on a simple network: • Every device IP Network address must be the same. • Every device node number must be different. Device Laptop EX: Omron PLC 192.168.1.1 192.168.1.1 Device Laptop EX: Omron PLC 127.27.250.5 192.168.1.1 Device Laptop EX: Omron PLC 192.168.1.3 192.168.1.1 Valin Corporation | www.valin.com Omron Default IP Address • Most Omron Ethernet devices use one of the following IP addresses by default. Omron PLC 192.168.250.1 OR 192.168.1.1 Valin Corporation | www.valin.com PING Command • PING is a way to check if the device is connected (both virtually and physically) to the network. • Windows Command Prompt command. • PC must use the same network number as device (See previous) • Example: “ping 172.21.90.5” will test to see if a device with that IP address is connected to the PC.
    [Show full text]
  • Disk Clone Industrial
    Disk Clone Industrial USER MANUAL Ver. 1.0.0 Updated: 9 June 2020 | Contents | ii Contents Legal Statement............................................................................... 4 Introduction......................................................................................4 Cloning Data.................................................................................................................................... 4 Erasing Confidential Data..................................................................................................................5 Disk Clone Overview.......................................................................6 System Requirements....................................................................................................................... 7 Software Licensing........................................................................................................................... 7 Software Updates............................................................................................................................. 8 Getting Started.................................................................................9 Disk Clone Installation and Distribution.......................................................................................... 12 Launching and initial Configuration..................................................................................................12 Navigating Disk Clone.....................................................................................................................14
    [Show full text]
  • Cisco Telepresence ISDN Link API Reference Guide (IL1.1)
    Cisco TelePresence ISDN Link API Reference Guide Software version IL1.1 FEBRUARY 2013 CIS CO TELEPRESENCE ISDN LINK API REFERENCE guide D14953.02 ISDN Link API Referenec Guide IL1.1, February 2013. Copyright © 2013 Cisco Systems, Inc. All rights reserved. 1 Cisco TelePresence ISDN Link API Reference Guide ToC - HiddenWhat’s in this guide? Table of Contents text The top menu bar and the entries in the Table of Introduction ........................................................................... 4 Description of the xConfiguration commands ......................17 Contents are all hyperlinks, just click on them to go to the topic. About this guide ...................................................................... 5 Description of the xConfiguration commands ...................... 18 User documentation overview.............................................. 5 We recommend you visit our web site regularly for Technical specification ......................................................... 5 Description of the xCommand commands .......................... 44 updated versions of the user documentation. Support and software download .......................................... 5 Description of the xCommand commands ........................... 45 What’s new in this version ...................................................... 6 Go to:http://www.cisco.com/go/isdnlink-docs Description of the xStatus commands ................................ 48 Automatic pairing mode ....................................................... 6 Description of the
    [Show full text]
  • Motor Vehicle Division Prestige License Plate Application
    For State or County use only: Denied Refund Form MV-9B (Rev. 08-2017) Web and MV Manual Georgia Department of Revenue - Motor Vehicle Division Prestige License Plate Application ______________________________________________________________________________________ Purpose of this Form: This form is to be used by a vehicle owner to request the manufacture of a Special Prestige (Personalized) License Plate. This form should not be used to record a change of ownership, change of address, or change of license plate classification. How to submit this form: After reviewing the MV-9B form instructions, this fully completed form must be submitted to your local County tag office. Please refer to our website at https://mvd.dor.ga.gov/motor/tagoffices/SelectTagOffice.aspx to locate the address(es) for your specific County. OWNER INFORMATION First Name Middle Initial Last Name Suffix Owners’ Full Legal Name: Mailing Address: City: State: Zip: Telephone Number: Owner(s)’ Full Legal Name: First Name Middle Initial Last Name Suffix If secondary Owner(s) are listed Mailing Address: City: State: Zip: Telephone Number: VEHICLE INFORMATION Vehicle Identification Number (VIN): Year: Make: Model: LICENSE PLATE COMBINATION Private Passenger Vehicle (Includes Motor Home and Non-Commercial Trailer) Note: Private passenger vehicles cannot exceed seven (7) letters and/or numbers including spaces. Meaning: ___________________________ Meaning: ___________________________ Meaning: ___________________________ (Required) (Required) (Required) Motorcycle Note: Motorcycles cannot exceed six (6) letters and/or numbers including spaces. Meaning: ___________________________ Meaning: ___________________________ Meaning: ___________________________ (Required) (Required) (Required) Note: No punctuation or symbols are allowed on a license plate. Only letters, numbers, and spaces are allowed. I request that a personal prestige license plate be manufactured.
    [Show full text]