Installing pre 0.4.0 version

Installing Mntd (<0.4.0)

Packages below should have been installed and got working (see Installing required packages).

Configure

 ./configure --prefix=/usr --sysconfdir=/etc

Note:

If you encounter problems, activate debugging mode with --with-debug.

Compile

 make

Install

 make install

Start it

 mntd -d

Installing required packages

In order to begin using Mntd, you should have at least the following packages installed:

• kernel 2.6.x (Homepage)
• udev-025 (Download Homepage)
• dbus-0.21 (Download Homepage)
• hal-0.2 (Download Homepage)

First of all download all needed packages and mntd-0.3.5 (Downloads). Follow each packages instructions on installing.

Some hints will follow below. All installing have to be done as root user.

Installing Kernel 2.6

You should have successfully installed a kernel 2.6.x with hotplug and usb support. If your devices and drivers and not loaded and you cannot mount them manually, then Mntd will not work either.

You will at least want to activate these options:

 CONFIG_HOTPLUG=y
 CONFIG_USB=y
 CONFIG_USB_DEVICEFS=y
 CONFIG_USB_EHCI_HCD=y
 CONFIG_USB_OHCI_HCD=y
 CONFIG_USB_UHCI_HCD=y
 CONFIG_USB_STORAGE=y

Some more can be nessessary for your configuration, e.g some kind of digital camera support or some exotic usb storage drivers.

Note:

If you have problems loading und unloading the USB kernel modules, try to configure them as builtin ('y'), as I have done :-) The kernel seems to be buggy regarding loading/unloading usb kernel modules.

Installing dbus

D-BUS is a message bus system, a simple way for applications to talk to one another.

See http://www.freedesktop.org/Software/dbus for details. Install it and run the dbus-daemon-1 as system dbus.

Start it with

 dbus-daemon-1 --system

Check if it is running

 ps ax | grep dbus | grep -v grep

If you see something like this, it's good.

 7237 ?        S      0:00 /usr/bin/dbus-daemon-1 --system

Installing udev

Linux dynamic and persistent device naming support (aka userspace devfs).

udev works entirely in userspace, using /sbin/hotplug calls that the kernel makes whenever a device is added or removed from the kernel. All naming policy, and permission control is done in userspace.

See http://www.kernel.org/pub/linux/utils/kernel/hotplug/udev-FAQ for details.

Compile the source with dbus support

 make EXTRAS="extras/scsi_id extras/dbus" \
 prefix=/usr \
 etcdir=/etc \
 mandir=/usr/share/man \
 usrbindir=/usr/bin \
 usrsbindir=/usr/sbin \
 udevdir=/udev

Install it

 make EXTRAS="extras/scsi_id extras/dbus" \
 prefix=/usr \
 etcdir=/etc \
 mandir=/usr/share/man \
 usrbindir=/usr/bin \
 usrsbindir=/usr/sbin \
 udevdir=/udev \
 install

Note:

dbus support is needed, that it will send a message to dbus, when connecting or disconnecting a device. udev can be used as replacement for devfs. Since it is not as stable (some people said that), I installed it additionally to devfs. Therefore I use /udev/ as directory.

How does it work

udev will be called by /sbin/hotplug from kernel for each hotplug event. It will in turn do the stuff and call scripts in /etc/dev.d/*/*.dev. The udev_dbus.dev is one of them, that will call udev_dbus to send the corresponding dbus signal to listening programs (like hald).

Note:

Check that the generated symbolic link in /etc/dev.d/default/udev_dbus.dev will point to /usr/sbin/udev_dbus. Check all config files in /etc/udev/*.

Installing hal

Hardware Abstraction Layer for kernel 2.6 with support for dbus.

Configure

 ./configure --prefix=/usr --sysconfdir=/etc

Compile

 make

Install

 make install

Start it

 hald &

---