Re: [WIP PATCH] linux-initrd: Allow own set of kernel modules.

[Tomáš Čech]

On Thu, Jul 28, 2016 at 03:05:34PM +0200, Ludovic Courtès wrote:
> Tomáš Čech <address@hidden> skribis:
>
> > * gnu/system/linux-initrd.scm(base-initrd): Add `linux-modules'
> >   parameter. Rename former `linux-modules' to
> >   `default-linux-modules'. Introduce used-linux-modules to make the code
> >   more readable.
> > ---
> >  gnu/system/linux-initrd.scm | 12 +++++++++---
> >  1 file changed, 9 insertions(+), 3 deletions(-)
> >
> > diff --git a/gnu/system/linux-initrd.scm b/gnu/system/linux-initrd.scm
> > index bbaa5c0..4934c92 100644
> > --- a/gnu/system/linux-initrd.scm
> > +++ b/gnu/system/linux-initrd.scm
> > @@ -138,6 +138,7 @@ MODULES and taken from LINUX."
> >                        qemu-networking?
> >                        (virtio? #t)
> >                        volatile-root?
> > +                      (linux-modules #f)
> >                        (extra-modules '()))
> >    "Return a monadic derivation that builds a generic initrd, with kernel
> >  modules taken from LINUX.  FILE-SYSTEMS is a list of file-systems to be
>
> It seems to serve the same purpose as #:extra-modules, no?
>
>  https://www.gnu.org/software/guix/manual/html_node/Initial-RAM-Disk.html

It gives me full control over the modules and not just appending to default set.

 #f --> default-kernel-modules (as it is now)
 '(some extraordinary special modules for other purpose) --> it will use this 
set
 '() --> it will use no module at all (my typical usecase)


But yes, it makes `extra-modules' useless.

I'd like to find a way, how to make default-kernel-modules available
as some lazy evaluated list (because what will go there is decided
when base-initrd is evaluated).

This is one of the steps for user defined kernel (besides specifying
kernel configuration) and I'm using it already.

If you're not against such change, it also would need to adjust
documentation (will do in next round).


S_W

signature.asc
Description: Digital signature