DOCSLIB.ORG

Ease Integration of UNIX, Linux and Windows-Based Computers And

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Ease Integration of UNIX, Linux and Windows-Based Computers And Product Datasheet Ease integration of UNIX, Linux and Windows-based computers and improve productivity, flexibility and power when developing or administering on Microsoft® Windows® platforms In its many forms, PTC MKS Toolkit enables • Securely Access and Administer Remote running your Unix scripts unmodified using Systems our 300-award winning utilities, and to • Effortless Control over the Quality of migrate Unix source code virtually your System Configuration unmodified to Windows using the 2700 standards-based POSIX, UNIX and X11 APIs PTC MKS Toolkit for Developers also we provide. If you need an X Server, pair up accelerates personal performance on the PTC MKS Toolkit for Developers and PTC Microsoft® Windows® platform by X/Server in PTC MKS Toolkit for including Windows specific tools to: Interoperability. The combination of the • Unify and automate software builds PTC MKS Toolkit UNIX APIs and the across UNIX and Windows command-line development environment on Microsoft® Windows® reduces the • Connect to remote UNIX and Windows complexity of a port from UNIX to machines Windows. • Access or update Windows users and groups With PTC MKS Toolkit, reduce the • Accounts, permissions, security immediate need for cross-platform training information, and local or remote and maximize the programming expertise registry entries of UNIX developers. • Query a database for information to be processed in batch mode Benefits of PTC MKS Toolkit for Developers: Issues of interoperability also affect • Lower Total Cost of Ownership development for the Web, as companies • Leverage investments in UNIX and blend together UNIX and Windows Web Windows servers. PTC MKS Toolkit for Developers • A Native Windows Architecture has high performance text utilities and specialized Web development tools that • Automation and Task Scheduling Page 1 of 16 | PTC MKS Toolkit ptc.com Product Datasheet are ideal for maintaining HTML and all Developers enables IT staff to easily and aspects of Web sites. efficiently establish, maintain and customize their organization’s Windows Lower Total Cost of Ownership network and user environment. Instead of choosing between Windows and UNIX, most IT organizations are opting for A Native Windows Architecture a mix of the two operating systems, with The ability to control Windows applications, many larger organizations using Windows interact with the latest technologies and as an add-on to their enterprise-wide improve team and inter-team backroom strategy. To decrease the total communication is key to successful cost of ownership (TCO) of their business, application development, saving valuable these companies need a single suite of time and enhancing program capabilities. tools that can help their teams be more Tuned for multibyte/Unicode characters productive. and 64-bit Windows systems, PTC provides support for the newest, most powerful “...I keep using MKS Toolkit, in systems, around the world. PTC MKS preference to Cygwin or Microsoft's Toolkit for Developers is developed on top Subsystem for UNIX-based applications, of the native Windows subsystem allowing because MKS allows use of Windows all the utilities to truly interact with any native file names in all contexts. This application or process running in the tremendously facilitates true "mixed- operating environment. Further, PTC MKS mode" development environments.” Toolkit allows you to interact with Nearspace Microsoft mail, database and Internet/ Intranet technologies. Leverage Investments in UNIX and Windows PTC MKS Toolkit’s numerous UNIX shell environments, including KornShell, bash and CShell, provide the ability to seamlessly port advanced UNIX scripts to the Windows environment. POSIX compliant file and text manipulation tools like vi, grep, and find simplify the interoperability initiative within an organization. PTC MKS Toolkit for Page 2 of 16 | PTC MKS Toolkit ptc.com Product Datasheet • Remote shell, rlogind and rexecd “The enhanced Vi and Viw features give services, for remote access to Windows our people the ability to customize their systems development environment, the way they • Remote utilities (rsh, rexec, rcp, rlogin) like it. It is a comfort to know that we can for accessing other UNIX and Windows transfer and manipulate files to and from machines remote UNIX and Windows systems, with • Visual SFTP –graphical application to the confidence that our data are secured transfer and manipulate files and-if necessary- encrypted.” to/from/on remote UNIX/Windows Steven Krauwer Project Manager, ELSNET the systems European Network in Human Language Technologies Effortless Control over the Quality of Securely Access and Administer your System Configuration Remote Systems A significant number of System By having PTC MKS Toolkit on each of your Administrators are fluent in the UNIX servers, you can connect to your network environment, so utilities that are UNIX- machines from anywhere else on your based and follow the UNIX philosophy, yet network or via a dialup line to perform operate in the Windows environment, can administration tasks. In a mixed UNIX and easily leverage the skills of these people on Windows environment, you will be able to the Windows platform. access applications on your UNIX servers, directly from your Windows desktops Harness the power of UNIX on without ever leaving your desk. Windows: • Remote access to legacy systems PTC MKS Toolkit for Developers contains through telnet, rsh, rexec. hundreds of authentic UNIX utilities such as • Secure shell client/service as well as df, du, and ls, as well as ksh, csh, and bash other secure utilities (scp, sftp). When shells. Therefore, you can immediately start you need sshd interactive using your UNIX skills and scripts on interoperability windows-to-windows or Windows windows-to-Unix – only the best will • Administer both Windows and UNIX do”. MKS Toolkit has proper tty systems using the Interoperability terminal mapping to allow Windows capabilities such as password console apps to run remotely. synchronization and remote utilities and daemons Page 3 of 16 | PTC MKS Toolkit ptc.com Product Datasheet • Use UNIX commands to perform file • Control services backups across multiple platforms • Perform complex file searches • Copy permissions UNIX system administrators will appreciate • Do UNIX-compatible backups a set of familiar commands on Windows • Move data and files between and UNIX-style command-line utilities for machines interacting with Windows features. • Remotely administer systems Windows system administrators will • Clone a system file tree or document appreciate the increased flexibility of tree traditional UNIX command-line tools in their Windows environment. Mail • Copy a standard user setup to a new administration, file management, registry user account editing, server management, the powerful • Using powerful UNIX commands such vi editor, are only a few of the many as awk, supplemented with our features of PTC MKS Toolkit products. KornShell’s dlg dialog building utility, you can get all the information Streamline your administrative workload: • Use automated scripts to: PTC MKS Toolkit for Developers • Improve manageability of Windows Features in large installations by populating • 400+ UNIX and Windows command-line and managing registry entries en- utilities (full POSIX.2 specification) masse • A wide selection of command • Administer user accounts in batch environments, (KornShell, CShell, bash, (e.g., after a reorganization or a Tclsh) offering greater control, merger), instead of one by one flexibility, and a wider range of • Perform repetitive tasks on large functionality then the traditional numbers of machines Windows Command Prompt • Manage Windows environments with • Access remote UNIX, Linux, and standardized tools and scripts that also Windows systems with Secure Shell work in UNIX and Linux environments utilities (secsh/secshd, scp, sftp), • Easily perform other common tasks Remote Shell utilities (rsh/rshd, that may be difficult to do using rexec/rexecd, rlogin/rlogind, rcp), standard Windows facilities telnetd, and xterm • Add users and groups Page 4 of 16 | PTC MKS Toolkit ptc.com Product Datasheet • PTC MKS Toolkit utilities use Unicode • Manipulate services, device drivers, APIs to address multibyte/Unicode Windows domains, and file associations characters within file content, file and (service, dev, domain, ftype) directory names, pipes, environment variables, console displays, and other System Administrator’s benefit areas from PTC MKS Toolkit for • A powerful scheduling interface as well as a suite of command-line utilities (at, Developers too batch, crontab, taskrun, and wts) for automating routine tasks PTC MKS Toolkit for Developers is also powerful administration suite that gives • Tools and utilities for manipulating users the ability to remotely administer HTML content (htdiff, htsplit, htstrip, systems, perform backups across multiple url, mkurl) platforms, and automate repetitive tasks • Commands to pull or push content using graphical Windows utilities. from local or remote servers, implement Web CGI scripting, and System Administration Benefits of PTC active Perl scripting (web, mkscgi, PScript™) MKS Toolkit for Developers PTC MKS Toolkit for Developers provides IT • File system handling commands organizations with: (mount, umount) and symbolic link • Access and Securely Administer Remote support Systems • Copy permissions between objects and • System Backup and File Archiving manipulate Win32 file and user security attributes (chacl,
Load more

