unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 30760@debbugs.gnu.org
Subject: bug#30760: guix system init broken on non GuixSD
Date: Fri, 9 Mar 2018 23:52:21 +0100	[thread overview]
Message-ID: <20180309235221.49e695d9@scratchpost.org> (raw)
In-Reply-To: <87efksyioy.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

[huge build]
> The current tradeoff is to make that diagnostic based on the running
> kernel, even if it’s an approximation.

Ah, good point.

> If that’s fine with you I’d like to fix this bug with the conservative
> patch below.

Sure, looks good.

While we are approximating we could also in a later version fall back to
(the host system's) "`cat /proc/sys/kernel/modprobe` --showconfig" - it
could be used to find aliases.

But maybe that would make it brittle.  Hmm...



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-03-09 22:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 17:35 bug#30760: guix system init broken on non GuixSD Tomáš Čech
2018-03-09 22:15 ` Danny Milosavljevic
2018-03-09 22:42   ` Ludovic Courtès
2018-03-09 22:52     ` Danny Milosavljevic [this message]
2018-03-09 23:19       ` Ludovic Courtès
2018-03-10 21:42         ` Tomáš Čech
2018-03-11 16:31         ` Danny Milosavljevic
     [not found]         ` <20180310063219.bxgl7bgspxu2o5ez@doom>
     [not found]           ` <874llmuwc5.fsf@gnu.org>
2018-03-12  9:19             ` Tomáš Čech
2018-03-12 12:24               ` Danny Milosavljevic
2018-03-12 12:38                 ` Danny Milosavljevic
2018-03-12 12:57                 ` Ludovic Courtès
2018-03-15 10:43                   ` Ludovic Courtès
2018-03-12 15:27                 ` Tomáš Čech

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=20180309235221.49e695d9@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=30760@debbugs.gnu.org \
    --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 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).