The /etc/rmmount.conf file is shown as:

# @(#)rmmount.conf 1.3     96/05/10 SMI
#
# Removable Media Mounter configuration file.
#

# File system identification
ident hsfs ident_hsfs.so cdrom
ident ufs ident_ufs.so cdrom floppy rmscsi pcmem
ident pcfs ident_pcfs.so floppy rmscsi pcmem

# Actions
action cdrom action_filemgr.so
action floppy action_filemgr.so
action rmscsi action_filemgr.so

The files in the /usr/lib/vold directory are listed as:

castle% ls -1 /usr/lib/vold
db_mem.so.1
db_nis.so.1
dev_cdrom.so.1
dev_floppy.so.1
dev_pcmem.so.1
dev_rmscsi.so.1
dev_test.so.1
eject_popup
label_cdrom.so.1
label_dos.so.1
label_sun.so.1
label_test.so.1
volcancel
volmissing
volmissing_popup
volstat
castle%

The files in the /usr/lib/rmmount directory are listed as:

oak% ls -1 /usr/lib/rmmount
action_filemgr.so.1
action_workman.so.1
oak%

If you encounter problems with volume management, check the /var/adm/vold.log file for information. An example of this file follows:

oak% more /var/adm/vold.log
Tue Jun  1 17:34:24 1993 warning: dev_use: couldn't find a driver
 for drive cdrom at /dev/dsk/cØt6
Tue Jun  1 17:39:12 1993 warning: dev_use: couldn't find a driver
 for drive cdrom at /dev/dsk/cØt6
Tue Jun  1 18:24:24 1993 warning: dev_use: couldn't find a driver
 for drive cdrom at /dev/dsk/cØt6
Wed Jun 23 15:Ø8:47 1993 warning: check device 36.2: device
 not managed
Wed Jun 23 15:Ø9:58 1993 warning: check device 36.2: device
 not managed
Wed Jun 23 15:11:Ø8 1993 warning: check device 36.2: device
 not managed
Thu Jul 15 13:51:23 1993 warning: check device 36.2: device not
 managed
Thu Jul 15 13:52:53 1993 warning: check device 36.2: device not
 managed
Thu Jul 15 14:Ø4:37 1993 warning: check device 36.2: device
 not managed
Thu Jul 15 14:Ø5:52 1993 warning: check device 36.2: device
 not managed
Thu Jul 15 14:Ø6:16 1993 warning: check device 36.2: device
 not managed
Wed Jul 21 16:33:33 1993 fatal: svc_tli_create: Cannot create
 server handle
Thu Jul 22 16:32:28 1993 warning: cdrom: /dev/rdsk/cØt6dØs2; Device busy
castle%

If you want to display debugging messages from the volume daemon, you can start the daemon by typing /usr/sbin/vold -v -L 10. With these flags set, the volume daemon logs quite a bit of information in /var/adm/vold.log.

Another way to gather debugging information is to run the rmmount command with the debug flag. To do so, edit /etc/vold.conf and change the lines that have /usr/sbin/rmmount to include the -D flag, as shown in the following example:

insert /vol*/dev/diskette[Ø-9]/* user=root /usr/sbin/rmmount -D

Volume Management Mount Points

Volume management automatically mounts CD-ROM file systems on the /cdrom mount point when you insert the media into the drive.

When you insert a diskette in the diskette drive, you must ask the system to check the diskette drive. You can check for a diskette in any one of the following ways:

•  From the command line, type volcheck and press Return.

•  From the CDE front panel, click on the Folders menu and then click on Open Floppy.

•  From the CDE File Manager File menu, choose Open Floppy.

•  From the OpenWindows File Manager File menu, choose Check for Floppy.

When you use any of these methods, the files are mounted on the /floppy mount point. Table 3-6 describes the mount points and how volume management uses them.

If the medium does not contain a file system, volume management provides block and character devices in the /vol file system, as shown in Table 3-7.

CD-ROMs and Volume Management

The following sections describe how to access files from local and remote CD-ROM drives.