unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Bengt Richter <bokr@bokr.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Testing the installer
Date: Fri, 24 Jan 2020 08:48:20 +0100	[thread overview]
Message-ID: <CAE4v=pjzTpAMPW_Abe9=FWMQ08T5ntP_bAXSViws-sRu4fN6_Q@mail.gmail.com> (raw)
In-Reply-To: <20200123230746.GA3116@LionPure>

Hello,

Bengt Richter <bokr@bokr.com> ezt írta (időpont: 2020. jan. 24., P, 0:08):
>
> Hello Gábor,
>
> On +2020-01-23 12:21:27 +0100, Gábor Boskovits wrote:
> [...]
>
> > This is a bit off topic, but I am about to create an automatic
> > installer, that is
> > a candidate for a new backend. It currently works by providing a configuration
> > record, and then executes a few things from the installer.
> >
> > (It does a lookup for a candidate installation target disk, autopartitions it,
> > then injects the bootloader and file-system fields into an operating-system
> > template, and finally does a system installation.)
> >
>
> Will your installer be able to create /boot and / images that will
> work with Coreboot/SeaBios/grub legacy-only (not UEFI) bootable systems
> (like PureOS)?

It is based on the current installation image, and it accepts a Guix
System configuration
template, so it works on systems that Guix System can currently operate on.
Right now the bootloader configuration is limited to that what the
autopartitoning in the
installer does for the option 'All in one partiton', which means that
UEFI or legacy is
autodetected, and installed accordingly. Does that answer you question?

>
> IOW, what kind of BIOS systems is it dependent on?
>
> > I will have a look at the new protocol soon, to see if this project
> > can benefit from that.
> [...]
>
> >
> > Best regards,
> > g_bor
> > --
> > OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
> >
>
> --
> Regards,
> Bengt Richter


Best regards,
g_bor
-- 
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21

  reply	other threads:[~2020-01-24  7:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-12 22:13 Testing the installer Ludovic Courtès
2020-01-12 23:34 ` sirgazil
2020-01-20 17:49   ` sirgazil
2020-01-14  8:02 ` Mathieu Othacehe
2020-01-22 22:27   ` Ludovic Courtès
2020-01-23  9:41     ` Mathieu Othacehe
2020-01-23 11:21       ` Gábor Boskovits
2020-01-23 23:07         ` Bengt Richter
2020-01-24  7:48           ` Gábor Boskovits [this message]
2020-01-24  9:23         ` Ludovic Courtès
2020-01-23 14:54       ` Ludovic Courtès
2020-01-20 11:47 ` Jonathan Brielmaier
  -- strict thread matches above, loose matches on Subject: below --
2018-06-13  3:57 swedebugia
2018-06-13 19:47 ` 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

  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='CAE4v=pjzTpAMPW_Abe9=FWMQ08T5ntP_bAXSViws-sRu4fN6_Q@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=bokr@bokr.com \
    --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).