From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Alex Kost <alezost@gmail.com>
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 09:39:14 -0700 [thread overview]
Message-ID: <87vb4636bx.fsf@dustycloud.org> (raw)
In-Reply-To: <87wpomyjum.fsf@gmail.com>
Alex Kost writes:
> myglc2 (2016-03-27 20:18 +0300) wrote:
>
>> Christopher Allan Webber <cwebber@dustycloud.org> writes:
>>
>>> myglc2 writes:
>>>
>>>> Christopher Allan Webber <cwebber@dustycloud.org> writes:
>>>> [...]
>>>>>
>>>>> Running all machines, I dunno. I do dual-boot Debian and GuixSD with
>>>>> them sharing the same user profile and store.
>>>>
>>>> Dual boot. Now that is cool!
>>>
>>> Dual booting allowed me to switch to GuixSD a lot more feasibly than I
>>> could have otherwise. I installed it on this laptop right before a 3
>>> month trip. Dual booting meant that when something wasn't in GuixSD
>>> yet, no problem, I could switch to Debian for a bit. Then I could work
>>> on packages at my leisure to switch over.
>>>
>>> The trick was realizing that the grub that Guix generates wasn't the one
>>> I should boot into... I needed to have Guix and Debian generate their
>>> own grub files on their own partitions, and then have a /boot/ grub
>>> which was reeeeaally small and simply had menu options to import those
>>> other grub files.
>>
>> Neat!. Normally grub would be installed like this...
>>
>> (bootloader (grub-configuration (device "/dev/sda")))
>> (file-systems (cons (file-system
>> (device "/dev/sda1")
>> (title 'device)
>> (mount-point "/")
>> (type "ext4"))
>> %base-file-systems))
>>
>> But it sounds like you are installing a custom /boot/grub in
>> /dev/sda. So where is the GuixSD Grub and /?
>
> 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. 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.
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
}
next prev parent reply other threads:[~2016-03-28 16:39 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 [this message]
2016-03-28 19:56 ` Alex Kost
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vb4636bx.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=alezost@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.