DOCSLIB.ORG

Whole of the Proceedings

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Whole of the Proceedings AsiaBSDCon 2007 Proceedings March 8-11, 2007 Tokyo, Japan INDEX P1: A NetBSD-based IPv6 NEMO Mobile Router 001 Jean Lorchat, Koshiro Mitsuya, Romain Kuntz (Keio University, Japan) P2: Reflections on Building a High Performance Computing Cluster Using FreeBSD 009 Brooks Davis (The Aerospace Corporation/[email protected], USA) P3: Support for Radio Clocks in OpenBSD 023 Marc Balmer ([email protected], Switzerland) P4: puffs - Pass to Userspace Framework File System 029 Antti Kantee (Helsinki University of Technology, Finland) P5: An ISP Perspective, jail(8) Virtual Private Servers 043 Isaac Levy (NYC*BUG/LESMUUG, USA) P6: Nsswitch Development: Nss-modules and libc Separation and Caching 051 Michael A. Bushkov (Southern Federal University/[email protected], Russia) P7: OpenBSD as a Development Platform – Ryan McBride ([email protected], Japan) P8: How the FreeBSD Project Works 057 Robert N. M. Watson (University of Cambridge/[email protected], United Kingdom) P9: OpenBSD Network Randomness Injection: Further Improvements – Ryan McBride ([email protected], Japan) P10: SHISA: The Mobile IPv6/NEMO BS Stack Implementation Current Status 067 Keiichi Shima (Internet Initiative Japan Inc., Japan), Koshiro Mitsuya, Ryuji Wakikawa (Keio University, Japan), Tsuyoshi Momose (NEC Corporation, Japan), Keisuke Uehara (Keio University, Japan) P11: Bluffs: BSD Logging Updated Fast File System – Stephan Uphoff (Yahoo!, Inc./[email protected], USA) P12: Implementation and Evaluation of the Dual Stack Mobile IPv6 079 Koshiro Mitsuya, Ryuji Wakikawa, Jun Murai (Keio University, Japan) P13: Recent Improvements in OpenBSD's IPsec Support – Mathieu Sauve-Frankel ([email protected], Japan) P14: SCTP Introduction – Randall R. Stewart (Cisco Systems) P15: Security Measures in OpenSSH 091 Damien Miller ([email protected], Australia) P16: Porting the ZFS File System to the FreeBSD Operating System 097 Pawel Jakub Dawidek ([email protected], Poland) A NetBSD-based IPv6/NEMO Mobile Router Jean Lorchat, Koshiro Mitsuya Romain Kuntz Keio University The University of Tokyo Graduate School of Media and Governance Gr. School of Information Science and Technology Fujisawa, Kanagawa 252-8520, Japan Information and Communication Engineering Email: lorchat,[email protected] Email: [email protected] Abstract— This paper defines the problem statement NEMO Basic Support allows a group of nodes to of vehicle-embedded networking in order to communi- connect to the Internet via a gateway: the mobile cate with the infrastructure (the Internet) as well as router. It can change its point of attachment to with other cars. Based on this problem statement, we the IPv6 Internet infrastructure while maintaining explain the steps that allowed us to build a mobile router addressing this problem by using state of the all the current connections transparently for all art software. This software includes the NetBSD-current the nodes within the mobile network and their kernel and networking code developed by the Japan- correspondent nodes. The only node in the mo- based WIDE project working groups: the KAME IPv6 bile network that is managing the mobility is stack with SHISA extensions for Mobile IPv6 (MIPv6) the mobile router itself. It updates its current and Network Mobility (NEMO) support, and the Zebra- location in the Internet to a special router known based OLSR daemon with IPv6 extensions allowing for a Mobile Ad Hoc Networks (MANET) and NEMO as the home agent, which is located in the home cooperation, formerly known as MANEMO. network. The home agent maintains a table of relationships between mobile routers permanent I. INTRODUCTION addresses, temporary addresses, and mobile net- Current research on Intelligent Transportation work prefixes. All the traffic to or from the mobile System (ITS) focuses on vehicle-to-vehicle com- network is exchanged between the mobile router munication and information exchange between and the home agent through an IPv6-over-IPv6 vehicles and the infrastructure network (Internet). tunnel. This protocol can then be used to bring In the near future, vehicles will embed various global access to any car component by adding a computers and sensor nodes, making a network, mobile router to the car environment. This is one whose data will be exchanged with nodes in the of our goals in the InternetCAR project [3], and Internet for various purposes such as monitoring, we show our communication model on Fig. 1. safety, or entertainment. For that purpose, the NEMO Basic Support is thus a very likely CALM1 (Communications, Air Interface, Long architecture to ensure permanent connectivity in and Medium Range) architecture specified at ISO mobile environments. Although the main use case (TC204, WG16) recommends the usage of IPv6 would be to connect any kind of vehicles to and IPv6 mobility protocols to ensure permanent the Internet (such as cars, trains, buses, etc.), and uninterrupted communication while moving the underlying architecture would be the same in the Internet topology. (IPv6 and NEMO Basic Support) but customized NEMO Basic Support [1], specified at the IETF at the application layer according to the usages: in the NEMO Working Group [2], was standard- monitoring, safety, entertainment, etc. ized to solve the IPv6 network mobility problem. The Internet Connected Automobile Research (InternetCAR) Working Group was established 1http://www.calm.hu/ within the WIDE Project [4] since 1998 to con- 1 between Wireless LAN and cellular interfaces. However, no vehicle-to-vehicle communication is possible, and no monitoring software on the mobile router makes the evaluation of the system difficult. The purpose of this paper is twofold: first we make out and explain the constraints of such in- vehicle network architecture for both hardware and software sides. We then explain the work done on the implementation side to build a new version of the InternetCAR’s in-vehicle mobile Fig. 1. InternetCAR communication model router, based on the NetBSD operating system with respect to the previously defined constraints. We then show an evaluation of this work. II. A CONSTRAINED ENVIRONMENT As explained in the previous section, one goal of the InternetCAR project is to build an em- bedded mobile router that is suitable for car operation. And while the car environment is not as constraining as some other environments from the embedded computing domain, it still has some features that must be accounted for when choosing hardware and software solutions to spe- Fig. 2. SHISA daemons architecture cific problems. We will explain these environment peculiarities by distinguishing between hardware nect vehicles to the Internet [5], [6], [7] by and software considerations. developing the necessary tools and demonstrate A. Hardware related considerations their applicability in a real-life testbed. We aim to implement all the missing protocols to build an Since the car is moving, we have to pay extra in-vehicle Mobile Router. It is designed to support attention to the toughness of the hardware. The IPv6 mobility and multihoming (simultaneous us- road conditions can make the embedded computer age of several interfaces to share and load-balance bump, so that moving parts should be avoided as the traffic, or for fault-tolerance purposes). much as possible. And of course, as long as the InternetCAR is also developing a monitoring car is moving, it makes wireless communications application for demonstration purposes. Most of (and especially all kinds of radio communica- the outputs are freely available implementations tions) mandatory. for BSD operating systems, such as contribution As an embedded car equipment, the size of to the KAME IPv6 stack [8], and the SHISA the mobile router must be kept to a minimum in mobility stack [9]. order to save space and weight inside the car. This The previous in-vehicle mobile router was means avoiding traditional personal computer de- based on the NetBSD 1.6.2 Operating System. sign and looking for single board computer alter- The KAME IPv6 stack and SHISA stack [10] natives. were used to manage the network mobility. Basic Although AC current from the mains is not multihoming features allowed vertical handover directly available inside the car, we have sufficient 2 access to power resources through the car power must also obey the guidelines that come from source, either the alternator or the car battery. hardware constraints of the car environment. Eventually, cars are equipped with lots of cable, yet there might be no networking cables available III. INTERNETCAR TEAM IMPLEMENTATION to interconnect equipments within the car, espe- cially for current vehicles. Which means that we A. Hardware Platform might have to resort to wireless communications again to provide in-car networking. By taking all hardware-related constraints into account, we decided to use a Soekris2 single- B. Networking related considerations board computer as the key element for our mobile router. While it features an integrated processor, We have already introduced the ISO specified memory and two network controllers on the same recommendation about IPv6 and NEMO proto- board, it also provides room fox expansion with cols. These protocols allow to hide mobility in a two Cardbus and one MiniPCI slots. This will very convenient way, especially by relieving car allow us to use many wireless network interfaces. equipments from any mobility-related overhead, The mass storage is fitted through a Compact handled by the mobile router. Flash slot, which can accommodate either a flash However, in addition to these next generation card or a micro hard-disk. We chose to use flash mobility protocols, we need to take the vehicle cards to achieve a zero-spin architecture, which to vehicle (V2V) scheme into account. Using means that our mobile router has no moving part. the previously mentioned mobility protocols, V2V communication can become very painful because the traffic has to go all the way back to both B. Operating System Choice home agents. In this case, protocols for mobile ad We chose the NetBSD operating system for hoc networks can be used to discover neighboring several reasons.
Load more

