kmod/libkmod
Lucas De Marchi ddbda02286 Add implementation of modprobe's insertion
Treat module insertion as modprobe does: look for (soft-)dependencies, run
install commands, apply blacklist.

The difference with the blacklist is that it's applied to all modules,
including the dependencies. If you want to apply a blacklist only on the
module it's better to call the filter function by yourself.

This implementation detects loops caused by poorly written
soft-dependencies and fail gracefully, printing the loop to the log.
2011-12-27 11:55:22 -02:00
..
.gitignore Rename libabc to libkmod 2011-11-21 14:35:35 -02:00
COPYING Change licenses 2011-12-12 18:24:35 -02:00
libkmod-config.c Add functions to get ctx blacklists 2011-12-27 02:49:46 -02:00
libkmod-elf.c elf: implement kmod_module_get_dependency_symbols() 2011-12-24 01:44:31 -02:00
libkmod-file.c Support for loading Xz-compressed modules 2011-12-24 20:26:22 +01:00
libkmod-hash.c Change licenses 2011-12-12 18:24:35 -02:00
libkmod-index.c index_file_open: fix another fd leak on error path. 2011-12-26 09:55:15 -02:00
libkmod-index.h Change licenses 2011-12-12 18:24:35 -02:00
libkmod-list.c Fix kmod_list_remove_n_latest() 2011-12-27 02:48:36 -02:00
libkmod-module.c Add implementation of modprobe's insertion 2011-12-27 11:55:22 -02:00
libkmod-private.h Add functions to get ctx blacklists 2011-12-27 02:49:46 -02:00
libkmod-util.c Add helper alias_normalize() 2011-12-13 10:41:18 -02:00
libkmod.c Add functions to get ctx blacklists 2011-12-27 02:49:46 -02:00
libkmod.h Add implementation of modprobe's insertion 2011-12-27 11:55:22 -02:00
libkmod.pc.in libkmod: remove external cflags from .pc file 2011-12-24 20:28:11 +01:00
libkmod.sym Add implementation of modprobe's insertion 2011-12-27 11:55:22 -02:00
macro.h Change licenses 2011-12-12 18:24:35 -02:00
README Rename project from libkmod to kmod 2011-12-12 16:54:18 -02:00

libkmod - linux kernel module handling library

ABSTRACT
========

libkmod was created to allow programs to easily insert, remove and
list modules, also checking its properties, dependencies and aliases.

there is no shared/global context information and it can be used by
multiple sites on a single program, also being able to be used from
threads, although it's not thread safe (you must lock explicitly).


OVERVIEW
========

Every user should create and manage it's own library context with:

   struct kmod_ctx *ctx = kmod_new(kernel_dirname);
   kmod_unref(ctx);


Modules can be created with by various means:

   struct kmod_module *mod;
   int err;

   err = kmod_module_new_from_path(ctx, path, &mod);
   if (err < 0) {
      /* code */
   } else {
      /* code */
      kmod_module_unref(mod);
   }

   err = kmod_module_new_from_name(ctx, name, &mod);
   if (err < 0) {
      /* code */
   } else {
      /* code */
      kmod_module_unref(mod);
   }


Or could be resolved from a known alias to a list of alternatives:

   struct kmod_list *list, *itr;
   int err;
   err = kmod_module_new_from_lookup(ctx, alias, &list);
   if (err < 0) {
      /* code */
   } else {
      kmod_list_foreach(itr, list) {
         struct kmod_module *mod = kmod_module_get_module(itr);
         /* code */
      }
   }