DOCSLIB.ORG

Introduction to OSS

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Introduction to OSS Introduction to OSS Module 1 What Is OSS? NonStop Kernel Open System Services API, command interpreter, and utilities HP NonStop system implementation of POSIX open standards Familiar interface and capabilities on top of NonStop system fundamentals © 2002 hp (524907-001) 2 Characteristics of Open Systems Compatibility — Applications running on the system will be able to run on future versions of the system. Portability — Applications running on the operating system on a given hardware platform will run on any vendor’s system that utilizes that same operating system. Scalability — Applications written for the system will run on the full range of computer architectures and sizes. Interoperability — Applications running on the system will be able to communicate with any other system using the same networking protocols. © 2002 hp (524907-001) 3 POSIX.1 APIs POSIX.1 (API examples) abort — Generate an abnormal process abort alarm — Schedule an alarm clock — Report processor time used cos — Cosine function execv — Execute a file Program exit — Terminate a process free — Free memory pause — Suspend process execution stat — Get file status time — Get system time © 2002 hp (524907-001) 4 POSIX.2 Commands POSIX.2 (command examples) cat — Concatenate and print files cp — Copy files date — Get the date and time grep — Search a file for a pattern ls — List directory contents man — Display manual pages rmdir — Remove a directory © 2002 hp (524907-001) 5 X/OPEN XPG4 COBOL FORTRAN Pascal ADA Operating System and C (ISO and Common Usage) Languages Internationalized System Commands Calls and Libraries and Utilities (POSIX) (POSIX) Base Profile © 2002 hp (524907-001) 6 What OSS Is Not UNIX Similar but different POSIX OSS is more than just this A development environment Facilities exist, but there are better ways © 2002 hp (524907-001) 7 OSS Versus UNIX Which UNIX? SVR4 versus BSD Whose UNIX? HP-UX Solaris AIX Like UNIX, but different No UNIX kernel No UNIX system administration Only Korn shell ... © 2002 hp (524907-001) 8 Products that Use OSS HP NonStop TUXEDO iTP WebServer HP Pathway/iTS HP NonStop SQL/MX HP NonStop CORBA All Java products HP NonStop SOAP Open Source Software ported to Open System Services (OSS): Apache Perl TCL and more ... © 2002 hp (524907-001) 9 NonStop Kernel Environments Application Guardian Environment OSS Environment Database Management Database Management Systems Management Systems Management SNA,X25,TCP/IP DCE/TCP/IP Pathway TUXEDO Guardian Services Open System Svcs Guardian Utilities OSS Utilities Guardian APIs OSS APIs NonStop Kernel © 2002 hp (524907-001) 10 OSS Product Features Guardian Services Open System Services TACL POSIX.2/XPG4 Tools Tools and Utilities and Utilities POSIX.1/XPG4 API Processes Guardian API 250+ Functions File system 250+ Functions 150+ C Functions I/O Pipes/FIFOs NonStop Kernel Signals l18N (L10N) © 2002 hp (524907-001) 11 Interoperability with Guardian Environment Guardian OSS Process Process 1. Access to Guardian services from OSS 1 2 processes Guardian API OSS API 2. Access to OSS services from Guardian processes 3 4 3. Accessing Guardian files 4. Accessing OSS files and Guardian OSS objects Objects Objects © 2002 hp (524907-001) 12 OSS/Guardian Interoperability Terminals/TELNET session Common user ID scheme TACL/shell bridge Access to /G objects Access to /E objects Process status display Print job spooling File attribute display © 2002 hp (524907-001) 13 OSS Environment Differences for Guardian users: File system Commands and utilities Access by means of TCP/IP, FTP, or NFS Aliasing of spooler locations Differences for UNIX users: System administration Not “vanilla” (plain) UNIX Use of OSS and Guardian sockets © 2002 hp (524907-001) 14 OSS File System Basics Module 2 Getting In and Out Logged in directly With TELNET Available Services: OSS TACL EXIT Enter Choice> oss login: Initiated from TACL with OSH 1> osh © 2002 hp (524907-001) 16 OSS Shell (Based on Korn Shell) Shell environment /etc/profile, $HOME/.profile Aliases Functions Command line and history editing HP extensions DEFINE facilities Built-in run command -W flags © 2002 hp (524907-001) 17 OSS File System File system characteristics Hierarchical file system with path names Capability to span multiple disk volumes Single file limited to one disk volume OSS path names Case-sensitive (1023 character maximum) Access to Guardian files in the /G directory Access to remote files on other nodes by means of the /E directory © 2002 hp (524907-001) 18 OSS Hierarchy / /E dev tmp users bin /G etc usr var Nodes tty,null vi Guardian profile bill ben .profile fileA dirB © 2002 hp (524907-001) 19 Guardian filenames and OSS files OSS Pathname Guardian Filename /usr/tandem/test $VOL.ZYQ00000. Z0000D03 OSS Name Server Application Disk Process Disk volume © 2002 hp (524907-001) 20 File System Terminology Fileset — Subtree of files in the OSS filename space Pathname — A character string pointing to a file Absolute pathname — A pathname that begins with a slash (/) Relative pathname — A pathname that does not begin with a slash (/) File name — Guardian file name File descriptor — (fd) Guardian file number — (fnum) File system © 2002 hp (524907-001) 21 OSS Pathname Made up of one or more component directory names separated by slashes (/) Can be up to 1023 bytes in length; each component can be up to 255 bytes in length Component name can be any string of ASCII characters, except null (‘\0’) and slash (/) Can be absolute or relative; for example: /home/stu01/program.c program.c Tilde (~) is home directory Dot (.) is current directory Two dots (..) mean “one level up” The names of hidden files begin with a dot (.) © 2002 hp (524907-001) 22 OSS Pathname to Guardian Files (1 of 2) /G directory for local files Disk: /G/<volume>[/<subvolume>[/filename]] <volume> has no leading $ Subvolume and filename have _ - . removed Filename is truncated to eight characters Examples: $DATA.PERSONEL.EMPLOYEE is accessed as /G/DATA/PERSONEL/EMPLOYEE /G/DATA/PERSONEL/EMPL_MAST becomes $DATA.PERSONEL.EMPLMAST /G/DATA/MY-SUB/MY.FILE becomes $DATA.MYSUB.MYFILE Other devices and processes: /G/<proc> Same character removal and length restrictions as for disk files $ZVPT is accessed as /G/ZVPT © 2002 hp (524907-001) 23 OSS Pathname for Guardian Files (2 of 2) /E directory for remote systems Remote passwords needed /E/<system-name> <system-name> has no leading \ /E/<system-name>/G Examples: \REMOTE.$DATA.MYSUB.AFILE is accessed as /E/REMOTE/G/DATA/MYSUB/AFILE © 2002 hp (524907-001) 24 OSS File Types OSS pathname: /filename/filename/………./filename (dir) (dir) Regular disk file Text file Object file Data file Directory file FIFO (named pipe) file Special character file C Link (hard/symbolic) file Sockets file for an AF_UNIX socket © 2002 hp (524907-001) 25 OSS Security Uses POSIX Security Model Default permissions preset for any file type Directory file: U=rwx G=rwx O=rwx Other file types: U=rw- G=rw- O=rw- r=read, w=write, x=execute U=User (file owner access) G=Group (file Group association access) O=Other (file access for other than U and G) © 2002 hp (524907-001) 26 Some Common Directories /usr — Contains standard subdirectories: /usr/include — Header files for compilation /usr/lib — Library files for linking /usr/tandem — Optional products /bin — Standard utilities /bin/unsupported — Unsupported utilities /users — Contains subdirectories for individuals /dev — Two entries only: tty — The current terminal session null — Standard bit bucket /etc — System files © 2002 hp (524907-001) 27 /dev Directory The /dev directory (device directory) contains: tty — The current controlling terminal null — A data sink Other devices Do not appear in /dev Are added and configured in the Guardian environment © 2002 hp (524907-001) 28 OSS File System / usr bin G E System RIDDLR Volume SYSTEM SPOOL DATA / Subvolume WORK TEST DUMP File ID … … … /G/data/test/foo $DATA.TEST.FOO /E/riddlr/G/data/test/foo \RIDDLR.$DATA.TEST.FOO © 2002 hp (524907-001) 29 file and tty Commands The file command displays the file type of OSS and Guardian files The file command displays: File type of OSS and Guardian Attributes such as: File type File code Target execution environment The tty command displays terminal session name © 2002 hp (524907-001) 30 Basic Commands and Utilities Module 3 Functionally Equivalent OSS Commands for Guardian Users Navigating to directories cd versus VOLUME Displaying directories ls and ls -l versus FILES and FILEINFO Copying files cp versus FUP DUP Editing files vi (and ed) versus TEDIT and EDIT Printing files lp and lpstat versus FUP COPY and PERUSE © 2002 hp (524907-001) 32 Commands and Utilities alias cpio fold lp ps tr ar csplit gencat lpstat pwd true awk cut genxlt ls read tty basename date getconf make rm type bc dc getopts man rmdir umask bg diff grep mkcatdefs sed unalias c89 dirname head mkdir sh uname cancel echo iconv mkfifo sleep uncompress cat ed id more sort unexpand cd egrep ipcrm mv split uniq chgrp env ipcs nm strings uudecode chmod expand jobs nohup strip uuencode chown expr join od stty vi cksum false kill passwd tail wait cmp fc lex paste tar wc comm fg ln pathck tee who command fgrep locale pax test xargs compress file logger pr time yacc cp find logname printf touch zcat © 2002 hp (524907-001) 33 cd and pwd Commands cd command: Positions to different directory Uses absolute or relative pathname: $ cd /usr/tandem/webserver $ cd terry/test $ cd .. go up one level $ cd - go to previous directory Position to home directory: $ cd $ cd ~ pwd command displays current directory: $ pwd © 2002 hp (524907-001) 34 ls Command List OSS and Guardian files Lists names of OSS files Lists names of /G files -l flag for details -a flag for hidden files -r for reverse order -t for modified timestamp order Guardian extension -W flag added $ ls -Wguardian [/G[/volume[/subvol[/filename]]]] .
Load more

