February 2015 Meeting Announcements

Total Page：16

File Type：pdf, Size：1020Kb

February 2015 Meeting Announcements OCLUG February Presentation 2015-02-05 2 OCLUG February Presentation 2015-02-05 3 Tarsnap ● Tarsnap is a secure online backup service for BSD, Linux, OS X, Minix, OpenIndiana, Cygwin, and probably many other UNIX-like operating systems. The Tarsnap client code provides a flexible and powerful command-line interface which can be used directly or via shell scripts. ● At the present time, Tarsnap does not support Windows (except via Cygwin) and does not have a graphical user interface. From the tarsnap home page http://tarsnap.com OCLUG February Presentation 2015-02-05 4 Tarsnap Design ● The design of Tarsnap was guided by the following four principles: – Security – Flexibility – Efficiency – Utility ● The website explains this in detail OCLUG February Presentation 2015-02-05 5 What it is ● An encrypted, deduplicated off-site block store with a tar like interface. ● An archive system – think of it more like a tape. ● Geared for servers and experienced sysadmins. OCLUG February Presentation 2015-02-05 6 What it is not ● A service like Dropbox or SpiderOak. ● A browsable offline collection. ● A file by file backup ● Geared to end-users ● Free OCLUG February Presentation 2015-02-05 7 Pricing ● The cost is based on byte storage and is calculated as 250 pico dollars/byte stored and the same for bandwidth. – By this math, 1TB of data will cost $250.00 to store per month. – On the other hand, 1GB costs $0.25/month – You only pay for transmission and storage, so if you are using less, you pay for less. OCLUG February Presentation 2015-02-05 8 Comparison: Other Service Pricing ● SpiderOak - $25/TB/Month ● Dropbox Pro - $10.99/month for 1TB ● Dropbox for Business – $17.00/user/month (minimum 5 users) (unlimited) OCLUG February Presentation 2015-02-05 9 Some Tarsnap Links ● For those who want to investigate further, here are a few links that detail a lot of the stuff I mentioned during the talk – www.tarsnap.com – http://blog.jan-ahrens.eu/2014/04/21/backup.html – https://github.com/pronoiac/tarsnap-cron – http://lwn.net/Articles/423747/ – https://lggagnon.wordpress.com/2015/01/07/in-praise-of-the-tarsnap-backup- system/ – https://jclement.ca/2014/04/simple-tarsnap-backup-with-pushover-notifications/ OCLUG February Presentation 2015-02-05 10.

Copy Link

Recommended publications

