Nix User's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Nix User’s Guide i Nix User’s Guide Ed. Version 1.3 Nix User’s Guide ii Copyright © 2004-2012 Eelco Dolstra Nix User’s Guide iii Contents 1 Introduction 1 1.1 About Nix . 1 1.1.1 Multiple versions . 1 1.1.2 Complete dependencies . 1 1.1.3 Multi-user support . 2 1.1.4 Atomic upgrades and rollbacks . 2 1.1.5 Garbage collection . 2 1.1.6 Functional package language . 2 1.1.7 Transparent source/binary deployment . 2 1.1.8 Binary patching . 3 1.1.9 Nix Packages collection . 3 1.1.10 Service deployment . 3 1.1.11 Portability . 3 1.1.12 NixOS . 3 1.2 About us . 3 1.3 About this manual . 3 1.4 License . 3 1.5 More information . 4 2 Quick Start 5 3 Installation 7 3.1 Supported platforms . 7 3.2 Installing a binary distribution . 7 3.3 Installing Nix from source . 8 3.3.1 Prerequisites . 8 3.3.2 Obtaining a source distribution . 8 3.3.3 Building Nix from source . 9 3.4 Security . 9 3.4.1 Single-user mode . 9 3.4.2 Multi-user mode . 9 Nix User’s Guide iv 3.4.2.1 Setting up the build users . 10 3.4.2.2 Nix store/database owned by root . 10 3.4.2.3 Nix store/database not owned by root . 11 3.4.2.4 Restricting access . 11 3.5 Using Nix . 11 4 Package Management 12 4.1 Basic package management . 12 4.2 Proﬁles . 14 4.3 Garbage collection . 15 4.3.1 Garbage collector roots . 16 4.4 Channels . 16 4.5 One-click installs . 17 4.6 Sharing packages between machines . 17 5 Writing Nix Expressions 19 5.1 A simple Nix expression . 19 5.1.1 The Nix expression . 19 5.1.2 The builder . 20 5.1.3 Composition . 21 5.1.4 Testing . 22 5.1.5 The generic builder . 23 5.2 The Nix expression language . 24 5.2.1 Values . 24 5.2.1.1 Simple values . 24 5.2.1.2 Lists . 25 5.2.1.3 Attribute sets . 26 5.2.2 Language constructs . 26 5.2.2.1 Recursive attribute sets . 26 5.2.2.2 Let-expressions . 27 5.2.2.3 Inheriting attributes . 27 5.2.2.4 Functions . 27 5.2.2.5 Conditionals . 28 5.2.2.6 Assertions . 28 5.2.2.7 With-expressions . 29 5.2.2.8 Comments . 30 5.2.3 Operators . 30 5.2.4 Derivations . 30 5.2.4.1 Advanced attributes . 32 5.2.5 Built-in functions . 34 5.3 The standard environment . 39 5.3.1 Customising the generic builder . 40 5.3.2 Debugging failed builds . 40 Nix User’s Guide v 6 Setting Up Distributed Builds 41 A Command Reference 43 A.1 Common options . 43 A.2 Common environment variables . 45 A.3 Main commands . 46 A.3.1 nix-env . 46 A.3.2 nix-instantiate . 55.

108

Copy Link

Recommended publications

