summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKay Sievers <kay@vrfy.org>2012-11-04 16:55:23 +0100
committerKay Sievers <kay@vrfy.org>2012-11-04 17:00:57 +0100
commit3dfb265083347cb5700dc38f7cc0f479f378e6e9 (patch)
tree98462b8c58c945687ab551e04e0effbc4d9192e0
parent1022373284b7562431fb0a6dba45db8af089a0e3 (diff)
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.
-rw-r--r--src/core/kmod-setup.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/core/kmod-setup.c b/src/core/kmod-setup.c
index 383a6b22be..20ab232374 100644
--- 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 },
- { "efivarfs", "/sys/firmware/efi/efivars", NULL },
{ "unix", "/proc/net/unix", NULL } ,
};