Recommended publications
  • A Postgresql Development Environment
    A PostgreSQL development environment Peter Eisentraut [email protected] @petereisentraut The plan tooling building testing developing documenting maintaining Tooling: Git commands Useful commands: git add (-N, -p) git ls-files git am git format-patch git apply git grep (-i, -w, -W) git bisect git log (-S, --grep) git blame -w git merge git branch (--contains, -d, -D, --list, git pull -m, -r) git push (-n, -f, -u) git checkout (file, branch, -b) git rebase git cherry-pick git reset (--hard) git clean (-f, -d, -x, -n) git show git commit (--amend, --reset, -- git status fixup, -a) git stash git diff git tag Tooling: Git configuration [diff] colorMoved = true colorMovedWS = allow-indentation-change [log] date = local [merge] conflictStyle = diff3 [rebase] autosquash = true [stash] showPatch = true [tag] sort = version:refname [versionsort] suffix = "_BETA" suffix = "_RC" Tooling: Git aliases [alias] check-whitespace = \ !git diff-tree --check $(git hash-object -t tree /dev/null) HEAD ${1:-$GIT_PREFIX} find = !git ls-files "*/$1" gtags = !git ls-files | gtags -f - st = status tags = tag -l wdiff = diff --color-words=[[:alnum:]]+ wshow = show --color-words Tooling: Git shell integration zsh vcs_info Tooling: Editor Custom settings for PostgreSQL sources exist. Advanced options: whitespace checking automatic spell checking (flyspell) automatic building (flycheck, flymake) symbol lookup ("tags") Tooling: Shell settings https://superuser.com/questions/521657/zsh-automatically-set-environment-variables-for-a-directory zstyle ':chpwd:profiles:/*/*/devel/postgresql(|/|/*)' profile postgresql chpwd_profile_postgresql() { chpwd_profile_default export EMAIL="[email protected]" alias nano='nano -T4' LESS="$LESS -x4" } Tooling — Summary Your four friends: vcs editor shell terminal Building: How to run configure ./configure -C/--config-cache --prefix=$(cd .
    [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]
  • Introduction to Command Line and Accessing Servers Remotely
    Introduction to command line and accessing servers remotely Marco Büchler, Emily Franzini, Greta Franzini, Maria Moritz eTRAP Research Group Göttingen Centre for Digital Humanities Institute of Computer Science Georg August University Göttingen, Germany DH Estonia 2015 - Text Reuse Hackathon 20. Oktober 2015 Who am I? • 2001/2 Head of Quality Assurance department in a software company • 2006 Diploma in Computer Science on big • scale co-occurrence analysis • 2007- Consultant for several SMEs in IT sector • 2008 Technical project management of eAQUA project • 2011 PI and project manager of eTRACES project • 2013 PhD in „Digital Humanities“ on Text Reuse • 2014- Head of Early Career Research Group eTRAP at Göttingen Centre for Digital Humanities DH Estonia 2015 - Text Reuse Hackathon 20. Oktober 2015 Agenda 1) Connecting to the server 2) Some command line introduction DH Estonia 2015 - Text Reuse Hackathon 20. Oktober 2015 Connecting to the server 1) Windows: Start Putty 2) Mac + Linux: Open a terminal 3) Connecting to server via ssh -l <login> 192.168.11.4 4) Enter password DH Estonia 2015 - Text Reuse Hackathon 20. Oktober 2015 Which folder am I on the server? Command: pwd (parent working directory) Usage: pwd <ENTER> Example: pwd <ENTER> DH Estonia 2015 - Text Reuse Hackathon 20. Oktober 2015 Which files and directories are contained in my pwd? Command: ls (list) Usage: ls -l <FOLDER> <ENTER> // list all files and directory one on each line ls -la <FOLDER> <ENTER> // show also hidden files ls -lh <FOLDER> <ENTER> // show e.g. files sizes in human- friendly version Example: ls -l <ENTER> ls -lh /home/mbuechler <ENTER> DH Estonia 2015 - Text Reuse Hackathon 20.
    [Show full text]
  • Wait, I Don't Want to Be the Linux Administrator for SAS VA
    SESUG Paper 88-2017 Wait, I don’t want to be the Linux Administrator for SAS VA Jonathan Boase; Zencos Consulting ABSTRACT Whether you are a new SAS administrator or switching to a Linux environment, you have a complex mission. This job becomes even more formidable when you are working with a system like SAS Visual Analytics that requires multiple users loading data daily. Eventually a user will have data issues or create a disruption that causes the system to malfunction. When that happens, what do you do next? In this paper, we will go through the basics of a SAS Visual Analytics Linux environment and how to troubleshoot the system when issues arise. INTRODUCTION Many companies choose to implement SAS Visual Analytics in a Linux environment. With a distributed deployment, it’s the only choice but many chose this operating system because it reduces operating costs. If you are the newly chosen SAS platform administrator, you might be more versed in a Windows environment and feel intimidated by Linux. This paper introduces using basic Linux commands and methods for troubleshooting a SAS Visual Analytics environment. The paper assumes that SAS Visual Analytics is installed on a SAS 9.4 platform for Linux and that the reader has some familiarity with other operating systems, such as Windows. PLATFORM ADMINISTRATION 101 SAS platform administrators work with three main product areas. Each area provides a different functionality based on the task the administrator needs to perform. The following figure defines each area and provides a general overview of its purpose. Figure 1 Platform Administrator Tools Operating System SAS Management SAS Environment •Contains installed Console Manager software •Access and manage the •Monitor the •Contains logs used for metadata environment troubleshooting •Control database •Configure custom alerts •Administer host system connections users •Manage user accounts •Manage the LASR server With any operating system, there is always a lot to learn.
    [Show full text]
  • Lecture 7 Network Management and Debugging
    SYSTEM ADMINISTRATION MTAT.08.021 LECTURE 7 NETWORK MANAGEMENT AND DEBUGGING Prepared By: Amnir Hadachi and Artjom Lind University of Tartu, Institute of Computer Science [email protected] / [email protected] 1 LECTURE 7: NETWORK MGT AND DEBUGGING OUTLINE 1.Intro 2.Network Troubleshooting 3.Ping 4.SmokePing 5.Trace route 6.Network statistics 7.Inspection of live interface activity 8.Packet sniffers 9.Network management protocols 10.Network mapper 2 1. INTRO 3 LECTURE 7: NETWORK MGT AND DEBUGGING INTRO QUOTE: Networks has tendency to increase the number of interdependencies among machine; therefore, they tend to magnify problems. • Network management tasks: ✴ Fault detection for networks, gateways, and critical servers ✴ Schemes for notifying an administrator of problems ✴ General network monitoring, to balance load and plan expansion ✴ Documentation and visualization of the network ✴ Administration of network devices from a central site 4 LECTURE 7: NETWORK MGT AND DEBUGGING INTRO Network Size 160 120 80 40 Management Procedures 0 AUTOMATION ILLUSTRATION OF NETWORK GROWTH VS MGT PROCEDURES AUTOMATION 5 LECTURE 7: NETWORK MGT AND DEBUGGING INTRO • Network: • Subnets + Routers / switches Time to consider • Automating mgt tasks: • shell scripting source: http://www.eventhelix.com/RealtimeMantra/Networking/ip_routing.htm#.VvjkA2MQhIY • network mgt station 6 2. NETWORK TROUBLES HOOTING 7 LECTURE 7: NETWORK MGT AND DEBUGGING NETWORK TROUBLESHOOTING • Many tools are available for debugging • Debugging: • Low-level (e.g. TCP/IP layer) • high-level (e.g. DNS, NFS, and HTTP) • This section progress: ping trace route GENERAL ESSENTIAL TROUBLESHOOTING netstat TOOLS STRATEGY nmap tcpdump … 8 LECTURE 7: NETWORK MGT AND DEBUGGING NETWORK TROUBLESHOOTING • Before action, principle to consider: ✴ Make one change at a time ✴ Document the situation as it was before you got involved.
    [Show full text]
  • Download the Specification
    Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 November 2020 Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 Copyright © 2014, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer 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. Warranty Disclaimer 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. Restricted Rights Notice 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
    [Show full text]
  • NOAA Technical Report NOS NGS 60
    NOAA Technical Report NOS NGS 60 NAD83 (NSR2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Rockville, MD August 2008 NOAA Technical Report NOS NGS 60 NAD 83(NSRS2007) National Readjustment Final Report Dale G. Pursell Mike Potterfield Silver Spring, MD August 2008 U.S. DEPARTMENT OF COMMERCE National Oceanic and Atmospheric Administration National Ocean Service Contents Overview ........................................................................................................................ 1 Part I. Background .................................................................................................... 5 1. North American Datum of 1983 (1986) .......................................................................... 5 2. High Accuracy Reference Networks (HARNs) .............................................................. 5 3. Continuously Operating Reference Stations (CORS) .................................................... 7 4. Federal Base Networks (FBNs) ...................................................................................... 8 5. National Readjustment .................................................................................................... 9 Part II. Data Inventory, Assessment and Input ....................................... 11 6. Preliminary GPS Project Analysis ................................................................................11 7. Master File .....................................................................................................................11
    [Show full text]
  • A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability
    A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica Electrical Engineering and Computer Sciences University of California at Berkeley Technical Report No. UCB/EECS-2014-172 http://www.eecs.berkeley.edu/Pubs/TechRpts/2014/EECS-2014-172.html October 11, 2014 Copyright © 2014, by the author(s). All rights reserved. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission. A Longitudinal and Cross-Dataset Study of Internet Latency and Path Stability Mosharaf Chowdhury Rachit Agarwal Vyas Sekar Ion Stoica UC Berkeley UC Berkeley Carnegie Mellon University UC Berkeley ABSTRACT Even though our work does not provide new active mea- We present a retrospective and longitudinal study of Internet surement techniques or new datasets, we believe that there is value in this retrospective analysis on several fronts. First, it latency and path stability using three large-scale traceroute provides a historical and longitudinal perspective of Internet datasets collected over several years: Ark and iPlane from path properties that are surprisingly lacking in the measure- 2008 to 2013 and a proprietary CDN’s traceroute dataset spanning 2012 and 2013. Using these different “lenses”, we ment community today. Second, it can help us revisit and revisit classical properties of Internet paths such as end-to- reappraise classical assumptions about path latency and sta- end latency, stability, and of routing graph structure.
    [Show full text]
  • Unix Command Line; Editors
    Unix command line; editors Karl Broman Biostatistics & Medical Informatics, UW–Madison kbroman.org github.com/kbroman @kwbroman Course web: kbroman.org/AdvData My goal in this lecture is to convince you that (a) command-line-based tools are the things to focus on, (b) you need to choose a powerful, universal text editor (you’ll use it a lot), (c) you want to be comfortable and skilled with each. For your work to be reproducible, it needs to be code-based; don’t touch that mouse! Windows vs. Mac OSX vs. Linux Remote vs. Not 2 The Windows operating system is not very programmer-friendly. Mac OSX isn’t either, but under the hood, it’s just unix. Don’t touch the mouse! Open a terminal window and start typing. I do most of my work directly on my desktop or laptop. You might prefer to work remotely on a server, instead. But I can’t stand having any lag in looking at graphics. If you use Windows... Consider Git Bash (or Cygwin) or turn on the Windows subsystem for linux 3 Cygwin is an effort to get Unix command-line tools in Windows. Git Bash combines git (for version control) and bash (the unix shell); it’s simpler to deal with than Cygwin. Linux is now accessible in Windows 10, but you have to enable it. If you use a Mac... Consider Homebrew and iTerm2 Also the XCode command line tools 4 Homebrew is a packaging system; iTerm2 is a Terminal replacement. The XCode command line tools are a must for most unixy things on a Mac.
    [Show full text]
  • Drilling Network Stacks with Packetdrill
    Drilling Network Stacks with packetdrill NEAL CARDWELL AND BARATH RAGHAVAN Neal Cardwell received an M.S. esting and troubleshooting network protocols and stacks can be in Computer Science from the painstaking. To ease this process, our team built packetdrill, a tool University of Washington, with that lets you write precise scripts to test entire network stacks, from research focused on TCP and T the system call layer down to the NIC hardware. packetdrill scripts use a Web performance. He joined familiar syntax and run in seconds, making them easy to use during develop- Google in 2002. Since then he has worked on networking software for google.com, the ment, debugging, and regression testing, and for learning and investigation. Googlebot web crawler, the network stack in Have you ever had the experience of staring at a long network trace, trying to figure out what the Linux kernel, and TCP performance and on earth went wrong? When a network protocol is not working right, how might you find the testing. [email protected] problem and fix it? Although tools like tcpdump allow us to peek under the hood, and tools like netperf help measure networks end-to-end, reproducing behavior is still hard, and know- Barath Raghavan received a ing when an issue has been fixed is even harder. Ph.D. in Computer Science from UC San Diego and a B.S. from These are the exact problems that our team used to encounter on a regular basis during UC Berkeley. He joined Google kernel network stack development. Here we describe packetdrill, which we built to enable in 2012 and was previously a scriptable network stack testing.
    [Show full text]
  • Getting to Grips with Unix and the Linux Family
    Getting to grips with Unix and the Linux family David Chiappini, Giulio Pasqualetti, Tommaso Redaelli Torino, International Conference of Physics Students August 10, 2017 According to the booklet At this end of this session, you can expect: • To have an overview of the history of computer science • To understand the general functioning and similarities of Unix-like systems • To be able to distinguish the features of different Linux distributions • To be able to use basic Linux commands • To know how to build your own operating system • To hack the NSA • To produce the worst software bug EVER According to the booklet update At this end of this session, you can expect: • To have an overview of the history of computer science • To understand the general functioning and similarities of Unix-like systems • To be able to distinguish the features of different Linux distributions • To be able to use basic Linux commands • To know how to build your own operating system • To hack the NSA • To produce the worst software bug EVER A first data analysis with the shell, sed & awk an interactive workshop 1 at the beginning, there was UNIX... 2 ...then there was GNU 3 getting hands dirty common commands wait till you see piping 4 regular expressions 5 sed 6 awk 7 challenge time What's UNIX • Bell Labs was a really cool place to be in the 60s-70s • UNIX was a OS developed by Bell labs • they used C, which was also developed there • UNIX became the de facto standard on how to make an OS UNIX Philosophy • Write programs that do one thing and do it well.
    [Show full text]
  • Cygwin User's Guide
    Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, 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 documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 .
    [Show full text]