DOCSLIB.ORG

Reproducible Software Deployment with GNU Guix

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Reproducible Software Deployment with GNU Guix Reproducible Software Deployment with GNU Guix Ludovic Courtes` Inria Rennes Bretagne Atlantique, November 2015 The difficulty of keeping software environments under control. #1. Upgrades are hard. #2. Stateful system management is intractable. $DISTRO $DISTRO $DISTRO $DISTRO apt-get update apt-get update state 1a state 1b $DISTRO $DISTRO apt-get update apt-get update state 1a state 1b apt-get install foo apt-get remove bar state 2a state 2b $DISTRO $DISTRO apt-get update apt-get update state 1a state 1b apt-get install foo apt-get remove bar state 2a state 2b apt-get remove bar apt-get install foo state 3a state 3b $DISTRO $DISTRO apt-get update apt-get update state 1a state 1b apt-get install foo apt-get remove bar = ? state 2a state 2b apt-get remove bar apt-get install foo state 3a state 3b #3. It’s worse than this. It’s worse, really. “Let’s Package jQuery: A Javascript Packaging Dystopian Novella” by Chris Webber http://dustycloud.org/blog/ javascript-packaging-dystopia/ ! “app bundles” (Docker images) Giving up? Giving up? ! “app bundles” (Docker images) Functional package management. hwloc = g(pciaccess; gcc; make; coreutils) gcc = h(make; coreutils; gcc0) ... openmpi = f (hwloc; gcc; make; coreutils) where f = ./configure && make && make install gcc = h(make; coreutils; gcc0) ... where f = ./configure && make && make install openmpi = f (hwloc; gcc; make; coreutils) hwloc = g(pciaccess; gcc; make; coreutils) where f = ./configure && make && make install openmpi = f (hwloc; gcc; make; coreutils) hwloc = g(pciaccess; gcc; make; coreutils) gcc = h(make; coreutils; gcc0) ... where f = ./configure && make && make install openmpi = f (hwloc; gcc; make; coreutils) hwloc = g(pciaccess; gcc; make; coreutils) gcc = h(make; coreutils; gcc0) ... the complete DAG is captured I A Safe and Policy-Free System for Software Deployment, Dolstra et al., 2003 Nix, http://nixos.org/nix/ I Functional Package Management with Guix, Courtes,` 2013 (define hello (package (name "hello") (version "2.10") (source (origin (method url-fetch) (uri (string-append "mirror://gnu/.../hello-" version ".tar.gz")) (sha256 (base32 "0wqd...dz6")))) (build-system gnu-build-system) (synopsis "Hello, world!") (description "Produce a friendly greeting.") (home-page "http://www.gnu.org/software/hello/") (license gpl3+))) build processes chroot, separate UIDs Guile Scheme (guix packages) , make, etc. , make, etc. , make, etc. (guix store) Guile Guile Guile build daemon build processes chroot, separate UIDs Guile Scheme (guix packages) , make, etc. , make, etc. , make, etc. (guix store) Guile Guile Guile build daemon RPCs build processes chroot, separate UIDs Guile Scheme (guix packages) , make, etc. , make, etc. , make, etc. (guix store) Guile Guile Guile build daemon RPCs /gnu/store/ h2g4sf72... -hello-2.10 $ guix gc --references /gnu/store/...-hello-2.10 /gnu/store/...-glibc-2.22 /gnu/store/...-gcc-4.9.3-lib /gnu/store/...-hello-2.10 $ guix build hello isolated build: chroot, separate name spaces, etc. $ guix gc --references /gnu/store/...-hello-2.10 /gnu/store/...-glibc-2.22 /gnu/store/...-gcc-4.9.3-lib /gnu/store/...-hello-2.10 $ guix build hello /gnu/store/ h2g4sf72... -hello-2.10 hash of all the dependencies $ guix build hello /gnu/store/ h2g4sf72... -hello-2.10 $ guix gc --references /gnu/store/...-hello-2.10 /gnu/store/...-glibc-2.22 /gnu/store/...-gcc-4.9.3-lib /gnu/store/...-hello-2.10 $ guix build hello /gnu/store/ h2g4sf72... -hello-2.10 $ guix gc --references /gnu/store/...-hello-2.10 /gnu/store/...-glibc-2.22 /gnu/store/...-gcc-4.9.3-lib /gnu/store/...-hello-2.10(nearly) bit-identical for everyone $ guix package -i gcc-toolchain coreutils sed grep ... demo $ eval `guix package --search-paths` ... $ guix package --manifest=my-software.scm ... A simple matter of installing the deps, right? Want your PhD student to hack on GNUnet? Want your PhD student to hack on GNUnet? A simple matter of installing the deps, right? gnunet-0.10.1 libextractor-1.3 glpk-4.56 ffmpeg-2.8 opus-1.1 libbluray-0.9.0 ladspa-1.13 lame-3.99.5 soxr-0.1.1 texlive-2015 xvid-1.3.3 texlive-texmf-2015 doxygen-1.8.7 lua-5.2.3 texlive-bin-2015 mpfr-3.1.3 graphviz-2.38.0 fontforge-20120731-b gst-plugins-base-1.6.1 libvpx-1.4.0 libx264-20150706-2245 libspiro-20071029 pango-1.38.1 libass-0.12.1 cdparanoia-10.2 orc-0.4.24 yasm-1.2.0 harfbuzz-1.0.5 enca-1.16 gstreamer-1.6.1 fribidi-0.19.6 libcaca-0.99.beta19 libtheora-1.1.1 libmicrohttpd-0.9.45 libquvi-0.4.1 potrace-1.11 gobject-introspection-1.46.0 ftgl-2.1.3-rc5 freeglut-3.0.0 curl-7.45.0 libquvi-scripts-0.4.21 lua-5.1.5 cairo-1.14.2 glu-9.0.0 openal-1.15.1 openldap-2.4.42 gnurl-7.45.0 poppler-0.37.0 recode-3.7.0.201402 mesa-11.0.3 pulseaudio-6.0 icu4c-55.1 bdb-5.3.21 groff-1.22.3 teckit-2.5.4 libuninameslist-0.4.20140731 s2tc-1.0 gts-0.7.6 cairo-1.14.2 presentproto-1.0 dri2proto-2.8 dri3proto-1.0 avahi-0.6.31 json-c-0.12 check-0.9.14 alsa-lib-1.0.27.1 libsamplerate-0.1.8 twolame-0.3.13 speex-1.2rc1 gss-1.0.3 libtool-2.4.6 netpbm-10.61.01 mesa-headers-11.0.3 libspectre-0.2.7 glib-2.46.1 libdaemon-0.14 intltool-0.51.0 libsndfile-1.0.25 shishi-1.0.2 automake-1.15 openjpeg-1.5.2 gd-2.1.1 pixman-0.32.8 ghostscript-9.14.0 tzdata-2015c perl-xml-parser-2.44 dbus-1.10.0 file-5.22 flac-1.3.1 libvorbis-1.3.5 linux-pam-1.2.1 gnutls-3.4.5 autoconf-wrapper-2.69 autoconf-wrapper-2.69 tcsh-6.18.01 libpng-1.5.21 lcms-2.6 libpaper-1.1.24 zziplib-0.13.62 graphite2-1.3.3 python-wrapper-3.4.3 libogg-1.3.2 libidn-1.32 cyrus-sasl-2.1.26 libtasn1-4.5 nettle-3.1.1 autoconf-2.69 guile-2.0.11 which-2.21 ruby-2.2.3 libtiff-4.0.5 libjpeg-8d coreutils-8.24 zip-3.0 python2-fonttools-2.5 python-2.7.10 python-3.4.3 mit-krb5-1.11.3 gmp-6.0.0a texinfo-6.0 bc-1.06 bash-4.3.39 libunistring-0.9.6 libjpeg-9a sqlite-3.8.11.1 libgc-7.4.2 libcap-2.24 python2-setuptools-18.3.1 bzip2-1.0.6 acl-2.2.52 libffi-3.1 gdbm-1.11 tk-8.6.4 libxaw-1.0.12 libxvmc-1.0.8 xinput-1.6.1 libltdl-2.4.6 bison-3.0.4 readline-6.3 libatomic-ops-7.4.2 attr-2.4.46 tcl-8.6.4 libxft-2.3.2 libxmu-1.1.2 libxpm-3.5.11 libxdamage-1.1.4 libva-without-mesa-1.6.1 libxi-1.7.4 libxxf86vm-1.1.3 libxrandr-1.4.2 libxv-1.0.10 libxinerama-1.1.3 flex-2.5.37 exiv2-0.23 giflib-5.1.1 fontconfig-2.11.94 libxrender-0.9.8 libxt-1.1.4 gettext-0.19.6 libxfixes-5.0.1 libxext-1.3.3 xf86vidmodeproto-2.3.1 xmlto-0.0.25 bison-2.7.1 indent-2.2.10 freetype-2.6 libsm-1.2.2 gs-fonts-8.11 expat-2.1.0 fixesproto-5.0 libx11-1.6.2 libcdio-paranoia-10.2+0.93+1 m4-1.4.17 procps-3.2.8 util-linux-2.27 libice-1.0.9 xextproto-7.3.0 libxcb-1.11 inputproto-2.3.1 eudev-3.1.5 libcdio-0.93 libssh2-1.4.3 libxslt-1.1.28 ncurses-6.0 net-base-5.3 xtrans-1.3.5 xcb-proto-1.11 kmod-17 makedepend-1.0.5 libxshmfence-1.1 libxdmcp-1.1.1 libxau-1.0.8 gperf-3.0.4 libcddb-1.3.0 libgcrypt-1.6.3 libgcrypt-1.5.4 libxml2-2.9.2 tar-1.28 xz-5.0.4 python-wrapper-3.4.3 renderproto-0.11.1 xproto-7.0.26 damageproto-1.2.1 libdrm-2.4.65 libgpg-error-1.19 python-minimal-3.4.3 libpciaccess-0.13.4 util-macros-1.19.0 libpthread-stubs-0.3 kbproto-1.0.6 randrproto-1.4.0 xineramaproto-1.2.1 videoproto-2.3.2 glproto-1.4.17 psutils-17 openssl-1.0.2d zlib-1.2.7 pkg-config-0.28 help2man-1.47.2 fftw-3.3.4 fftwf-3.3.4 perl-5.16.1 $ guix environment --container gnunet ... $ guix environment --ad-hoc python-ipython python-numpy \ -E ipython ... Whole-system deployment. Linux-libre Linux-libre initial RAM disk Linux-libre initial RAM disk Guile Linux-libre initial RAM disk Guile PID 1: GNU dmd services... Linux-libre initial RAM disk Guile PID 1: GNU dmd services... Guile Linux-libre initial RAM disk Guile PID 1: GNU dmd services... Guile applications Trustworthiness. Debian’s dirtiest secret: Binary packages built by developers are used in the archive — Lucas Nussbaum, FOSDEM 2015 Transparent binary/source deployment alice@foo$ guix package --install=emacs The following package will be installed: emacs-24.5 /gnu/store/...-emacs-24.5 The following files will be downloaded: /gnu/store/...-emacs-24.5 /gnu/store/...-libxpm-3.5.10 /gnu/store/...-libxext-1.3.1 /gnu/store/...-libxaw-1.0.11 Transparent binary/source deployment alice@foo$ guix package --install=emacs The following package will be installed: emacs-24.5 /gnu/store/...-emacs-24.5 The following files will be downloaded: /gnu/store/...-libxext-1.3.1 /gnu/store/...-libxaw-1.0.11 The following derivations will be built: /gnu/store/...-emacs-24.5.drv /gnu/store/...-libxpm-3.5.10.drv (define foo (package ...)) user (define foo (package ...)) user test guix build foo /gnu/store/...-foo-1.0 (define foo (package ...)) user test guix build foo /gnu/store/...-foo-1.0 git push git.sv.gnu.org (define foo (package ...)) user test pull guix build foo hydra.gnu.org /gnu/store/...-foo-1.0 build farm pull git push git.sv.gnu.org (define foo (package ...)) user test get binary pull guix build foo hydra.gnu.org /gnu/store/...-foo-1.0 build farm pull git push git.sv.gnu.org (define foo (package ...)) user test pull guix build foo /gnu/store/...-foo-1.0 git push git.sv.gnu.org (define foo (package ...)) user test guix build foo no “maintainer /gnu/store/...-foo-1.0 uploads” no single point of trust git push git.sv.gnu.org source ? binary package recipes hydra.gnu.org (define emacs (package ..
Load more

Recommended publications
  • On the Impact of Exception Handling Compatibility on Binary Instrumentation†
    On the Impact of Exception Handling Compatibility on Binary Instrumentation† Soumyakant Priyadarshan Huan Nguyen R. Sekar Stony Brook University Stony Brook University Stony Brook University Stony Brook, NY, USA Stony Brook, NY, USA Stony Brook, NY, USA [email protected] [email protected] [email protected] Abstract overheads, but has been held back by challenges in accurate dis- assembly and code pointer identification. With the emergence of To support C++ exception handling, compilers generate metadata position-independent (or relocatable) binaries as the dominant for- that is a rich source of information about the code layout. On mat in recent years, researchers have been able to address these Linux, this metadata is also used to support stack tracing, thread challenges, e.g., in Egalito [41], RetroWrite [11] and SBR[28, 29] cleanup and other functions. For this reason, Linux binaries contain systems. code-layout-revealing metadata for C-code as well. Even hand- written assembly in low-level system libraries is covered by such Despite recent advances, deployability of binary instrumentation metadata. We investigate the implications of this metadata in this continues to face significant challenges. One of the major concerns paper, and show that it can be used to (a) improve accuracy of is compatibility. In particular, existing static binary instrumentation disassembly, (b) achieve significantly better accuracy at function tools tend to break stack tracing (for C and C++) as well as C++ boundary identification as compared to previous research, and(c) exception handling. While compatibility with these features may as a rich source of information for defeating fine-grained code not be important for proof-of-concept instrumentations, it is hardly randomization.
    [Show full text]
  • MASTERCLASS GNUPG MASTERCLASS You Wouldn’T Want Other People Opening Your Letters and BEN EVERARD Your Data Is No Different
    MASTERCLASS GNUPG MASTERCLASS You wouldn’t want other people opening your letters and BEN EVERARD your data is no different. Encrypt it today! SECURE EMAIL WITH GNUPG AND ENIGMAIL Send encrypted emails from your favourite email client. our typical email is about as secure as a The first thing that you need to do is create a key to JOHN LANE postcard, which is good news if you’re a represent your identity in the OpenPGP world. You’d Ygovernment agency. But you wouldn’t use a typically create one key per identity that you have. postcard for most things sent in the post; you’d use a Most people would have one identity, being sealed envelope. Email is no different; you just need themselves as a person. However, some may find an envelope – and it’s called “Encryption”. having separate personal and professional identities Since the early 1990s, the main way to encrypt useful. It’s a personal choice, but starting with a single email has been PGP, which stands for “Pretty Good key will help while you’re learning. Privacy”. It’s a protocol for the secure encryption of Launch Seahorse and click on the large plus-sign email that has since evolved into an open standard icon that’s just below the menu. Select ‘PGP Key’ and called OpenPGP. work your way through the screens that follow to supply your name and email address and then My lovely horse generate the key. The GNU Privacy Guard (GnuPG), is a free, GPL-licensed You can, optionally, use the Advanced Key Options implementation of the OpenPGP standard (there are to add a comment that can help others identify your other implementations, both free and commercial – key and to select the cipher, its strength and set when the PGP name now refers to a commercial product the key should expire.
    [Show full text]
  • Source Code Trees in the VALLEY of THE
    PROGRAMMING GNOME Source code trees IN THE VALLEY OF THE CODETHORSTEN FISCHER So you’ve just like the one in Listing 1. Not too complex, eh? written yet another Unfortunately, creating a Makefile isn’t always the terrific GNOME best solution, as assumptions on programs program. Great! But locations, path names and others things may not be does it, like so many true in all cases, forcing the user to edit the file in other great programs, order to get it to work properly. lack something in terms of ease of installation? Even the Listing 1: A simple Makefile for a GNOME 1: CC=/usr/bin/gcc best and easiest to use programs 2: CFLAGS=`gnome-config —cflags gnome gnomeui` will cause headaches if you have to 3: LDFLAGS=`gnome-config —libs gnome gnomeui` type in lines like this, 4: OBJ=example.o one.o two.o 5: BINARIES=example With the help of gcc -c sourcee.c gnome-config —libs —cflags 6: gnome gnomeui gnomecanvaspixbuf -o sourcee.o 7: all: $(BINARIES) Automake and Autoconf, 8: you can create easily perhaps repeated for each of the files, and maybe 9: example: $(OBJ) with additional compiler flags too, only to then 10: $(CC) $(LDFLAGS) -o $@ $(OBJ) installed source code demand that everything is linked. And at the end, 11: do you then also have to copy the finished binary 12: .c.o: text trees. Read on to 13: $(CC) $(CFLAGS) -c $< manually into the destination directory? Instead, 14: find out how. wouldn’t you rather have an easy, portable and 15: clean: quick installation process? Well, you can – if you 16: rm -rf $(OBJ) $(BINARIES) know how.
    [Show full text]
  • Libressl Presentatie2
    Birth of LibreSSL and its current status Frank Timmers Consutant, Snow B.V. Background What is LibreSSL • A fork of OpenSSL 1.0.1g • Being worked on extensively by a number of OpenBSD developers What is OpenSSL • OpenSSL is an open source SSL/TLS crypto library • Currently the de facto standard for many servers and clients • Used for securing http, smtp, imap and many others Alternatives • Netscape Security Services (NSS) • BoringSSL • GnuTLS What is Heartbleed • Heartbleed was a bug leaking of private data (keys) from both client and server • At this moment known as “the worst bug ever” • Heartbeat code for DTLS over UDP • So why was this also included in the TCP code? • Not the reason to create a fork Why did this happen • Nobody looked • Or at least didn’t admit they looked Why did nobody look • The code is horrible • Those who did look, quickly looked away and hoped upstream could deal with it Why was the code so horrible • Buggy re-implementations of standard libc functions like random() and malloc() • Forces all platforms to use these buggy implementations • Nested #ifdef, #ifndefs (up to 17 layers deep) through out the code • Written in “OpenSSL C”, basically their own dialect • Everything on by default Why was it so horrible? crypto_malloc • Never frees memory (Tools like Valgrind, Coverity can’t spot bugs) • Used LIFO recycling (Use after free?) • Included debug malloc by default, logging private data • Included the ability to replace malloc/free at runtime #ifdef trees • #ifdef, #elif, #else trees up to 17 layers deep • Throughout the complete source • Some of which could never be reached • Hard to see what is or not compiled in 1.
    [Show full text]
  • Object Oriented Programming
    No. 52 March-A pril'1990 $3.95 T H E M TEe H CAL J 0 URN A L COPIA Object Oriented Programming First it was BASIC, then it was structures, now it's objects. C++ afi<;ionados feel, of course, that objects are so powerful, so encompassing that anything could be so defined. I hope they're not placing bets, because if they are, money's no object. C++ 2.0 page 8 An objective view of the newest C++. Training A Neural Network Now that you have a neural network what do you do with it? Part two of a fascinating series. Debugging C page 21 Pointers Using MEM Keep C fro111 (C)rashing your system. An AT Keyboard Interface Use an AT keyboard with your latest project. And More ... Understanding Logic Families EPROM Programming Speeding Up Your AT Keyboard ((CHAOS MADE TO ORDER~ Explore the Magnificent and Infinite World of Fractals with FRAC LS™ AN ELECTRONIC KALEIDOSCOPE OF NATURES GEOMETRYTM With FracTools, you can modify and play with any of the included images, or easily create new ones by marking a region in an existing image or entering the coordinates directly. Filter out areas of the display, change colors in any area, and animate the fractal to create gorgeous and mesmerizing images. Special effects include Strobe, Kaleidoscope, Stained Glass, Horizontal, Vertical and Diagonal Panning, and Mouse Movies. The most spectacular application is the creation of self-running Slide Shows. Include any PCX file from any of the popular "paint" programs. FracTools also includes a Slide Show Programming Language, to bring a higher degree of control to your shows.
    [Show full text]
  • Red Hat Enterprise Linux 6 Developer Guide
    Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Dave Brolley William Cohen Roland Grunberg Aldy Hernandez Karsten Hopp Jakub Jelinek Developer Guide Jeff Johnston Benjamin Kosnik Aleksander Kurtakov Chris Moller Phil Muldoon Andrew Overholt Charley Wang Kent Sebastian Red Hat Enterprise Linux 6 Developer Guide An introduction to application development tools in Red Hat Enterprise Linux 6 Edition 0 Author Dave Brolley [email protected] Author William Cohen [email protected] Author Roland Grunberg [email protected] Author Aldy Hernandez [email protected] Author Karsten Hopp [email protected] Author Jakub Jelinek [email protected] Author Jeff Johnston [email protected] Author Benjamin Kosnik [email protected] Author Aleksander Kurtakov [email protected] Author Chris Moller [email protected] Author Phil Muldoon [email protected] Author Andrew Overholt [email protected] Author Charley Wang [email protected] Author Kent Sebastian [email protected] Editor Don Domingo [email protected] Editor Jacquelynn East [email protected] Copyright © 2010 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
    [Show full text]
  • Using the GNU Compiler Collection (GCC)
    Using the GNU Compiler Collection (GCC) Using the GNU Compiler Collection by Richard M. Stallman and the GCC Developer Community Last updated 23 May 2004 for GCC 3.4.6 For GCC Version 3.4.6 Published by: GNU Press Website: www.gnupress.org a division of the General: [email protected] Free Software Foundation Orders: [email protected] 59 Temple Place Suite 330 Tel 617-542-5942 Boston, MA 02111-1307 USA Fax 617-542-2652 Last printed October 2003 for GCC 3.3.1. Printed copies are available for $45 each. Copyright c 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being \GNU General Public License" and \Funding Free Software", the Front-Cover texts being (a) (see below), and with the Back-Cover Texts being (b) (see below). A copy of the license is included in the section entitled \GNU Free Documentation License". (a) The FSF's Front-Cover Text is: A GNU Manual (b) The FSF's Back-Cover Text is: You have freedom to copy and modify this GNU Manual, like GNU software. Copies published by the Free Software Foundation raise funds for GNU development. i Short Contents Introduction ...................................... 1 1 Programming Languages Supported by GCC ............ 3 2 Language Standards Supported by GCC ............... 5 3 GCC Command Options .........................
    [Show full text]
  • The Debian GNU/Linux
    The Debian GNU/Linux FAQ translator: etony C.F.AN <[email protected]> Debian FAQ Authors version 5.0.1, 17 March 2012 XXX要要要 ,文cãT一些s于 Debian GNU/Linux 的8Á问题. HHHCCC声声声明明明 Copyright © 1996-2003 by Software in the Public Interest (u守v包+,文cHC声明的MÐ下, A¸6\和发布,文c的完t拷贝. (u守上述完t拷贝H,有sHC声明的MÐ下, A¸拷贝和发布ú于,文c完t拷贝的修9H,, v且, 发布@有通Ç修9 ,文c而得0的工\成果, {使(与,文c的¸可声明一致的¸可声明. (u守上述修9H,HC声明的MÐ下, A¸拷贝和发布,文cv它语言的û译H,, 如果,¸可声明有Ïê1o件ú金 会(Free Software Foundation)8Æ的S0化译,, 则uªS0化译,. i Contents 1 定定定II义与与与概概概述述述 1 1.1 什么/ Debian GNU/Linux?...............................................1 1.2 OK, 现(我知SDebian /. Linux/什么?!.......................................1 1.3 什么/ “Hurd”?.......................................................2 1.4 Debian GNU/Linux 与v他 Linux 发LH有什么不同? 为什么要选éDebian GNU/Linux?............2 1.5 Debian ¡划与ê1o件ú金会的GNU¡划 .......................................2 1.6 Debian 的发音Ê+I?...................................................2 2 Debian GNU/Linux 的的的···取取取与与与安安安ÅÅÅ 3 2.1 Debian 的最新H,/?...................................................3 2.2 如U得0 Debian 的安Å盘?................................................3 2.3 如UÎIq安Å Debian?..................................................3 2.4 我有;U:, 可以·取 Debian qÏ吗?..........................................3 2.5 可以o盘安Å吗?.......................................................3 2.6 可以Q络安Å吗?.......................................................4 3 |||¹¹¹'''问问问题题题 5 3.1 可以(什么7的l件û统上ÐL?.............................................5 3.2 与v他的linux发LH|¹L如U?.............................................5 3.3 Debian 源码与v他
    [Show full text]
  • Beginning Portable Shell Scripting from Novice to Professional
    Beginning Portable Shell Scripting From Novice to Professional Peter Seebach 10436fmfinal 1 10/23/08 10:40:24 PM Beginning Portable Shell Scripting: From Novice to Professional Copyright © 2008 by Peter Seebach All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN-13 (pbk): 978-1-4302-1043-6 ISBN-10 (pbk): 1-4302-1043-5 ISBN-13 (electronic): 978-1-4302-1044-3 ISBN-10 (electronic): 1-4302-1044-3 Printed and bound in the United States of America 9 8 7 6 5 4 3 2 1 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Frank Pohlmann Technical Reviewer: Gary V. Vaughan Editorial Board: Clay Andres, Steve Anglin, Ewan Buckingham, Tony Campbell, Gary Cornell, Jonathan Gennick, Michelle Lowman, Matthew Moodie, Jeffrey Pepper, Frank Pohlmann, Ben Renow-Clarke, Dominic Shakeshaft, Matt Wade, Tom Welsh Project Manager: Richard Dal Porto Copy Editor: Kim Benbow Associate Production Director: Kari Brooks-Copony Production Editor: Katie Stence Compositor: Linda Weidemann, Wolf Creek Press Proofreader: Dan Shaw Indexer: Broccoli Information Management Cover Designer: Kurt Krames Manufacturing Director: Tom Debolski Distributed to the book trade worldwide by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013.
    [Show full text]
  • IPFS and Friends: a Qualitative Comparison of Next Generation Peer-To-Peer Data Networks Erik Daniel and Florian Tschorsch
    1 IPFS and Friends: A Qualitative Comparison of Next Generation Peer-to-Peer Data Networks Erik Daniel and Florian Tschorsch Abstract—Decentralized, distributed storage offers a way to types of files [1]. Napster and Gnutella marked the beginning reduce the impact of data silos as often fostered by centralized and were followed by many other P2P networks focusing on cloud storage. While the intentions of this trend are not new, the specialized application areas or novel network structures. For topic gained traction due to technological advancements, most notably blockchain networks. As a consequence, we observe that example, Freenet [2] realizes anonymous storage and retrieval. a new generation of peer-to-peer data networks emerges. In this Chord [3], CAN [4], and Pastry [5] provide protocols to survey paper, we therefore provide a technical overview of the maintain a structured overlay network topology. In particular, next generation data networks. We use select data networks to BitTorrent [6] received a lot of attention from both users and introduce general concepts and to emphasize new developments. the research community. BitTorrent introduced an incentive Specifically, we provide a deeper outline of the Interplanetary File System and a general overview of Swarm, the Hypercore Pro- mechanism to achieve Pareto efficiency, trying to improve tocol, SAFE, Storj, and Arweave. We identify common building network utilization achieving a higher level of robustness. We blocks and provide a qualitative comparison. From the overview, consider networks such as Napster, Gnutella, Freenet, BitTor- we derive future challenges and research goals concerning data rent, and many more as first generation P2P data networks, networks.
    [Show full text]
  • Ethereal Developer's Guide Draft 0.0.2 (15684) for Ethereal 0.10.11
    Ethereal Developer's Guide Draft 0.0.2 (15684) for Ethereal 0.10.11 Ulf Lamping, Ethereal Developer's Guide: Draft 0.0.2 (15684) for Ethere- al 0.10.11 by Ulf Lamping Copyright © 2004-2005 Ulf Lamping Permission is granted to copy, distribute and/or modify this document under the terms of the GNU General Public License, Version 2 or any later version published by the Free Software Foundation. All logos and trademarks in this document are property of their respective owner. Table of Contents Preface .............................................................................................................................. vii 1. Foreword ............................................................................................................... vii 2. Who should read this document? ............................................................................... viii 3. Acknowledgements ................................................................................................... ix 4. About this document .................................................................................................. x 5. Where to get the latest copy of this document? ............................................................... xi 6. Providing feedback about this document ...................................................................... xii I. Ethereal Build Environment ................................................................................................14 1. Introduction .............................................................................................................15
    [Show full text]
  • A Compiler Front-End for the WOOL Parallelization Library
    A compiler front-end for the WOOL Parallelization library GEORGIOS VARISTEAS KTH Information and Communication Technology Master of Science Thesis Stockholm, Sweden 2010 TRITA-ICT-EX-2010:291 Royal Institute of Technology A compiler front-end for the WOOL Parallelization library Georgios Varisteas yorgos(@)kth.se 15 October, 2010 A master thesis project conducted at Examiner: Mats Brorsson Supervisor: Karl-Filip Faxén Abstract WOOL is a C parallelization library developed at SICS by Karl-Filip Faxén. It provides the tools for develop- ing fine grained independent task based parallel applications. This library is distinguished from other similar projects by being really fast and light; it manages to spawn and synchronize tasks in under 20 cycles. However, all software development frameworks which expose radically new functionality to a programming language, gain a lot by having a compiler to encapsulate and implement them. WOOL does not differ from this category. This project is about the development of a source-to-source compiler for the WOOL parallelization library, supporting an extension of the C language with new syntax that implements the WOOL API, transform- ing it and eventually outputting GNU C code. Additionally, this compiler is augmented with a wrapper script that performs compilation to machine code by using GCC. This script is configurable and fully automatic. The main advantage gained from this project is to satisfy the need for less overhead in software development with WOOL. The simplified syntax results in faster and more economical code writing while being less error- prone. Moreover, this compiler enables the future addition of many more features not applicable with the current state of WOOL as a library.
    [Show full text]