Recommended publications
  • La Sécurité Informatique Edition Livres Pour Tous (
    La sécurité informatique Edition Livres pour tous (www.livrespourtous.com) PDF générés en utilisant l’atelier en source ouvert « mwlib ». Voir http://code.pediapress.com/ pour plus d’informations. PDF generated at: Sat, 13 Jul 2013 18:26:11 UTC Contenus Articles 1-Principes généraux 1 Sécurité de l'information 1 Sécurité des systèmes d'information 2 Insécurité du système d'information 12 Politique de sécurité du système d'information 17 Vulnérabilité (informatique) 21 Identité numérique (Internet) 24 2-Attaque, fraude, analyse et cryptanalyse 31 2.1-Application 32 Exploit (informatique) 32 Dépassement de tampon 34 Rétroingénierie 40 Shellcode 44 2.2-Réseau 47 Attaque de l'homme du milieu 47 Attaque de Mitnick 50 Attaque par rebond 54 Balayage de port 55 Attaque par déni de service 57 Empoisonnement du cache DNS 66 Pharming 69 Prise d'empreinte de la pile TCP/IP 70 Usurpation d'adresse IP 71 Wardriving 73 2.3-Système 74 Écran bleu de la mort 74 Fork bomb 82 2.4-Mot de passe 85 Attaque par dictionnaire 85 Attaque par force brute 87 2.5-Site web 90 Cross-site scripting 90 Défacement 93 2.6-Spam/Fishing 95 Bombardement Google 95 Fraude 4-1-9 99 Hameçonnage 102 2.7-Cloud Computing 106 Sécurité du cloud 106 3-Logiciel malveillant 114 Logiciel malveillant 114 Virus informatique 120 Ver informatique 125 Cheval de Troie (informatique) 129 Hacktool 131 Logiciel espion 132 Rootkit 134 Porte dérobée 145 Composeur (logiciel) 149 Charge utile 150 Fichier de test Eicar 151 Virus de boot 152 4-Concepts et mécanismes de sécurité 153 Authentification forte
    [Show full text]
  • Portace Na Jin´E Os
    VYSOKEU´ CENˇ ´I TECHNICKE´ V BRNEˇ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA INFORMACNˇ ´ICH TECHNOLOGI´I USTAV´ INFORMACNˇ ´ICH SYSTEM´ U˚ FACULTY OF INFORMATION TECHNOLOGY DEPARTMENT OF INFORMATION SYSTEMS REDIRFS - PORTACE NA JINE´ OS PORTING OF REDIRFS ON OTHER OS DIPLOMOVA´ PRACE´ MASTER’S THESIS AUTOR PRACE´ Bc. LUKA´ Sˇ CZERNER AUTHOR VEDOUC´I PRACE´ Ing. TOMA´ Sˇ KASPˇ AREK´ SUPERVISOR BRNO 2010 Abstrakt Tato pr´acepopisuje jak pˇr´ıpravu na portaci, tak samotnou portaci Linuxov´ehomodulu RedirFS na operaˇcn´ısyst´emFreeBSD. Jsou zde pops´any z´akladn´ırozd´ılypˇr´ıstupuk Lin- uxov´emu a FreeBSD j´adru,d´alerozd´ılyv implementaci, pro RedirFS z´asadn´ı,ˇc´astij´adra a sice VFS vrstvy. D´alezkoum´amoˇznostia r˚uzn´epˇr´ıstupy k implementaci funkcionality linuxov´ehoRedirFS na operaˇcn´ımsyst´emu FreeBSD. N´aslednˇejsou zhodnoceny moˇznostia navrˇzenide´aln´ıpostup portace. N´asleduj´ıc´ıkapitoly pak popisuj´ıpoˇzadovanou funkcional- itu spolu s navrhovanou architekturou nov´ehomodulu. D´aleje detailnˇepops´ann´avrha implementace nov´ehomodulu tak, aby mˇelˇcten´aˇrjasnou pˇredstavu jak´ymzp˚usobem modul implementuje poˇzadovanou funkcionalitu. Abstract This thesis describes preparation for porting as well aw porting itself of RedirFS Linux kernel module to FreeBSD. Basic differences between Linux and FreeBSD kernels are de- scribed as well as differences in implementation of the Virtual Filesystem, crucial part for RedirFS. Further there are described possibilities and different approaches to implemen- tation RedirFS functionality to FreeBSD. Then, the possibilities are evaluated and ideal approach is proposed. Next chapters introduces erquired functionality of the new module as well as its solutions. Then the implementation details are describet so the reader can very well understand how the new module works and how the required functionality is implemented into the module.
    [Show full text]
  • Introduzione Al Mondo Freebsd
    Introduzione al mondo FreeBSD Corso avanzato Netstudent Netstudent http://netstudent.polito.it E.Richiardone [email protected] maggio 2009 CC-by http://creativecommons.org/licenses/by/2.5/it/ The FreeBSD project - 1 ·EÁ un progetto software open in parte finanziato ·Lo scopo eÁ mantenere e sviluppare il sistema operativo FreeBSD ·Nasce su CDROM come FreeBSD 1.0 nel 1993 ·Deriva da un patchkit per 386BSD, eredita codice da UNIX versione Berkeley 1977 ·Per problemi legali subisce un rallentamento, release 2.0 nel 1995 con codice royalty-free ·Dalla release 5.0 (2003) assume la struttura che ha oggi ·Disponibile per x86 32 e 64bit, ia64, MIPS, ppc, sparc... ·La mascotte (Beastie) nasce nel 1984 The FreeBSD project - 2 ·Erede di 4.4BSD (eÁ la stessa gente...) ·Sistema stabile; sviluppo uniforme; codice molto chiaro, ordinato e ben commentato ·Documentazione ufficiale ben curata ·Licenza molto permissiva, spesso attrae aziende per progetti commerciali: ·saltuariamente esterni collaborano con implementazioni ex-novo (i.e. Intel, GEOM, atheros, NDISwrapper, ZFS) ·a volte no (i.e. Windows NT) ·Semplificazione di molte caratteristiche tradizionali UNIX Di cosa si tratta Il progetto FreeBSD include: ·Un sistema base ·Bootloader, kernel, moduli, librerie di base, comandi e utility di base, servizi tradizionali ·Sorgenti completi in /usr/src (~500MB) ·EÁ giaÁ abbastanza completo (i.e. ipfw, ppp, bind, ...) ·Un sistema di gestione per software aggiuntivo ·Ports e packages ·Documentazione, canali di assistenza, strumenti di sviluppo ·i.e. Handbook,
    [Show full text]
  • The Pfsense Book Release
    The pfSense Book Release The pfSense Team May 10, 2017 CONTENTS 1 Preface 1 1.1 Acknowledgements...........................................1 1.2 Feedback.................................................3 1.3 Typographic Conventions........................................3 1.4 Authors..................................................4 2 Foreword 7 3 Introduction 9 3.1 What does pfSense stand for/mean?...................................9 3.2 Why FreeBSD?..............................................9 3.3 Common Deployments.......................................... 10 3.4 Interface Naming Terminology..................................... 11 3.5 Finding Information and Getting Help.................................. 12 3.6 Project Inception............................................. 13 4 Networking Concepts 15 4.1 Understanding Public and Private IP Addresses............................. 15 4.2 IP Subnetting Concepts......................................... 16 4.3 IP Address, Subnet and Gateway Configuration............................. 16 4.4 Understanding CIDR Subnet Mask Notation.............................. 17 4.5 CIDR Summarization.......................................... 18 4.6 Broadcast Domains............................................ 19 4.7 IPv6.................................................... 19 4.8 Brief introduction to OSI Model Layers................................. 32 5 Hardware 33 5.1 Minimum Hardware Requirements................................... 33 5.2 Hardware Selection........................................... 33
    [Show full text]
  • PC-BSD 9 Turns a New Page
    CONTENTS Dear Readers, Here is the November issue. We are happy that we didn’t make you wait for it as long as for October one. Thanks to contributors and supporters we are back and ready to give you some usefull piece of knowledge. We hope you will Editor in Chief: Patrycja Przybyłowicz enjoy it as much as we did by creating the magazine. [email protected] The opening text will tell you What’s New in BSD world. It’s a review of PC-BSD 9 by Mark VonFange. Good reading, Contributing: especially for PC-BSD users. Next in section Get Started you Mark VonFange, Toby Richards, Kris Moore, Lars R. Noldan, will �nd a great piece for novice – A Beginner’s Guide To PF Rob Somerville, Erwin Kooi, Paul McMath, Bill Harris, Jeroen van Nieuwenhuizen by Toby Richards. In Developers Corner Kris Moore will teach you how to set up and maintain your own repository on a Proofreaders: FreeBSD system. It’s a must read for eager learners. Tristan Karstens, Barry Grumbine, Zander Hill, The How To section in this issue is for those who enjoy Christopher J. Umina experimenting. Speed Daemons by Lars R Noldan is a very good and practical text. By reading it you can learn Special Thanks: how to build a highly available web application server Denise Ebery with advanced networking mechanisms in FreeBSD. The Art Director: following article is the �nal one of our GIS series. The author Ireneusz Pogroszewski will explain how to successfully manage and commission a DTP: complex GIS project.
    [Show full text]
  • BSD UNIX Toolbox 1000+ Commands for Freebsd, Openbsd
    76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iii BSD UNIX® TOOLBOX 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD®Power Users Christopher Negus François Caen 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page ii 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page i BSD UNIX® TOOLBOX 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page ii 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iii BSD UNIX® TOOLBOX 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD®Power Users Christopher Negus François Caen 76034ffirs.qxd:Toolbox 4/2/08 12:50 PM Page iv BSD UNIX® Toolbox: 1000+ Commands for FreeBSD®, OpenBSD, and NetBSD® Power Users Published by Wiley Publishing, Inc. 10475 Crosspoint Boulevard Indianapolis, IN 46256 www.wiley.com Copyright © 2008 by Wiley Publishing, Inc., Indianapolis, Indiana Published simultaneously in Canada ISBN: 978-0-470-37603-4 Manufactured in the United States of America 10 9 8 7 6 5 4 3 2 1 Library of Congress Cataloging-in-Publication Data is available from the publisher. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except as permitted under Sections 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 646-8600. Requests to the Publisher for permis- sion should be addressed to the Legal Department, Wiley Publishing, Inc., 10475 Crosspoint Blvd., Indianapolis, IN 46256, (317) 572-3447, fax (317) 572-4355, or online at http://www.wiley.com/go/permissions.
    [Show full text]
  • Advanced Integration
    ZFS: Advanced Integration Allan Jude -- [email protected] @allanjude Introduction: Allan Jude • 16 Years as FreeBSD Server Admin • FreeBSD src/doc committer (ZFS, installer, boot loader, GELI, bhyve, libucl, libxo) • FreeBSD Core Team (July 2016 - 2018) • Co-Author of “FreeBSD Mastery: ZFS” and “FreeBSD Mastery: Advanced ZFS” with Michael W. Lucas • Architect of the ScaleEngine CDN (HTTP and Video) • Host of weekly BSDNow.tv Podcast • Personally Responsible for 1000 TB of ZFS Storage ZFS: What Is It? • ZFS is a filesystem with a built in volume manager (combine multiple disks into a pool) • Space from the pool is thin-provisioned to multiple filesystems or block volumes (zvols) • All data and metadata is checksummed • Optional transparent compression • Copy-on-Write with snapshots and clones • Each filesystem is tunable with properties Snapshots and Clones • Copy-on-Write means snapshots are instant • Blocks referenced by a snapshot kept when they are removed from the live filesystem • Snapshots allows you to access the file- system as it was when snapshot was taken • No performance impact on reads/writes • Take no additional space until blocks change • Clones allow you to “fork” a filesystem Boot Environments • If the root filesystem is on ZFS, you can snapshot before an upgrade, then clone it • You now have 2 filesystems, one before the upgrade, and one after. Only takes the space of blocks that changed • FreeBSD boot loader allows you to select which one to use from a menu • Upgrade without fear, can always rollback Boot Environment Tooling • Existing tool: sysadmin/beadm • GSoC 2017: be(8) and libbe(3) • New tool supports better management of filesystem properties for boot integration • New tool will support “deep” boot environments.
    [Show full text]
  • MNHO-068 DATASHEET Intel® J1900 4 LAN 1 COM Wifi 4G Firewall Router Mini Server
    MNHO-068 DATASHEET Intel® J1900 4 LAN 1 COM WiFi 4G Firewall Router Mini Server https://www.pondesk.com/product/MNHO-068 Features ● Small Security Gateway, Firewall Router, Mini Server ● Intel® Celeron® J1900 Quad Core Processor ● 4 Threads, 2M Cache, up to 2.42 GHz ● Four Intel 82574L Gigabit Ethernet ● Support Network wake-up/PXE ● RJ45-DB9 COM (Cisco Standard) ● Support WiFi, 3G/4G WWAN Networks (optional) ● Watchdog (L256, 0~255 seconds) ● Support up to 8GB DDR3L Memory ● Support Dual Storage (mSATA SSD & 2.5" SATA SSD/HDD) ● VGA Display, USB 2.0 ● Intel® HD Graphics ● Energy Efficient 10W (idle) Low Power Consumption ● Ready for IoT - Simply Connected Using 3G/4G LTE via Mini PCIe ● Support Windows/Linux/Unix/MikroTik/Firewalls etc. ● Can be configured as a Firewall, LAN/WAN Router, VPN, DNS Server, DHCP Server ● Perfect for Security Gateway, Server, VPN and Firewall such as pfSense, Untangle, ● Sophos, Smoothwall, ClearOS, m0n0wall etc. Specifications Dimensions Processor Advanced Technologies Intel® Celeron® Processor J1900 Intel® Virtualization Technology (VT-x) 4 Core, 4 Threads Intel® 64 2M Cache, up to 2.42 GHz Enhanced Intel SpeedStep® Technology Memory Onboard I/O Support up to 8GB 1 x JVGA1 (2*12pin) W DDR3L SODIMM 1.35V Low Voltage 1 x SYS FAN (1*3pin) Single Sided non-ECC Memory 1 x CPU FAN (1*4pin) One Memory Slot 1 x ATX_4P +12V 1 x COM (2*5pin) Storage 1 x SATA2.0 Support 1 x mSATA SSD 1 x JLAN_LED (2*8pin) L H Support 1 x 2.5" SATA SSD/HDD 1 x Full height mini PCIe (For WiFi & 3G module) LAN 1 x mSATA (For SSD) 197mm
    [Show full text]
  • The Release Engineering of Freebsd 4.4
    The Release Engineering of FreeBSD 4.4 Murray Stokely [email protected] Wind River Systems Abstract different pace, and with the general assumption that they This paper describes the approach used by the FreeBSD re- have first gone into FreeBSD-CURRENT and have been lease engineering team to make production-quality releases thoroughly tested by our user community. of the FreeBSD operating system. It details the methodol- In the interim period between releases, nightly snap- ogy used for the release of FreeBSD 4.4 and describes the shots are built automatically by the FreeBSD Project build tools available for those interested in producing customized machines and made available for download from ftp: FreeBSD releases for corporate rollouts or commercial pro- //stable.FreeBSD.org. The widespread availabil- ductization. ity of binary release snapshots, and the tendency of our user community to keep up with -STABLE development with CVSup and “make world”[8] helps to keep FreeBSD- 1 Introduction STABLE in a very reliable condition even before the qual- ity assurance activities ramp up pending a major release. The development of FreeBSD is a very open process. Bug reports and feature requests are continuously sub- FreeBSD is comprised of contributions from thousands of mitted by users throughout the release cycle. Problem people around the world. The FreeBSD Project provides reports are entered into our GNATS[9] database through anonymous CVS[1] access to the general public so that email, the send-pr(1) application, or via a web-based form. others can have access to log messages, diffs between de- In addition to the multitude of different technical mailing velopment branches, and other productivity enhancements lists about FreeBSD, the FreeBSD quality-assurance mail- that formal source code management provides.
    [Show full text]
  • The Journal of AUUG Inc. Volume 25 ¯ Number 3 September 2004
    The Journal of AUUG Inc. Volume 25 ¯ Number 3 September 2004 Features: mychart Charting System for Recreational Boats 8 Lions Commentary, part 1 17 Managing Debian 24 SEQUENT: Asynchronous Distributed Data Exchange 51 Framework News: Minutes to AUUG board meeting of 5 May 2004 13 Liberal license for ancient UNIX sources 16 First Australian UNIX Developer’s Symposium: CFP 60 First Digital Pest Symposium 61 Regulars: Editorial 1 President’s Column 3 About AUUGN 4 My Home Network 5 AUUG Corporate Members 23 A Hacker’s Diary 29 Letters to AUUG 58 Chapter Meetings and Contact Details 62 AUUG Membership AppLication Form 63 ISSN 1035-7521 Print post approved by Australia Post - PP2391500002 AUUGN The journal of AUUG Inc. Volume 25, Number 3 September 2004 Editor ial Gr eg Lehey <[email protected]> After last quarter's spectacularly late delivery of For those newcomers who don't recall the “Lions AUUGN, things aregradually getting back to nor- Book”, this is the “Commentary on the Sixth Edi- mal. I had hoped to have this on your desk by tion UNIX Operating System” that John Lions the end of September,but it wasn't to be. Given wr ote for classes at UNSW back in 1977. Suppos- that that was only a couple of weeks after the “Ju- edly they werethe most-photocopied of all UNIX- ly” edition, this doesn’t seem to be such a prob- related documents. Ihad mislaid my photocopy, lem. I'm fully expecting to get the December is- poor as it was (weren't they all?) some time earli- sue out in time to keep you from boredom over er,soIwas delighted to have an easy to read ver- the Christmas break.
    [Show full text]
  • Freebsd Handbook
    FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... FreeBSD Handbook The FreeBSD Documentation Project Copyright © 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013 The FreeBSD Documentation Project Welcome to FreeBSD! This handbook covers the installation and day to day use of FreeBSD 8.3-RELEASE and FreeBSD 9.1-RELEASE. This manual is a work in progress and is the work of many individuals. As such, some sections may become dated and require updating. If you are interested in helping out with this project, send email to the FreeBSD documentation project mailing list. The latest version of this document is always available from the FreeBSD web site (previous versions of this handbook can be obtained from http://docs.FreeBSD.org/doc/). It may also be downloaded in a variety of formats and compression options from the FreeBSD FTP server or one of the numerous mirror sites. If you would prefer to have a hard copy of the handbook, you can purchase one at the FreeBSD Mall. You may also want to search the handbook. REDISTRIBUTION AND USE IN SOURCE (XML DOCBOOK) AND 'COMPILED' FORMS (XML, HTML, PDF, POSTSCRIPT, RTF AND SO FORTH) WITH OR WITHOUT MODIFICATION, ARE PERMITTED PROVIDED THAT THE FOLLOWING CONDITIONS ARE MET: 1. REDISTRIBUTIONS OF SOURCE CODE (XML DOCBOOK) MUST RETAIN THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER AS THE FIRST LINES OF THIS FILE UNMODIFIED. 2. REDISTRIBUTIONS IN COMPILED FORM (TRANSFORMED TO OTHER DTDS, CONVERTED TO PDF, POSTSCRIPT, RTF AND OTHER FORMATS) MUST REPRODUCE THE ABOVE COPYRIGHT NOTICE, THIS LIST OF CONDITIONS AND THE FOLLOWING DISCLAIMER IN THE DOCUMENTATION AND/OR OTHER MATERIALS PROVIDED WITH THE DISTRIBUTION.
    [Show full text]
  • Kratka Povijest Unixa Od Unicsa Do Freebsda I Linuxa
    Kratka povijest UNIXa Od UNICSa do FreeBSDa i Linuxa 1 Autor: Hrvoje Horvat Naslov: Kratka povijest UNIXa - Od UNICSa do FreeBSDa i Linuxa Licenca i prava korištenja: Svi imaju pravo koristiti, mijenjati, kopirati i štampati (printati) knjigu, prema pravilima GNU GPL licence. Mjesto i godina izdavanja: Osijek, 2017 ISBN: 978-953-59438-0-8 (PDF-online) URL publikacije (PDF): https://www.opensource-osijek.org/knjige/Kratka povijest UNIXa - Od UNICSa do FreeBSDa i Linuxa.pdf ISBN: 978-953- 59438-1- 5 (HTML-online) DokuWiki URL (HTML): https://www.opensource-osijek.org/dokuwiki/wiki:knjige:kratka-povijest- unixa Verzija publikacije : 1.0 Nakalada : Vlastita naklada Uz pravo svakoga na vlastito štampanje (printanje), prema pravilima GNU GPL licence. Ova knjiga je napisana unutar inicijative Open Source Osijek: https://www.opensource-osijek.org Inicijativa Open Source Osijek je član udruge Osijek Software City: http://softwarecity.hr/ UNIX je registrirano i zaštićeno ime od strane tvrtke X/Open (Open Group). FreeBSD i FreeBSD logo su registrirani i zaštićeni od strane FreeBSD Foundation. Imena i logo : Apple, Mac, Macintosh, iOS i Mac OS su registrirani i zaštićeni od strane tvrtke Apple Computer. Ime i logo IBM i AIX su registrirani i zaštićeni od strane tvrtke International Business Machines Corporation. IEEE, POSIX i 802 registrirani i zaštićeni od strane instituta Institute of Electrical and Electronics Engineers. Ime Linux je registrirano i zaštićeno od strane Linusa Torvaldsa u Sjedinjenim Američkim Državama. Ime i logo : Sun, Sun Microsystems, SunOS, Solaris i Java su registrirani i zaštićeni od strane tvrtke Sun Microsystems, sada u vlasništvu tvrtke Oracle. Ime i logo Oracle su u vlasništvu tvrtke Oracle.
    [Show full text]