From: elaexuotee@wilsonb.com
To: help-guix@gnu.org
Subject: What are you chroot battle stories?
Date: Sun, 01 Nov 2020 11:20:39 +0900 [thread overview]
Message-ID: <34AYU3HLES6UB.2ERLLEWJD0BO7@wilsonb.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 605 bytes --]
Hey Guix,
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.
The channel asked me to write a blog post detailing what I did, so I'd like to
do it justice and first collect your battle stories. Have you tried and failed
to run guix in a chroot? How did you set up the chroot? What exactly failed?
Of course, if you have *success* stories, I'd like to hear those as well!
Your input will help me flesh out my ideas into a full technical article.
Cheers!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next reply other threads:[~2020-11-01 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 2:20 elaexuotee [this message]
2020-11-01 11:18 ` What are you chroot battle stories? Tobias Geerinckx-Rice
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=34AYU3HLES6UB.2ERLLEWJD0BO7@wilsonb.com \
--to=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).