Содержащиеся в
Найти другие документы
Ресурсы поддержки
| Загрузить это руководство в формате PDF
Setting Up a CD-ROM or Floppy Disk Drive
4
- Be sure to read the requirements that you must have completed before you start to configure the operating system for a new CD-ROM or floppy disk drive.
- CD-ROMs provide large data capacity and have quickly become today's medium of choice for software distribution. CD-ROM drives allow you to add both operating system and application packages quickly and easily to the workstations you administer.
- Floppies provide small amounts of data storage and are typically used to transfer files to a non-networked personal computer or to store individual user files.
-
For important information about how the Solaris 2.4 or higher operating environment manages CD-ROM and floppy devices, read the "How Solaris Manages CD-ROM and Floppy Devices" in this chapter.
Requirements
- Before you start to configure the operating environment for a new CD-ROM or floppy disk drive, you must have:
-
- Installed the Solaris 2.4 operating environment
- Shut down the system and those peripherals that are already connected as described in Chapter 1, "Before You Start"
-
Note - If you did not follow the procedures as described in Chapter 1, "Before You Start," the operating system may not recognize the presence of the new CD-ROM or floppy disk drive.
-
- Installed the CD-ROM or floppy disk drive as described in the hardware installation manual that accompanies your disk drive. If you have not yet installed and set the SCSI address of your CD-ROM or floppy disk drive, do so now before you proceed.
-
Note - The floppy disk drive is not a SCSI device.
- This task includes finding the location of the address switch or jumpers on the CD-ROM or floppy disk drive as well as setting the SCSI target ID.
- For information on how to select device addresses, go to Chapter 6, "Selecting Addresses," in this handbook.
How Solaris Manages CD-ROM and Floppy Devices
- Volume Management automates the interaction between you and your CD-ROMs and floppies. For example, in previous Solaris releases (Solaris 2.1 or any releases preceding Solaris 2.1), to mount and access data on a CD-ROM you had to follow these steps.
-
# cd /
# mkdir /cdrom
# mount -F ufs -o ro /dev/dsk/c0t6d0s2 /cdrom
|
- If you attempt to follow these instructions while using the Solaris 2.3.2 or higher system software, you may see one or both of these messages.
-
# mkdir /cdrom
mkdir: Failed to make directory "/cdrom"; File exists
# mount -F ufs -o ro /dev/dsk/c0t6d0s0 /cdrom
mount: /dev/dsk/c0t6d0s0 is already mounted, /cdrom is busy,
or allowable number of mount points exceeded
|
- You will also see the following messages when you attempt to use the /dev/diskette path to access or eject floppies.
-
% tar cvf /dev/diskette proposal status reviewers
tar: cannot open /dev/diskette.
% eject /dev/diskette
/dev/rdiskette is busy (try /vol name?)
|
- In the Solaris 2.2 or higher version of the system, Volume Management automatically mounts CD-ROMs and floppies with file systems at /cdrom/cdrom_name and /floppy/floppy_name respectively. It also keeps track of CD-ROM and floppy file systems during a workstation session (rebooting will clear the in-memory database). To view the media that has been inserted during a workstation session, list /vol/dsk.
-
% ls /vol/dsk
solaris_2_1/ unnamed_cdrom#1
unnamed_cdrom unnamed_floppy
|
- Volume Management uses the configuration file /etc/vold.conf to determine which devices it manages. The default /etc/vold.conf file contains the following information.
-
# @(#)vold.conf 1.13 92/10/28 SMI
#
# Volume Daemon Configuration file
#
# Database to use (must be first)
db db_mem.so
# Labels supported
label dos label_dos.so floppy
label cdrom label_cdrom.so cdrom
label sun label_sun.so floppy
# Devices to use
use cdrom drive /dev/dsk/c0t6 dev_cdrom.so cdrom0
use floppy drive /dev/fd0 dev_floppy.so floppy0
# Actions
insert /vol*/dev/fd[0-9]/* user=root /usr/sbin/rmm
insert /vol*/dev/dsk/* user=root /usr/sbin/rmm
eject /vol*/dev/fd[0-9]/* user=root /usr/sbin/rmm
eject /vol*/dev/dsk/* user=root /usr/sbin/rmm
notify /vol*/rdsk/* group=tty /usr/lib/vold/volmissing -c
# List of file system types unsafe to eject
unsafe ufs hsfs pcfs
|
- Before you add secondary CD-ROM and floppy drives to a system, update this file by adding the new devices to the "Devices to use" list. The syntax for a "Devices to use" entry
-
use device type special shared_object symname options
- Here are the explanations of each variable item in the device control line.
-
Table 4-1
| Syntax item | Description | Supported and default values |
| device | The type of removable media device to be used. | cdrom, floppy |
| type | The class of device--multiple or single media support | drive |
| special | Pathname of the device to be used. Path
usually begins with /dev. | Default support is for the devices
/dev/dsk/c0t6 and /dev/diskette |
| shared object | The location of the code that manages this device. | The default location is /usr/lib/vold/name_ of_shared_object |
| symname | The symbolic name that refers to this device.
The symname is placed in the device
directory (either /cdrom or /floppy) | Default values are
cdrom0, floppy0 |
| options | The user, group, and mode permissions for the media inserted. | Default values are
user=nobody, group=nobody, mode=0666
|
- After updating the /etc/vold.conf file, you attach the drive and reboot your system with a reconfiguration boot. To do so enter either boot -r or touch /reconfigure.
-
Note - Volume Management controls the /dev/dsk/c0t6d0s0 path to a CD-ROM drive and the /dev/diskette path to a floppy drive. An attempt to access a CD-ROM or floppy using these paths will result in an error message.
- For more information about volume management, see the man page for vold.conf(4) and the Solaris 2.4 Driver Developer AnswerBook manual.
Configuring the System
- Most CD-ROM drives conform to the Small Computer Systems Interface (SCSI) protocol. This means getting a CD-ROM drive up and running on your workstation usually involves little more than plugging in the cables and, if applicable, setting the jumpers or SCSI target switch to 6 (or another number if it is a secondary drive). Consult the documentation accompanying your CD-ROM drive for information about physical connections.
- When you boot the system after adding a CD-ROM or floppy disk drive, Solaris 2.4 automatically configures the system by assigning a device address to the CD-ROM or floppy disk drive if:
-
- To configure the system for the addition of a CD-ROM or floppy disk drive:
-
-
Check that the address switch for the CD-ROM or floppy disk drive has been correctly set.
You should already have correctly set the physical SCSI switch or jumpers on your CD-ROM or floppy disk drive, as described in your CD-ROM or floppy disk drive installation manual and Chapter 6, "Selecting Addresses." For example, the SCSI address switch for CD-ROM drives has typically been preset by the factory to SCSI target ID 6.
-
Note - If you have more than one SCSI device, such as a CD-ROM drive, you must set each SCSI address switch to a different target ID.
-
-
Turn on power to all external peripheral devices, including the CD-ROM drive that you plan to configure, and then the system.
The system automatically boots and configures the new drive. You are now ready to mount the CD-ROM or floppy disk drive.
Adding an Additional CD-ROM Drive
-
Note - Be sure that the target number you select is not already used by a peripheral attached to your system. Use ls /dev/dsk to list the existing devices and their addresses.
- To add an additional CD-ROM drive for the Solaris operating system version 2.2 or greater:
-
Note - You can connect no more than seven CD-ROM drives to a single SCSI bus provided that the total cable length does not exceed 6 meter.
-
-
Edit the /etc/vold.conf file to add the CD-ROM drive to the list of devices managed by Volume Management.
- Copy the default CD-ROM line under "Devices to use" and change the device address and mount location.
-
# Devices to use
use cdrom drive /dev/dsk/c0t6 dev_cdrom.so cdrom0
use cdrom drive /dev/dsk/c0t5 dev_cdrom.so cdrom1
|
- In this example, a new entry was added for a CD-ROM drive with a target number of 5. When a CD-ROM containing a file system is inserted into this secondary CD-ROM drive, it will automatically be mounted as /cdrom/cdrom1. If the CD-ROM does not contain a file system, it can be accessed at /vol/dev/dsk/ct05/unnamed_cdrom as a block device.
-
-
Shut down the operating environment as described in Chapter 1, "Before You Start."
-
Turn on power to all external peripheral devices, including the second CD-ROM drive that you plan to configure, and then the system.
The system automatically boots and configures the new drive.
Reference Material for CD-ROM and Floppy Devices
- CD-ROM and floppy file systems are automatically mounted in default locations by Volume Management when the media is inserted. See Table 4-2 for more information.
- These mount points are only created and mounted if a file system is already resident on the floppy disk.
-
Table 4-2
| Media type | Mount location | State of media |
| Floppy | /floppy/floppy0 | Symbolic link to mounted floppy in local floppy drive |
| Floppy | /floppy/floppy_name | Mounted named floppy |
| Floppy | /floppy/unnamed_floppy | Mounted unnamed floppy |
| CD-ROM | /cdrom/cdrom0 | Symbolic link to mounted CD-ROM in local CD-ROM drive |
| CD-ROM | /cdrom/CD-ROM_name | Mounted named CD-ROM |
| CD-ROM | /cdrom/CD-ROM_name/partition | Mounted named CD-ROM with partitioned file system |
| CD-ROM | /cdrom/unnamed_cdrom | Mounted unnamed CD-ROM |
- To inform Volume Management that a floppy with a file system has been inserted into the drive, use volcheck(1). You do not need to use this command if you are going to use the commands fdformat(1) or eject(1). For more information on how to use floppies, see the AnswerBook Administrator's Guide.
- If there is no file system on the media, Volume Management provides block and character devices in the /vol file system. See Table 4-3 for the location of floppy and cdrom media in the /vol file system.
-
Note - All releases provide a symbolic link in /vol/dev/aliases.
-
Table 4-3 /vol
| Solaris 2.2 |
|
| Media type | Device location | State of media |
| Floppy | /vol/dev/fd0/unnamed_floppy | Formatted unnamed floppy--block device access |
| Floppy | /vol/dev/rfd0/unnamed_floppy | Formatted unnamed floppy--raw device access |
| Floppy | /vol/dev/fd0/unlabeled | Unlabeled floppy--block device access |
| Floppy | /vol/dev/rfd0/unlabeled | Unlabeled floppy--raw device accesss |
| CD-ROM | /vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM--block device access |
| CD-ROM | /vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM--raw device access |
| Solaris 2.3 or higher |
| Media type | Device location | State of media |
| Floppy | /vol/dev/diskette0/unnamed_floppy | Formatted unnamed floppy--block device access |
| Floppy | /vol/dev/rdiskette0/unnamed_floppy | Formatted unnamed floppy--raw device access |
| Floppy | /vol/dev/diskette0/unlabeled | Unlabeled floppy--block device access |
| Floppy | /vol/dev/rdiskette0/unlabeled | Unlabeled floppy--raw device accesss |
| CD-ROM | /vol/dev/dsk/c0t6/unnamed_cdrom | CD-ROM--block device access |
| CD-ROM | /vol/dev/rdsk/c0t6/unnamed_cdrom | CD-ROM--raw device access |
Ejecting a CD-ROM
-
-
Type
-
- or
-
- This command applies only to a CD-ROM disk drive that has been connected to the on-board SCSI bus. If your CD-ROM disk drive is connected to a SCSI bus other than the on-board SCSI bus, you may need to manually eject the CD-ROM disk.
|
|