From: Alex Kost <alezost@gmail.com>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: myglc2 <myglc2@gmail.com>, help-guix@gnu.org
Subject: Re: Guix/GNU/Linux multi distro + GuixSD multi-site scenario
Date: Mon, 28 Mar 2016 22:56:04 +0300 [thread overview]
Message-ID: <87twjq8jhn.fsf@gmail.com> (raw)
In-Reply-To: <87vb4636bx.fsf@dustycloud.org> (Christopher Allan Webber's message of "Mon, 28 Mar 2016 09:39:14 -0700")
Christopher Allan Webber (2016-03-28 19:39 +0300) wrote:
> Alex Kost writes:
[...]
>> Hi, I also use double boot (GuixSD and ArchLinux). I do it like this:
>> at first I never let GuixSD to reinstall grub by using --no-grub option
>> ("guix system reconfigure --no-grub ..."). Instead I installed grub
>> manually (into a separate "boot" partition) and I use my own "grub.cfg",
>> which has an entry for the latest GuixSD system. This entry may look
>> like this:
>>
>> menuentry 'GuixSD' {
>> search --no-floppy --label --set guix
>> linux /var/guix/profiles/system/kernel/bzImage --root=guix --system=/var/guix/profiles/system --load=/var/guix/profiles/system/boot
>> initrd /var/guix/profiles/system/initrd
>> }
>>
>> My grub config¹ also has entries for a previous system generation (I can
>> boot any generation by editing a number in a grub boot menu) and for a
>> particular system (sometimes I do "guix system build …" and put the
>> result directory of this "testing" system to my grub.cfg).
>>
>> ¹ https://github.com/alezost/config/blob/master/etc/grub.cfg
>
> Hm, I think this approach is not quite as nice, IMO.
Yeah, I think it is not suitable for most people, but it is very nice
for me :-)
> One downside here
> is that by not using the grub that guix generates for you, you can't
> simply boot into a prior system revision if something goes long, which
> is a huge advantage in GuixSD.
As I wrote I can boot into any prior system simply by editing a generation
number in the grub menu.
> Here's what I do on my grub.cfg (or libreboot_grub.cfg technically):
>
> set timeout=5
> insmod ahci
> insmod chain
>
> menuentry "Guix" {
> set root=(ahci0,msdos7)
> configfile /boot/grub/grub.cfg
> unset superusers # probably not needed
> }
>
> menuentry "Debian" {
> set root=(ahci0,msdos6)
> configfile /boot/grub/grub.cfg
> unset superusers # probably not needed
> }
Thanks for sharing! I didn't think about using "configfile" before.
--
Alex
next prev parent reply other threads:[~2016-03-28 19:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 16:32 Guix/GNU/Linux multi distro + GuixSD multi-site scenario myglc2
2016-03-26 23:31 ` Christopher Allan Webber
2016-03-27 0:53 ` myglc2
2016-03-27 1:48 ` Christopher Allan Webber
2016-03-27 17:18 ` myglc2
2016-03-28 10:31 ` Alex Kost
2016-03-28 14:09 ` myglc2
2016-03-28 14:32 ` Chris Marusich
2016-03-28 20:05 ` Alex Kost
2016-03-28 16:39 ` Christopher Allan Webber
2016-03-28 19:56 ` Alex Kost [this message]
2016-03-29 16:03 ` 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=87twjq8jhn.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=myglc2@gmail.com \
/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).