unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
* What are you chroot battle stories?
@ 2020-11-01  2:20 elaexuotee
  2020-11-01 11:18 ` Tobias Geerinckx-Rice
  0 siblings, 1 reply; 3+ messages in thread
From: elaexuotee @ 2020-11-01  2:20 UTC (permalink / raw)
  To: help-guix


[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: What are you chroot battle stories?
  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
  0 siblings, 1 reply; 3+ messages in thread
From: Tobias Geerinckx-Rice @ 2020-11-01 11:18 UTC (permalink / raw)
  To: elaexuotee; +Cc: help-guix

[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: What are you chroot battle stories?
  2020-11-01 11:18 ` Tobias Geerinckx-Rice
@ 2020-11-02  0:33   ` elaexuotee
  0 siblings, 0 replies; 3+ messages in thread
From: elaexuotee @ 2020-11-02  0:33 UTC (permalink / raw)
  To: Tobias Geerinckx-Rice; +Cc: help-guix


[-- 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 --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2020-11-02  0:34 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).