From: Oleg Pykhalov <go.wigust@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Nils Gillmann <ng0@n0.is>
Subject: Re: Chrooting into GuixSD
Date: Thu, 14 Jun 2018 17:29:21 +0300 [thread overview]
Message-ID: <87d0wt4f26.fsf@gmail.com> (raw)
In-Reply-To: <877en1bjub.fsf@elephly.net> (Ricardo Wurmus's message of "Thu, 14 Jun 2018 15:04:12 +0200")
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
Hello,
Ricardo Wurmus <rekado@elephly.net> writes:
> Nils Gillmann <ng0@n0.is> writes:
>
>> Thorsten Wilms transcribed 1.2K bytes:
>>> On 13.06.2018 10:13, Nils Gillmann wrote:
[…]
>>> 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=guixbuild &
>>>
>>> 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="$HOME/.guix-profile/etc/ssl/certs"
>>> export
>>> SSL_CERT_FILE="$HOME/.guix-profile/etc/ssl/certs/ca-certificates.crt"
>>> export GIT_SSL_CAINFO="$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 would because I posted articles like the current one sometime ago.
Maybe a separate ‘users-stories.texi’ should be as was discussed
somewhere on a mailing list (as I remember)?
https://lists.nongnu.org/archive/cgi-bin/namazu.cgi?query=Reinstall+GuixSD+from+another+distribution+with+chroot+%28Recover+Grub%29&submit=Search&idxname=help-guix
https://lists.gnu.org/archive/html/help-guix/2017-10/msg00035.html
[…]
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-06-14 14:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 4:04 Chrooting into GuixSD swedebugia
2018-06-13 7:13 ` Hartmut Goebel
2018-06-13 8:13 ` Nils Gillmann
2018-06-13 10:09 ` Thorsten Wilms
2018-06-14 12:18 ` Nils Gillmann
2018-06-14 13:04 ` Ricardo Wurmus
2018-06-14 14:29 ` Oleg Pykhalov [this message]
2018-06-14 15:01 ` Ricardo Wurmus
2018-06-15 10:21 ` swedebugia
2018-07-05 8:55 ` Chris Marusich
2018-06-15 15:01 ` Ludovic Courtès
2018-06-15 18:20 ` Thorsten Wilms
2018-06-16 15:43 ` Ludovic Courtès
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=87d0wt4f26.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).