all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Tomáš Čech" <sleep_walker@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 30760@debbugs.gnu.org
Subject: bug#30760: guix system init broken on non GuixSD
Date: Mon, 12 Mar 2018 16:27:32 +0100	[thread overview]
Message-ID: <20180312152732.a7km7vad4gack5ww@doom> (raw)
In-Reply-To: <20180312132437.2a4b2ca7@scratchpost.org>

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

On Mon, Mar 12, 2018 at 01:24:37PM +0100, Danny Milosavljevic wrote:
>> 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.

Just small note - In my case I always run `system build` before
`system init` so I don't mind having any deeper analysis based on code
and configuration as long as it is correct. Maybe more people is using
same approach.

Best regards,

S_W

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2018-03-12 15:28 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
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 [this message]

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=20180312152732.a7km7vad4gack5ww@doom \
    --to=sleep_walker@gnu.org \
    --cc=30760@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 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.