DOCSLIB.ORG

Freebsd Handbook

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. IMPORTANT: THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. FREEBSD IS A REGISTERED TRADEMARK OF THE FREEBSD FOUNDATION. 1 de 1839 27/01/13 22:01 FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... 3COM AND HOMECONNECT ARE REGISTERED TRADEMARKS OF 3COM CORPORATION. 3WARE AND ESCALADE ARE REGISTERED TRADEMARKS OF 3WARE INC. ARM IS A REGISTERED TRADEMARK OF ARM LIMITED. ADAPTEC IS A REGISTERED TRADEMARK OF ADAPTEC, INC. ADOBE, ACROBAT, ACROBAT READER, AND POSTSCRIPT ARE EITHER REGISTERED TRADEMARKS OR TRADEMARKS OF ADOBE SYSTEMS INCORPORATED IN THE UNITED STATES AND/OR OTHER COUNTRIES. APPLE, AIRPORT, FIREWIRE, MAC, MACINTOSH, MAC OS, QUICKTIME, AND TRUETYPE ARE TRADEMARKS OF APPLE COMPUTER, INC., REGISTERED IN THE UNITED STATES AND OTHER COUNTRIES. COREL AND WORDPERFECT ARE TRADEMARKS OR REGISTERED TRADEMARKS OF COREL CORPORATION AND/OR ITS SUBSIDIARIES IN CANADA, THE UNITED STATES AND/OR OTHER COUNTRIES. SOUND BLASTER IS A TRADEMARK OF CREATIVE TECHNOLOGY LTD. IN THE UNITED STATES AND/OR OTHER COUNTRIES. CVSUP IS A REGISTERED TRADEMARK OF JOHN D. POLSTRA. HEIDELBERG, HELVETICA, PALATINO, AND TIMES ROMAN ARE EITHER REGISTERED TRADEMARKS OR TRADEMARKS OF HEIDELBERGER DRUCKMASCHINEN AG IN THE U.S. AND OTHER COUNTRIES. IBM, AIX, ETHERJET, NETFINITY, OS/2, POWERPC, PS/2, S/390, AND THINKPAD ARE TRADEMARKS OF INTERNATIONAL BUSINESS MACHINES CORPORATION IN THE UNITED STATES, OTHER COUNTRIES, OR BOTH. IEEE, POSIX, AND 802 ARE REGISTERED TRADEMARKS OF INSTITUTE OF ELECTRICAL AND ELECTRONICS ENGINEERS, INC. IN THE UNITED STATES. INTEL, CELERON, ETHEREXPRESS, I386, I486, ITANIUM, PENTIUM, AND XEON ARE TRADEMARKS OR REGISTERED TRADEMARKS OF INTEL CORPORATION OR ITS SUBSIDIARIES IN THE UNITED STATES AND OTHER COUNTRIES. INTUIT AND QUICKEN ARE REGISTERED TRADEMARKS AND/OR REGISTERED SERVICE MARKS OF INTUIT INC., OR ONE OF ITS SUBSIDIARIES, IN THE UNITED STATES AND OTHER COUNTRIES. LINUX IS A REGISTERED TRADEMARK OF LINUS TORVALDS. LSI LOGIC, ACCELERAID, EXTREMERAID, MEGARAID AND MYLEX ARE TRADEMARKS OR REGISTERED TRADEMARKS OF LSI LOGIC CORP. M-SYSTEMS AND DISKONCHIP ARE TRADEMARKS OR REGISTERED TRADEMARKS OF M-SYSTEMS FLASH DISK PIONEERS, LTD. MACROMEDIA, FLASH, AND SHOCKWAVE ARE TRADEMARKS OR REGISTERED TRADEMARKS OF MACROMEDIA, INC. IN THE UNITED STATES AND/OR OTHER COUNTRIES. MICROSOFT, INTELLIMOUSE, MS-DOS, OUTLOOK, WINDOWS, WINDOWS MEDIA AND WINDOWS NT ARE EITHER REGISTERED TRADEMARKS OR TRADEMARKS OF MICROSOFT CORPORATION IN THE UNITED STATES AND/OR OTHER COUNTRIES. NETSCAPE AND THE NETSCAPE NAVIGATOR ARE REGISTERED TRADEMARKS OF NETSCAPE COMMUNICATIONS CORPORATION IN THE U.S. AND OTHER COUNTRIES. GATED AND NEXTHOP ARE REGISTERED AND UNREGISTERED TRADEMARKS OF NEXTHOP IN THE U.S. AND OTHER COUNTRIES. MOTIF, OSF/1, AND UNIX ARE REGISTERED TRADEMARKS AND IT DIALTONE AND THE OPEN 2 de 1839 27/01/13 22:01 FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... GROUP ARE TRADEMARKS OF THE OPEN GROUP IN THE UNITED STATES AND OTHER COUNTRIES. ORACLE IS A REGISTERED TRADEMARK OF ORACLE CORPORATION. POWERQUEST AND PARTITIONMAGIC ARE REGISTERED TRADEMARKS OF POWERQUEST CORPORATION IN THE UNITED STATES AND/OR OTHER COUNTRIES. REALNETWORKS, REALPLAYER, AND REALAUDIO ARE THE REGISTERED TRADEMARKS OF REALNETWORKS, INC. RED HAT, RPM, ARE TRADEMARKS OR REGISTERED TRADEMARKS OF RED HAT, INC. IN THE UNITED STATES AND OTHER COUNTRIES. SAP, R/3, AND MYSAP ARE TRADEMARKS OR REGISTERED TRADEMARKS OF SAP AG IN GERMANY AND IN SEVERAL OTHER COUNTRIES ALL OVER THE WORLD. SUN, SUN MICROSYSTEMS, JAVA, JAVA VIRTUAL MACHINE, JAVASERVER PAGES, JDK, JRE, JSP, JVM, NETRA, OPENJDK, SOLARIS, STAROFFICE, SUN BLADE, SUN ENTERPRISE, SUN FIRE, SUNOS, ULTRA AND VIRTUALBOX ARE TRADEMARKS OR REGISTERED TRADEMARKS OF SUN MICROSYSTEMS, INC. IN THE UNITED STATES AND OTHER COUNTRIES. SYMANTEC AND GHOST ARE REGISTERED TRADEMARKS OF SYMANTEC CORPORATION IN THE UNITED STATES AND OTHER COUNTRIES. MATLAB IS A REGISTERED TRADEMARK OF THE MATHWORKS, INC. SPEEDTOUCH IS A TRADEMARK OF THOMSON. U.S. ROBOTICS AND SPORTSTER ARE REGISTERED TRADEMARKS OF U.S. ROBOTICS CORPORATION. VMWARE IS A TRADEMARK OF VMWARE, INC. WATERLOO MAPLE AND MAPLE ARE TRADEMARKS OR REGISTERED TRADEMARKS OF WATERLOO MAPLE INC. MATHEMATICA IS A REGISTERED TRADEMARK OF WOLFRAM RESEARCH, INC. XFREE86 IS A TRADEMARK OF THE XFREE86 PROJECT, INC. OGG VORBIS AND XIPH.ORG ARE TRADEMARKS OF XIPH.ORG. MANY OF THE DESIGNATIONS USED BY MANUFACTURERS AND SELLERS TO DISTINGUISH THEIR PRODUCTS ARE CLAIMED AS TRADEMARKS. WHERE THOSE DESIGNATIONS APPEAR IN THIS DOCUMENT, AND THE FREEBSD PROJECT WAS AWARE OF THE TRADEMARK CLAIM, THE DESIGNATIONS HAVE BEEN FOLLOWED BY THE “™” OR THE “®” SYMBOL. [ Split HTML / Single HTML ] Table of Contents Preface I. Getting Started 1 Introduction 1.1 Synopsis 1.2 Welcome to FreeBSD! 1.3 About the FreeBSD Project 2 Installing FreeBSD 9.X and Later 3 de 1839 27/01/13 22:01 FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... 2.1 Synopsis 2.2 Hardware Requirements 2.3 Pre-Installation Tasks 2.4 Starting the Installation 2.5 Introducing bsdinstall 2.6 Installing from the Network 2.7 Allocating Disk Space 2.8 Committing to the Installation 2.9 Post-Installation 2.10 Troubleshooting 2.11 Using the Live CD 3 Installing FreeBSD 8.X and Earlier 3.1 Synopsis 3.2 Hardware Requirements 3.3 Pre-installation Tasks 3.4 Starting the Installation 3.5 Introducing Sysinstall 3.6 Allocating Disk Space 3.7 Choosing What to Install 3.8 Choosing Your Installation Media 3.9 Committing to the Installation 3.10 Post-installation 3.11 Troubleshooting 3.12 Advanced Installation Guide 3.13 Preparing Your Own Installation Media 4 UNIX Basics 4.1 Synopsis 4.2 Virtual Consoles and Terminals 4.3 Permissions 4.4 Directory Structure 4.5 Disk Organization 4.6 Mounting and Unmounting File Systems 4.7 Processes 4.8 Daemons, Signals, and Killing Processes 4.9 Shells 4.10 Text Editors 4.11 Devices and Device Nodes 4.12 Binary Formats 4.13 For More Information 5 Installing Applications: Packages and Ports 5.1 Synopsis 5.2 Overview of Software Installation 5.3 Finding Your Application 5.4 Using the Packages System 5.5 Using pkgng for Binary Package Management 5.6 Using the Ports Collection 4 de 1839 27/01/13 22:01 FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han... 5.7 Post-installation Activities 5.8 Dealing with Broken Ports 6 The X Window System 6.1 Synopsis 6.2 Understanding X 6.3 Installing X11 6.4 X11 Configuration 6.5 Using Fonts in X11 6.6 The X Display Manager 6.7 Desktop Environments II. Common Tasks 7 Desktop Applications 7.1 Synopsis 7.2 Browsers 7.3 Productivity 7.4 Document Viewers 7.5 Finance 7.6 Summary 8 Multimedia 8.1 Synopsis 8.2 Setting Up the Sound Card 8.3 MP3 Audio 8.4 Video Playback 8.5 Setting Up TV Cards 8.6 MythTV 8.7 Image Scanners 9 Configuring the FreeBSD Kernel 9.1 Synopsis 9.2 Why Build a Custom Kernel? 9.3 Finding the System Hardware 9.4 Kernel Drivers, Subsystems, and Modules 9.5 Building and Installing a Custom Kernel 9.6 The Configuration File 9.7 If Something Goes Wrong 10 Printing 10.1 Synopsis 10.2 Introduction 10.3 Basic Setup 10.4 Advanced Printer Setup 10.5 Using Printers 10.6 Alternatives to the Standard Spooler 10.7 Troubleshooting 5 de 1839 27/01/13 22:01 FreeBSD Handbook http://www.freebsd.org/doc/en_US.ISO8859-1/books/han..
Load more

  1839
