User manual QUANTUM DLT1SUNOS413

[. . . ] DLTTM Tape Unit Installation Sun® SPARCstationTM SunOS 4. 1. 3 Installation Instructions will cover the installation of the DLT tape peripheral hardware and configuration of the system to communicate with the DLT tape peripheral. SunOS 4. 1. 3 includes a driver to efficiently communicate with tape drives, such as the DLT tape peripheral. [. . . ] Edit the file st_conf. c by adding the following to the end of the table: ' /* DEC 1/2" Cartridge */ { "<DLT tape unit>", 15, "<DLT tape unit>", ST_T YPE_HIC, 16384, (ST _VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE), 400, 400, { <Density 1>, <Density2>, <Density 3>, <Density 4>}, { 0, 0, 0, 0 } } Where: · <DLT tape unit> is the vendor and product ID for the DLT device. Depending on the DLT tape peripheral you are installing, you must insert the appropriate vendor and product ID string for <DLT tape unit> as described in the following table: DLT Tape Product <DLT tape unit> DLT1 QUANTUM DLT7000 Total string character count, including spaces, in <DLT tape unit> must equal 15. · <Density 1> and <Density 2> define part of the density code selection option and are set according to the following table. <Density 1> is the default density. DLT Tape Product <Density 1> <Density 2> <Density 3> <Density 4> DLT1 0x40 0x86 0x87 The above table entry is applied to a structure called st_drivetype and is defined in /usr/sys/scsi/targets/stdef. h. The structure is shown below: struct st_drivetype { char *name; /* Name for debug */ char length; /* Length of vendor id */ char vid [24]; /* Vendor id and model id */ char t ype; /* Drive type for driver */ short bsize; /* Block size */ int option; /* Drive option */ 0x7F int max_rretries; /* Max read retries */ int max_wretries; /* Max write retries */ u_char densities[NDENSITIES]; /* Density codes */ u_char speeds[NSPEEDS]; /* Sp eed codes */ } 1. Enter the following command to identify the kernel architecture: /bin/arch -k The response to the command should be similar to sun4mand is used to substitute for the <kernel arch> strings that appear in succeeding steps. 1. Change directory to /usr/share/sys/<kernel arch>/conf, where <kernel arch>is the kernel architecture identifier obtained from the previous step. Enter the following command in preparation for kernel rebuild. GENERIC may be substituted for <kernel config file>in the command string. /usr/etc/config <kernel config file> 3. Change directory to . . /<kernel config file>. Enter the following command to rebuild the VMUNIX kernel: /bin/make 5. Enter the following command to save the existing kernel: /bin/mv /vmunix /vmunix. old 6. Enter the following command to copy the new kernel to the root directory: /bin/cp . /vmunix /vmunix 7. Enter the following command to shut down the system: shutdown -h now 8. Boot the system with the installed DLT tape peripheral and the software files modified for system recognition of the tape drive. The system creates special files that enable communication with the DLT device. The special files nrst (no rewind on close) and rst (rewind on close) reside in the /dev directory. The following table shows the created device files and the corresponding density codes for a DLT device installed with a SCSI ID of 4 or 5. SCSI ID 4 SCSI ID 5 Density Code DLT1 nrst0, rst0 nrst8, rst8 nrst1, rst1 nrst9, rst9 0x40 0x87 0x86 · Enter the following command to verify the installation: mt -f /dev/rst0 status Note that the device file rst0 is for an installed DLT device with SCSI ID of 4. [. . . ] Therefore, an installed DLT7 mini-library can not be utilized in random access mode and can only be accessed in sequential mode. Refer to the DLT1/DLT7 Install and Operations Guide manual for detailed description of these access modes. [. . . ]