DOCSLIB.ORG

Wireshark User's Guide 27488 for Wireshark 1.0.0

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Wireshark User's Guide 27488 for Wireshark 1.0.0 Wireshark User's Guide 27488 for Wireshark 1.0.0 Ulf Lamping, Richard Sharpe, NS Computer Software and Services P/L Ed Warnicke, Wireshark User's Guide: 27488 for Wireshark 1.0.0 by Ulf Lamping, Richard Sharpe, and Ed Warnicke Copyright © 2004-2008 Ulf Lamping Richard Sharpe Ed Warnicke Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later version published by the Free Software Foundation. All logos and trademarks in this document are property of their respective owner. Table of Contents Preface ............................................................................................................... ix 1. Foreword ................................................................................................ ix 2. Who should read this document? .................................................................. x 3. Acknowledgements ................................................................................... xi 4. About this document ................................................................................ xii 5. Where to get the latest copy of this document? ............................................. xiii 6. Providing feedback about this document ......................................................xiv 1. Introduction ...................................................................................................... 1 1.1. What is Wireshark? ................................................................................. 1 1.1.1. Some intended purposes ................................................................. 1 1.1.2. Features ...................................................................................... 1 1.1.3. Live capture from many different network media ................................ 2 1.1.4. Import files from many other capture programs .................................. 2 1.1.5. Export files for many other capture programs ..................................... 2 1.1.6. Many protocol decoders ................................................................. 2 1.1.7. Open Source Software ................................................................... 2 1.1.8. What Wireshark is not ................................................................... 3 1.2. System Requirements ............................................................................... 4 1.2.1. General Remarks .......................................................................... 4 1.2.2. Microsoft Windows ....................................................................... 4 1.2.3. Unix / Linux ................................................................................ 5 1.3. Where to get Wireshark? .......................................................................... 6 1.4. A brief history of Wireshark ...................................................................... 7 1.5. Development and maintenance of Wireshark ................................................ 8 1.6. Reporting problems and getting help ........................................................... 9 1.6.1. Website ...................................................................................... 9 1.6.2. Wiki ........................................................................................... 9 1.6.3. FAQ ........................................................................................... 9 1.6.4. Mailing Lists ............................................................................... 9 1.6.5. Reporting Problems ......................................................................10 1.6.6. Reporting Crashes on UNIX/Linux platforms ....................................10 1.6.7. Reporting Crashes on Windows platforms ........................................11 2. Building and Installing Wireshark ........................................................................13 2.1. Introduction ..........................................................................................13 2.2. Obtaining the source and binary distributions ...............................................14 2.3. Before you build Wireshark under UNIX ....................................................15 2.4. Building Wireshark from source under UNIX ..............................................17 2.5. Installing the binaries under UNIX ............................................................18 2.5.1. Installing from rpm's under Red Hat and alike ...................................18 2.5.2. Installing from deb's under Debian ..................................................18 2.5.3. Installing from portage under Gentoo Linux ......................................18 2.5.4. Installing from packages under FreeBSD ..........................................18 2.6. Troubleshooting during the install on Unix ..................................................19 2.7. Building from source under Windows ........................................................20 2.8. Installing Wireshark under Windows .........................................................21 2.8.1. Install Wireshark .........................................................................21 2.8.2. Manual WinPcap Installation .........................................................23 2.8.3. Update Wireshark ........................................................................23 2.8.4. Update WinPcap ..........................................................................23 2.8.5. Uninstall Wireshark .....................................................................23 2.8.6. Uninstall WinPcap .......................................................................24 3. User Interface ..................................................................................................26 3.1. Introduction ..........................................................................................26 3.2. Start Wireshark ......................................................................................27 3.3. The Main window ..................................................................................28 3.3.1. Main Window Navigation .............................................................29 3.4. The Menu .............................................................................................30 iv Wireshark User's Guide 3.5. The "File" menu .....................................................................................31 3.6. The "Edit" menu ....................................................................................34 3.7. The "View" menu ...................................................................................36 3.8. The "Go" menu ......................................................................................40 3.9. The "Capture" menu ...............................................................................42 3.10. The "Analyze" menu .............................................................................44 3.11. The "Statistics" menu ............................................................................46 3.12. The "Tools" menu .................................................................................49 3.13. The "Help" menu ..................................................................................50 3.14. The "Main" toolbar ...............................................................................52 3.15. The "Filter" toolbar ...............................................................................55 3.16. The "Packet List" pane ..........................................................................56 3.17. The "Packet Details" pane ......................................................................57 3.18. The "Packet Bytes" pane ........................................................................58 3.19. The Statusbar .......................................................................................59 4. Capturing Live Network Data .............................................................................62 4.1. Introduction ..........................................................................................62 4.2. Prerequisites ..........................................................................................63 4.3. Start Capturing ......................................................................................64 4.4. The "Capture Interfaces" dialog box ...........................................................65 4.5. The "Capture Options" dialog box .............................................................67 4.5.1. Capture frame .............................................................................67 4.5.2. Capture File(s) frame ....................................................................69 4.5.3. Stop Capture... frame ....................................................................69 4.5.4. Display Options frame ..................................................................70 4.5.5. Name Resolution frame ................................................................70 4.5.6. Buttons ......................................................................................70 4.6. The "Interface Details" dialog box .............................................................71 4.7. Capture files and file modes .....................................................................72 4.8. Link-layer header type ............................................................................74 4.9. Filtering while
Load more