Github: a Case Study of Linux/BSD Perceptions from Microsoft's
1 FLOSS != GitHub: A Case Study of Linux/BSD Perceptions from Microsoft’s Acquisition of GitHub Raula Gaikovina Kula∗, Hideki Hata∗, Kenichi Matsumoto∗ ∗Nara Institute of Science and Technology, Japan {raula-k, hata, matumoto}@is.naist.jp Abstract—In 2018, the software industry giants Microsoft made has had its share of disagreements with Microsoft [6], [7], a move into the Open Source world by completing the acquisition [8], [9], the only reported negative opinion of free software of mega Open Source platform, GitHub. This acquisition was not community has different attitudes towards GitHub is the idea without controversy, as it is well-known that the free software communities includes not only the ability to use software freely, of ‘forking’ so far, as it it is considered as a danger to FLOSS but also the libre nature in Open Source Software. In this study, development [10]. our aim is to explore these perceptions in FLOSS developers. We In this paper, we report on how external events such as conducted a survey that covered traditional FLOSS source Linux, acquisition of the open source platform by a closed source and BSD communities and received 246 developer responses. organization triggers a FLOSS developers such the Linux/ The results of the survey conﬁrm that the free community did trigger some communities to move away from GitHub and raised BSD Free Software communities. discussions into free and open software on the GitHub platform. The study reminds us that although GitHub is inﬂuential and II. TARGET SUBJECTS AND SURVEY DESIGN trendy, it does not representative all FLOSS communities.
[Show full text]
Debian \ Amber \ Arco-Debian \ Arc-Live \ Aslinux \ Beatrix
Debian \ Amber \ Arco-Debian \ Arc-Live \ ASLinux \ BeatriX \ BlackRhino \ BlankON \ Bluewall \ BOSS \ Canaima \ Clonezilla Live \ Conducit \ Corel \ Xandros \ DeadCD \ Olive \ DeMuDi \ \ 64Studio (64 Studio) \ DoudouLinux \ DRBL \ Elive \ Epidemic \ Estrella Roja \ Euronode \ GALPon MiniNo \ Gibraltar \ GNUGuitarINUX \ gnuLiNex \ \ Lihuen \ grml \ Guadalinex \ Impi \ Inquisitor \ Linux Mint Debian \ LliureX \ K-DEMar \ kademar \ Knoppix \ \ B2D \ \ Bioknoppix \ \ Damn Small Linux \ \ \ Hikarunix \ \ \ DSL-N \ \ \ Damn Vulnerable Linux \ \ Danix \ \ Feather \ \ INSERT \ \ Joatha \ \ Kaella \ \ Kanotix \ \ \ Auditor Security Linux \ \ \ Backtrack \ \ \ Parsix \ \ Kurumin \ \ \ Dizinha \ \ \ \ NeoDizinha \ \ \ \ Patinho Faminto \ \ \ Kalango \ \ \ Poseidon \ \ MAX \ \ Medialinux \ \ Mediainlinux \ \ ArtistX \ \ Morphix \ \ \ Aquamorph \ \ \ Dreamlinux \ \ \ Hiwix \ \ \ Hiweed \ \ \ \ Deepin \ \ \ ZoneCD \ \ Musix \ \ ParallelKnoppix \ \ Quantian \ \ Shabdix \ \ Symphony OS \ \ Whoppix \ \ WHAX \ LEAF \ Libranet \ Librassoc \ Lindows \ Linspire \ \ Freespire \ Liquid Lemur \ Matriux \ MEPIS \ SimplyMEPIS \ \ antiX \ \ \ Swift \ Metamorphose \ miniwoody \ Bonzai \ MoLinux \ \ Tirwal \ NepaLinux \ Nova \ Omoikane (Arma) \ OpenMediaVault \ OS2005 \ Maemo \ Meego Harmattan \ PelicanHPC \ Progeny \ Progress \ Proxmox \ PureOS \ Red Ribbon \ Resulinux \ Rxart \ SalineOS \ Semplice \ sidux \ aptosid \ \ siduction \ Skolelinux \ Snowlinux \ srvRX live \ Storm \ Tails \ ThinClientOS \ Trisquel \ Tuquito \ Ubuntu \ \ A/V \ \ AV \ \ Airinux \ \ Arabian
[Show full text]
Free Gnu Linux Distributions
Free gnu linux distributions The Free Software Foundation is not responsible for other web sites, or how up-to-date their information is. This page lists the GNU/Linux distributions that are Linux and GNU · Why we don't endorse some · GNU Guix. We recommend that you use a free GNU/Linux system distribution, one that does not include proprietary software at all. That way you can be sure that you are. Canaima GNU/Linux is a distribution made by Venezuela's government to distribute Debian's Social Contract states the goal of making Debian entirely free. The FSF is proud to announce the newest addition to our list of fully free GNU/Linux distributions, adding its first ever small system distribution. Trisquel, Kongoni, and the other GNU/Linux system distributions on the FSF's list only include and only propose free software. They reject. The FSF's list consists of ready-to-use full GNU/Linux systems whose developers have made a commitment to follow the Guidelines for Free. GNU Linux-libre is a project to maintain and publish % Free distributions of Linux, suitable for use in Free System Distributions, removing. A "live" distribution is a Linux distribution that can be booted The portability of installation-free distributions makes them Puppy Linux, Devil-Linux, SuperGamer, SliTaz GNU/Linux. They only list GNU/Linux distributions that follow the GNU FSDG (Free System Distribution Guidelines). That the software (as well as the. Trisquel GNU/Linux is a fully free operating system for home users, small making the distro more reliable through quicker and more traceable updates.
[Show full text]
A Deep Dive Into Nixos: from Configuration to Boot CS5250: Advanced Operating Systems
A Deep Dive into NixOS: From Configuration To Boot CS5250: Advanced Operating Systems Chen Jingwen A0111764L National University of Singapore Abstract Mature operating systems (e.g. Windows, Fedora) are inherently stateful and imperative, adding layers of complexity by installing or upgrading software. This causes side-effects such as breaking existing software while upgrading shared libraries without maintaining backwards compatibility. NixOS is a Linux distribution designed to be purely functional, where building everything from the kernel to the web browser has no side- effects. System configuration files are written in the Nix language, a lazy functional domain specific language with a declarative syntax, and software packages are managed by the Nix package manager. A distinct feature of NixOS is the ability to declare the configuration of an entire system in one file, which is then used to build a bootable system deterministically. This report gives an overview and the motivations of NixOS, and a deep dive into how the configuration of an operating system can be derived from a single file. 1 Contents 1 Introduction 4 2 Motivation 5 2.1 Multiple versions . 5 2.2 Destructive updates . 5 2.3 Rollback difficulties . 6 2.4 Non-atomic upgrades . 6 2.5 Inability to reproduce builds . 6 3 NixOS Architecture 7 3.1 Package specifications and the Nix expression language . 7 3.1.1 Nix expression language . 8 3.1.2 Derivations . 9 3.2 Nix store . 9 3.2.1 Cryptographic hash . 9 3.2.2 Source to binary deployment . 10 3.2.3 Nix database . 10 3.3 Nix package manager .
[Show full text]
Nix(OS) - Revolutionizing Packaging and Configuration Management!
Nix(OS) - Revolutionizing packaging and configuration management! The Purely Functional Linux Distribution 1 Before we begin (FYI) Ask questions at any time Please ask lots of questions :) The slides contain some redundancy There are a few optional slides at the end Please give me feedback Louder Faster/slower More/less details Etc. 2 About me Michael Weiss aka. primeos Computer science student at the University of Tübingen I love free soware, etc. First nixpkgs commit: 2016-10-05 I maintain ~41 packages and ~3 modules (2018-06-08) I also love privacy (i.e. no more details :P) Email: [email protected] (#privacy) 3 Main components Nix (package manager) Nixpkgs (Nix packages collection) NixOS (operating system) NixOps (DevOps / cloud deployment tool) 4 Nix* ISO/OSI model NixOps NixOS Nixpkgs Nix 5 Other tools Hydra (Nix based continuous build system) Disnix (distributed services deployment) PatchELF (change dynamic linker and RPATH) {cabal,go,node,pip,python,pypi,composer,hex,bower,vim,...}2 6 History Started as a research project (with funding) First paper in 2004 (many will follow) Nix package manager developed by Eelco Dolstra as part of his PhD research (~2003) First NixOS prototype developed by Armijn Hemel as his master's thesis project Hydra developed as part of the LaQuSo Buildfarm project 7 Timeline 2003: init (research begins) 2007: NixOS becomes usable + x86_64 support 2008: Website moved to nixos.org 2009: Nix logo + Nix(OS) build on Hydra 2011: Migration from Subversion to Git(Hub) 2013: Switch from Upstart to systemd +
[Show full text]
Porteus Kali 1.0.6
DISTROHOPPER DISTROHOPPER We’ve tapped GCHQ’s communications to find out what’s going on in distro land. Porteus Lightning-fast live Linux. orteus is a distribution designed for running directly off a USB stick. Big Pdeal – almost every distribution can do that these days, so you may wonder if there’s still room for a distro like Porteus. However, there’s plenty that’s unusual about it. Porteus doesn’t have a download link like you may expect, but a build service where you can customise your own version of Porteus. You can select things like the desktop environment, the web browser and word processor, and in the Advanced options you can set things like the system passwords and boot behaviour. The second unusual thing about Porteus is how quickly it boots. On our test system, Porteus Mate got from Grub to the desktop in under 10 seconds, and this was in a Porteus Kiosk has a bounty scheme where you can donate money towards certain features. virtual machine. The VM was allocated two cores of the i7 processor, but to put it into distro, it took just 15 seconds. On the down targeted very firmly at people who want context, OpenSuse took just over a minute. side there is quite a limited choice for the a minimal live distro. Of course, this isn’t This speed is incredible for a live distro. We applications you can install, and there’s really a problem, because there are loads of ran the test again with the KDE version of little else other than those you select in the alternative options for people who want a Porteus, and even with the heavyweight build system.
[Show full text]
Nixos: Järjestelmäkonfiguraation Hallintaan Erikoistunut Linux-Jakelu
Kalle Kumpulainen NIXOS: JÄRJESTELMÄKONFIGURAATION HALLINTAAN ERIKOISTUNUT LINUX-JAKELU Informaatioteknologian ja viestinnän tiedekunta Kandidaatintyö Toukokuu 2019 i TIIVISTELMÄ Kalle Kumpulainen: NixOS: Järjestelmäkonfiguraation Hallintaan Erikoistunut Linux-jakelu English title: NixOS: A Linux Distribution Specialized in System Configuration Management Kandidaatintyö Tampereen yliopisto Tieto- ja sähkötekniikka Toukokuu 2019 Työn analyysin kohteena oli hollantilaisen Eelco Dolstran tutkimusprojektina alkanut ja sittem- min väitöskirjaksi asti päätynyt projekti NixOS, joka on järjestelmäkonfiguroinnin hallintaan ja oh- jelmistojen jakeluun liittyvien ongelmakohtien ratkaisemiseen erikoistunut Linux-pohjainen käyt- töjärjestelmä. Tämän työn tarkoituksena oli selvittää tarkemmin mitä nämä ongelmakohdat tosia- siassa ovat, millaisilla ratkaisuilla niitä on NixOS:ssä ratkaistu ja millaisia eroavaisuuksia NixOS si- sältää verrattuna muihin suosittuihin Linux-käyttöjärjestelmiin. Tämän lisäksi tavoitteena oli myös selvittää millaisiin käyttökohteisiin NixOS sopii. Työssä perehdyttiin aluksi tavallisten Linux-jakeluiden rakenteeseen, josta erityisesti pakettien- hallintaan, koska se on NixOS:n poikkeuksellisin ja tärkein komponentti. Näillä tiedoilla siirryttiin NixOS:n esittelyyn, josta käytiin läpi sen historiaa, rakennetta ja erityisiä ominaisuuksia. Tämän jälkeen keskityttiin NixOS:n tärkeimpään ominaisuuteen, eli sen pakettienhallintajärjestelmään. Siitä käytiin läpi sen toimintaperiaate ja erot muihin pakettienhallintajärjestelmiin.
[Show full text]
Journal of Functional Programming Nixos: a Purely Functional Linux
Journal of Functional Programming http://journals.cambridge.org/JFP Additional services for Journal of Functional Programming: Email alerts: Click here Subscriptions: Click here Commercial reprints: Click here Terms of use : Click here NixOS: A purely functional Linux distribution EELCO DOLSTRA, ANDRES LÖH and NICOLAS PIERRON Journal of Functional Programming / Volume 20 / Special Issue 56 / November 2010, pp 577 615 DOI: 10.1017/S0956796810000195, Published online: 15 October 2010 Link to this article: http://journals.cambridge.org/abstract_S0956796810000195 How to cite this article: EELCO DOLSTRA, ANDRES LÖH and NICOLAS PIERRON (2010). NixOS: A purely functional Linux distribution. Journal of Functional Programming,20, pp 577615 doi:10.1017/ S0956796810000195 Request Permissions : Click here Downloaded from http://journals.cambridge.org/JFP, by Username: nrnr, IP address: 108.20.67.9 on 31 Aug 2012 JFP 20 (5 & 6): 577–615, 2011. c Cambridge University Press 2010 577 doi:10.1017/S0956796810000195 First published online 15 October 2010 NixOS: A purely functional Linux distribution EELCO DOLSTRA Department of Software Technology, Delft University of Technology, Postbus 5031, 2600 GA Delft, The Netherlands (e-mail: [email protected]) ANDRES LOH¨ Department of Information and Computing Sciences, Utrecht University, Postbus 80 . 089, 3508 TB Utrecht, The Netherlands (e-mail: [email protected]) NICOLAS PIERRON EPITA Research and Development Laboratory, 14-16 rue Voltaire, 94276 Le Kremlin-Bicetreˆ cedex, France (e-mail: [email protected]) Abstract Existing package and system configuration management tools suffer from an imperative model, where system administration actions such as package upgrades or changes to system configuration files are stateful: they destructively update the state of the system.
[Show full text]
Reproducible Builds Summit IV December 11 – 13, 2019
Reproducible Builds Summit IV December 11 – 13, 2019. Paris, France Event Documentation Aspiration, 2973 16th Street, Suite 300, San Francisco, CA 94103 Phone: (415) 839-6456 • [email protected] • aspirationtech.org Table of Contents Agenda..........................................................................................................................................4 Session notes..............................................................................................................................10 Day 1.......................................................................................................................................10 Project updates...................................................................................................................10 Agenda brainstorming........................................................................................................13 Strategic working sessions I...............................................................................................21 Tooling............................................................................................................................21 Compilers.......................................................................................................................23 User verification..............................................................................................................24 Terminology....................................................................................................................28
[Show full text]
Sage Installation Guide Release 9.4
Sage Installation Guide Release 9.4 The Sage Development Team Aug 24, 2021 CONTENTS 1 Linux package managers 3 2 Install from Pre-built Binaries5 2.1 Download Guide.............................................5 2.2 Linux...................................................5 2.3 macOS..................................................6 2.4 Microsoft Windows (Cygwin)......................................6 3 Install from conda-forge 7 4 Install from Source Code 9 4.1 Supported platforms...........................................9 4.2 Prerequisites............................................... 10 4.3 Additional software........................................... 18 4.4 Step-by-step installation procedure.................................... 20 4.5 Make targets............................................... 25 4.6 Environment variables.......................................... 25 4.7 Installation in a Multiuser Environment................................. 30 5 Launching SageMath 33 5.1 Using a Jupyter Notebook remotely................................... 33 5.2 WSL Post-installation steps....................................... 34 5.3 Setting up SageMath as a Jupyter kernel in an existing Jupyter notebook or JupyterLab installation.. 35 6 Troubleshooting 37 Index 39 i ii Sage Installation Guide, Release 9.4 You can install SageMath either from a package manager, a pre-built binary tarball or from its sources. Installing SageMath from your distribution package manager is the preferred and fastest solution (dependencies will be automatically taken care of and SageMath will be using your system Python). It is the case at least for the following GNU/Linux distributions: Debian version >= 9, Ubuntu version >= 18.04, Arch Linux, and NixOS. If you are in this situation, see Linux package managers. If your operating system does not provide SageMath, you can also use a pre-built binary. See the section Install from Pre-built Binaries. Or you could install the sage package from the conda-forge project.
[Show full text]
Nixos: the Purely Functional Linux Distribution
NixOS: The Purely Functional Linux Distribution Eelco Dolstra LogicBlox 21 November 2013 Upgrading is risky business I No way to roll back I Not atomic / transactional Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) So what was wrong with the previous 298 distributions? Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) So what was wrong with the previous 298 distributions? Upgrading is risky business I No way to roll back I Not atomic / transactional Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) So what was wrong with the previous 298 distributions? Upgrading is risky business I No way to roll back I Not atomic / transactional Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce So what was wrong with the previous 298 distributions? Upgrading is risky business I No way to roll back I Not atomic / transactional Not declarative I Configuration is result of automated/manual changes over time I Therefore hard to reproduce Package management limitations I Hard to have multiple versions of a package I Need to be root to install packages I Upgrading one package may break others (“DLL hell”) Analysis Conventional Linux distributions have an imperative (stateful) approach to configuration / package management.
[Show full text]
Self-Scaling Clusters and Reproducible Containers to Enable Scientific Computing
Self-Scaling Clusters and Reproducible Containers to Enable Scientific Computing Peter Z. Vaillancourt∗, J. Eric Coultery, Richard Knepperz, Brandon Barkerx ∗Center for Advanced Computing Cornell University, Ithaca, New York, USA Email: [email protected] yCyberinfrastructure Integration Research Center Indiana University, Bloomington, IN, USA Email: [email protected] zCenter for Advanced Computing Cornell University, Ithaca, New York, USA Email: [email protected] xCenter for Advanced Computing Cornell University, Ithaca, New York, USA Email: [email protected] Abstract—Container technologies such as Docker have become cyberinfrastructure at a number of campuses, enabling them a crucial component of many software industry practices espe- to provide computational resources to their faculty members cially those pertaining to reproducibility and portability. The con- [2]. As more organizations utilize cloud resources in order tainerization philosophy has influenced the scientific computing community, which has begun to adopt – and even develop – con- to provide flexible infrastructure for research purposes, CRI tainer technologies (such as Singularity). Leveraging containers has begun providing tools to harness the scalability and utility for scientific software often poses challenges distinct from those of cloud infrastructure, working together with the members encountered in industry, and requires different methodologies. of the Aristotle Cloud Federation Project [3]. Red Cloud, the This is especially true for HPC. With an increasing number Cornell component of the Aristotle Cloud Federation, provides of options for HPC in the cloud (including NSF-funded cloud projects), there is strong motivation to seek solutions that provide an OpenStack cloud services much like the Jetstream resource, flexibility to develop and deploy scientific software on a variety that is available both to Cornell faculty as well as to Aristotle of computational infrastructures in a portable and reproducible members.
[Show full text]