Funny thing that. If you look at the default st.conf that comes in
Solaris, all the entries in the tape-config section end in commas, only
the data portion all end in semi-colons. In fact, the Veritas media
manager configuration guide (that Bill so kindly pointed out) lists the
tape-config entry as ending with a comma, which mine now does. To date,
no errors.
~JK
George Drew wrote:
>
> The "unexpected token" error is because you have a comma at the end of the
> second line, instead of a semi-colon. The driver has
> to know where to stop reading the tape config list.
>
> Use ATL's entry:
>
> # grep ISDLT /usr/include/sys/mtio.h
> #define MT_ISDLT 0x38 /* sun: SCSI DLT tape drive */
>
> George
>
> On Tue, 23 Jul 2002, Jeff Kennedy wrote:
>
> > I am getting conflicting stories on what should go in st.conf for the
> > DLT 7k.
> >
> > ATL says the following:
> >
> > tape-config-list=
> > "QUANTUM DLT7000", "DLT 7000", "DLT7000",
> > DLT7000 = 1,0x38,0,0x8639,4,0x82,0x83,0x84,0x85,3;
> >
> > However, Sun says the following:
> >
> > tape-config-list=
> > "QUANTUM DLT7000", "QUANTUM DLT7000", "DLT7k-data";
> > DLT7k-data = 1,0x36,0,0x1D639,4,0x82,0x83,0x84,0x85,2;
> >
> > And the main reason I post this is that with ATL's entry for DLT7k I get
> > unexpected token errors from st.conf. Funny thing though, the SDLT
> > entry is fine.
> >
> > Can anyone verify a Solaris st.conf dlt7k entry for an ATL library for
> > me?
> >
> > Thanks.
> >
--
=====================
Jeff Kennedy
Unix Administrator
AMCC
jlkennedy AT amcc DOT com
|