Recommended publications
  • Wireshark User's Guide
    Wireshark User’s Guide For Wireshark 2.1 Ulf Lamping <ulf.lamping[AT]web.de> Richard Sharpe, NS Computer Software and Services P/L <rsharpe[AT]ns.aus.com> Ed Warnicke <hagbard[AT]physics.rutgers.edu> Wireshark User’s Guide: For Wireshark 2.1 by Ulf Lamping, Richard Sharpe, and Ed Warnicke Copyright © 2004-2014 Ulf Lamping, Richard Sharpe, Ed Warnicke Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later version published by the Free Software Foundation. All logos and trademarks in this document are property of their respective owner. Preface ...................................................................................................................... viii 1. Foreword ....................................................................................................... viii 2. Who should read this document? ....................................................................... viii 3. Acknowledgements .......................................................................................... viii 4. About this document ......................................................................................... ix 5. Where to get the latest copy of this document? ....................................................... ix 6. Providing feedback about this document ............................................................... ix 1. Introduction .............................................................................................................
    [Show full text]
  • Virtualization of the RIOT Operating System
    Computer Systems and Telematics — Distributed, Embedded Systems Diploma Thesis Virtualization of the RIOT Operating System Ludwig Ortmann Matr. 3914103 Supervisor: Dr. Emmanuel Baccelli Assisting Supervisor: Prof. Dr.-Ing. Jochen Schiller Institute of Computer Science, Freie Universität Berlin, Germany March 2, 2015 iii I hereby declare to have written this thesis on my own. I have used no other literature and resources than the ones referenced. All text passages that are literal or logical copies from other publications have been marked accordingly. All figures and pictures have been created by me or their sources are referenced accordingly. This thesis has not been submitted in the same or a similar version to any other examination board. Berlin, March 2, 2015 (Ludwig Ortmann) Abstract Abstract Software developers in the growing field of the Internet of Things face many hurdles which arise from the limitations of embedded systems and wireless networking. The employment of hardware and network virtualization promises to allow developers to test and debug hard- ware independent code without being affected by these limitations. This thesis presents RIOT native, a hardware and network emulation implementation for the RIOT operating system, which enables developers to compile and run RIOT as a process in their host operat- ing system. Running the operating system as a process allows for the use of debugging tools and techniques only available on desktop computers otherwise, the integration of common network analysis tools, and the emulation of arbitrary network topologies. By enabling the use of these tools and techniques for the development of software for distributed embedded systems, the hurdles they impose on the development process are significantly reduced.
    [Show full text]
  • Hands-On Network Forensics, FIRST 2015
    2015-04-30 WWW.FORSVARSMAKTEN.SE Hands-on Network Forensics Workshop Preparations: 1. Unzip the virtual machine from NetworkForensics_ VirtualBox.zip on your EXTENSIVE USE OF USB thumb drive to your local hard drive COMMAND LINE 2. Start VirtualBox and run the Security Onion VM IN THIS WORKSHOP 3. Log in with: user/password 1 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE Hands-on Network Forensics Erik Hjelmvik, Swedish Armed Forces CERT FIRST 2015, Berlin 2 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE Hands-on Network Forensics Workshop Preparations: 1. Unzip the virtual machine from NetworkForensics_ VirtualBox.zip on your EXTENSIVE USE OF USB thumb drive to your local hard drive COMMAND LINE 2. Start VirtualBox and run the Security Onion VM IN THIS WORKSHOP 3. Log in with: user/password 3 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE ”Password” Ned 4 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE SysAdmin: Homer 5 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE PR /Marketing: Krusty the Clown 6 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE Password Ned AB = pwned.se 7 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE pwned.se Network [INTERNET] | Default Gateway 192.168.0.1 PASSWORD-NED-XP www.pwned.se | 192.168.0.53 192.168.0.2 [TAP]--->Security- | | | Onion -----+------+---------+---------+----------------+------- | | Homer-xubuntu Krustys-PC 192.168.0.51 192.168.0.54 8 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE Security Onion 9 FM CERT 2015-04-30 WWW.FORSVARSMAKTEN.SE Paths (also on Cheat Sheet) • PCAP files: /nsm/sensor_data/securityonion_eth1/dailylogs/ • Argus files:
    [Show full text]
  • Network Intell: Enabling the Non-Expert Analysis of Large Volumes of Intercepted Network Traffic
    Chapter 1 NETWORK INTELL: ENABLING THE NON- EXPERT ANALYSIS OF LARGE VOLUMES OF INTERCEPTED NETWORK TRAFFIC Erwin van de Wiel, Mark Scanlon and Nhien-An Le-Khac Abstract In criminal investigations, telecommunication wiretaps have become a common technique used by law enforcement. While phone-based wire- tapping is well documented and the procedure for their execution are well known, the same cannot be said for Internet taps. Lawfully inter- cepted network traffic often contains a lot of encrypted traffic making it increasingly difficult to find useful information inside the traffic cap- tured. The advent of Internet-of-Things further complicates the pro- cess for non-technical investigators. The current level of complexity of intercepted network traffic is close to a point where data cannot be analysed without supervision of a digital investigator with advanced network knowledge. Current investigations focus on analysing all traffic in a chronological manner and are predominately conducted on the data contents of the intercepted traffic. This approach often becomes overly arduous when the amount of data to be analysed becomes very large. In this paper, we propose a novel approach to analyse large amounts of intercepted network traffic based on network metadata. Our approach significantly reduces the duration of the analysis and also produces an arXiv:1712.05727v2 [cs.CR] 27 Jan 2018 insight view of analysing results for the non-technical investigator. We also test our approach with a large sample of network traffic data. Keywords: Network Investigation, Big Data Forensics, Intercepted Network Traffic, Internet tap, Network Metadata Analysis, Non-Technical Investigator. 1. Introduction Lawful interception is a method that is used by the police force in some countries in almost all middle-to high-level criminal investigations.
    [Show full text]
  • I3: Maximizing Packet Capture Performance
    I3: Maximizing Packet Capture Performance Andrew Brown Agenda • Why do captures drop packets, how can you tell? • Software considerations • Hardware considerations • Potential hardware improvements • Test configurations/parameters • Performance results Sharkfest 2014 What is a drop? • Failure to capture a packet that is part of the traffic in which you’re interested • Dropped packets tend to be the most important • Capture filter will not necessarily help Sharkfest 2014 Why do drops occur? • Applications don’t know that their data is being captured • Result: Only one chance to capture a packet • What can go wrong? Let’s look at the life of a packet Sharkfest 2014 Internal packet flow • Path of a packet from NIC to application (Linux) • Switch output queue drops • Interface drops • Kernel drops Sharkfest 2014 Identifying drops • Software reports drops • L4 indicators (TCP ACKed lost segment) • L7 indicators (app-level sequence numbers revealed by dissector) Sharkfest 2014 When is (and isn’t) it necessary to take steps to maximize capture performance? • Not typically necessary when capturing traffic of <= 1G end device • More commonly necessary when capturing uplink traffic from a TAP or SPAN port • Some sort of action is almost always necessary at 10G • Methods described aren’t always necessary • Methods focus on free solutions Sharkfest 2014 Software considerations - Windows • Quit unnecessary programs • Avoid Wireshark for capturing ˗ Saves to TEMP ˗ Additional processing for packet statistics • Uses CPU • Uses memory over time, can lead
    [Show full text]
  • Airpcap User's Guide
    AirPcap User’s Guide May 2013 © 2013 Riverbed Technology. All rights reserved. Accelerate®, AirPcap®, BlockStream™, Cascade®, Cloud Steelhead®, Granite™, Interceptor®, RiOS®, Riverbed®, Shark®, SkipWare®, Steelhead®, TrafficScript®, TurboCap®, Virtual Steelhead®, Whitewater®, WinPcap®, Wireshark®, and Stingray™ are trademarks or registered trademarks of Riverbed Technology, Inc. in the United States and other countries. Riverbed and any Riverbed product or service name or logo used herein are trademarks of Riverbed Technology. All other trademarks used herein belong to their respective owners. The trademarks and logos displayed herein cannot be used without the prior written consent of Riverbed Technology or their respective owners. Riverbed Technology 199 Fremont Street San Francisco, CA 94105 Tel: +1 415 247 8800 Fax: +1 415 247 8801 www.riverbed.com 712-00090-02 ii Contents The AirPcapProduct Family .................................................................................... 1 A Brief Introduction to 802.11 ................................................................................. 2 Terminology ........................................................................................................ 2 802.11 Standards ................................................................................................. 3 Channels ............................................................................................................. 3 Types of Frames ................................................................................................
    [Show full text]
  • RIOT: an Open Source Operating System for Low-End Embedded Devices in the Iot Emmanuel Baccelli, Cenk Gundo¨ Gan,˘ Oliver Hahm, Peter Kietzmann, Martine S
    This article has been accepted for publication in a future issue of this journal, but has not been fully edited. Content may change prior to final publication. Citation information: DOI 10.1109/JIOT.2018.2815038, IEEE Internet of Things Journal 1 RIOT: an Open Source Operating System for Low-end Embedded Devices in the IoT Emmanuel Baccelli, Cenk Gundo¨ gan,˘ Oliver Hahm, Peter Kietzmann, Martine S. Lenders, Hauke Petersen, Kaspar Schleiser, Thomas C. Schmidt, and Matthias Wahlisch¨ Abstract—As the Internet of Things (IoT) emerges, compact low-end IoT devices. RIOT runs on minimal memory in the operating systems are required on low-end devices to ease devel- order of ≈10kByte, and can run on devices with neither MMU opment and portability of IoT applications. RIOT is a prominent (memory management unit) nor MPU (memory protection free and open source operating system in this space. In this paper, we provide the first comprehensive overview of RIOT. We cover unit). The goal of this paper is to provide an overview of the key components of interest to potential developers and users: RIOT, both from the operating system point of view, and from the kernel, hardware abstraction, and software modularity, both an open source software and ecosystem point of view. conceptually and in practice for various example configurations. We explain operational aspects like system boot-up, timers, power Prior work [28], [29] has surveyed the space of operating management, and the use of networking. Finally, the relevant APIs as exposed by the operating system are discussed along systems for low-end IoT devices.
    [Show full text]
  • Implementing Powerpc Linux on System I Platform
    Front cover Implementing POWER Linux on IBM System i Platform Planning and configuring Linux servers on IBM System i platform Linux distribution on IBM System i Platform installation guide Tips to run Linux servers on IBM System i platform Yessong Johng Erwin Earley Rico Franke Vlatko Kosturjak ibm.com/redbooks International Technical Support Organization Implementing POWER Linux on IBM System i Platform February 2007 SG24-6388-01 Note: Before using this information and the product it supports, read the information in “Notices” on page vii. Second Edition (February 2007) This edition applies to i5/OS V5R4, SLES10 and RHEL4. © Copyright International Business Machines Corporation 2005, 2007. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . vii Trademarks . viii Preface . ix The team that wrote this redbook. ix Become a published author . xi Comments welcome. xi Chapter 1. Introduction to Linux on System i platform . 1 1.1 Concepts and terminology . 2 1.1.1 System i platform . 2 1.1.2 Hardware management console . 4 1.1.3 Virtual Partition Manager (VPM) . 10 1.2 Brief introduction to Linux and Linux on System i platform . 12 1.2.1 Linux on System i platform . 12 1.3 Differences between existing Power5-based System i and previous System i models 13 1.3.1 Linux enhancements on Power5 / Power5+ . 14 1.4 Where to go for more information . 15 Chapter 2. Configuration planning . 17 2.1 Concepts and terminology . 18 2.1.1 Processor concepts .
    [Show full text]
  • Dr. Ralf S. Engelschall Architecture Fundamentals AF Goal Focus 00.0
    Dr. Ralf S. Engelschall Architecture Fundamentals AF Goal Focus 00.0 Step 1: Your Insight (Believe) Concepts Methods Technologies ReproductionUnauthorized Prohibited. Ralf All Rights S. Engelschall <http://engelschall.com>, Reserved. © 2018-2019 Dr. 1.0.2 (2019-06-28), Copyright Version Graphical Illustration: Ralf S. Engelschall Dr. 2010-2019 by 1.0.2 (2019-06-28), Authored Version Intellectual Content: Concepts have a larger life-time than particular technologies and products. know scope of Step 2: Our Preparation this training Concepts have to be assembled in a concise subsequent understand München (TUM) Universität Science lecture contexts in Computer only. reproduction for Technische Licensed to form to be handy in practice. task of trainee in practice apply AN ARCHITECT Step 3: Your Application 1. THINKING LIKE 1. 2. BEING GOOD AT Concepts can be applied in practice both CONCEPTUALIZATION proactive/constructive and reactive/analytical. Scope Type Focus Content Computer Literature Industry Theory knows about knows about Science more things more things Diagrams Statements (written) Abstraction Generalization Software (Conceptual) Trainer Architecture Rationales Model Theory Practice (verbal) Engineering Fundamentals Software & Examples Trainer Systems (verbal) Practice Architecture the most Instantiation relevant concepts Specialization Software Engineering Disciplines AF ANALYTICAL CONSTRUCTIVE STEERING 01.1 REQ Requirements ENV Environment RES Resources Intellectual Content: Version 1.0.7 (2010-07-21), Authored 2006-2010 by Dr. Ralf S. Engelschall, inspired by Rational Unied Process (RUP) Rational by Ralf inspired Unied Process S. Engelschall, Dr. 2006-2010 by 1.0.7 (2010-07-21), Authored Version Intellectual Content: Graphical Illustration: Version 1.0.9 (2019-06-28), Copyright © 2007-2019 Dr.
    [Show full text]
  • Introduction to Wireshark
    ¡ ¢ £ ¤ ¥ £ ¢ ¦ ¢ £ § ¨ ¤ © ¢ ¦ ¥ ¡ ¥ ¤ ¥ ¢ ¡ ¦ © £ £ ¨ ¡ ¥ ¢ ¨ ¡ 3 INTRODUCTION TO WIRESHARK As mentioned in Chapter 1, several packet-sniffing applications are available for performing network analysis, but we’ll focus mostly on Wireshark in this book. This chapter introduces Wireshark. A Brief History of Wireshark Wireshark has a very rich history. Gerald Combs, a computer science gradu- ate of the University of Missouri at Kansas City, originally developed it out of necessity. The first version of Combs’s application, called Ethereal, was released in 1998 under the GNU Public License (GPL). Eight years after releasing Ethereal, Combs left his job to pursue other career opportunities. Unfortunately, his employer at that time had full rights to the Ethereal trademarks, and Combs was unable to reach an agreement that would allow him to control the Ethereal brand. Instead, Combs and the rest of the development team rebranded the project as Wireshark in mid-2006. ¡ ¢ £ ¤ ¥ £ ¢ ¦ ¢ £ § ¨ ¤ © ¢ ¦ ¥ ¡ ¥ ¤ ¥ ¢ ¡ ¦ © £ £ ¨ ¡ ¥ ¢ ¨ ¡ Wireshark has grown dramatically in popularity, and its collaborative development team now boasts more than 500 contributors. The program that exists under the Ethereal name is no longer being developed. The Benefits of Wireshark Wireshark offers several benefits that make it appealing for everyday use. Aimed at both the up-and-coming and the expert packet analyst, it offers a variety of features to entice each. Let’s examine Wireshark according to the criteria defined in Chapter 1 for selecting a packet-sniffing tool. Supported protocols Wireshark excels in the number of protocols that it supports—more than 1,000 as of this writing. These range from common ones like IP and DHCP to more advanced proprietary proto- cols like DNP3 and BitTorrent.
    [Show full text]
  • NS-3 Advanced Tutorial: Visualization and Data Collection
    NS-3 Advanced Tutorial: Visualization and Data Collection Tom Henderson (University of Washington and Boeing Research & Technology) L. Felipe Perrone (Bucknell University) March 2013 NS-3 Consortium Meeting 1 March 2013 Outline Getting visualization and raw data from ns-3 • Tracing and packet traces • Gnuplot and Matplotlib • Flow Monitor • PyViz • NetAnim • Statistics • Data Collection Framework 2 NS-3 Consortium Meeting March 2013 Tracing requirements • Tracing is a structured form of simulation output • Example (from ns-2): + 1.84375 0 2 cbr 210 ------- 0 0.0 3.1 225 610 - 1.84375 0 2 cbr 210 ------- 0 0.0 3.1 225 610 r 1.84471 2 1 cbr 210 ------- 1 3.0 1.0 195 600 r 1.84566 2 0 ack 40 ------- 2 3.2 0.1 82 602 + 1.84566 0 2 tcp 1000 ------- 2 0.1 3.2 102 611 Problem: Tracing needs vary widely – would like to change tracing output without editing the core – would like to support multiple outputs 3 NS-3 Consortium Meeting March 2013 Tracing in ns-3 • ns-3 configures multiple 'TraceSource' objects (TracedValue, TracedCallback) • Multiple types of 'TraceSink' objects can be hooked to these sources • A special configuration namespace helps to manage access to trace sources TracedValue Config::Connect ("/path/to/traced/value", callback1); TraceSource Config::Connect ("/path/to/trace/source", callback2); TraceSource unattached NS-3 Consortium Meeting March 2013 NetDevice trace hooks • Example: CsmaNetDevice NetDevice:: CsmaNetDevice::Send () ReceiveCallback MacTx MacRx MacDrop queue Sniffer PromiscSniffer MacTxBackoff PhyTxBegin PhyRxEnd
    [Show full text]
  • Administration Système GNU/Linux
    AAddmmiinniissttrraattiioonn SSyyssttèèmmee GGNNUU//LLiinnuuxx AAddmmiinniissttrraattiioonn SSyyssttèèmmee GGNNUU//LLiinnuuxx ● Historique ● Composants ● Organisation ● Shell ● Commandes de base ● Utilisateurs & Droits ● Disques & Filesystems AAddmmiinniissttrraattiioonn SSyyssttèèmmee GGNNUU//LLiinnuuxx ● Editeurs ● Shell & commandes avancés ● Packages ● Boot & Runlevels ● Réseau ● Interfaces graphiques ● Fichiers spéciaux ● Etudes de cas HHiissttoorriiqquuee « I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu) for 386(486) AT clones. » Li nus Torvalds HHiissttoorriiqquuee UUnniixx UUnniixx P h i l o s o p h i e 1) Ce qui est petit est beau 2) Chaque programme fait une chose et la fait bien 3) Construire un prototype dès que possible 4) Choisir la portabilité plutôt que l'efficacité 5) Enregistrer les données dans des fichiers plats 6) Utiliser le logiciel comme une force 7) Utiliser les scripts shells pour accroître cette force 8) Eviter les interfaces utilisateur captives 9) Faire de chaque programme un filtre UUnniixx P h i l o s o p h i e 1) Small is beautiful. 2) Make each program do one thing well. 3) Build a prototype as soon as possible. 4) Choose portability over efficiency. 5) Store data in flat text files. 6) Use software leverage to your advantage. 7) Use shell scripts to increase leverage and portability. 8) Avoid captive user interfaces. 9) Make every program a filter. UUnniixx P h i l o s o p h i e « timtowtdi » There is more than one way to do it leitmotiv perl, qui s'applique très bien à Unix UUnniixx P h i l o s o p h i e Sous unix, tout est fichier – fichiers (!) – répertoires – devices – liens – pipes – sockets UUnniixx P h i l o s o p h i e Sous unix, les fichiers doivent être – lisibles par l'homme – exploitables simplement par la machine ...donc sous Unix : – tous les fichiers de configuration sont texte..
    [Show full text]