unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: elaexuotee@wilsonb.com
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: What are you chroot battle stories?
Date: Mon, 02 Nov 2020 09:33:36 +0900	[thread overview]
Message-ID: <3S8KN2IQ5UQSZ.3AQ6CLZ85MY1Z@wilsonb.com> (raw)
In-Reply-To: <87v9epl40h.fsf@nckx>


[-- Attachment #1.1: Type: text/plain, Size: 799 bytes --]

Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> This is about chrooting a serviceable Guix-the-package-manager, 
> not running Guix System/Shepherd in the chroot, right?

Exactly. You've understood correctly.

> Did you manage to rescue your system in the end?

Yup!

> 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.

This is what I thought, too! That is part of the reason for this post. I was
thinking that there *must* be something I am missing. You are probably correct
that #guix was thinking I meant runnig Shepherd.

Anyway, thank's for taking the time to clear that up.

Cheers,

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

      reply	other threads:[~2020-11-02  0:34 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
2020-11-02  0:33   ` elaexuotee [this message]

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=3S8KN2IQ5UQSZ.3AQ6CLZ85MY1Z@wilsonb.com \
    --to=elaexuotee@wilsonb.com \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).