Adventures with Illumos
> Adventures with illumos Peter Tribble Theoretical Astrophysicist Sysadmin (DBA) Technology Tinkerer > Introduction ● Long-time systems administrator ● Many years pointing out bugs in Solaris ● Invited onto beta programs ● Then the OpenSolaris project ● Voted onto OpenSolaris Governing Board ● Along came Oracle... ● illumos emerged from the ashes > key strengths ● ZFS – reliable and easy to manage ● Dtrace – extreme observability ● Zones – lightweight virtualization ● Standards – pretty strict ● Compatibility – decades of heritage ● “Solarishness” > Distributions ● Solaris 11 (OpenSolaris based) ● OpenIndiana – OpenSolaris ● OmniOS – server focus ● SmartOS – Joyent's cloud ● Delphix/Nexenta/+ – storage focus ● Tribblix – one of the small fry ● Quite a few others > Solaris 11 ● IPS packaging ● SPARC and x86 – No 32-bit x86 – No older SPARC (eg Vxxx or SunBlades) ● Unique/key features – Kernel Zones – Encrypted ZFS – VM2 > OpenIndiana ● Direct continuation of OpenSolaris – Warts and all ● IPS packaging ● X86 only (32 and 64 bit) ● General purpose ● JDS desktop ● Generally rather stale > OmniOS ● X86 only ● IPS packaging ● Server focus ● Supported commercial offering ● Stable components can be out of date > XStreamOS ● Modern variant of OpenIndiana ● X86 only ● IPS packaging ● Modern lightweight desktop options ● Extra applications – LibreOffice > SmartOS ● Hypervisor, not general purpose ● 64-bit x86 only ● Basis of Joyent cloud ● No inbuilt packaging, pkgsrc for applications ● Added extra features – KVM guests – Lots of zone features –
[Show full text]
Free Berkeley Software Distribution
Free berkeley software distribution Berkeley Software Distribution (BSD) was a Unix operating system derivative developed and . The lawsuit slowed development of the free- software descendants of BSD for nearly two years while their legal status was in question, and as a OS family: Unix. Software Central is a consolidation of several IST sites that offer software to UC Berkeley faculty, staff and students. The products available through this site are Productivity Software · Mathematics & Sciences · VMware · Stata. Software Central. The API department runs the Campus Software Distribution Service, which: Runs a distribution service through (link is. Free Speech Online Blue Ribbon Campaign. Welcome to ! UNIX! Live free or die! Google. Custom Search. What is this page all about? This page is. BSD stands for “Berkeley Software Distribution”. which is available on CD-ROM and for free download from FTP sites, for example OpenBSD. All of the documentation and software included in the BSD and As you know, certain of the Berkeley Software Distribution ("BSD") source. Template:Redirect Berkeley Software Distribution (BSD, sometimes called many other operating systems, both free and proprietary, to incorporate BSD code. BSD (originally: Berkeley Software Distribution) refers to the particular version of the UNIX operating system that was developed at and distributed fro. Short for Berkeley Software Distribution, BSD is a Unix-like NetBSD is another free version of BSD compatible with a very large variety of. Berkeley Software Distribution (BSD) is a prominent version of the Unix operating system that was developed and distributed by the Computer Systems. Early in , Joy put together the "Berkeley Software Distribution.
[Show full text]
Eurobsdcon 2019, Lillehammer, Norway [email protected] Summary & Introductions
The Future of OpenZFS and FreeBSD EuroBSDCon 2019, Lillehammer, Norway [email protected] Summary & Introductions Allan Jude Klara Inc. FreeBSD Core Team FreeBSD Professional OpenZFS Developer Services and Support Covered in this presentation OpenZFS Challenges Changing What does the Past, Present, Facing FreeBSD’s future hold for Future OpenZFS Upstream OpenZFS? The Evolution of ZFS ● ZFS was originally developed at Sun Microsystems starting in 2001, and open sourced under the CDDL license in 2005 ● Oracle bought Sun in 2010, and close sourced further work ● illumos, a fork of the last open source version of Solaris became the new upstream for work on ZFS ● ZFS was ported to many platforms, including FreeBSD in 2007 and Linux in 2008. The OpenZFS project was founded to coordinate development across platforms. OpenZFS ● The original plan for OpenZFS was a single common repository where the OS independent code would live and be tested ● Each OS would pull in this repo and maintain local glue bits ● However, the effort required to maintain a repo that would not be directly used by any of the consumers was too great ● The “repo of record” became a copy of the illumos repo, pull requests were carried through illumos’ RTI by Matt’s team ● FreeBSD tracked this repo very closely, commit by commit Platforms ● OpenZFS is now available on almost every platform ○ illumos (OmniOS, OpenIndiana, SmartOS, DilOS, Tribblix) ■ FreeBSD (FreeNAS, XigmaNAS, TrueOS, pfSense, etc) ● NetBSD ■ ZFS-on-Linux (Ubuntu, Gentoo, Proxmox, OviOS) ● Mac OS X (https://openzfsonosx.org/) ● Windows (https://openzfsonwindows.org/) ● OSv Divergence ● Each different platform’s version of ZFS started to diverge ● OpenZFS replaced the old “pool version number” with “Feature Flags”, since features would land in different orders ● Bugs were fixed in one repo and not necessarily upstreamed or communicated to other platform’s could apply the same fix ● Each camp did their development within their own community, and other communities might not be aware of duplicate efforts, etc.
[Show full text]
The Rise & Development of Illumos
Fork Yeah! The Rise & Development of illumos Bryan Cantrill VP, Engineering [email protected] @bcantrill WTF is illumos? • An open source descendant of OpenSolaris • ...which itself was a branch of Solaris Nevada • ...which was the name of the release after Solaris 10 • ...and was open but is now closed • ...and is itself a descendant of Solaris 2.x • ...but it can all be called “SunOS 5.x” • ...but not “SunOS 4.x” — thatʼs different • Letʼs start at (or rather, near) the beginning... SunOS: A peopleʼs history • In the early 1990s, after a painful transition to Solaris, much of the SunOS 4.x engineering talent had left • Problems compounded by the adoption of an immature SCM, the Network Software Environment (NSE) • The engineers revolted: Larry McVoy developed a much simpler variant of NSE called NSElite (ancestor to git) • Using NSElite (and later, TeamWare), Roger Faulkner, Tim Marsland, Joe Kowalski and Jeff Bonwick led a sufﬁciently parallelized development effort to produce Solaris 2.3, “the ﬁrst version that worked” • ...but with Solaris 2.4, management took over day-to- day operations of the release, and quality slipped again Solaris 2.5: Do or die • Solaris 2.5 absolutely had to get it right — Sun had new hardware, the UltraSPARC-I, that depended on it • To assure quality, the engineers “took over,” with Bonwick installed as the gatekeeper • Bonwick granted authority to “rip it out if itʼs broken" — an early BDFL model, and a template for later generations of engineering leadership • Solaris 2.5 shipped on schedule and at quality
[Show full text]
Considerations for the SDP Operating System
DocuSign Envelope ID: E376CF60-053D-4FF0-8629-99235147B54B Considerations for the SDP Operating System Document Number .......SDP Memo 063 ………………………………………………………………… Document Type .. MEMO ……………………………………………………………………… ………… Revision . 01 ………………………………………………………………………… ………… ………… Author . N. Erdödy, R. O’Keefe ………………………………………………………………………… … Release Date ... .2018-08-31 …………………………………………………………………………… … Document Classification ... Unrestricted ………………………………………………………………… Status ... Draft ………………………………………………………………………………………… … Document No: 063 Unrestricted Revision: 01 Author: N. Erdödy Release Date: 2018-08-31 Page 1 of 56 DocuSign Envelope ID: E376CF60-053D-4FF0-8629-99235147B54B Lead Author Designation Affiliation Nicolás Erdödy SDP Team Open Parallel Ltd. NZ SKA Alliance (NZA). Signature & Date: 10/21/2018 8:19:36 PM PDT With contributions and reviews Affiliation greatly appreciated from Dr. Richard O’Keefe SDP Team, NZA University of Otago - Open Parallel (NZA) Dr. Andrew Ensor Director, NZA AUT University (NZA) Piers Harding SDP Team, NZA Catalyst IT (NZA) Robert O’Brien Systems Engineer / Security Independent Anonymous Reviewer CEng (UK), CPEng (NZ) Manager, NZ Govt ORGANISATION DETAILS Name Science Data Processor Consortium Address Astrophysics Cavendish Laboratory JJ Thomson Avenue Cambridge CB3 0HE Website http://ska-sdp.org Email [email protected] Document No: 063 Unrestricted Revision: 01 Author: N. Erdödy Release Date: 2018-08-31 Page 2 of 56 DocuSign Envelope ID: E376CF60-053D-4FF0-8629-99235147B54B 1. SDP Memo Disclaimer The SDP memos are designed to allow the quick recording of investigations and research done by members of the SDP. They are also designed to raise questions about parts of the SDP design or SDP process. The contents of a memo may be the opinion of the author, not the whole of the SDP. Acknowledgement: The authors wish to acknowledge the inputs, corrections and continuous support from the NZA Team Members Dr.
[Show full text]
Incorporating the Digital Commons:Corporate Involvement in Free and Open Source Software
INCORPORATING THE DIGITAL COMMONS DIGITAL THE INCORPORATING INCORPORATING THE CDSMS DIGITAL COMMONS he concept of ‘the commons’ has been used as a framework to understand resources shared by a community rather than a private BENJAMIN J. BIRKINBINE T entity, and it has also inspired social movements working against the enclosure of public goods and resources. One such resource is free (libre) and open source software (FLOSS). FLOSS emerged as an alternative to proprietary software in the 1980s. However, both the products and production processes of FLOSS have become incorporated into capitalist INCORPORATING THE production. For example, Red Hat, Inc. is a large publicly traded company whose business model relies entirely on free software, and IBM, Intel, Cisco, Samsung, Google are some of the largest contributors to Linux, the DIGITAL COMMONS open-source operating system. This book explores the ways in which FLOSS has been incorporated into digital capitalism. Just as the commons have been used as a motivational frame for radical social movements, it has also Corporate Involvement in Free served the interests of free-marketeers, corporate libertarians, and states to expand their reach by dragging the shared resources of social life onto and Open Source Software digital platforms so they can be integrated into the global capitalist system. The book concludes by asserting the need for a critical political economic understanding of the commons that foregrounds (digital) labour, class struggle, and uneven power distribution within the digital commons as well as between FLOSS communities and their corporate sponsors. BENJAMIN J. BIRKINBINE J. BENJAMIN COMMUNICATION STUDIES | POLITICAL ECONOMY | MEDIA INDUSTRIES CDSMS CRITICAL DIGITAL AND SOCIAL MEDIA STUDIES THE AUTHOR Benjamin J.
[Show full text]
Adventures with Illumos
> Adventures with illumos Peter Tribble Theoretical Astrophysicist Sysadmin (DBA) Technology Tinkerer > Introduction ● Long-time systems administrator ● Many years pointing out bugs in Solaris ● Invited onto beta programs ● Then the OpenSolaris project ● Voted onto OpenSolaris Governing Board ● Along came Oracle... ● illumos emerged from the ashes > illumos key differentiators ● ZFS – reliable and easy to manage ● Dtrace – extreme observability ● Zones – lightweight virtualization ● Standards – pretty strict ● Compatibility – decades of heritage ● “Solarishness” ● No systemd ;-) > Diverse distributions ● OpenIndiana – OpenSolaris ● OmniOS – server focus ● SmartOS – Joyent's cloud ● Delphix/Nexenta/+ – storage focus ● DilOS, osdyson – debian ● Tribblix – one of the small fry > Distro differences ● Packaging – IPS: OI, Omnios, XStreamOS – SVR4: OpenSXCE, Tribblix – Deb: DilOS, osdyson – Pkgsrc: SmartOS – Storage vendors don't have (exposed) packaging – (No active rpm distro – Belenix is inactive) > Distro differences ● X86/X64 – Pretty much everything ● SPARC – OpenSXCE or Tribblix ● X64 only – SmartOS ● Minimum memory depends on packaging – IPS needs > 1G – Others happy in 512M > Distro focus ● OpenIndiana – copy OpenSolaris ● OmniOS – server, supported ● OpenSXCE – copy Solaris 10 ● XStreamOS – modern OpenIndiana ● SmartOS – foundation for cloud ● Tribblix – what OpenSolaris should have been > Why do it yourself? ● Challenging and interesting ● Understand the inner workings ● Satisfy the target audience ● Make a flexible platform for development
[Show full text]
LINUX JOURNAL | Issue 284 | March 2018
What’s New Shell Scripting Raspberry Pi in Qubes 4 Security Alternatives Since 1994: The original magazine of the Linux community DEEP DIVE BLOCKCHAIN PLUS POSTGRESQL 10 The Latest and Most Interesting Features BITCOIN AND TAXES Cryptocurrency and Uncle Sam LINUXBOOT FOSS Project Spotlight ISSUE 284 | MARCH 2018 www.linuxjournal.com MARCH 2018 CONTENTS ISSUE 284 DEEP DIVE: Blockchain 95 Blockchain, Part I: Introduction and Cryptocurrency by Petros Koutoupis What makes both bitcoin and blockchain so exciting? What do they provide? Why is everyone talking about this? And, what does the future hold? 105 Blockchain, Part II: Configuring a Blockchain Network and Leveraging the Technology by Petros Koutoupis How to set up a private etherium blockchain using open-source tools and a look at some markets and industries where blockchain technologies can add value. 2 | March 2018 | http://www.linuxjournal.com CONTENTS 6 From the Editor—Doc Searls Help Us Cure Online Publishing of Its Addiction to Personal Data UPFRONT 18 FOSS Project Spotlight: LinuxBoot by David Hendricks, Ron Minnich, Chris Koch and Andrea Barberio 24 Readers’ Choice Awards 26 Shorter Commands by Kyle Rankin 29 For Open-Source Software, the Developers Are All of Us by Derek Zimmer 32 Taking Python to the Next Level by Joey Bernard 37 Learning IT Fundamentals by Kyle Rankin 40 Introducing Zero-K, a Real-Time Strategy Game for Linux by Oflameo 45 News Briefs COLUMNS 46 Kyle Rankin’s Hack and / What’s New in Qubes 4 52 Reuven M. Lerner’s At the Forge PostgreSQL 10: a Great New Version for a Great Database 64 Shawn Powers’ The Open-Source Classroom Cryptocurrency and the IRS 72 Zack Brown’s diff -u What’s New in Kernel Development 76 Susan Sons’ Under the Sink Security: 17 Things 86 Dave Taylor’s Work the Shell Shell Scripting and Security 178 Glyn Moody’s Open Sauce Looking Back: What Was Happening Ten Years Ago? LINUX JOURNAL (ISSN 1075-3583) is published monthly by Linux Journal, LLC.
[Show full text]
Adventures with Illumos
> Adventures with illumos Peter Tribble Theoretical Astrophysicist Sysadmin (DBA) Technology Tinkerer > Introduction ● Long-time systems administrator ● Many years pointing out bugs in Solaris ● Invited onto beta programs ● Then the OpenSolaris project ● Voted onto OpenSolaris Governing Board ● Along came Oracle... ● illumos emerged from the ashes > illumos key strengths ● ZFS – reliable and easy to manage ● Dtrace – extreme observability ● Zones – lightweight virtualization ● Standards – pretty strict ● Compatibility – decades of heritage ● “Solarishness” > Directions ● ZFS (OpenZFS) ● XPG7 standards ● Missing pieces from open code ● Cleaning cruft – But can we preserve heritage? ● LX brand (native Linux emulation) > Distributions ● OpenIndiana – OpenSolaris ● OmniOS – server focus ● SmartOS – Joyent's cloud ● Delphix/Nexenta/+ – storage focus ● Tribblix – one of the small fry ● Quite a few others > Why? ● Because it's hard ● Understand the inner workings ● Satisfy the target audience ● Make a flexible platform for development of new ideas ● Didn't like other distros! > Tribblix values ● Modern components ● Retro styling ● Lightweight window managers ● SVR4 packaging ● Lightweight and fast ● Simplicity and “just works” > Tribblix futures ● Zones and app deployment – Sparse-root, whole, partial, alien ● Simplify administration - “just works” – Make internals invisible ● Modern application stacks – Many on top of go – Integrated with zones and zfs > Potholes ● Not enough time/people ● Fragmentation – All the work done at the distro level ● SPARC port struggling ● No cgo yet > Further reading http://www.illumos.org/ http://www.tribblix.org/ http://www.petertribble.co.uk/ [email protected] .
[Show full text]
ZFS on Linux on Raspberry Pi
Andrew Gabriel Cucumber Technology Ltd [email protected] 17th June 2015 What is ZFS? New file system developed by Sun Microsystems, starng development in 2001, open sourced 2005, released 2006. • Built-in data integrity for exponenally increasing data volumes with fixed disk error rates. Got Checksums? • Transaconal – always consistent on disk – no fsck(1M) • No size limits. • Simplify storage management. Everything shares a pool (like system memory). No separate volume management. • Performance. ZFS Ports History ZFSSA Solaris Oracle ZFS (Illumos) OpenZFS OpenSolaris OmniOS/ CDDL Open Source Apple/Zevo/Greenbytes OpenIndiana Nexenta/Tegile/Joyent/Delphix Greenbytes OSv FreeBSD ZFS on FUSE ZFS on Linux on Linux … MacZFS OSx … What is OpenZFS? OpenZFS is a community project founded by open source ZFS developers from mulple operang systems: Illumos, FreeBSD, Linux, OS X, … The goals of the OpenZFS project are: • to raise awareness of the quality, ulity, and availability of open source implementaons of ZFS • to encourage open communica8on about ongoing efforts to improve open source ZFS • to ensure consistent reliability, funconality, and performance of all distribuons of ZFS. OpenZFS Plaorm Diversity OS X OpenZFS On OSX “OOO” 879 Commits 33 Contributors Zetavault (EMC) 98 Commits 298 Commits 372 Commits 34 Contributors 52 Contributors 33 Contributors Commits and Contributors (with at least 2 commits), figures are over a 1 year period Trademarks are the property of their respecve owners ZFS on Linux on Raspberry Pi Here’s ZFS built, and running on a Raspberry Pi ! The picture shows ZFS running on a Pi B+ (512MB memory). I rebuilt it on the new Pi 2 (1GB memory, 4-core).
[Show full text]
One Big PDF Volume
Proceedings of the Linux Symposium July 14–16th, 2014 Ottawa, Ontario Canada Contents Btr-Diff: An Innovative Approach to Differentiate BtrFs Snapshots 7 N. Mandliwala, S. Pimpale, N. P. Singh, G. Phatangare Leveraging MPST in Linux with Application Guidance to Achieve Power and Performance Goals 13 M.R. Jantz, K.A. Doshi, P.A. Kulkarni, H. Yun CPU Time Jitter Based Non-Physical True Random Number Generator 23 S. Müller Policy-extendable LMK filter framework for embedded system 49 K. Baik, J. Kim, D. Kim Scalable Tools for Non-Intrusive Performance Debugging of Parallel Linux Workloads 63 R. Schöne, J. Schuchart, T. Ilsche, D. Hackenberg Veloces: An Efficient I/O Scheduler for Solid State Devices 77 V.R. Damle, A.N. Palnitkar, S.D. Rangnekar, O.D. Pawar, S.A. Pimpale, N.O. Mandliwala Dmdedup: Device Mapper Target for Data Deduplication 83 V. Tarasov, D. Jain, G. Kuenning, S. Mandal, K. Palanisami, P. Shilane, S. Trehan, E. Zadok SkyPat: C++ Performance Analysis and Testing Framework 97 P.H. Chang, K.H. Kuo, D.Y. Tsai, K. Chen, Luba W.L. Tang Computationally Efficient Multiplexing of Events on Hardware Counters 101 R.V. Lim, D. Carrillo-Cisneros, W. Alkowaileet, I.D. Scherson The maxwell(8) random number generator 111 S. Harris Popcorn: a replicated-kernel OS based on Linux 123 A. Barbalace, B. Ravindran, D. Katz Conference Organizers Andrew J. Hutton, Linux Symposium Emilie Moreau, Linux Symposium Proceedings Committee Ralph Siemsen With thanks to John W. Lockhart, Red Hat Robyn Bergeron Authors retain copyright to all submitted papers, but have granted unlimited redistribution rights to all as a condition of submission.
[Show full text]
Openindiana Small System Server Build Version 1.25 Jon Green
OpenIndiana Small System Server Build Version 1.25 Jon Green Jon Green No Warranty All the information on this document United Kingdom is published in good faith and for general informa- www.jasspa.com tion purpose only. Jon Green does not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find in this document, is strictly at your own risk. Jon Green will not be li- able for any losses and/or damages in connection with the use of this document. www.jasspa.com oi_setup v1.25 2015/08/16 11:39:06 OpenIndiana Small System Server Build Jon Green. United Kingdom Mail: Read right to left, from the top of the last column and snake between columns c.aj oas@j mpsno All the information on this document is published in good faith and for general information purpose only. Jon Green does not make any warranties about the completeness, reliability and accuracy of this information. Any action you take upon the information you find in this document, is strictly at your own risk. Jon Green will not be liable for any losses and/or damages in connection with the use of this document. Title: OpenIndiana Small System Server Build Reference: oi_setup Version v1.25 Date: 2015/08/16 11:39:06 Typeset with the TeX Live 2012 LATEX Documentation System. www.jasspa.com ii oi_setup v1.25 2015/08/16 11:39:06 OpenIndiana Small System Server Build Revision History Revision History Date Who Description Revision 2015/08/16 JG Added notes on postfix 587 submission 1.25 Added notes on strengthening DH for Dovecot and Postfix.
[Show full text]