[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#30604] bug#34902: guix cannot find a module on boot

From: Ludovic Courtès
Subject: [bug#30604] bug#34902: guix cannot find a module on boot
Date: Fri, 16 Aug 2019 23:10:15 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (gnu/linux)


Danny Milosavljevic <address@hidden> skribis:

> Maybe I'm too paranoid but can we have "guix" in the file name ""
> somewhere?  Otherwise I see it coming that upstream uses for an
> incompatible purpose and then we'd be with a guix interface that's broken
> and/or break their interface.
> (So much complexity for something so silly.  Honestly, I feel like E-mailing
> the upstream author and telling him what I think.  WTF :P)
> Should we warn when we use the fallback?  I like the defensive programming
> but I feel we shouldn't have it *silently* fall back when the database is
> broken/missing.
> Otherwise LGTM!

So I went ahead and pushed these patches, derived from our beautiful
patch set at <>:

  c85ccf60bf linux-modules: Define and use a module name database.
  e1a9a7f275 linux-modules: Add 'load-linux-modules-from-directory'.
  2a693b69ca linux-modules: Add "modules.devname" writer.
  4f8b9d1a6f linux-modules: Add "modules.alias" writer.

The actual fix for the hyphen/underscore mismatch that Julien reported
is commit c85ccf60bf.  The “modules.devname” and “modules.alias” are
actually unused so far but (1) it was easier to preserve them, and (2)
that’ll give us an incentive to finish
<>.  :-)

I added an explicit comment that “” uses a Guix-specific
format.  We can always rename it if the kernel folks decide to acquire
that file name.

Julien, could you please confirm that your initial issue is fixed?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]