From: Danny Milosavljevic <dannym@scratchpost.org>
To: ludo@gnu.org
Cc: 30760@debbugs.gnu.org
Subject: bug#30760: guix system init broken on non GuixSD
Date: Fri, 9 Mar 2018 23:15:43 +0100 [thread overview]
Message-ID: <20180309231543.2ede5fa1@scratchpost.org> (raw)
In-Reply-To: <20180309173530.wfdw356rf53tesck@doom>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
Hi Ludo,
there's a problem with check-device-initrd-modules: on "guix system init"
it doesn't get linux-module-directory and doesn't pass it on to matching-modules.
matching-modules then eventually defaults to (current-alias-file) - which is not
found on a non-GuixSD system.
Would it be possible to get rid of the defaults in gnu/build/linux-modules.scm ?
I don't think those are safe or useful for our requirements. I've had to work
around those before.
check-initrd-modules could use the initrd's new kernel modules to find
out which modules to include (after all).
Then we could also check the dependencies directly in the new Linux kernel
modules and all in all it would be safer.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-09 22:16 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 [this message]
2018-03-09 22:42 ` Ludovic Courtès
2018-03-09 22:52 ` Danny Milosavljevic
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=20180309231543.2ede5fa1@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).