From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms0.migadu.com with LMTPS id KH3wFK8+CGLoJgAAgWs5BA (envelope-from ) for ; Sun, 13 Feb 2022 00:11:43 +0100 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id aMhOEq8+CGKckAAA9RJhRA (envelope-from ) for ; Sun, 13 Feb 2022 00:11:43 +0100 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id D102A30F08 for ; Sun, 13 Feb 2022 00:11:38 +0100 (CET) Received: from localhost ([::1]:41082 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nJ1YH-0006xe-9G for larch@yhetil.org; Sat, 12 Feb 2022 18:11:37 -0500 Received: from eggs.gnu.org ([209.51.188.92]:37516) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJ1Y4-0006vf-E5 for help-guix@gnu.org; Sat, 12 Feb 2022 18:11:24 -0500 Received: from mx.nixnet.email ([94.16.121.167]:56836) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nJ1Y1-0006Km-Un for help-guix@gnu.org; Sat, 12 Feb 2022 18:11:24 -0500 Received: from [127.0.0.1] (localhost [127.0.0.1]) by mx.nixnet.email (Postfix) with ESMTPSA id ED97C2005CB; Sat, 12 Feb 2022 18:11:17 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nixnet.email; s=202002021149; t=1644707478; h=from:from:reply-to:subject:subject:to:to:cc:cc; bh=YWSa65WVqpzojv3TsbOdeJWCzNHNEXjY/6xU7Ch4L5Q=; b=U09WOUAJuc/iMbuDDPCi5aBewm/aV64C7FsKtRWqqqCZsrhPGC3zW9HMYOCZKSdYqwayV0 2Kc7rwcAfLPmTgC0Ex+4X9T8Dv7ndTyl27oj/tPSm2Vlgs5BEuEXytarpiMvEhRKo67U8I Y6KHttVUMKFJhGx2ZJeozBhjSgMdOm4= MIME-Version: 1.0 Date: Sat, 12 Feb 2022 23:11:17 +0000 From: SeerLite To: coralgoat@tuta.io Cc: Help Guix Subject: Re: Stuck at scheme prompt when booting In-Reply-To: References: Message-ID: X-Sender: seerlite@nixnet.email Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Received-SPF: pass client-ip=94.16.121.167; envelope-from=seerlite@nixnet.email; helo=mx.nixnet.email X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-guix@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+larch=yhetil.org@gnu.org Sender: "Help-Guix" X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1644707499; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=YWSa65WVqpzojv3TsbOdeJWCzNHNEXjY/6xU7Ch4L5Q=; b=PwzC9yBdosBCfTb9lcn8LDZfdorvkysogXc3yuJt3Zoe5WhQgztqlDsos2GbZ8UJeCgzHs I2sqkgpOfF9P+KqD1q0WYPf7AsbBfyjDQTs6vrCqviljyMJXCPNOATSp9v+9dDaHJL85Qu IHVLA5lIYq5JVZ4Zl78rYYnrCaZCZ4YExspJMI/cvWnZZzoMNgmmV0THibbM4JAuSfCqY7 dS6vqlBAGlBUzixhnLLw5Mt8glRNGP2oFpy88YU+9ixk4QSJGSSidFD8WepYZ8f7o397Pv TaFtSnHH3tUTNhjFIryhlGMFblg+9VkbKXBB27fnHXjJoRRNF7I8/FBY/D4sew== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1644707499; a=rsa-sha256; cv=none; b=ZBXyDFlJpJZy9GD8k62JR/cS+zoBse1jlZspLTrdvk5r0ZoH3MfTqY98VhzoED7gz42vxf 6hpNWh9g4Sv5YzjnsriGcxAbMgJqL6x5v6XsJQpCuD5jgcYhQAqJqRJYk1KzAAddZ5BAOw 8SQ4oWlRtFXj6RT6p71QsIomwDQdB6iJjXl1oFVtpY634M5OaoHyCjti3Ri1rAitA7mSS+ p1MFDeYg2lFxStZ7yQAqrD6+doUJ5r1kYJGoSidpE5cMkiEAqbXrnVNomQZLgPtdFGvOgL 2q4KlpD1DOLp62/TDjUJcap5XX9Azo77KEp+cQ951o2jC53tybMx1r77UJ5OJg== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=nixnet.email header.s=202002021149 header.b=U09WOUAJ; dmarc=pass (policy=reject) header.from=nixnet.email; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -6.13 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=nixnet.email header.s=202002021149 header.b=U09WOUAJ; dmarc=pass (policy=reject) header.from=nixnet.email; spf=pass (aspmx1.migadu.com: domain of "help-guix-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="help-guix-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: D102A30F08 X-Spam-Score: -6.13 X-Migadu-Scanner: scn0.migadu.com X-TUID: Fi02ypjxIDWc On 2/12/22 15:15, coralgoat--- via wrote: > I could try booting an operating system in memory and then use a disk > encryption program to decrypt the hard drive with my passphrase and > then run `chattr -i /etc/resolv.conf`.  What disk encryption program > should I use to decrypt the hard disk? Guix uses dm-crypt so you should be able to use the cryptsetup tool available in most distributions by default: cryptsetup open /dev/sda2 guix The above command creates decrypted representation of the /dev/sda2 partition at /dev/mapper/guix. You can mount this file like any other partition. This should be enough to access the contents of the system in case the boot process completely breaks. However in this case Ricardo's advice may be enough to get it to work from within Guix itself. I explained the above for future reference or in case it doesn't work. > I resolved the domain name resolution errors by doing 2 > things: > 1) editing /etc/resolv.conf changing it to a single line that set a > specific nameserver > 2) I ran this command `chattr +i /etc/resolv.conf` If you want to avoid getting /etc/resolv.conf modified, instead of adding the immutable attribute to the file (AKA changing the "state" of the file) you should configure the responsible service so it doesn't modify it in the first place. This is especially important in a declarative system like Guix, where the operating-system and its services should function no matter the *state* of the files in it. Almost every system-level setting can be configured with Guix's configuration system. And using it prevents broken configurations like these from making the system completely unbootable, as you would be able to boot to a previous generation from the boot menu. I'm assuming you're using a configuration based on the official example, so the service that modifies this file should be NetworkManager coming from %desktop-services. To disable its modification to /etc/resolv.conf you can set the `dns` field to "none" in its `network-manager-configuration`. You can modify it by using `modify-services` on %desktop-services. See these manual pages for the usage of modify-services and also documentation of network-manager-configuration: * https://guix.gnu.org/manual/en/html_node/Service-Reference.html * https://guix.gnu.org/manual/en/html_node/Networking-Services.html SeerLite