From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org
Subject: Re: Chrooting into GuixSD
Date: Fri, 15 Jun 2018 12:21:26 +0200 [thread overview]
Message-ID: <3c3b50f5-6d98-ca7a-9e50-021934b922e1@riseup.net> (raw)
In-Reply-To: <8736xpbeeg.fsf@elephly.net>
On 2018-06-14 17:01, Ricardo Wurmus wrote:
> Oleg Pykhalov <go.wigust@gmail.com> writes:
>
>>> Would any of you like to document this in the manual?
>> I would because I posted articles like the current one sometime ago.
> Excellent!
>
>> Maybe a separate ‘users-stories.texi’ should be as was discussed
>> somewhere on a mailing list (as I remember)?
> I think that this particular section on tools that Guix provides to
> recover a broken system (and the peculiarities of chrooting into a
> GuixSD system) can go right into the manual. This does not preclude the
> option to have a more detailed step by step guide in a
> “user-stories.texi”.
+1
Does GuixSD by the way support dropping to a root shell by passing
"single" as a kernel parameter? I once used a distro that had a feature
like that.
Ubuntu supports dropping to a root shell (and memtesting RAM?) among
more options if "recovery" is choosen in the grub menu. I like that
feature. If something like that had been possible on this old
GuixSD-installation I would not have had to resort to chrooting.
--
---
Swedebugia
next prev parent reply other threads:[~2018-06-15 10:19 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
2018-06-14 15:01 ` Ricardo Wurmus
2018-06-15 10:21 ` swedebugia [this message]
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=3c3b50f5-6d98-ca7a-9e50-021934b922e1@riseup.net \
--to=swedebugia@riseup.net \
--cc=guix-devel@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.
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).