mirror of
https://git.savannah.gnu.org/git/guix.git
synced 2025-01-30 22:36:50 +01:00
No description
b57cdccc7c
This commit disables one of the backends for the persistent storage driver pstore in the Linux kernel, in particular the backend which allows it to save data to EFI variables storage in UEFI NVRAM, such as error log "dump" files. This reduces writes to UEFI to reduce the chances of it wearing out or malfunctioning for other reasons, as well as prevents situations when the efivar is full and cannot take new variables, which is known to cause "Could not prepare Boot variable: No space left on device" errors on computers with some UEFI implementations which are susceptible to such problems, typically on relatively older machines. The user is confronted by the issue at the later stages of guix system reconfiguration when the new boot entry is created. It may be difficult to recover from because the exact cause depends on UEFI. Sometimes it is enough to remove dumps from efivars. Disabling the EFI pstore backend is expected to reduce the chances of unaware users running into issues with UEFI and failing to boot their Guix Systems. Sophisticated users may still enable the backend by changing the option via the kernel arguments, either in the system configuration or in GRUB. The above is my summary of what was previously discussed in guix-help mailing list: <https://lists.gnu.org/archive/html/help-guix/2025-01/msg00173.html>. * gnu/packages/linux.scm (default-extra-linux-options): Enable the kernel build-time configuration option CONFIG_EFI_VARS_PSTORE_DEFAULT_DISABLE. Change-Id: Id0294fa90ccbf3bacbb55a22aeb4f0a863efe22c Signed-off-by: Leo Famulari <leo@famulari.name> |
||
---|---|---|
.mumi | ||
build-aux | ||
doc | ||
etc | ||
gnu | ||
guix | ||
m4 | ||
nix | ||
po | ||
scripts | ||
tests | ||
.dir-locals.el | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.guix-authorizations | ||
.guix-channel | ||
.mailmap | ||
.patman | ||
AUTHORS | ||
bootstrap | ||
ChangeLog | ||
CODE-OF-CONDUCT | ||
config-daemon.ac | ||
configure.ac | ||
COPYING | ||
gnu.scm | ||
guix.scm | ||
HACKING | ||
Makefile.am | ||
manifest.scm | ||
NEWS | ||
README | ||
ROADMAP | ||
THANKS | ||
TODO |
-*- mode: org -*- [[https://www.gnu.org/software/guix/][GNU Guix]] (IPA: /ɡiːks/) is a purely functional package manager, and associated free software distribution, for the [[https://www.gnu.org/gnu/gnu.html][GNU system]]. In addition to standard package management features, Guix supports transactional upgrades and roll-backs, unprivileged package management, per-user profiles, and garbage collection. It provides [[https://www.gnu.org/software/guile/][Guile]] Scheme APIs, including a high-level embedded domain-specific languages (EDSLs) to describe how packages are to be built and composed. GNU Guix can be used on top of an already-installed GNU/Linux distribution, or it can be used standalone (we call that “Guix System”). Guix is based on the [[https://nixos.org/nix/][Nix]] package manager. * Requirements If you are building Guix from source, please see the manual for build instructions and requirements, either by running: info -f doc/guix.info "Requirements" or by checking the [[https://guix.gnu.org/manual/en/html_node/Requirements.html][web copy of the manual]]. * Installation See the manual for the installation instructions, either by running info -f doc/guix.info "Installation" or by checking the [[https://guix.gnu.org/manual/en/html_node/Installation.html][web copy of the manual]]. * Building from Git For information on building Guix from a Git checkout, please see the relevant section in the manual, either by running info -f doc/guix.info "Building from Git" or by checking the [[https://guix.gnu.org/manual/en/html_node/Building-from-Git.html][web_copy of the manual]]. * How It Works Guix does the high-level preparation of a /derivation/. A derivation is the promise of a build; it is stored as a text file under =/gnu/store/xxx.drv=. The (guix derivations) module provides the `derivation' primitive, as well as higher-level wrappers such as `build-expression->derivation'. Guix does remote procedure calls (RPCs) to the build daemon (the =guix-daemon= command), which in turn performs builds and accesses to the store on its behalf. The RPCs are implemented in the (guix store) module. * Contact GNU Guix is hosted at https://savannah.gnu.org/projects/guix/. Please email <help-guix@gnu.org> for questions and <bug-guix@gnu.org> for bug reports; email <gnu-system-discuss@gnu.org> for general issues regarding the GNU system. Join #guix on irc.libera.chat. * Guix & Nix GNU Guix is based on [[https://nixos.org/nix/][the Nix package manager]]. It implements the same package deployment paradigm, and in fact it reuses some of its code. Yet, different engineering decisions were made for Guix, as described below. Nix is really two things: a package build tool, implemented by a library and daemon, and a special-purpose programming language. GNU Guix relies on the former, but uses Scheme as a replacement for the latter. Using Scheme instead of a specific language allows us to get all the features and tooling that come with Guile (compiler, debugger, REPL, Unicode, libraries, etc.) And it means that we have a general-purpose language, on top of which we can have embedded domain-specific languages (EDSLs), such as the one used to define packages. This broadens what can be done in package recipes themselves, and what can be done around them. Technically, Guix makes remote procedure calls to the ‘nix-worker’ daemon to perform operations on the store. At the lowest level, Nix “derivations” represent promises of a build, stored in ‘.drv’ files in the store. Guix produces such derivations, which are then interpreted by the daemon to perform the build. Thus, Guix derivations can use derivations produced by Nix (and vice versa). With Nix and the [[https://nixos.org/nixpkgs][Nixpkgs]] distribution, package composition happens at the Nix language level, but builders are usually written in Bash. Conversely, Guix encourages the use of Scheme for both package composition and builders. Likewise, the core functionality of Nix is written in C++ and Perl; Guix relies on some of the original C++ code, but exposes all the API as Scheme. * Related software - [[https://nixos.org][Nix, Nixpkgs, and NixOS]], functional package manager and associated software distribution, are the inspiration of Guix - [[https://www.gnu.org/software/stow/][GNU Stow]] builds around the idea of one directory per prefix, and a symlink tree to create user environments - [[https://www.pvv.ntnu.no/~arnej/store/storedoc_6.html][STORE]] shares the same idea - [[https://live.gnome.org/OSTree/][GNOME's OSTree]] allows bootable system images to be built from a specified set of packages - The [[https://www.gnu.org/s/gsrc/][GNU Source Release Collection]] (GSRC) is a user-land software distribution; unlike Guix, it relies on core tools available on the host system