Endeavour recognizes your system's filesystem configuration file
(typically /etc/fstab
), this is a formal listing of all
devices configured on your system that are capable of posessing a
filesystem.
In addition, Endeavour also keeps a separate configuration of
each device within its own configuration
file located in $HOME/.endeavour2/devices.ini
.
First make sure that the device(s) you intend to have Endeavour reference are set up properly on your system. Once you have verified that the device(s) is/are functioning properly, go to Settings->Devices...
You can modify an existing device reference by selecting the device entry and then click on Edit... or you can add a new device reference by selecting a device entry you want to insert at and then click on Add...
You should then see the dialog as shown below:
/etc/fstab
).
Icons for this device can be set by clicking on the corresponding icon
frame on the right column and selecting an .xpm
file. Each
icon has a Standard, Selected, and Unmounted state. In most cases you only
need to set the Standard icon. Endeavour comes with a set of commonly used
icons located in /usr/share/endeavour2/icons/
The specified mount and unmount commands will be used to mount or unmount the device in question. Depending on the type of system you are using, the mount and unmount commands may vary.
If (and only if) you want Endeavour to be able to mount or
unmount a particular device when runned by any non-root user, you must set
up that device on your system to allow any user to mount or unmount it.
To allow any user to mount or unmount a device on a Linux system, first
edit /etc/fstab
and specify the user
argument
in the options list. For example, to make the first floppy drive
(/dev/fd0
) mountable by any user, specify in
/etc/fstab
:
/dev/fd0 /mnt/fd0 msdos user,noauto 0 0
The above line would allow any user to mount or unmount the
device /dev/fd0
on the mount point
directory /mnt/fd0
.
Some devices may require that a driver/module be loaded before
the device is mounted, this can present a problem for non-root
users who are not allowed to load or unload the driver/module.
However, a driver/module can configured to be automatically loaded
when a device is mounted. On Linux, to specify that a module be loaded
when a particular device is mounted, edit
/etc/conf.modules
and add something similar to:
# /dev/scd0 - An IDE CDROM accessed using SCSI
alias scd0 sr_mod
pre-install sr_mod /sbin/modprobe ide-scsi
# /dev/sda4 - IOMega Zip Drive (parallel port version)
alias block-major-8 sd_mod
pre-install sd_mod modprobe -r lp ; modprobe -r bpck-fdc ; \
modprobe -r zftape ; modprobe -r ftape ; modprobe parport ; \
modprobe parport_pc
post-install sd_mod modprobe ppa
# /dev/lp0 - Printer
pre-install lp modprobe -r bpck-fdc ; modprobe -r zftape ; \
modprobe -r ftape ; modprobe -r ppa ; modprobe -r sd_mod
The above shows a set up for loading (and unloading) modules for an IDE CDROM (that is accessed using SCSI), a zip drive, and a printer connected to the same cable as the zip drive. Note that the module for the printer is unloaded when the zip drive is mounted and vice versa.
Once the device has been properly set up on both the system and in Endeavour, it can be mounted in one of two ways:
To unmount a device, simply repeat the above step. You will notice that the Mount button or menu item becomes Unmount when the device in question is already mounted.
Do not forget to unmount the device before you remove the media.
Back to the top
Endeavour Mark II is Copyright © 1997-2002 WolfPack Entertainment