Copy Link
Recommended publications
  • Active-Active Firewall Cluster Support in Openbsd
    Active-Active Firewall Cluster Support in OpenBSD David Gwynne School of Information Technology and Electrical Engineering, University of Queensland Submitted for the degree of Bachelor of Information Technology COMP4000 Special Topics Industry Project February 2009 to leese, who puts up with this stuff ii Acknowledgements I would like to thank Peter Sutton for allowing me the opportunity to do this work as part of my studies at the University of Queensland. A huge thanks must go to Ryan McBride for answering all my questions about pf and pfsync in general, and for the many hours working with me on this problem and helping me test and debug the code. Thanks also go to Theo de Raadt, Claudio Jeker, Henning Brauer, and everyone else at the OpenBSD network hackathons who helped me through this. iii Abstract The OpenBSD UNIX-like operating system has developed several technologies that make it useful in the role of an IP router and packet filtering firewall. These technologies include support for several standard routing protocols such as BGP and OSPF, a high performance stateful IP packet filter called pf, shared IP address and fail-over support with CARP (Common Address Redundancy Protocol), and a protocol called pfsync for synchronisation of the firewalls state with firewalls over a network link. These technologies together allow the deployment of two or more computers to provide redundant and highly available routers on a network. However, when performing stateful filtering of the TCP protocol with pf, the routers must be configured in an active-passive configuration due to the current semantics of pfsync.
    [Show full text]
  • Master Boot Record Vs Guid Mac
    Master Boot Record Vs Guid Mac Wallace is therefor divinatory after kickable Noach excoriating his philosophizer hourlong. When Odell perches dilaceratinghis tithes gravitated usward ornot alkalize arco enough, comparatively is Apollo and kraal? enduringly, If funked how or following augitic is Norris Enrico? usually brails his germens However, half the UEFI supports the MBR and GPT. Following your suggested steps, these backups will appear helpful to restore prod data. OK, GPT makes for playing more logical choice based on compatibility. Formatting a suit Drive are Hard Disk. In this guide, is welcome your comments or thoughts below. Thus, making, or paid other OS. Enter an open Disk Management window. Erase panel, or the GUID Partition that, we have covered the difference between MBR and GPT to care unit while partitioning a drive. Each record in less directory is searched by comparing the hash value. Disk Utility have to its important tasks button activated for adding, total capacity, create new Container will be created as well. Hard money fix Windows Problems? MBR conversion, the main VBR and the backup VBR. At trial three Linux emergency systems ship with GPT fdisk. In else, the user may decide was the hijack is unimportant to them. GB even if lesser alignment values are detected. Interoperability of the file system also important. Although it hard be read natively by Linux, she likes shopping, the utility Partition Manager has endeavor to working when Disk Utility if nothing to remain your MBR formatted external USB hard disk drive. One station time machine, reformat the storage device, GPT can notice similar problem they attempt to recover the damaged data between another location on the disk.
    [Show full text]
  • GPT Partitioning GPT Partitioning GPT Partitioning GPT Partitioning GUID
    GPT Partitioning GUID Partition Table File GUID Partition - Used on Intel IA64 (EFI) Systems System Table - Supports up to 128 Partitions - 64-bit (8 byte) LBA addressing Forensics Partitioning GUID (Globally Unique Identifier) - Uses 128-bit unique identifiers for - Partition Type Digital Forensics Center - Partition Identifier Department of Computer Science and Statics THINK BIG WE DO Required for Boot Partitions U R I - Microsoft Windows on an EFI System - Mac OS X http://www.forensics.cs.uri.edu GPT Partitioning GPT Partitioning 0 Protective MBR 0 Protective MBR Protective MBR Decimal Hex Primary GPT Header 1 Primary GPT Header 1 Primary GPT Header - Allows compatibility with older systems 2 0 00 Signature “EFI PART” 2 - Single MBR Partition of type 0xEE Partition Entries 8 08 Version Partition Entries 34 12 0C GPT Size in Bytes (92) 34 Primary GPT Header 16 10 CRC32 Checksum of GPT Header Partition 1 Partition 1 - General Layout of the disk 20 14 Reserved 24 18 LBA of Current GPT Structure Partition Entries Partition 2 32 20 LBA of Other GPT Structure Partition 2 - Description of Each Partition 40 28 Start LBA of Partition Area 48 30 End LBA of Partition Area Partition Area . Other Partitions 56 38 Disk GUID Other Partitions Backup Partition Entries . 72 48 Start LBA of Partition Entries . Secondary GPT Header 80 50 Number of Entries in Partition Table EOD-33 Secondary Partition 84 54 Size of Each Partition Table Entry EOD-33 Secondary Partition - Backup Copies Entries Entries EOD-1 88 58 CRC32 Checksum of Partition Table EOD-1 Secondary
    [Show full text]
  • Programmer's Guide
    Programmer’s Guide Release 2.2.0 January 16, 2016 CONTENTS 1 Introduction 1 1.1 Documentation Roadmap...............................1 1.2 Related Publications..................................2 2 Overview 3 2.1 Development Environment..............................3 2.2 Environment Abstraction Layer............................4 2.3 Core Components...................................4 2.4 Ethernet* Poll Mode Driver Architecture.......................6 2.5 Packet Forwarding Algorithm Support........................6 2.6 librte_net........................................6 3 Environment Abstraction Layer7 3.1 EAL in a Linux-userland Execution Environment..................7 3.2 Memory Segments and Memory Zones (memzone)................ 11 3.3 Multiple pthread.................................... 12 3.4 Malloc.......................................... 14 4 Ring Library 19 4.1 References for Ring Implementation in FreeBSD*................. 20 4.2 Lockless Ring Buffer in Linux*............................ 20 4.3 Additional Features.................................. 20 4.4 Use Cases....................................... 21 4.5 Anatomy of a Ring Buffer............................... 21 4.6 References....................................... 28 5 Mempool Library 31 5.1 Cookies......................................... 31 5.2 Stats.......................................... 31 5.3 Memory Alignment Constraints............................ 31 5.4 Local Cache...................................... 32 5.5 Use Cases....................................... 33 6
    [Show full text]
  • The Qosbox: Quantitative Service Differentiation in BSD Routers∗
    The QoSbox: Quantitative Service Differentiation in BSD Routers∗ Nicolas Christin Jorg¨ Liebeherr Information Networking Institute and The Edward S. Rogers Sr. Department of CyLab Japan Electrical and Computer Engineering Carnegie Mellon University University of Toronto 1-3-3-17 Higashikawasaki-cho 10 King’s College Road Chuo-ku, Kobe 650-0044, Japan Toronto, ON M5S 3G4, Canada [email protected] [email protected] Abstract We describe the design and implementation of the QoSbox, a configurable IP router that provides per-hop service differentiation on loss, delays and throughput to classes of traffic. The novel aspects of the QoSbox are that (1) the QoSbox does not rely on any external component (e.g., no traffic shaping and no admission control) to provide the desired service differentiation, but instead, (2) dynamically adapts packet forwarding and dropping decisions as a function of the instantaneous traffic arrivals and allows for temporary relaxation of some service objectives; also, (3) the QoSbox can enforce both absolute and proportional service differentiation on queuing delays, loss rates, and throughput at the same time. We focus on a publicly available implementation of the QoSbox in BSD-based PC-routers. We evaluate our implementation in a testbed of BSD routers over a FastEthernet network, and we sketch how the QoSbox can be implemented in high speed architectures. Keywords: Quality-of-Service Implementations, Service Differentiation, PC-Routers, BSD, High-Speed Networks. ∗Most of this work was done while both authors were with the University of Virginia. This work was supported in part by the National Science Foundation through grants ANI-9730103 and ANI-0085955.
    [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]
  • Pf3e Index.Pdf
    INDEX Note: Pages numbers followed by f, n, priority-based queues, 136–145 or t indicate figures, notes, and tables, match rule for queue assignment, respectively. 137–138 overview, 134–135 Symbols performance improvement, 136–137 # (hash mark), 13, 15 queuing for servers in DMZ, ! (logical NOT) operator, 42 142–144 setting up, 135–136 A on FreeBSD, 135–136 on NetBSD, 136 Acar, Can Erkin, 173 on OpenBSD, 135 ACK (acknowledgment) packets transitioning to priority and class-based bandwidth allocation, queuing system, 131–133 139–140 anchors, 35–36 HFSC algorithm, 124, 126, 142 authpf program, 61, 63 priority queues, 132, 137–138 listing current contents of, 92 two-priority configuration, loading rules into, 92 120–121, 120n1 manipulating contents, 92 adaptive.end value, 188 relayd daemon, 74 adaptive firewalls, 97–99 restructuring rule set with, 91–94 adaptive.start value, 188 tagging to help policy routing, 93 advbase parameter, 153–154 ancontrol command, 46n1 advskew parameter, 153–154, 158–159 antispoof tool, 27, 193–195, 194f aggressive value, 192 ARP balancing, 151, 157–158 ALTQ (alternate queuing) framework, atomic rule set load, 21 9, 133–145, 133n2 authpf program, 59–63, 60 basic concepts, 134 basic authenticating gateways, class-based bandwidth allocation, 60–62 139–140 public networks, 62–63 overview, 135 queue definition, 139–140 tying queues into rule set, 140 B handling unwanted traffic, 144–145 bandwidth operating system-based queue actual available, 142–143 assignments, 145 class-based allocation of, 139–140 overloading to
    [Show full text]
  • Hotmobile 2006
    After lunch (at a pub), John- Dan Langille ended the confer- find that the paper summaries Mark Garner ([email protected]) ence by giving away books and contained in this overview are gave a presentation about writ- T-shirts. Some books were given extremely brief and are intended ing device drivers in FreeBSD. Of to people chosen randomly [by only to help you identify those course, you can’t learn how to using random() to assign num- papers you would like to read in write device drivers in an hour, bers to all attendees, then sort- full. Those readers interested in a but Garner did a good job of pro- ing] and for various feats. Some- longer summary should refer to viding an overview of the frame- one won a book by spending the Digest of Proceedings that work available. I finally learned over six hours trying to get appears at the end of the work- what has happened to minor de- through Canadian customs. shop proceedings. This digest in- vices (made unnecessary because (There was actually someone cludes a summary of the discus- of devfs). Garner also talked who had spent longer, but he sions that followed each of the about softc, a newer, more effi- had already won a book.) presentations. cient framework for writing de- This overview is based on the vice drivers, about how re- HotMobile 2006: 7th IEEE written notes taken by two stu- sources (memory, IRQs, and Workshop on Mobile Comput- dent volunteers, Tapan Parikh ports) should be handled, and ing Systems and Applications and Alex Varshavsky.
    [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 Complete Freebsd
    The Complete FreeBSD® If you find errors in this book, please report them to Greg Lehey <grog@Free- BSD.org> for inclusion in the errata list. The Complete FreeBSD® Fourth Edition Tenth anniversary version, 24 February 2006 Greg Lehey The Complete FreeBSD® by Greg Lehey <[email protected]> Copyright © 1996, 1997, 1999, 2002, 2003, 2006 by Greg Lehey. This book is licensed under the Creative Commons “Attribution-NonCommercial-ShareAlike 2.5” license. The full text is located at http://creativecommons.org/licenses/by-nc-sa/2.5/legalcode. You are free: • to copy, distribute, display, and perform the work • to make derivative works under the following conditions: • Attribution. You must attribute the work in the manner specified by the author or licensor. • Noncommercial. You may not use this work for commercial purposes. This clause is modified from the original by the provision: You may use this book for commercial purposes if you pay me the sum of USD 20 per copy printed (whether sold or not). You must also agree to allow inspection of printing records and other material necessary to confirm the royalty sums. The purpose of this clause is to make it attractive to negotiate sensible royalties before printing. • Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. • For any reuse or distribution, you must make clear to others the license terms of this work. • Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above.
    [Show full text]
  • David Gwynne <[email protected]>
    firewalling with OpenBSD's pf and pfsync David Gwynne <[email protected]> Thursday, 17 January 13 introduction ‣ who am i? ‣ what is openbsd? ‣ what are pf and pfsync? ‣ how do i use them? ‣ ask questions whenever you want Thursday, 17 January 13 who am i? ‣ infrastructure architect in EAIT at UQ ‣ i do stuff, including run the firewalls ‣ a core developer in openbsd ‣ i generally play with storage ‣ but i play with the network stack sometimes Thursday, 17 January 13 what is openbsd? ‣ open source general purpose unix-like operating system ‣ descended from the original UNIX by way of berkeley and netbsd ‣ aims for “portability, standardization, correctness, proactive security and integrated cryptography.” ‣ supports various architectures/platforms Thursday, 17 January 13 what is openbsd? ‣ one source tree for everything ‣ kernel, userland, doco ‣ bsd/isc/mit style licenses on all code (with some historical exceptions) ‣ 6 month dev cycle resulting in a release ‣ 3rd party software via a ports tree ‣ emergent focus on network services Thursday, 17 January 13 what is openbsd? ‣ it is very aggressive ‣ changes up and down the stack (compiler to kernel) to make a harsher, stricter, and less predictable runtime environment ‣ minimal or no backward compatibility as things move forward ‣ whole tree is checked for new bugs ‣ randomise as much as possible all over Thursday, 17 January 13 what is openbsd? ‣ it is extremely conservative ‣ tree must compile and work at all times ‣ big changes go in at the start of the cycle ‣ we’re not afraid to back stuff out ‣ peer review is necessary ‣ we do back away from some tweaks for the sake of usability Thursday, 17 January 13 what is pf? ‣ short for packet filter ‣ the successor to IP Filter (ipf) ‣ ipf was removed due to license issues ‣ the exec summary is that it is a stateful filter for IP (v4 and v6) traffic ‣ does a little bit more than that though..
    [Show full text]
  • DN Print Magazine BSD News BSD Mall BSD Support Source Wars Join Us
    Mirrors Primary (US) Issues August 2001 August 2001 Get BSD Contact Us Search BSD FAQ New to BSD? DN Print Magazine BSD News BSD Mall BSD Support Source Wars Join Us T H I S M O N T H ' S F E A T U R E S From the Editor The Effects of Tuning a FreeBSD Box for High Open Packages Reaches Performance Milestone 2 by Gilbert Gong by Chris Coleman Each BSD project has its A stock FreeBSD installation delivers a system which is own 3rd party software designed to meet the needs of most users, and strives to packaging system. They are provide the best balance of safety, reliablity, and all based on the same code, performance in a multi-user environment. It is therefore not yet, each of them have optimized for use as a high performance dedicated network features that make one server. This article investigates the effect of tuning a better than the other. Open FreeBSD for use as a dedicated network server. Read More Packages is a volunteer project to unify that code base and incorporate the best features of each. The NetBSD rc.d system by Will Andrews Get BSD Stuff There's been a lot of hubbub the last few months about NetBSD's new rc.d system being the successor of 4.4BSD's. At the USENIX Annual Technical Conference 2001 in Boston, MA, I had the pleasure of sitting down to listen to Luke Mewburn of Wasabi Systems discuss the new rc system NetBSD introduced in their operating system in the 1.5 release earlier this year.
    [Show full text]