unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Mathieu Othacehe <m.othacehe@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27007@debbugs.gnu.org
Subject: bug#27007: [PATCH 1/2] bootloader: Use menu-entry to define custom bootloader entries.
Date: Fri, 02 Jun 2017 11:29:38 +0200	[thread overview]
Message-ID: <86inkeka9p.fsf@gmail.com> (raw)
In-Reply-To: <20170601131454.634a9d42@scratchpost.org>


Hi !

> People apparently start other Linux distributions with it :)

Yes because they use initrd only to mount root partition, then kernel is
starting /sbin/init provided by systemd or other init mechanism.

For people who's custom kernel is able to access root partition without
loading any module, maybe we could provide a kernel argument init=<path
of the boot script launching shepherd>.

Before GuixSD I didn't use an initrd to boot fastly. On GuixSD, because
shepherd start is quite slow (unparallelized ?) compared to systemd, the
few ms spent in initrd execution seems unsignificant.

But maybe there are other advantages not to run an initrd.

> How's the error reporting?  If a user still has boot-parameters in his bootloader configuration menu-entries, will "guix system reconfigure" fail *before* he reboots?  If so, does the error message hint on how to fix it?

Yes it will fail, some users have sadly already experimented this error.

> LGTM as is.  The user interface is now the same as it had been before (in 0.13.0) - so it's an improvement.
>
> I just checked:  The 0.13.0 release is safe.  Phiew.

Ok, let's wait for Ludo's approval then :)

Thanks for reviewing Danny,

Mathieu

  reply	other threads:[~2017-06-02  9:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-20 20:00 bug#27007: boot-parameters are not documented Tomáš Čech
2017-05-20 20:31 ` Mathieu Othacehe
2017-05-20 21:07   ` Leo Famulari
2017-05-20 21:43   ` Tomáš Čech
2017-05-20 20:52 ` Danny Milosavljevic
2017-05-20 21:00   ` Tomáš Čech
2017-05-22 15:55     ` Ludovic Courtès
2017-05-22 17:31       ` Mathieu Othacehe
2017-05-23  8:13         ` Ludovic Courtès
2017-05-23  9:31           ` Mathieu Othacehe
2017-05-23  9:57             ` Tomáš Čech
2017-05-23 11:23             ` Ludovic Courtès
2017-05-23 11:40               ` Mathieu Othacehe
2017-05-23 12:24                 ` Ludovic Courtès
2017-05-31  7:23                   ` bug#27007: [PATCH 0/2] Use menu-entry to define custom bootloader entries Mathieu Othacehe
2017-05-31  7:23                     ` bug#27007: [PATCH 1/2] bootloader: " Mathieu Othacehe
2017-05-31 22:11                       ` Danny Milosavljevic
2017-06-01  8:34                         ` Mathieu Othacehe
2017-06-01 11:14                           ` Danny Milosavljevic
2017-06-02  9:29                             ` Mathieu Othacehe [this message]
2017-06-02 14:30                               ` Marius Bakke
2017-06-01 11:22                           ` Ludovic Courtès
2017-06-05 10:23                       ` Ludovic Courtès
2017-06-06  8:14                         ` Mathieu Othacehe
2017-05-31  7:23                     ` bug#27007: [PATCH 2/2] doc: Adapt to multiple bootloader support Mathieu Othacehe
2017-05-31 21:57                       ` Danny Milosavljevic
2017-06-05 10:38                         ` Ludovic Courtès
2017-06-05 10:36                       ` Ludovic Courtès
2017-06-05 14:11                         ` Danny Milosavljevic
2017-06-06 22:51                           ` Ludovic Courtès
2017-06-08 10:59                             ` Mathieu Othacehe
2017-06-06  9:20                         ` Mathieu Othacehe
2017-05-24 20:11           ` bug#27007: boot-parameters are not documented Danny Milosavljevic
2017-05-26  8:47             ` Ludovic Courtès
2017-05-26  9:03               ` ng0
2017-06-08 10:57 ` bug#27007: [PATCH v2 1/2] bootloader: Use menu-entry to define custom bootloader entries Mathieu Othacehe
2017-06-08 10:57   ` bug#27007: [PATCH v2 2/2] doc: Adapt to multiple bootloader support Mathieu Othacehe
2017-06-08 12:39     ` Ludovic Courtès
2017-06-08 14:33       ` Mathieu Othacehe
2017-06-08 12:36   ` bug#27007: [PATCH v2 1/2] bootloader: Use menu-entry to define custom bootloader entries 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=86inkeka9p.fsf@gmail.com \
    --to=m.othacehe@gmail.com \
    --cc=27007@debbugs.gnu.org \
    --cc=dannym@scratchpost.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).