From: ludo@gnu.org (Ludovic Courtès)
To: Amirouche Boubekki <amirouche.boubekki@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Automatically detect other OSs and generate grub entries
Date: Tue, 18 Jul 2017 12:00:19 +0200 [thread overview]
Message-ID: <874lua2hfw.fsf@gnu.org> (raw)
In-Reply-To: <CAL7_Mo9gHRZdWTF9OyPqURx3bO5LSf2_8xGj7zYatJuJNK5zMw@mail.gmail.com> (Amirouche Boubekki's message of "Mon, 17 Jul 2017 17:38:46 +0000")
Amirouche Boubekki <amirouche.boubekki@gmail.com> skribis:
> On Mon, Jul 17, 2017 at 3:39 PM Ludovic Courtès <ludo@gnu.org> wrote:
>
>> Arun Isaac <arunisaac@systemreboot.net> skribis:
>>
>> > Instead of having to manually specify custom grub entries in config.scm,
>> > can Guix use os-prober to automatically detect other operating system
>> > and generate grub entries?
>> >
>> > https://joeyh.name/code/os-prober/
>>
>> I think there is value in having everything in the GuixSD config, which
>> can then be put under version control.
>>
>> Now, I have a single OS on my machines so I’m probably not part of the
>> target audience. :-)
>>
>> Thoughts?
>>
>
> My understanding is that os-probe could generate part of GuixSD config.
Ah yes, that’d be easy and useful. The first step would be to make a
package for it.
Ludo’.
next prev parent reply other threads:[~2017-07-18 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 20:42 Automatically detect other OSs and generate grub entries Arun Isaac
2017-07-17 13:36 ` Ludovic Courtès
2017-07-17 17:38 ` Amirouche Boubekki
2017-07-18 10:00 ` Ludovic Courtès [this message]
2017-08-29 19:23 ` Arun Isaac
[not found] ` <5d344b4e.ADkAAC1SuZUAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZpb8_@mailjet.com>
2017-08-30 10:18 ` Ludovic Courtès
2017-08-30 11:56 ` Arun Isaac
2017-07-17 19:59 ` Arun Isaac
[not found] ` <b2c51b44.AEEANfr63OgAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZbRc4@mailjet.com>
2017-07-18 10: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=874lua2hfw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=amirouche.boubekki@gmail.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 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.