From: Tobias Geerinckx-Rice <me@tobias.gr>
To: elaexuotee@wilsonb.com
Cc: help-guix@gnu.org
Subject: Re: What are you chroot battle stories?
Date: Sun, 01 Nov 2020 12:18:06 +0100 [thread overview]
Message-ID: <87v9epl40h.fsf@nckx> (raw)
In-Reply-To: <34AYU3HLES6UB.2ERLLEWJD0BO7@wilsonb.com>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Brandon,
This is about chrooting a serviceable Guix-the-package-manager,
not running Guix System/Shepherd in the chroot, right?
Did you manage to rescue your system in the end?
elaexuotee@wilsonb.com 写道：
> Chatting on #guix, I heard that running Guix in a chroot was an
> "open problem."
> Somehow, I seem to have stumbled into the right setup and
> managed to get it
> working without any issues.
I find that claim surprising too. Running/rescuing Guix in a
chroot has never been anything less than routine IME (...I guess
that's a success story? :-) The steps[0] you use to chroot Guix
apply to most any other distribution.
Kind regards,
T G-R
[0]: http://ix.io/2CAm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-11-01 11:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 2:20 What are you chroot battle stories? elaexuotee
2020-11-01 11:18 ` Tobias Geerinckx-Rice [this message]
2020-11-02 0:33 ` elaexuotee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9epl40h.fsf@nckx \
--to=me@tobias.gr \
--cc=elaexuotee@wilsonb.com \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).