From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Tomáš Čech" <sleep_walker@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 30760@debbugs.gnu.org
Subject: bug#30760: guix system init broken on non GuixSD
Date: Mon, 12 Mar 2018 13:24:37 +0100 [thread overview]
Message-ID: <20180312132437.2a4b2ca7@scratchpost.org> (raw)
In-Reply-To: <20180312091923.q47b3mrhzsl4vr75@doom>
[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]
> I'm afraid this is still not correct.
>
> # guix system init config.scm /mnt/mnt/
> ...
> config.scm:64:9: error: you may need these modules in the initrd for /dev/nvme0n1p2: shpchp
> hint: Try adding them to the `initrd-modules' field of your `operating-system' declaration, along these lines:
>
> (operating-system
> ;; ...
> (initrd-modules (append (list "shpchp")
> %base-initrd-modules)))
>
> I don't have `shpchp` as a module as I have it compiled into kernel
> directly. Can I somehow disable the check?
I think it's a good idea to add a command-line switch that disables the check.
But then people will just disable the check always and it won't improve until
it's correct. It's still a good idea to give people the choice.
@Ludo: It would also be great to have a command-line switch to check the slow,
correct, way. We'd also have to check modules.builtin of the new system's initrd
- but we'd do it only when the option is passed :)
I suggest to change it to:
> # guix system init config.scm /mnt/mnt/
> ...
> config.scm:64:9: WARNING: you may need these modules in the initrd for /dev/nvme0n1p2: shpchp
^^^ not error
> hint: Try adding them to the `initrd-modules' field of your `operating-system' declaration, along these lines:
>
> (operating-system
> ;; ...
> (initrd-modules (append (list "shpchp")
> %base-initrd-modules)))
>
> If you think this warning is mistaken, invoke guix again with the option
> --enable-paranoid-initrd-checks to be on the safe side, or with the option
> --skip-initrd-checks to continue regardless.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-03-12 12:30 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180312132437.2a4b2ca7@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=30760@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=sleep_walker@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.