From: Marius Bakke <mbakke@fastmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, guix-devel <guix-devel@gnu.org>
Cc: John Darrington <john@darrington.wattle.id.au>
Subject: Re: Planning for the next release
Date: Mon, 03 Apr 2017 00:13:01 +0200 [thread overview]
Message-ID: <87shlqv4pe.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87wpb7ym78.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> 3. UEFI support documented and possibly improved.
>
> We can certainly document the UEFI setup and add the /boot/efi
> partition in some of the ‘operating-system’ examples.
>
> The more difficult part is the installation: do we need to make a
> second, UEFI-specific, installation image? When I installed
> GuixSD on UEFI, I booted our installation image as “legacy”, but
> then GRUB would default to a legacy install, not a UEFI install:
>
> https://lists.gnu.org/archive/html/guix-devel/2016-12/msg00799.html
>
> I’m not sure exactly what needs to be done. Thoughts?
I plan to work on this over the next few days. The most common way is to
create a "hybrid" disk image that supports both UEFI and BIOS boot. IIRC
Debian achieves this by using Isolinux to create the EFI payload and
chainload to Grub. More information next week :-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-04-02 22:13 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 12:37 Planning for the next release Ludovic Courtès
2017-03-31 13:57 ` ng0
2017-03-31 16:25 ` Ludovic Courtès
2017-03-31 16:33 ` ng0
2017-03-31 23:07 ` Leo Famulari
2017-04-01 7:24 ` ng0
2017-04-04 10:39 ` Ricardo Wurmus
2017-05-20 8:40 ` Ludovic Courtès
2017-05-20 10:51 ` Ricardo Wurmus
2017-05-20 12:15 ` Ludovic Courtès
2017-05-20 21:45 ` Ricardo Wurmus
2017-05-20 22:29 ` Ludovic Courtès
2017-05-20 15:14 ` Ludovic Courtès
2017-05-20 19:40 ` Marius Bakke
2017-05-20 21:40 ` Marius Bakke
2017-05-20 22:32 ` Ludovic Courtès
2017-05-20 23:18 ` Ludovic Courtès
2017-05-20 21:42 ` Ricardo Wurmus
2017-04-02 22:13 ` Marius Bakke [this message]
2017-04-03 8:23 ` Ludovic Courtès
2017-04-17 20:41 ` UEFI support in boot image Marius Bakke
2017-04-19 20:26 ` Ludovic Courtès
2017-04-19 21:43 ` Marius Bakke
2017-05-05 20:54 ` Ludovic Courtès
2017-05-06 14:49 ` Marius Bakke
2017-05-07 14:42 ` Marius Bakke
2017-04-03 0:28 ` Planning for the next release Leo Famulari
2017-04-03 8:26 ` Ludovic Courtès
2017-04-03 17:52 ` Leo Famulari
2017-04-04 11:56 ` Ludovic Courtès
2017-04-21 22:27 ` Ludovic Courtès
2017-04-21 22:33 ` Leo Famulari
2017-04-27 12:40 ` Ricardo Wurmus
2017-05-11 9:00 ` Ludovic Courtès
2017-05-12 5:45 ` Ricardo Wurmus
2017-05-12 12:13 ` Hartmut Goebel
2017-05-12 15:25 ` Ludovic Courtès
2017-05-12 18:50 ` Ricardo Wurmus
[not found] ` <CAFtzXzMOGmQ6PKxarkmAKENR0EkWsfVoN7qdUjsnvZ6fgrAdTA@mail.gmail.com>
[not found] ` <CAFtzXzO7+7nO0XF0xDWktoApobNwVyHSg_1q6Z2hmeLc6czf4w@mail.gmail.com>
[not found] ` <CAFtzXzMBqiHBhusVx651nm1xH+XvacLKeuDDZ-iaMzx7FawyhA@mail.gmail.com>
2017-05-12 18:18 ` Fwd: " Manolis Ragkousis
2017-05-13 7:06 ` Ricardo Wurmus
2017-05-12 18:04 ` Leo Famulari
2017-05-12 21:04 ` ng0
2017-05-13 13:59 ` Ludovic Courtès
2017-05-13 14:20 ` Vincent Legoll
2017-05-14 19:14 ` Leo Famulari
2017-05-14 20:19 ` Leo Famulari
2017-05-15 1:52 ` Leo Famulari
2017-05-15 12:44 ` Ludovic Courtès
2017-05-16 14:41 ` sirgazil
2017-05-16 18:17 ` Leo Famulari
2017-05-16 18:19 ` Leo Famulari
2017-05-17 0:51 ` sirgazil
2017-05-17 3:02 ` Leo Famulari
2017-05-17 8:29 ` Ludovic Courtès
2017-05-16 17:12 ` Alex Kost
2017-05-16 23:03 ` Leo Famulari
2017-05-17 12:38 ` Ludovic Courtès
2017-05-17 18:20 ` Leo Famulari
2017-05-22 11:49 ` Building the web site Ludovic Courtès
2017-05-21 13:04 ` Planning for the next release Ricardo Wurmus
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=87shlqv4pe.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
--cc=ludo@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 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.