Initialization of Module directory failed!

Chapter 6. Initialization of Module directory failed!

There's no mods.d directory!

This page describes what the mods.d directory is and how to solve this problem!

6.1. What is the mods.d directory?
6.2. How do I solve this problem?
6.3. Can I start BibleTime without this directory?
6.1.

What is the mods.d directory?

The mods.d directory is the directory which should contain the config files of the modules! You must have this directory, otherwise you can't use Bibletime and Sword! Please read the installation instructions on our homepage!

6.2.

How do I solve this problem?

The solution is to create a directory mods.d: Please go into your Sword directory and type "mkdir mods.d" to create the directory. Now copy the config files of your modules into this package and remove (if they exist) the file mods.conf which isn't required any more. The mods.d directory replaced this file.

If you find mods.d exists, then the global configuration does not exist. The preferred method of installing the global configuration if you installed Sword from the cvs or a tarball is to cd to the directory containing your sword source, and make install_config. The global configuration will be placed into /etc/sword.conf. If you have a nonstandard installation where /etc/sword.conf can not be set, then set SWORD_PATH to the location of your sword modules directory. For example in Linux-Mandrake™ adding the line export SWORD_PATH=/usr/share/sword to ~/.bash_profile or /etc/bashrc is the same as /etc/sword.conf containing the line /usr/share/sword

6.3.

Can I start BibleTime without this directory?

Yes, it's possible. But it's not very useful. There are no modules in the main index. It's possible to test BibleTime this way, but it's not possible to work with it without modules.

KDE Logo