From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Marusich Subject: Re: Chrooting into GuixSD Date: Thu, 05 Jul 2018 01:55:58 -0700 Message-ID: <87muv62h9d.fsf@gmail.com> References: <8FCA4777-D0E1-4379-AF97-FD0785D26585@riseup.net> <5e600d9e-b123-17c0-302f-3f3cd6626e26@crazy-compilers.com> <20180613081346.jhkzdorwjp6albqx@abyayala> <20180614121856.n7os3fotwtpv675k@abyayala> <877en1bjub.fsf@elephly.net> <87d0wt4f26.fsf@gmail.com> <8736xpbeeg.fsf@elephly.net> <3c3b50f5-6d98-ca7a-9e50-021934b922e1@riseup.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39413) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fb03b-0005Ra-5E for guix-devel@gnu.org; Thu, 05 Jul 2018 04:56:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fb03Z-0007xP-R5 for guix-devel@gnu.org; Thu, 05 Jul 2018 04:56:07 -0400 Received: from mail-pf0-x22a.google.com ([2607:f8b0:400e:c00::22a]:41378) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fb03Z-0007v2-JQ for guix-devel@gnu.org; Thu, 05 Jul 2018 04:56:05 -0400 Received: by mail-pf0-x22a.google.com with SMTP id c21-v6so176782pfn.8 for ; Thu, 05 Jul 2018 01:56:05 -0700 (PDT) In-Reply-To: <3c3b50f5-6d98-ca7a-9e50-021934b922e1@riseup.net> (swedebugia's message of "Fri, 15 Jun 2018 12:21:26 +0200") 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: swedebugia Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable swedebugia writes: > On 2018-06-14 17:01, Ricardo Wurmus wrote: >> Oleg Pykhalov writes: >> >>>> Would any of you like to document this in the manual? >>> I would because I posted articles like the current one sometime ago. >> Excellent! >> >>> Maybe a separate =E2=80=98users-stories.texi=E2=80=99 should be as was = discussed >>> somewhere on a mailing list (as I remember)? >> I think that this particular section on tools that Guix provides to >> recover a broken system (and the peculiarities of chrooting into a >> GuixSD system) can go right into the manual. This does not preclude the >> option to have a more detailed step by step guide in a >> =E2=80=9Cuser-stories.texi=E2=80=9D. > +1 > > Does GuixSD by the way support dropping to a root shell by passing > "single" as a kernel parameter? I once used a distro that had a > feature like that. > > Ubuntu supports dropping to a root shell (and memtesting RAM?) among > more options if "recovery" is choosen in the grub menu. I like that > feature. If something like that had been possible on this old > GuixSD-installation I would not have had to resort to chrooting. If you pass the "--repl" option on the Linux kernel command line (e.g., from the GRUB menu), I believe you can do this. See "(guix) Initial RAM Disk" in the manual for details. =2D-=20 Chris --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEy/WXVcvn5+/vGD+x3UCaFdgiRp0FAls93R4ACgkQ3UCaFdgi Rp2MqA//YEXaDlv2tOM2lFYiGA8dz6C7ZYES/QiEhzg1e+E4Q/bK/Tb9MEn0AJO/ CcQaUB020eABD1vgloyT3bBO9pHUVdxgpcNLdgFgNYq9zl8b6MTpoOSGhuVS3Pvb Dbb1usHEUoXH5eG25CwDG1soaz6PYIZfM+Im2dCjWGNxlhd4afTStbQTJvDz6FpS WZCyGPd7zu3h+RNVUAAknj+B61noQ2tFF3le/In3+zA+JUAxaq/mqGTvG0N9YQwY ZFqoLNieSy3VxW9c2DWOLuxwL73Nsfb3Amp9vfzC0UwHxA4+8LhPRLBKhaLHc8ko q78tgWzmmIo9TWRqQ70VlWpYUsCqEm4gLq6L80VwN8MMtCrm7TbpPVuj7zwxt9FW xxy7LNmkP8vCpkIYoHNr8ppiibyIp+MQoLxjXe0VnB3qvEx5rZCzQ9nILP/OvMH0 zLLpN7WPW/rKigUcZdyoqQKGFFWp71M34EXuA4iuEy/eFFrmGZJQWmgV3/5kHGw/ IuyRsCM01AzIvpH1Rw/VXhoi8fAYDsgIPbEpz7tdQ5AyHFjtWN4Jfg2F3oHiKhB4 dVughrJF26liKf41A0sPMDvP53A3+xlRSg02mZREb/v803BnWhuaWfaLVRtsutBd 23oF3WhS8xPBnnMihElZM5D4sOI73EOfm/5PRHzCbnQn/S0OjAE= =IkEU -----END PGP SIGNATURE----- --=-=-=--