Recommended publications
  • Beginning Portable Shell Scripting from Novice to Professional
    Beginning Portable Shell Scripting From Novice to Professional Peter Seebach 10436fmfinal 1 10/23/08 10:40:24 PM Beginning Portable Shell Scripting: From Novice to Professional Copyright © 2008 by Peter Seebach 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-13 (pbk): 978-1-4302-1043-6 ISBN-10 (pbk): 1-4302-1043-5 ISBN-13 (electronic): 978-1-4302-1044-3 ISBN-10 (electronic): 1-4302-1044-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 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: Frank Pohlmann Technical Reviewer: Gary V. Vaughan Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Michelle Lowman, Matthew Moodie, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Project Manager: Richard Dal Porto Copy Editor: Kim Benbow Associate Production Director: Kari Brooks-Copony Production Editor: Katie Stence Compositor: Linda Weidemann, Wolf Creek Press Proofreader: Dan Shaw Indexer: Broccoli Information Management Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
    [Show full text]
  • Chapter 3 Composite Default Screen Blind Folio 3:61
    Color profile: GenericORACLE CMYK printerTips & Techniques profile 8 / Oracle9i for Windows 2000 Tips & Techniques / Jesse, Sale, Hart / 9462-6 / Chapter 3 Composite Default screen Blind Folio 3:61 CHAPTER 3 Configuring Windows 2000 P:\010Comp\OracTip8\462-6\ch03.vp Wednesday, November 14, 2001 3:20:31 PM Color profile: GenericORACLE CMYK printerTips & Techniques profile 8 / Oracle9i for Windows 2000 Tips & Techniques / Jesse, Sale, Hart / 9462-6 / Chapter 3 Composite Default screen Blind Folio 3:62 62 Oracle9i for Windows 2000 Tips & Techniques here are three basic configurations of Oracle on Windows 2000: as T a management platform, as an Oracle client, and as a database server. The first configuration is the platform from which you will manage Oracle installations across various machines on various operating systems. Most system and database administrators are given a desktop PC to perform day-to-day tasks that are not DBA specific (such as reading e-mail). From this desktop, you can also manage Oracle components installed on other operating systems (for example, Solaris, Linux, and HP-UX). Even so, you will want to configure Windows 2000 to make your system and database administrative tasks quick and easy. The Oracle client software configuration is used in more configurations than you might first suspect: ■ Web applications that connect to an Oracle database: ■ IIS 5 ASPs that use ADO to connect to an Oracle database ■ Perl DBI application running on Apache that connects to an Oracle database ■ Any J2EE application server that uses the thick JDBC driver ■ Client/server applications: ■ Desktop Visual Basic application that uses OLEDB or ODBC to connect to an Oracle Database ■ Desktop Java application that uses the thick JDBC to connect to Oracle In any of these configurations, at least an Oracle client installation is required.
    [Show full text]
  • Technical Computing on the OS … That Is Not Linux! Or How to Leverage Everything You‟Ve Learned, on a Windows Box As Well
    Tools of the trade: Technical Computing on the OS … that is not Linux! Or how to leverage everything you‟ve learned, on a Windows box as well Sean Mortazavi & Felipe Ayora Typical situation with TC/HPC folks Why I have a Windows box How I use it It was in the office when I joined Outlook / Email IT forced me PowerPoint I couldn't afford a Mac Excel Because I LIKE Windows! Gaming It's the best gaming machine Technical/Scientific computing Note: Stats completely made up! The general impression “Enterprise community” “Hacker community” Guys in suits Guys in jeans Word, Excel, Outlook Emacs, Python, gmail Run prepackaged stuff Builds/runs OSS stuff Common complaints about Windows • I have a Windows box, but Windows … • Is hard to learn… • Doesn‟t have a good shell • Doesn‟t have my favorite editor • Doesn‟t have my favorite IDE • Doesn‟t have my favorite compiler or libraries • Locks me in • Doesn‟t play well with OSS • …. • In summary: (More like ) My hope … • I have a Windows box, and Windows … • Is easy to learn… • Has excellent shells • Has my favorite editor • Supports my favorite IDE • Supports my compilers and libraries • Does not lock me in • Plays well with OSS • …. • In summary: ( or at least ) How? • Recreating a Unix like veneer over windows to minimize your learning curve • Leverage your investment in know how & code • Showing what key codes already run natively on windows just as well • Kicking the dev tires using cross plat languages Objective is to: Help you ADD to your toolbox, not take anything away from it! At a high level… • Cygwin • SUA • Windowing systems “The Unix look & feel” • Standalone shell/utils • IDE‟s • Editors General purpose development • Compilers / languages / Tools • make • Libraries • CAS environments Dedicated CAS / IDE‟s And if there is time, a couple of demos… Cygwin • What is it? • A Unix like environment for Windows.
    [Show full text]
  • ARM Optimizing C/C++ Compiler V20.2.0.LTS User's Guide (Rev. V)
    ARM Optimizing C/C++ Compiler v20.2.0.LTS User's Guide Literature Number: SPNU151V January 1998–Revised February 2020 Contents Preface ........................................................................................................................................ 9 1 Introduction to the Software Development Tools.................................................................... 12 1.1 Software Development Tools Overview ................................................................................. 13 1.2 Compiler Interface.......................................................................................................... 15 1.3 ANSI/ISO Standard ........................................................................................................ 15 1.4 Output Files ................................................................................................................. 15 1.5 Utilities ....................................................................................................................... 16 2 Using the C/C++ Compiler ................................................................................................... 17 2.1 About the Compiler......................................................................................................... 18 2.2 Invoking the C/C++ Compiler ............................................................................................. 18 2.3 Changing the Compiler's Behavior with Options ......................................................................
    [Show full text]
  • Learning the Bash Shell, 3Rd Edition
    1 Learning the bash Shell, 3rd Edition Table of Contents 2 Preface bash Versions Summary of bash Features Intended Audience Code Examples Chapter Summary Conventions Used in This Handbook We'd Like to Hear from You Using Code Examples Safari Enabled Acknowledgments for the First Edition Acknowledgments for the Second Edition Acknowledgments for the Third Edition 1. bash Basics 3 1.1. What Is a Shell? 1.2. Scope of This Book 1.3. History of UNIX Shells 1.3.1. The Bourne Again Shell 1.3.2. Features of bash 1.4. Getting bash 1.5. Interactive Shell Use 1.5.1. Commands, Arguments, and Options 1.6. Files 1.6.1. Directories 1.6.2. Filenames, Wildcards, and Pathname Expansion 1.6.3. Brace Expansion 1.7. Input and Output 1.7.1. Standard I/O 1.7.2. I/O Redirection 1.7.3. Pipelines 1.8. Background Jobs 1.8.1. Background I/O 1.8.2. Background Jobs and Priorities 1.9. Special Characters and Quoting 1.9.1. Quoting 1.9.2. Backslash-Escaping 1.9.3. Quoting Quotation Marks 1.9.4. Continuing Lines 1.9.5. Control Keys 4 1.10. Help 2. Command-Line Editing 2.1. Enabling Command-Line Editing 2.2. The History List 2.3. emacs Editing Mode 2.3.1. Basic Commands 2.3.2. Word Commands 2.3.3. Line Commands 2.3.4. Moving Around in the History List 2.3.5. Textual Completion 2.3.6. Miscellaneous Commands 2.4. vi Editing Mode 2.4.1.
    [Show full text]
  • La Kornshell: Lenguaje De Programación Y Comando
    La KornShell: Lenguaje de Programación y Comando Una guía para programadores de Shell Scripts de Unix Jesús Alberto Vidal Cortés http://inicia.es/de/chube [email protected] www.kornshell.com Madrid, Agosto de 2001 Índice PARTE I: INTRODUCCIÓN......................................................................................................... 11 1. SOBRE EL LENGUAJE KORNSHELL ........................................................................................... 12 ¿Qué es una Shell?.............................................................................................................. 12 Beneficios del uso de ksh..................................................................................................... 13 Mejoras como Lenguaje de Comandos ................................................................................................................ 13 Mejoras como Lenguaje de Programación........................................................................................................... 14 Versiones a las que se aplica este manual............................................................................. 15 ¿Cómo obtener ksh?............................................................................................................ 16 2. NOTACIÓN UTILIZADA EN ESTE MANUAL..................................................................................... 18 General ............................................................................................................................... 18 Teclas sobre
    [Show full text]
  • Microsoft Windows NT from a UNIX Point of View 1
    Microsoft ® Windows NT™ from a Unix ® Point of View A White Paper from the Business Systems Technology Series Microsoft Windows NT ™ from a Unix ® Point of View A White Paper from the Business Systems Technology Series Abstract This paper provides a technical overview of Windows NT for the information technology (IT) professional with a strong background in Unix. It approaches the subject from the Unix point of view and relates the concepts of Windows NT to corresponding ones found in Unix. It begins with a technical comparison of the two operating systems, moves on to cover how the two can coexist in a heterogeneous environment, and finishes with a brief section describing some of the tools available to aid developers in creating applications for both platforms. About the Microsoft Business Systems Technology Series The Microsoft® Business Systems Technology Series consists of a number of interrelated white papers dedicated to educating information technology (IT) professionals about Windows NT and the Microsoft BackOffice™ family of products. While current technologies used in Microsoft products are often covered, the real purpose of this series is to give the reader an idea of how major technologies are evolving, how Microsoft is using those technologies, and what this means to IT planners. Legal Notice The descriptions of other companies’ products in this paper are provided only as a convenience to the reader. Microsoft cannot guarantee their accuracy, and the products may change over time. Also, the descriptions are intended as brief highlights to aid understanding, rather than as thorough coverage. For authoritative descriptions of these products, please consult their respective manufacturers.
    [Show full text]
  • Squeezing Water from Stone: Kornshell in 2019
    Squeezing Water from Stone: KornShell in 2019 Siteshwar Vashisht @SiteshwarV main() { printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);} ● Winner of IOCCC (The International Obfuscated C Code Contest) one line entry in 1987. ● Termed as best one liner ever received. ● Written by David Korn. What this talk is about ? ● It’s about AT&T KornShell (ksh, not mksh or pdksh). ● Brief status update from new upstream maintainers (Kurtis Rader and Siteshwar Vashisht). ● No deep dive in the source code. ● It is slightly extended version of my talk from FOSDEM 2019 and All Systems Go! 2019. /whois situ ● Siteshwar Vashisht. ● Based in Brno, Czech Republic. ● Maintainer of bash and ksh at Red Hat. ● Previously involved with fish shell and Sailfish OS. ● Current upstream maintainer of ksh. What is KornShell ? ● Direct descendant of Bourne shell. ● Initial development based on original bourne shell. ● Roots back to late 70’s and early 80’s. Spot the bug! #!/bin/bash echo $'hello world' | while read foo do bar="$foo" done echo "bar: " "$bar" $bar is not available outside loop. Bash forks last command in a new process and $bar is lost. Advantages ● Superior language specification (Support for Discipline functions, namespaces, compound data type, enums etc.). ● Better POSIX compliance. ● Fastest POSIX shell. Show me the numbers! $ cat test.sh for ((i=0;i<10000;i++)) do foo=$(echo "bar baz") done $ time bash test.sh $ time zsh test.sh $ time ksh test.sh real 0m2.977s real 0m2.433s real 0m0.078s user 0m2.032s user 0m1.570s user 0m0.062s sys 0m1.167s sys 0m1.233s sys 0m0.015s A 20 year old bug State of ksh in 2017 ● Previous developers have left.
    [Show full text]
  • Common Desktop Environment: Desktop Kornshell User's Guide
    Common Desktop Environment: Desktop KornShell User’s Guide Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303 U.S.A. Part No: 805-3917–10 October 1998 Copyright 1998 Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303-4900 U.S.A. All rights reserved. This product or document is protected by copyright and distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, SunDocs, Java, the Java Coffee Cup logo, and Solaris are trademarks, registered trademarks, or service marks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.
    [Show full text]
  • Squeezing Water from Stone: Kornshell in 2019
    Squeezing Water from Stone: KornShell in 2019 Siteshwar Vashisht @SiteshwarV main() { printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);} ● Winner of IOCCC (The International Obfuscated C Code Contest) one line entry in 1987. ● Termed as best one liner ever received. ● Written by David Korn. What this talk is about ? ● It’s about AT&T KornShell (ksh, not mksh or pdksh). ● Brief status update from new upstream maintainers (Kurtis Rader and Siteshwar Vashisht). ● No deep dive in the source code. ● It is slightly extended version of my talk from FOSDEM 2019. /whois situ ● Siteshwar Vashisht. ● Based in Brno, Czech Republic. ● Maintainer of bash and ksh at Red Hat. ● Previously involved with fish shell and Sailfish OS. ● Current upstream maintainer of ksh. What is KornShell ? ● Direct descendant of Bourne shell. ● Initial development based on original bourne shell. ● Roots back to late 70’s and early 80’s. Spot the bug! #!/bin/bash echo $'hello world' | while read foo do bar="$foo" done echo "bar: " "$bar" $bar is not available outside loop. Bash forks last command in a new process and $bar is lost. Advantages ● Superior language specification (Support for Discipline functions, namespaces, compound data type, enums etc.). ● Better POSIX compliance. ● Fastest POSIX shell. Show me the numbers! $ cat test.sh for ((i=0;i<10000;i++)) do foo=$(echo "bar baz") done $ time bash test.sh $ time zsh test.sh $ time ksh test.sh real 0m2.977s real 0m2.433s real 0m0.078s user 0m2.032s user 0m1.570s user 0m0.062s sys 0m1.167s sys 0m1.233s sys 0m0.015s A 20 year old bug State of ksh in 2017 ● Previous developers have left.
    [Show full text]
  • Building and Installing GNU Units on Microsoft Windows with the MKS Toolkit Edition 2.1 for Units Version 2.21
    Building and Installing GNU units on Microsoft Windows with the MKS Toolkit Edition 2.1 for units Version 2.21 Jeff Conrad This manual is for building and installing GNU units (version 2.21) on Microsoft Windows with the PTC MKS Toolkit. Copyright c 2016{2020 Free Software Foundation, Inc. i Table of Contents Preface ::::::::::::::::::::::::::::::::::::::::::::::: 1 Building and Installing units ::::::::::::::::::::::: 1 Overview :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 Configuring configure :::::::::::::::::::::::::::::::::::::::::::::: 2 Customizing the Installation ::::::::::::::::::::::::::::::::::::::::: 2 Administrative Privilege ::::::::::::::::::::::::::::::::::::::::::::: 3 Environment Variables for Visual Studio ::::::::::::::::::::::::::::: 3 Initialization with the Korn Shell ::::::::::::::::::::::::::::::::: 3 Adjustment for Different Visual Studio Installations ::::::::::::::: 3 \install" Programs ::::::::::::::::::::::::::::::::::::::::::::::::::: 4 Running with Administrative Privilege :::::::::::::::::::::::::::: 4 Providing a Manifest File ::::::::::::::::::::::::::::::::::::::::: 4 Embedding a Manifest in the install Program ::::::::::::::::::::: 4 Fine Tuning Makefile ::::::::::::::::::::::::::::::: 5 Behavior of PAGER ::::::::::::::::::::::::::::::::::::::::::::::::::: 5 MKS make and Suffix Rules :::::::::::::::::::::::::::::::::::::::::: 5 Install Program :::::::::::::::::::::::::::::::::::::::::::::::::::::: 5 Icons and File Association :::::::::::::::::::::::::: 6 MKS units:::::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Squeezing Water from Stone: Kornshell in 2019
    Squeezing Water from Stone: KornShell in 2019 main() { printf(&unix["\021%six\012\0"],(unix)["have"]+"fun"-0x60);} ●Winner of IOCCC (The International Obfuscated C Code Contest) one line entry in 1987. ●Termed as best one liner ever received. ●Written by David Korn. What this talk is about ? ●It’s about AT&T KornShell (and not mksh/pdksh). ●Brief status update from new upstream maintainers (Kurtis Rader and Siteshwar Vashisht). ●No deep dive in the source code. /whois situ ●Siteshwar Vashisht. ●Based in Brno, Czech Republic. ●Maintainer of bash and ksh at Red Hat. ●Previously involved with fish shell and Sailfish OS. ●Current upstream maintainer of ksh. What is KornShell ? ●Direct descendant of Bourne shell. ●Initial development based on original bourne shell. ●Roots back to late 70s/early 80s. Advantages ●Superior language specification (Support for Discipline functions, namespaces, compound data type, enums etc.). ●Better POSIX compliance. ●Fastest POSIX shell. A 20 year old bug State of ksh in 2017 ●Previous developers have left. ●Codebase has origins going back to the 80s. ●Old Tooling. ●No revision control history. ●Almost no comments in the source code. ●Spaghetti code. ●Bad test coverage. ●Lots of old bugs. ●And ... How to maintain the unmaintainable ? One of my most productive days was throwing away 1,000 lines of code - Ken Thompson We threw away more than 500,000 lines of code. Lines of code (ksh93v-) Lines of code (current) What did we drop ? ●Support for non-POSIX operating systems. ●Reimplementation of POSIX functions. ●Entire subsystems like the AST vmalloc and locale. ●Lots of code that was not used by ksh.
    [Show full text]