In regard to: Re: [Networker] (Migration) jbconfig problem, Matt Hemingway...:

>Oh, yesterday, I accidently installed 7.1.1 (or something, the latest
>one) and jbconfig worked fine.  When I realized that, and noticed how I
>*have* to install the same version of Networker on the Linux server
>(target) as the one on the Solaris server (source), I removed 7.1.x and
>installed 6.1.1.
>
>If I can't use 6.1.1, then how will a migration AND an upgrade from 6.1.1
>to 7.1.x work?

Why not upgrade the source to 7.1.1, and then do the migration from
Solaris -> Linux?  Or update both to 6.1.4, do the migration, and then
decide if you want to go to 7.1.x now or later.

>  Is that even possible?  Can I use the version of jbconfig
>that comes with 7.1.x to configure the library/drive for use on 6.1.1?

No.

It's possible your kernel version (2.6.5?) has something to do with it.
Trying the 2.4.x vendor-recommended kernel might be better.

What does the Legato `inquire' command report (it's probably in
/etc/LGTOuscsi)?  What happens if you re-run jbconfig and choose the
same options but override the control port and use /dev/sg0?  Does
that work?

Tim
--
Tim Mooney                              mooney AT dogbert.cc.ndsu.NoDak DOT edu
Information Technology Services         (701) 231-1076 (Voice)
Room 242-J6, IACC Building              (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=