From: ng0 <ngillmann@runbox.com>
To: 宋文武 <iyzsong@member.fsf.org>, help-guix@gnu.org
Subject: Re: Some questions regarding GuixSD
Date: Sat, 01 Oct 2016 08:42:31 +0000 [thread overview]
Message-ID: <87r380xxxk.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87fuogenw1.fsf@member.fsf.org>
宋文武 <iyzsong@member.fsf.org> writes:
> dian_cecht@zoho.com writes:
>
>> On Sat, Oct 01, 2016 at 09:50:11AM +0800, 宋文武 wrote:
>>> dian_cecht@zoho.com writes:
>>>
>>> On GuixSD, you can rollback the whole system safely and easily (by
>>> choosing a grub menu item at boot).
>>
>> I don't guess you happen to be able to supply me with the options passed to do
>> this, would you?
>
> Ah, that's managed by guix on GuixSD, which produces a grub.cfg with menu
> containing all systems (current and previous if not deleted explicitly)
> it ever built. No option needed.
>
>> My systems aren't exactly standard installs, and I don't use
>> GRUB for anything at the moment (this may or may not change depending on where I
>> feel Guix fits into my systems, and whether I end up migrating everything over,
>> or if it's just one computer that has a GuixSD install on it).
>
> OK, muli-boot with GuixSD can be done with chainloader, etc. but it's a
> bit tricky. You probably want to try it in a VM (eg: guix system vm)
> first :-)
I think we should add this to the docs, this is a relatively regular
occuring question, the multi booting.
>
>
--
next prev parent reply other threads:[~2016-10-01 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-30 1:09 Some questions regarding GuixSD dian_cecht
2016-09-30 8:18 ` Ludovic Courtès
2016-09-30 12:07 ` ng0
2016-09-30 16:07 ` Ludovic Courtès
2016-09-30 16:47 ` ng0
2016-09-30 19:50 ` dian_cecht
2016-09-30 19:46 ` dian_cecht
2016-10-01 1:50 ` 宋文武
2016-10-01 2:19 ` dian_cecht
2016-10-01 3:42 ` 宋文武
2016-10-01 8:42 ` ng0 [this message]
2016-10-02 13:14 ` 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=87r380xxxk.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=help-guix@gnu.org \
--cc=iyzsong@member.fsf.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).