kmod-setup: mounting efivarfs, *after* we tried to mount it, is pointless

The mount() system call, which we issue before loading modules, will trigger
a modprobe by the kernel and block until it returns. Trying to load it again
later, will have exactly the same result as the first time.

diff --git a/src/core/kmod-setup.c b/src/core/kmod-setup.c
index 383a6b22be72f4ca6c793d3b63b78473884f3efc..20ab23237477114aac391095df2b91ceb1686ad5 100644 (file)
--- a/src/core/kmod-setup.c
+++ b/src/core/kmod-setup.c
@@ -39,7 +39,6 @@ typedef struct Kmodule {
 static const KModule kmod_table[] = {
         { "autofs4",  "/sys/class/misc/autofs",    NULL } ,
         { "ipv6",     "/sys/module/ipv6",          NULL },
 static const KModule kmod_table[] = {
         { "autofs4",  "/sys/class/misc/autofs",    NULL } ,
         { "ipv6",     "/sys/module/ipv6",          NULL },

-        { "efivarfs", "/sys/firmware/efi/efivars", NULL },

         { "unix",     "/proc/net/unix",            NULL } ,
 };
 
         { "unix",     "/proc/net/unix",            NULL } ,
 };