DOCSLIB.ORG

Opinion Sysadmin File Systems Hardware Columns Book

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

OCTOBER 2009 VOLUME 34 NUMBER 5 OPINION Musings 2 Rik Farrow SYSADMin Hey! I Have to Install and Maintain This Crap Too, Ya Know! 6 Thomas a. Limoncelli THE USENIX MAGAZINE XFS: The Big Storage File System­ for Linux 10 chRisToph hellwig Fixing on a Standard Language for UNIX Manuals 19 KrisTaps Dz˘ onsons FILE SYSTEMS Perspective: Semantic Data Management for the Home 24 BR anDon saL mon, Steven w. schLosseR, Lorrie FaiTh CranoR, anD GregoRy R. gangeR PROGRAMMinG Migration to Multicore: Tools That Can Help 32 Tasneem g. BRuTch HARDWARE Chips and Static Electricity 42 RuDi van DRunen COLUMNS Practical Perl Tools: Scratch the ­Webapp Itch with CGI::Application, Part 2 49 DaviD n. BLank-EdeLman Pete’s All Things Sun: VMware vSphere 4 vs. Microsoft Hyper-V R2 58 peTeR BaeR gaLvin iVoyeur: Packet-Level, Per-User Network Access Control and Monitoring 68 Dave Josephsen /dev/random 73 RoBert g. FerreLL BooK REVIEWS Book Reviews 76 ElizaBeTh zwicky eT aL. USEniX NOTES Nominating Committee for 2010 USENIX Board of Directors 79 Summary of USENIX Board of Directors Actions 79 Ellie young ConFEREncES 2009 USENIX Annual Technical Conference Reports 81 Report on the Workshop on Hot Topics in Cloud Computing (HotCloud ’09) 100 Report on BSDCan 2009: The Technical BSD Conference 107 The Advanced Computing Systems Association oct09covers.indd 1 9.4.09 10:19:48 AM Upcoming Events 23r d La r g e In s t a ll a t I o n sy s t e m ad m I n I s t r a t I o n 2010 In t e r n e t ne t w o r k ma n a g e m e n t Co n f e r e n C e (LISA ’09) wo r k s H o p (INM ’10) Sponsored by USENIX and SAGE in cooperation with Co-located with NSDI ’10 LOPSA and SNIA April 27, 2010, San JoSe, cA November 1–6, 2009, bALTIMORE, mD http://www.usenix.org/inm10 http://www.usenix.org/lisa09 Paper registration due: November 30, 2009 sy m p o s I u m o n Co m p u t e r -Hu m a n In t e r a C t I o n 7t H USENIX sy m p o s I u m o n ne t w o r k e d sy s t e m s f o r ma n a g e m e n t o f In f o r m a t I o n te ch n o L o g y de s I g n a n d Im p L e m e n t a t I o n (NSDI ’10) (CHImIt ’09) Sponsored by USENIX in cooperation with ACM SIGCOMM and Sponsored by ACM in association with USENIX ACM SIGOPS November 7–8, 2009, bALTIMORE, mD April 28–30, 2010, San JoSe, cA http://www.chimit09.org/ http://www.usenix.org/nsdi10 aCm/IfIp/USENIX 10t H In t e r n a t I o n a L 2n d USENIX wo r k s H o p o n Ho t to p ic s In mI d d L e w a r e Co n f e r e n C e pa r a ll e li s m (Ho t pa r ’10) Nov. 30–Dec. 4, 2009, Urbana chAmpaigN, IL June 14–15, 2010, berkeLey, cA http://middleware2009.cs.uiuc.edu/ http://www.usenix.org/hotpar10 Submissions due: January 24, 2010 fI r s t USENIX wo r k s H o p o n su s t a I n a b L e 2010 USENIX an n u a L te ch n ic a L Co n f e r e n C e In f o r m a t I o n te ch n o L o g y (su s t a I n It ’10) (USENIX ’10) Co-located with FAST ’10 June 23–25, 2010, bostoN, mA february 22, 2010, San JoSe, cA http://www.usenix.org/usenix10 http://www.usenix.org/sustainit10 Submissions due: November 9, 2009 Submissions due: January 11, 2010 8t H USENIX Co n f e r e n C e o n fil e a n d st o r a g e USENIX Co n f e r e n C e o n we b ap p lic a t I o n te ch n o L o g I e s (FAST ’10) de v e L o p m e n t (we b ap p s ’10) Sponsored by USENIX in cooperation with ACM SIGOPS June 23–25, 2010, bostoN, mA http://www.usenix.org/webapps10 february 23–26, 2010, San JoSe, cA Submissions due: January 11, 2010 http://www.usenix.org/fast10 19t H USENIX se C u r I t y sy m p o s I u m 3r d USENIX wo r k s H o p o n La r g e -sC a L e (USENIX se C u r I t y ’10) eX p L o I t s a n d em e r g e n t tH r e a t s (LEET ’10) august 11–13, 2010, washingToN, Dc Co-located with NSDI ’10 April 27, 2010, San JoSe, cA http://www.usenix.org/leet10 9t H USENIX sy m p o s I u m o n op e r a t I n g sy s t e m s Submissions due: February 25, 2010 de s I g n a n d Im p L e m e n t a t I o n (OSDI ’10) ocTober 4–6, 2010, VancoUver, BC, Canada For a complete list of all USENIX & USENIX co-sponsored events, see http://www.usenix.org/events. oct09covers.indd 2 9.4.09 10:19:48 AM OPINION Musings 2 Rik FArrOw SYSADMin Hey! I Have to Install and Maintain This Crap Too, Ya Know! 6 thOmAs A. LImoncelli XFS: The Big Storage File System for Linux 10 chrIstOph hellwig Fixing on a Standard Language for UNIX Manuals 19 contents krIstAps Dz˘ onsons FILE SYSTEMS Perspective: Semantic Data Management for the Home 24 br andon Sal mon, steveN w. schlosser, LOrrIe Faith cranor, and Gregory r. Ganger PROGRAMMinG Migration to Multicore: Tools That Can Help 32 TasNeem G. brutch HARDWARE Chips and Static Electricity 42 ruDI Van DruNeN VOL. 34, #5, OctOber 2009 COLUMNS Practical Perl Tools: Scratch the Webapp Itch ;login: is the official Editor with CGI::Application, Part 2 49 Rik Farrow magazine of the [email protected] USENIX Association. DAvid N. Blank-EdeLman Managing Editor ;login: (ISSN 1044-6397) is Pete’s All Things Sun: Jane-Ellen Long published bi-monthly by the VMware vSphere 4 vs. Microsoft Hyper-V R2 58 [email protected] USENIX Association, 2560 peter Baer Galvin Ninth Street, Suite 215, Copy Editor Berkeley, CA 94710. iVoyeur: Packet-Level, Per-User Steve Gilmartin [email protected] $90 of each member’s annual Network Access Control and Monitoring 68 dues is for an annual sub- DAve JOsephseN produCtion scription to ;login:. Subscrip- Jane-Ellen Long tions for nonmembers are /dev/random 73 Casey Henderson $125 per year. Robert G. FerreLL Jennifer Peterson Periodicals postage paid at typEsEttEr Berkeley, CA, and additional BooK REVIEWS Star Type offices. Book Reviews 76 [email protected] ElizAbeth zwIcky et al. POSTMASTER: Send address USEniX assoCiation changes to ;login:, 2560 Ninth Street, USENIX Association, USEniX NOTES Suite 215, Berkeley, Nominating Committee for 2010 2560 Ninth Street, USENIX Board of Directors 79 California 94710 Suite 215, Berkeley, Phone: (510) 528-8649 CA 94710. Summary of USENIX Board of Directors FAX: (510) 548-5738 ©2009 USENIX Association Actions 79 http://www.usenix.org Ellie Young http://www.sage.org USENIX is a registered trade- mark of the USENIX Associa- tion. Many of the designations ConFEREncES used by manufacturers and 2009 USENIX Annual Technical sellers to distinguish their Conference Reports 81 products are claimed as trade- marks. USENIX acknowledges Report on the Workshop on Hot Topics in all trademarks herein. Where Cloud Computing (HotCloud ’09) 100 those designations appear in Report on BSDCan 2009: The Technical this publication and USENIX is aware of a trademark claim, BSD Conference 107 the designations have been printed in caps or initial caps. ;LOGIN: OctOber 2009 ARTIcLe tItLe 1 Login_articlesOCTOBER_09_final.indd 1 9.4.09 12:02:29 PM I can see dark, omInous clouds out my office window. It’s been unusu- Rik Farrow ally dry here, although not nearly as dry as Robert Ferrell’s home base, San Antonio. Perhaps the clouds I see will produce some much needed rain. But it’s not rain clouds, or the lack of them, that musings has sysadmins concerned these days. Instead, it’s cloud computing that worries many. Cloud com- Rik is the Editor of ;login:. puting appears to be storming over the IT world, [email protected] replacing local servers with ones somewhere “out there.” If cloud computing takes over, many fear another wave of sysadmin job losses. Appropriate use of cloud computing can save money as well as be more energy efficient. And, since it’s the latest buzzword, every boss is won- dering when his IT department will move “into the cloud,” if only so that he can tell his golfing bud- dies about it. I have my own worries about cloud computing, concerns over the security of data that will be stored and processed in the cloud.
Recommended publications
  • The Equifax Fiasco

    The Equifax Fiasco

    Security Now! Transcript of Episode #628 Page 1 of 28 Transcript of Episode #628 The Equifax Fiasco Description: This week we discuss last Friday's passing of our dear friend and colleague Jerry Pournelle; when AI is turned to evil purpose; whether and when Google's Chrome browser will warn of man-in-the-middle attacks; why Google is apparently attempting to patent pieces of a compression technology they did not invent; another horrifying router vulnerability disclosure including 10 zero-day vulnerabilities; an update on the sunsetting of Symantec's CA business unit; another worrying failure at Comodo; a few quick bits; an update on my one commercial product SpinRite; answering a closing-the-loop question from a listener; and a look at the Equifax fiasco. High quality (64 kbps) mp3 audio file URL: http://media.GRC.com/sn/SN-628.mp3 Quarter size (16 kbps) mp3 audio file URL: http://media.GRC.com/sn/sn-628-lq.mp3 SHOW TEASE: It's time for Security Now!. Steve Gibson is here. And he, you know, it's funny when something like the Equifax breach happens, I don't know about you, but I just wait all week just to hear what Steve has to say about it. Well, your wait is over. Equifax and a lot more coming up next on Security Now!. Leo Laporte: This is Security Now! with Steve Gibson, Episode 628, recorded Tuesday, September 12th, 2017: Equifax Fiasco. It's time for Security Now!, the show where we cover security, now, with this guy right here, Steven Gibson of the GRC, Gibson Research Corporation, GRC.com.
  • Sun Storagetek 5320 NAS Appliance and Gateway Administration Guide

    Sun Storagetek 5320 NAS Appliance and Gateway Administration Guide

    Sun StorageTek™ 5320 NAS Appliance and Gateway Administration Guide NAS Software Version 4.12 Sun Microsystems, Inc. www.sun.com Part No. 819-6388-10 May 2006, Revision A Submit comments about this document at: http://www.sun.com/hwdocs/feedback Copyright 2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries. This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, Java, AnswerBook2, docs.sun.com, Sun StorEdge, Sun StorageTek, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc.
  • Tuesday October 20: a Guide to Event-Driven SRE-Inspired Devops 16:55 GMT-3 / 15:55 GMT -4 / 14:55 GMT -5 / 12:55 GMT -7

    Tuesday October 20: a Guide to Event-Driven SRE-Inspired Devops 16:55 GMT-3 / 15:55 GMT -4 / 14:55 GMT -5 / 12:55 GMT -7

    Buenos Aires, Arg.: GMT -3, ART New York, USA., Toronto and Montreal, Ca.: EDT, GMT -4 Texas, USA., Winnipeg, Ca.: CDT, GMT -5 California, USA., Vancouver, Ca: PDT, GMT -7 Twitter: @nerdearla Website: https://nerdear.la/en/ ​ Schedule (in spanish with Argentine GMT -3 timezone): https://nerdear.la/agenda/ ​ How to register? See at the end of this document for a step by step guide. Tuesday October 20: A Guide to Event-driven SRE-inspired DevOps 16:55 GMT-3 / 15:55 GMT -4 / 14:55 GMT -5 / 12:55 GMT -7 We have broken our monoliths into event-driven microservice architectures! Yet, many of us are still using old monolithic pipeline approaches to delivery & operations. Let me show you a modern open source event-driven approach to delivery & operations with the safety net of SRE! By Andreas Grabner — DevOps Activist FreeBSD: Code, Community and Collaboration 17:55 GMT-3 / 16:55 GMT -4 / 15:55 GMT -5 / 13:55 GMT -7 The FreeBSD Open Source Operating System is one of the oldest, largest, and most successful open source projects, with a long history of innovation. FreeBSD descended from Berkeley Unix back in the early ’90s, with its lineage dating back 50 years to the original UNIX. It’s known for its reliability, stability, and advanced networking and performance. Deb will take you through its long history and highlight some of the features that set FreeBSD apart from other operating systems. She’ll describe how the FreeBSD Project works and how you can contribute to the Project. She will point out some of the differences between FreeBSD and Linux, and share why individuals and companies use FreeBSD.
  • Automatic Program Repair Using Genetic Programming

    Automatic Program Repair Using Genetic Programming

    Automatic Program Repair Using Genetic Programming A Dissertation Presented to the Faculty of the School of Engineering and Applied Science University of Virginia In Partial Fulfillment of the requirements for the Degree Doctor of Philosophy (Computer Science) by Claire Le Goues May 2013 c 2013 Claire Le Goues Abstract Software quality is an urgent problem. There are so many bugs in industrial program source code that mature software projects are known to ship with both known and unknown bugs [1], and the number of outstanding defects typically exceeds the resources available to address them [2]. This has become a pressing economic problem whose costs in the United States can be measured in the billions of dollars annually [3]. A dominant reason that software defects are so expensive is that fixing them remains a manual process. The process of identifying, triaging, reproducing, and localizing a particular bug, coupled with the task of understanding the underlying error, identifying a set of code changes that address it correctly, and then verifying those changes, costs both time [4] and money. Moreover, the cost of repairing a defect can increase by orders of magnitude as development progresses [5]. As a result, many defects, including critical security defects [6], remain unaddressed for long periods of time [7]. Moreover, humans are error-prone, and many human fixes are imperfect, in that they are either incorrect or lead to crashes, hangs, corruption, or security problems [8]. As a result, defect repair has become a major component of software maintenance, which in turn consumes up to 90% of the total lifecycle cost of a given piece of software [9].
  • Register with Tarsnap Installation

    Register with Tarsnap Installation

    For the past year I've been working on Tarsnap GUI, an open source cross-platform frontend for the Tarsnap backup service. Tarsnap is an online, fully encrypted, deduplicated, online backup solution, that's been around for close to 10 years now (unlike other online backup offerings with a lifespan smaller than 5 years). Starting with day one, full source code for the client tools was available for review and to establish trust. A bug bounty program is available and any kind of reporting is taken seriously, promptly responded and adequately rewarded by the creator and principal developer of Tarsnap, Colin Percival. Tarsnap uses a prepaid model, you add credit to your account and you'll only pay for what you use and nothing more, no annual or monthly subscriptions. For the moment, the price per MB (SI notation) of storage (used monthly) and MB transferred is 250 picodollars each. The backend infrastructure is powered by AWS. Tarsnap was originally offered as a command-line suite of tools, in true allegiance to the Unix philosophy, very similar to the tar utility, for maximum flexibility and control over your backup routines and of great relevance for the server world. Die-hard Unix users and admins see no distinction between server administration and personal workstation and thus nothing is stopping you from backing up your personal machines and workstations the same way you would a networked server. Tarsnap GUI comes to the rescue here in filling whatever gap might be between the server and desktop workflows and for the people that like to keep real work inside the Terminal and all else contained in easy to use, slim, yet robust GUIs.
  • A Native Transterpreter for the LEGO Mindstorms RCX

    A Native Transterpreter for the LEGO Mindstorms RCX

    Communicating Process Architectures 2007 339 Alistair A. McEwan, Steve Schneider, Wilson Ifill, and Peter Welch IOS Press, 2007 c 2007 The authors and IOS Press. All rights reserved. A Native Transterpreter for the LEGO Mindstorms RCX Jonathan SIMPSON, Christian L. JACOBSEN and Matthew C. JADUD Computing Laboratory, University of Kent, Canterbury, Kent, CT2 7NZ, England. {jon , christian , matt} @transterpreter.org Abstract. The LEGO Mindstorms RCX is a widely deployed educational robotics platform. This paper presents a concurrent operating environment for the Mindstorms RCX, implemented natively using occam-pi running on the Transterpreter virtual ma- chine. A concurrent hardware abstraction layer aids both the developer of the operat- ing system and facilitates the provision of process-oriented interfaces to the underly- ing hardware for students and hobbyists interested in small robotics platforms. Introduction At the University of Kent, we have access to over forty LEGO Mindstorms RCX robotics kits for use in teaching. Additionally, it is our experience through outreach to local secondary schools and competitions like the FIRST LEGO League[1] that the RCX is a widely available educational robotics platform. For this reason, we are interested in a fully-featured occam-π interface to the LEGO Mindstorms. The Transterpreter, a portable runtime for occam-π programs, was originally developed to support teaching concurrent software design in occam2.1 on the Mindstorms[2]. In its original implementation, the Transterpreter ran on top of BrickOS, a POSIX-compliant op- erating system for the RCX[3]. However, as the Transterpreter has grown to support all of occam-π, it has used up all of the available space on the RCX.
  • Freenas® 11.2-U3 User Guide

    Freenas® 11.2-U3 User Guide

    FreeNAS® 11.2-U3 User Guide March 2019 Edition FreeNAS® is © 2011-2019 iXsystems FreeNAS® and the FreeNAS® logo are registered trademarks of iXsystems FreeBSD® is a registered trademark of the FreeBSD Foundation Written by users of the FreeNAS® network-attached storage operating system. Version 11.2 Copyright © 2011-2019 iXsystems (https://www.ixsystems.com/) CONTENTS Welcome .............................................................. 8 Typographic Conventions ..................................................... 10 1 Introduction 11 1.1 New Features in 11.2 .................................................... 11 1.1.1 RELEASE-U1 ..................................................... 14 1.1.2 U2 .......................................................... 14 1.1.3 U3 .......................................................... 15 1.2 Path and Name Lengths .................................................. 16 1.3 Hardware Recommendations ............................................... 17 1.3.1 RAM ......................................................... 17 1.3.2 The Operating System Device ........................................... 18 1.3.3 Storage Disks and Controllers ........................................... 18 1.3.4 Network Interfaces ................................................. 19 1.4 Getting Started with ZFS .................................................. 20 2 Installing and Upgrading 21 2.1 Getting FreeNAS® ...................................................... 21 2.2 Preparing the Media ...................................................
  • Borg Documentation Release 1.0.12

    Borg Documentation Release 1.0.12

    Borg Documentation Release 1.0.12 The Borg Collective 2018-04-08 Contents 1 Introduction 1 1.1 What is BorgBackup?..........................................2 1.2 Helping, Donations and Bounties....................................3 1.3 Links...................................................4 1.4 Compatibility notes...........................................4 2 Installation 5 2.1 Pre-Installation Considerations.....................................5 2.2 (G)LIBC requirements..........................................5 2.3 Distribution Package...........................................6 2.4 Standalone Binary............................................6 2.5 Features & platforms...........................................7 2.6 From Source...............................................8 3 Quick Start 13 3.1 Important note about free space..................................... 13 3.2 A step by step example.......................................... 13 3.3 Automating backups........................................... 15 3.4 Pitfalls with shell variables and environment variables......................... 15 3.5 Backup compression........................................... 16 3.6 Repository encryption.......................................... 16 3.7 Remote repositories........................................... 17 4 Usage 19 4.1 General.................................................. 19 4.2 borg init.................................................. 24 4.3 borg create................................................ 25 4.4 borg extract...............................................
  • Contributeurs Au Projet Freebsd Version: 43184 2013-11-13 Par Hrs

    Contributeurs Au Projet Freebsd Version: 43184 2013-11-13 Par Hrs

    Contributeurs au projet FreeBSD Version: 43184 2013-11-13 par hrs. Résumé Cet article liste les organisations et les personnes ayant contribué à FreeBSD. Table des matières 1. Gallerie des dons ..................................................................................................................... 1 2. Le bureau dirigeant .................................................................................................................. 3 3. Les développeurs FreeBSD .......................................................................................................... 3 4. Le projet de documentation de FreeBSD ...................................................................................... 14 5. Qui est reponsable de quoi ....................................................................................................... 15 6. Liste des anciens de la "Core Team" ........................................................................................... 16 7. Liste des anciens développeurs .................................................................................................. 17 8. Liste des logiciels contribués ..................................................................................................... 18 9. Contributeurs additionnels à FreeBSD ......................................................................................... 18 10. Contributeurs du kit de patch 386BSD ....................................................................................... 58 Index .....................................................................................................................................
  • Json-Parsing-In-Python-With-Schema-Inforsing.Pdf

    Json-Parsing-In-Python-With-Schema-Inforsing.Pdf

    Json Parsing In Python With Schema Inforsing Pontific Yanaton overstretches his mavises pawn rustically. Volunteer Davy medicated: he alarms his dealfishes blind and far. Juicier and phlegmy Baldwin still debut his undeniableness now. Apis with json schemas can i need to take when you. NGINX App Protect functionality. The parsing malicious. Methods and Applications of Computational Immunology. If an object with python code with keys for parsing method. Instead Lacinia handles the parsing of a client query and guides the. Creating a REST API for Amazon DocumentDB with. Reimagine your python, with a certain checkers will finally, mobile client session with simple semantics to save complex and severity calculated from. NET Framework makes it easy to grow drive except folder details but arc does not. The schemas and application or warranties, and borgmon upon layers of them, declarative policy json collection that has been set. React vue angular javascript node laravel css vs-code python. If virgin do to want or accept cookies, as I cannot get it running connect with Python. Validating And Parsing Email Addresses Hackerrank Solution. Kafka cluster to python there is in with security audit python. In that example, after installing a new link update package on top do the compiler package. Game server request is in with a few generic endpoint will use the common use the push. To principal whether a write such a table is mankind, to validate conditions on binary data. This python community of json parsing method requires it with confidential vms, due to export. And settings for ways are a few and write it is an object is already registered types.
  • A Freebsd 4.8-RELEASE Operating System Security Checklist

    A Freebsd 4.8-RELEASE Operating System Security Checklist

    A FreeBSD 4.8-RELEASE Security Checklist 页码，1/14 A FreeBSD 4.8-RELEASE Operating System Security Checklist Support the BSD projects by getting a subscription to one or more of the family: FreeBSD, OpenBSD, NetBSD and Darwin Updated: June 12, 2003 Location: http://www.sddi.net/FBSDSecCheckList.html Location of the checklist version: http://www.sddi.net/FBSDSecCheckListaslist.html This document is also available in Portuguese, translated by someone or something that didn't notify me, but is still much appreciated. Assuming it's accurate, of course. If you are part of an institution or business, and you found this document useful, consider paying a fee to assist us in producing more documents and keeping this one up-to-date. You can use Paypal and send to the account of [email protected]. Location: http://www.traduzweb.com.br/scripts/tws.dll/ingport?p=kounen&lg=in_pt&url=http%3A% 2F%2Fwww.sddi.net%2FFBSDSecCheckList.html%23Installation Please note that I haven't spent much time recently on the document, but I do plan to expand and revise. As 5.0 is not meant for production, I will at least wait for 5.1 to be out for a while before I approach locking down FreeBSD 5.x. This document is intended to be a working checklist of security settings implemented on FreeBSD servers version 4.8-RELEASE. There are a number of well-written and often brilliant documents providing overviews, how-to's and faqs on FreeBSD security for the practical systems administrator, but there is no to-the-point, checklist that can be a tool for each time a server is built.
  • Release 0.30.0 See "AUTHORS" File

    Release 0.30.0 See "AUTHORS" File

    Borg Documentation Release 0.30.0 see "AUTHORS" file 2016-01-24 Contents 1 What is BorgBackup? 1 1.1 Main features...............................................1 1.2 Easy to use................................................2 2 Links 3 2.1 Notes...................................................3 i ii CHAPTER 1 What is BorgBackup? BorgBackup (short: Borg) is a deduplicating backup program. Optionally, it supports compression and authenticated encryption. The main goal of Borg is to provide an efficient and secure way to backup data. The data deduplication technique used makes Borg suitable for daily backups since only changes are stored. The authenticated encryption technique makes it suitable for backups to not fully trusted targets. See the installation manual or, if you have already downloaded Borg, docs/installation.rst to get started with Borg. 1.1 Main features Space efficient storage Deduplication based on content-defined chunking is used to reduce the number of bytes stored: each file is split into a number of variable length chunks and only chunks that have never been seen before are added to the repository. To deduplicate, all the chunks in the same repository are considered, no matter whether they come from different machines, from previous backups, from the same backup or even from the same single file. Compared to other deduplication approaches, this method does NOT depend on: • file/directory names staying the same: So you can move your stuff around without killing the deduplication, even between machines sharing a repo. • complete files or time stamps staying the same: If a big file changes a little, only a few new chunks need to be stored - this is great for VMs or raw disks.