From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Chrooting into GuixSD Date: Thu, 14 Jun 2018 15:04:12 +0200 Message-ID: <877en1bjub.fsf@elephly.net> References: <8FCA4777-D0E1-4379-AF97-FD0785D26585@riseup.net> <5e600d9e-b123-17c0-302f-3f3cd6626e26@crazy-compilers.com> <20180613081346.jhkzdorwjp6albqx@abyayala> <20180614121856.n7os3fotwtpv675k@abyayala> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38124) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fTRvz-0006AI-6c for guix-devel@gnu.org; Thu, 14 Jun 2018 09:05:11 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fTRvt-0006Kj-65 for guix-devel@gnu.org; Thu, 14 Jun 2018 09:05:03 -0400 Received: from sender-of-o51.zoho.com ([135.84.80.216]:21053) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fTRvs-0006JQ-S1 for guix-devel@gnu.org; Thu, 14 Jun 2018 09:04:57 -0400 In-reply-to: <20180614121856.n7os3fotwtpv675k@abyayala> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Nils Gillmann Cc: guix-devel@gnu.org Nils Gillmann writes: > Thorsten Wilms transcribed 1.2K bytes: >> On 13.06.2018 10:13, Nils Gillmann wrote: >> > > > Is this ability to chroot into GuixSD worth mentioning in the manu= al? >> > > IMHO it is not worth to be mentioned in the manual, as it is the sam= e as >> > > for all Linux systems. >> > Not really, since you can not*fully* chroot a GuixSD. Some functions >> > will not work, like interacting with the daemon or what it was. Last >> > time I tried this was at least 1.5 years ago. >> >> You can interact with the daemon: >> >> cd /path/to/guix/root >> sudo mount --bind /dev dev >> sudo mount --bind /proc proc >> sudo mount --bind /sys sys >> sudo unshare -m sudo chroot . /run/current-system/profile/bin/bash >> source /etc/profile >> >> guix-daemon --build-users-group=3Dguixbuild & >> >> If you then `su` to a plain user, do `source /etc/profile` again. >> >> I think all of `guix pull`. `reconfigure` and `package` search, install = and >> update worked here with that approach. `guix download` failed due to nss >> certificates, until I added: >> export SSL_CERT_DIR=3D"$HOME/.guix-profile/etc/ssl/certs" >> export >> SSL_CERT_FILE=3D"$HOME/.guix-profile/etc/ssl/certs/ca-certificates.crt" >> export GIT_SSL_CAINFO=3D"$SSL_CERT_FILE" > > Huh. Okay, cool. Thanks for documeting this at least on the mailing list = :) Would any of you like to document this in the manual? I see that the manual does not mention the rescue REPL, bournish, or anything really about how to recover from failure. I think it would be good to have a sub-section in the manual under section =E2=80=9C6 GNU Distribution=E2=80=9D, after =E2=80=9CSystem Configuration=E2=80=9D maybe? The section could first mention recovery by booting into a previous generation of the system in GRUB, explain the use of the rescue REPL, and finally introduce how to recover the system with chroot by booting from the installer disk image. What do you think? -- Ricardo