From: Andreas Enge <andreas@enge.fr>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Kernel modules in initrd
Date: Sat, 24 Feb 2018 00:02:39 +0100 [thread overview]
Message-ID: <20180223230239.GA6140@jurong> (raw)
In-Reply-To: <20180223152855.6a08f8bd@scratchpost.org>
Hello,
On Fri, Feb 23, 2018 at 03:28:55PM +0100, Danny Milosavljevic wrote:
> No, wait, according to https://unix.stackexchange.com/questions/43699/debian-does-not-detect-serial-pci-card-after-reboot/43723#43723 ,
> the kernel should be doing that even without udev. Are we sure we need to manually modprobe the stuff in gnu/build/linux-boot.scm in
> the first place? I think we should just add kmod to the initrd - that's it.
in that case, if I understand correctly, the security question would not
be a problem any more, right, as only really needed modules would be loaded
by the kernel? Then we could add more modules to the initrd.
Andreas
next prev parent reply other threads:[~2018-02-23 23:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 21:17 Kernel modules in initrd Andreas Enge
2018-02-22 21:29 ` Jan Nieuwenhuizen
2018-02-22 21:44 ` Danny Milosavljevic
2018-02-22 21:34 ` Danny Milosavljevic
2018-02-22 21:50 ` [PATCH] linux-initrd: Add ATA and SAS modules to the default set of modules Danny Milosavljevic
2018-02-27 15:03 ` Ludovic Courtès
2018-02-22 21:53 ` Kernel modules in initrd Andreas Enge
2018-02-22 22:01 ` Mark H Weaver
2018-02-23 1:00 ` Danny Milosavljevic
2018-02-23 14:28 ` Danny Milosavljevic
2018-02-23 23:02 ` Andreas Enge [this message]
2018-02-25 11:43 ` Danny Milosavljevic
2018-02-26 15:20 ` Ludovic Courtès
2018-02-26 16:26 ` Danny Milosavljevic
2018-02-27 15:02 ` Ludovic Courtès
2018-02-27 19:32 ` Danny Milosavljevic
2018-02-27 20:52 ` Danny Milosavljevic
2018-02-28 21:49 ` Ludovic Courtès
2018-02-23 22:39 ` Ludovic Courtès
2018-02-24 8:28 ` ng0
2018-02-27 15:04 ` 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=20180223230239.GA6140@jurong \
--to=andreas@enge.fr \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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).