DOCSLIB.ORG

Muuglines the Manitoba UNIX User Group Newsletter

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Muuglines the Manitoba UNIX User Group Newsletter MUUGLines The Manitoba UNIX User Group Newsletter June 2011 Volume 23 No. 10 Next Meeting: June 14th, 2011 Upcoming Meetings Topic: Practical Security (Sean Cody) September 13th, 2011 For our last meeting of the season, Sean Cody will be We’ll start the 2011/2012 year with our first meeting speaking on Practical Security. The term “security” is on Tuesday, September 13th. Stay tuned (and make thrown around quite readily and its meaning has been sure you’re subscribed to one of the mailing lists) for diluted to being a product adjective as opposed to a details on that month’s presentation. process or mind set. This presentation will go over the basic theory of computer security and will attempt to Linux Kernel 3.0-RC1 Announced. equip you with the knowledge to properly evaluate computer security, products and mitigation strategies. As originally noted in a posting by Linus (http://lwn.net/Articles/445222/) the Linux kernel Where to find the Meeting branding is jumping a few points to 3.0. Meetings are held at the No, marketing firms aren’t searching for a new IBM offices at 400 internet buzzword. The kernel major revision number Ellice Ave. (between is getting renumbered to 3. Linus explains the Edmonton and Kennedy reasoning for the jump as “I can no longer [sic] Streets). When you comfortably count as high as 40.” arrive, you will have to sign in at the reception No big changes are actually expected. As usual, there desk. Please try to will be some driver updates and random fixes. Code arrive by about 7:15pm, regarding VM’s and VFS has been cleaned up some so the meeting can start as well. Duplicate code and out-of-tree patches for promptly at 7:30pm. ARM architecture has been improved somewhat, and will be ongoing. Limited parking is available for free on the street, either on Ellice Ave. or The goal is to have a “nice stable 3.0” release instead on some of the intersecting streets. Indoor parking is of aiming for typical problems that plague a .0 release also available nearby, at Portage Place, for $5.00 for – sure and steady. the evening. Bicycle parking is available in a bike rack under video surveillance located behind the Red Hat Enterprise Linux 6.1 Released May 19 building on Webb Place. RHEL being a staple for Linux installation in the enterprise has shipped their next point release of the version 6 product line. Updates listed: 1 that are designed to only ask for a • Additional configuration options for advanced password. storage configurations with improvements in FCoE, Datacenter Bridging and iSCSI offload, If you feel comfortable with giving which allow networked storage to deliver the Google your cell phone number, you quality of service commonly associated with can turn on “2-step verification” in directly connected storage your Account Settings – click on • Enhancements in virtualization, file systems, your email address in the upper right scheduler, resource management and high when logged into Gmail. availability • New technologies that enable smoother enterprise Pcc 1.0 Has Been Released deployments and tighter integration with heterogeneous systems “pcc” is a BSD licensed C-Compiler that has been gaining some • A technology preview of Red Hat Enterprise popularity and attention in the past Identity (IPA) services, based on the open source year. Not to be confused with the FreeIPA project CLANG project. The recent work on • Support for automatic failover for virtual machines pcc was funded by the BSD Fund and applications using the Red Hat High and the focus was on optimizing the Availability Add-On compiler (already noted for its performance) and having it be able • Integrated developer tools that provide the ability to self host on and compile the kernels (and userland) to write, debug, profile and deploy applications of the BSD’s. This release can now build the userland without leaving the graphical environment and kernel of FreeBSD, NetBSD and OpenBSD base • Improvements to network traffic processing to systems with the Linux kernel compatibility being leverage multi-processor servers that are getting targeted next. increasingly common pcc has been around since the 1970’s, but now has For those not familiar with IPA, “Identity, Policy, and been released with AMD64 support and improved Audit” suite is similar to Novell’s Identity Manager GCC compatibility, thanks to the BSD Fund and pcc and Microsoft’s Active Directory. maintainer Anders Magnusson. Future plans are noted: Gmail Gains Two Factor Authentication A Gmail account can now use a new authentication With a little more help, pcc should run on the key scheme referred to as two-factor authentication. mobile platforms we all carry today. Portability never Basically two-factor authentication is composed of goes out of style and pcc’s permissive licensing makes tokens matching something you know (account it attractive to the widest possible audience." password), and something you have (such as a generated authentication code on a mobile device). Carriers and vendors are unlikely to support this, but Users can now have Gmail send them the persistent programmers and hobbyists seem to live by authentication code via SMS or install an app on their the motto “void your warranty.” We can count on Android, Blackberry, or iPhone to generate the code seeing some interesting applications in the future! themselves. OpenBSD 4.9 Released You have the option of your machine remembering the verification code for 30 days. You can also set up one-time, application-specific passwords to sign in to With little fanfare, OpenBSD 4.9 was released on st your account from non-browser based applications May 1 . The theme art of the release is modelled after the “Hitch Hiker’s Guide to the Galaxy.” 2 The highlights of the release include: Ubuntu 11.04 Natty Narwhal Exposed • NTFS (read-only) enabled by default in GENERIC There has been a ton of press on the radical changes kernel. Canonical is taking on the distribution of Ubuntu 11.04 (including an article in last month’s newsletter). • vmt(4) driver enabled by default for VMWare tools The chief criticism is in the replacement of the support as a guest (this is a big deal for those GNOME desktop with Unity. Some people really like wanting to utilize and manage OpenBSD VM it and many “old-school” despise it, but you have to hosts). give a nod of respect to Canonical for trying something different. • Lots of usual work and improvements to the network stack and pf(4) firewall code. If you are moving to this release there is a nice post by Manual Jose going over and linking to a bunch of • Re-audit and validation of the IPsec code (given the useful tidbits on what has changed and how to make “scare” of a back-door which so far has proven to best use of the new features of this release. be FUD). You can check out his post at • Mandoc replacement for groff and friends finally http://www.techdrivein.com/2011/06/everything- considered stable and part of the release. For more you-need-to-know-about.html. information on this check out the BSDTalk podcast (#204) with the authors of this tool Oracle to Hand Over OpenOffice.org (http://bsdtalk.blogspot.com/). to Apache Incubator OpenBSD’s IPsec Backdoor FUD Is Just That... Ever since Oracle acquired Sun, there have been rumours and posturing over the future of A huge bit of media hype surrounded an implication OpenOffice.org. Like the botched handling of by one Gregory Perry that authors of part of the IPsec MySQL, the community of users was very wary of implementation for OpenBSD was subverted with Oracle’s embarrassment of the popular product and back-door code sponsored by the FBI. While many members of the community jumped ship and preposterous, Theo de Raadt made the accusation forked the project as Libre Office. public and launched an effort to either validate or re- audit the code in question. The reputation of Since then, Oracle has proposed that the OpenBSD and its security & licensing morals are OpenOffice.org IP be “donated” to the Apache what blew this out of proportion, but since every Foundation as part of its Apache Incubator project. accusation must at least be investigated, the media Should this proceed, it would definitely solidify the made a big deal out of what ended up being nothing. licensing and availability of the product (using both LGPLv3+ and MPL liceses) and allow for continued Mikel King has assembled a bunch of articles, the OpenSource contributions while maintaining a original complaint and disclosure, as well as many commercial-friendly status. other posts on this topic. The articles range from well- thought out to absolutely insane, but a good read Network World has posted a good summary article on nonetheless... this proceeding and announcement at: http://www.networkworld.com/community/blog/or http://bsdnews.net/index.php/2010/12/17/bsd-and- acle-proposes-openofficeorg-apache-incubato. the-fbi-sponsored-ipsec-backdoor-yawn/ 3 A Simple Yet Effective “First Step” in management issues. All of these vulnerabilities would Locking Down OpenSSH. be entirely hidden from users, but thankfully there are studious folks out there like Mr. Percival who are OpenSSH is the de-facto SSH implementation in use auditing these services. If you want more detail about by almost every product offering an SSH these issues, check out Colon’s blog post on the topic implementation/feature. Over the past year, there have at: http://www.daemonology.net/blog/2011-06-03- been increasingly aggressive attempts to brute force insecurity-in-the-jungle.html accounts on SSH daemons addressable over the internet.
Load more

Recommended publications
  • BSD – Alternativen Zu Linux
    ∗BSD { Alternativen zu Linux Karl Lockhoff March 19, 2015 Inhaltsverzeichnis I Woher kommt BSD? I Was ist BSD? I Was ist sind die Unterschiede zwischen FreeBSD, NetBSD und OpenBSD? I Warum soll ich *BSD statt Linux einsetzen? I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I 1978 I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Bill Joy erstellt eine Sammlung von Tools, 1BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den vi in Berkeley I 2BSD erscheint (Basis f¨urdie Weiterentwicklung PDP-11) I 3BSD erscheint (erstmalig mit einen eigenen Kernel) I 4BSD erscheint (enth¨altdas fast file system (ffs)) I Bill Joy wechselt zu Sun Microsystems I Kirk McKusick ¨ubernimmt die Entwicklung von BSD I Unix Version 7 erscheint I 1979 I 1980 I 1981 Woher kommt BSD? I 1976 I Unix Version 6 erscheint I 1978 I Chuck Haley und Bill Joy entwickeln den
    [Show full text]
  • 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.
    [Show full text]
  • Mandoc: Becoming the Main BSD Manual Toolbox
    mandoc: becoming the main BSD manual toolbox BSDCan 2015, June 13, Ottawa Ingo Schwarze <[email protected]> Cynthia Livingston’sOTTB “Bedifferent” (c) 2013 C. Livingston (with permission) > Ingo Schwarze: mandoc page 2: INTROI BSDCan 2015, June 13, Ottawa Brief history of UNIX documentation • The key point: All documentation in one place and one format. Easy to find, uniform and easy to read and write. Be correct, complete, concise. • 1964: RUNOFF/roffmarkup syntax by Jerome H. Saltzer,MIT. Unobtrusive,diff(1)-friendly,easy to hand-edit, simple tools, high quality output. • 1971: Basic manual structure by Ken Thompson and Dennis Ritchie for the AT&T Version 1 UNIX manuals, Bell Labs. • 1979: man(7) physical markup language for AT&T Version 7 UNIX. • 1989: mdoc(7) semantic markup by Cynthia Livingston for 4.3BSD-Reno. Powerful, self-contained, portable. • 1989: GNU troffbyJames Clarke. • 2001: mdoc(7) rewrite by Werner Lemberg and Ruslan Ermilovfor groff-1.17. • 2008: mandoc(1) started by Kristaps Dzonsons. • 2010: mandoc(1) is the only documentation formatter in the OpenBSD base system. • 2014: mandoc(1) used by default in OpenBSD, FreeBSD, NetBSD, illumos. 16:19:30 What is the mandoc toolbox? → < > Ingo Schwarze: mandoc page 3: INTROIIBSDCan 2015, June 13, Ottawa What is the mandoc toolbox? User perspective:man(1), the manual viewer One comprehensive tool! Normal operation always proceeds in three steps: 1. Find one or more manuals in the file system or using a database by manual name — man(1) — or by search query — apropos(1) =man -k The result of this step can be printed out with man -w.
    [Show full text]
  • Openbsd 6.4 / Openbgpd 6.4
    OpenBSD 6.4 / OpenBGPD 6.4 Peter Hessler [email protected] OpenBSD 18 October, 2018 openbsd 23 year anniversary on October 18th 6.4 released today 6.4 major improvements to our arm64 and armv7 platforms many improvements and drivers for modern amd64 based laptops many improvements for guest OSes in our virtualization hypervisor defenses against ROP attacks and misbehaving applications we are upstream for openssh tmux libressl mandoc opensmtpd network wifi join lacp administrative knobs microtik EoIP further work in an SMP-safe network stack more unlocked syscalls (sendmsg, sendto, recvfrom, and recvmsg) networks(5) support has been removed network daemons ospf6d routing domains (VRFs) slaacd fully pledged slaacd better behaved on networks (DAD, network roaming, etc) rad replaces rtadvd OpenBGPD and the RIPE Community Projects Fund money was raised Thank you to RIPE Community Projects Fund DE-CIX, Netnod, AMS-IX, BCIX, LONAP, Asteroid, Namex, University of Oslo apologies if I missed anyone OpenBGPD and the RIPE Community Projects Fund money was spent Claudio Jeker is now working full time on OpenBGPD 1 year of funding is secured 5 months of effort so far OpenBGPD 6.4 RFC8212 compliance (default deny policy) remove announce self, move to filter rules instead RPKI ROA support (static table, no RTR support) sets for prefixes, ASNum, and origins (prefix + source-as) ... replaces many filter rules with a single fast lookup background soft-reconfig on config reload ... on reload, withdraws and updates are still processed 154 commits since 6.3 OpenBGPD 6.4 YYCIX is using this in production already 46 members 6.3 370,000 filter rules 6.4 less than 6,000 filter rules OpenBGPD 6.5 - the future better community filtering ..
    [Show full text]
  • Mandoc
    mandoc from scratch to the standard BSD documentation toolkit in 6 years EuroBSDCon, Stockholm, October 4, 2015 Ingo Schwarze <[email protected]> using some material from: Training a foal to replace Enhancing the modern Let’smake mandoc: becoming avenerable workhorse: toolbox for the classic manuals the main BSD mandoc in OpenBSD documentation formats: more useful! manual toolbox BSDCan 2011 newtrends in mandoc EuroBSD- BSDCan 2015 BSDCan 2014 Con 2014 Csikó — Foal © 2010 Keajuvenile © 2007 Sofi ©2014 “Bedifferent” © 2013 Adam Tomkó @flickr (CC) Brent Barrett @flickr (CC) Alica Dimitrova Cynthia Livingston > Ingo Schwarze: 6 years of mandoc page 2: INTROI Stockholm, October 4, 2015 Contents 1. Intro: Documentation — whyand how(EuroBSDCon/BSDCan 2014) 2. Using mandoc: Searching — unified interface — web display (BSDCan 2014/15) News: equations — unicode (BSDCan 2015) Maintaining documentation: warnings — help — portable software (all) 3. The groff → mandoc replacement project (BSDCan 2011) 4. Software isn’tperfect. Bugs, security issues, performance (BSDCan 2015/14) 5. Conclusion —status — future — thanks (BSDCan 2015) http://mdocml.bsd.lv/press.html has all the slides of these talks Black Lakenear King Mountain, Gatineau Park, Quebec, Canada © 2012 Lezumbalaberenjena@flickr (CC) 14:04:30 NYC*BUG 2015 Whydocument software? → < > Ingo Schwarze: 6 years of mandoc page 3: INTROIIStockholm, October 4, 2015 Let’smakemanuals more useful! Requirements for good documentation • correct • complete • concise • easy to find and access, all in one local place • not just plain text: function of words must be marked up for display and search Rotonda Sveti Georgi, Sofi ©2006 Preslav @wikimedia (PD) • easy to read: in particular,uniform display markup and style • easy to write: in particular,one simple, standard input language The formatted documentation must seem simple to end users.
    [Show full text]
  • Free, Functional, and Secure
    Free, Functional, and Secure Dante Catalfamo What is OpenBSD? Not Linux? ● Unix-like ● Similar layout ● Similar tools ● POSIX ● NOT the same History ● Originated at AT&T, who were unable to compete in the industry (1970s) ● Given to Universities for educational purposes ● Universities improved the code under the BSD license The License The license: ● Retain the copyright notice ● No warranty ● Don’t use the author's name to promote the product History Cont’d ● After 15 years, the partnership ended ● Almost the entire OS had been rewritten ● The university released the (now mostly BSD licensed) code for free History Cont’d ● AT&T launching Unix System Labories (USL) ● Sued UC Berkeley ● Berkeley fought back, claiming the code didn’t belong to AT&T ● 2 year lawsuit ● AT&T lost, and was found guilty of violating the BSD license History Cont’d ● BSD4.4-Lite released ● The only operating system ever released incomplete ● This became the base of FreeBSD and NetBSD, and eventually OpenBSD and MacOS History Cont’d ● Theo DeRaadt ○ Originally a NetBSD developer ○ Forked NetBSD into OpenBSD after disagreement the direction of the project *fork* Innovations W^X ● Pioneered by the OpenBSD project in 3.3 in 2002, strictly enforced in 6.0 ● Memory can either be write or execute, but but both (XOR) ● Similar to PaX Linux kernel extension (developed later) AnonCVS ● First project with a public source tree featuring version control (1995) ● Now an extremely popular model of software development anonymous anonymous anonymous anonymous anonymous IPSec ● First free operating system to implement an IPSec VPN stack Privilege Separation ● First implemented in 3.2 ● Split a program into processes performing different sub-functions ● Now used in almost all privileged programs in OpenBSD like httpd, bgpd, dhcpd, syslog, sndio, etc.
    [Show full text]
  • Current Status of Openbsd / Openbgpd
    Current Status of OpenBSD / OpenBGPd Peter Hessler [email protected] OpenBSD 27 October, 2015 openbsd 20 year anniversary on October 18th 5.8 released on that date, last week the berlin u2k15 hackathon is happening right now everything mentioned is committed in either in 5.8 or in -current openbsd projects openssh pf opensmtpd mandoc libressl ... and many others openbsd outside of openbsd pretty much everyone uses openssh pf is in all apple devices, the *bsds, a windows port, and even solaris! a rather large part of the android libc is from openbsd and a huge amount of people are switching to libressl software defined operations devops ... it’s a unix system, i know this ... atomic config reloads ... automated deployments (ansible, salt, chef, puppet, etc) sdn compatible ... networking on a full unix-like environment ... triggers on network states ... carp / ifstated / relayd router / perl openntpd ntp time keeping ... simple and (reasonably) accurate ... network and/or timedelta sensors driven ... a portable version also exists mostly cve free routing daemons bgp ldp ospf (v2 and v3) eigrp rip, routed openbgpd been around a long time (2004-present) massive improvements have been made in the last years openbgpd all the features you need ... edge router ... ibgp ... route reflector ... route server and many features you want ... multi-RIB ... mrt dumps ... mpls (vrf) ... mpls vpn (vpls / pseudo-wire) ... looking glass openbgpd scaling hundreds of peers many full-feeds more than 8 million prefixes 1500+ nexthops openbgpd config configuration language ... templates ... groups ... macros openbgpd config group "IXP-Peers" { transparent-as yes enforce neighbor-as no passive max-prefix 1000 neighbor 2001:db8:42::/48 neighbor 2001.db8:42::6939 { max-prefix 120000 } } deny from any allow from group "IXP-Peers" match from any community 1234:666 \ prefix ::/0 prefixlen = 128 set nexthop 2001:db8:42::666 openbgpd as an edge router works great as a client router at my day job, we use it in production ..
    [Show full text]
  • 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].
    [Show full text]
  • 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.
    [Show full text]
  • 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 ...................................................
    [Show full text]
  • Limits and the Practical Usability of Bsds, a Big Data Prospective
    Limits and the Practical Usability of BSDs, a Big Data Prospective Predrag Punosevacˇ [email protected] The Auton Lab Carnegie Mellon University June 11, 2016 1 / 22 Thanks Thanks to organizers for this great meeting and for giving me the op- portunity to speak. note 1 of slide 1 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ❖ NetBSD ❖ OpenBSD ❖ pf.conf and pfctl ❖ OpenBSD cons ❖ FreeBSD ❖ TrueOS ❖ TurnKey Appliance ❖ FreeNAS ❖ pfSense ❖ DragonFly BSD ❖ HAMMER ❖ Dark Clouds ❖ References 2 / 22 Intro ❖ Intro ● Who am I? ❖ Chronology ❖ Chronology II ❖ Genealogy Tree ● What is the Auton Lab? ❖ General Limitations ❖ Scientific ● Why don’t we just use SCS computing facilities? Computing ❖ Continuation ❖ misc issues ● How did
    [Show full text]
  • Bsync: Sistema Extensible Para La Sincronizaci´Ony Copia De Seguridad De ficheros Para Su Uso En Organizaciones
    Escuela Polit´ecnicaSuperior Departamento de Inform´atica Proyecto de Fin de Carrera bsync: Sistema extensible para la sincronizaci´ony copia de seguridad de ficheros para su uso en organizaciones Javier Torres Ni~no Tutores Juan Miguel G´omezBerb´ıs Alejandro Rodr´ıguezGonz´alez 28 de Julio de 2011 2 Resumen En la actualidad existen muchos sistemas de sincronizaci´ony copia de segu- ridad de ficheros, pero la mayor´ıade ellos no comercializan el producto, optando por comercializar los servicios ofrecidos por medio de estos. Esto impide el uso de estas herramientas a entidades que necesiten que sus datos no salgan de su entorno, por lo que el objetivo de este Proyecto de Fin de Carrera es el dise~no y desarrollo de un sistema similar a estos otros productos. Se analizan las caracter´ısticasde los competidores, y se dise~naun programa que incluye en el n´ucleolas caracter´ısticasb´asicasy sea capaz de incluir to- das las caracter´ısticasadicionales mediante el uso de extensiones o plugins. Es precisamente esta extensibilidad la que caracteriza el sistema, permitiendo que un mismo producto pueda adaptarse a las necesidades de multitud de clientes, que pueden precisar, por ejemplo, de distintos sistemas de autenticaci´on(para integrar el sistema en la arquitectura existente) o utilizar la infraestructura para sincronizar m´asque ficheros. Palabras clave: sincronizaci´on,copia de seguridad, extensibilidad, plugins, sistemas distribuidos 3 4 Agradecimientos Es impensable dejar este proyecto sin unas breves l´ıneas en las que agradecer a todas las personas que me han soportado durante estos ´ultimoscinco a~nos,y especialmente los ´ultimosmeses.
    [Show full text]