GNU logs - #36054, boring messages

Message sent to bug-guix@HIDDEN:

Subject: bug#36054: [wishlist] Simplify chrooting into installed system from install image
Resent-From: "pelzflorian (Florian Pelz)" <pelzflorian@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Sun, 02 Jun 2019 12:43:01 +0000
Resent-Message-ID: <handler.36054.B.155947935424504 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 36054 <at> debbugs.gnu.org
Date: Sun, 2 Jun 2019 14:33:33 +0200
From: "pelzflorian (Florian Pelz)" <pelzflorian@HIDDEN>
Message-ID: <20190602123333.cjeqmrwz6be7uykd@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
User-Agent: NeoMutt/20180716
Content-Transfer-Encoding: quoted-printable
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

When bootloader installation fails or when the installed bootloader
does not allow selecting old generations (like the U-Boot bootloader),
chrooting may become necessary to repair a broken Guix system.

Guix should offer officially supported instructions in the manual and
perhaps more tooling for chrooting into an installed Guix System from
a Guix install USB/DVD/SD (and perhaps from a foreign distro) to
enable debugging.

Arch has <https://wiki.archlinux.org/index.php/Chroot#Usage>.  They
offer an official arch-chroot script to chroot into an Arch system (it
is shipped with their install image) as well as documentation for
chrooting without the script.  Their documentation for chrooting
without the arch-chroot script also works on Guix, but some more steps
are required:

* Mounting the (perhaps encrypted) drive with the broken Guix System.
  This is not part of Arch=E2=80=99 chroot instructions, but could perhap=
s be
  part of a more interactive guix-chroot script, since Guix=E2=80=99 targ=
et
  audience is different from Arch=E2=80=99s.  Note that the name given to
  cryptsetup must be the same as specified in /etc/config.scm if one
  wishes to reconfigure from the chroot.

* When following the
  <https://wiki.archlinux.org/index.php/Chroot#Using_chroot>
  instructions from the Arch wiki (without rebinding /run), I can
  chroot into /run/current-system/profile/bin/bash.  What if the user
  wants a different shell and not bash?  This perhaps could be
  selectable in an (interactive?) guix-chroot script.

* Afterwards a Guix daemon must be started in the chroot to use Guix
  from within such a chroot.

* The /run/current-system/profile/etc/profile,
  ~/.guix-profile/etc/profile and ~/.config/guix/current/etc/profile
  need to be sourced to use the installed system=E2=80=99s Guix profile.

* Networking automatically works for me in the chroot without needing
  to follow any Arch wiki instructions to get it working, but I do not
  know if that is always the case.

Note that for me reconfiguring did not work when chrooting from a
Debian live image into Guix because GRUB claimed to have no crypto
support.  I needed to chroot from the Guix install image for
reconfiguring.  Perhaps the environment visible to GRUB is not pure.

What do you think?  Is a guix-chroot script a good idea?  I do not
know how to write one.  Do you think only chroot instructions in the
manual are a better solution?  They should explain all the above steps
though, I believe.

Regards,
Florian

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: "pelzflorian (Florian Pelz)" <pelzflorian@HIDDEN>
Subject: bug#36054: Acknowledgement ([wishlist] Simplify chrooting into
 installed system from install image)
Message-ID: <handler.36054.B.155947935424504.ack <at> debbugs.gnu.org>
References: <20190602123333.cjeqmrwz6be7uykd@HIDDEN>
X-Gnu-PR-Message: ack 36054
X-Gnu-PR-Package: guix
Reply-To: 36054 <at> debbugs.gnu.org
Date: Sun, 02 Jun 2019 12:43:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guix@HIDDEN

If you wish to submit further information on this problem, please
send it to 36054 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
36054: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D36054
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Last modified: Mon, 25 Nov 2019 12:00:02 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.