Install tape driver error on zlinux
Our linux is SUSE Enterprise Server 11 SP1 running on z/VM V5.4. Our linux kernel is 2.6.32.12-0.7-default (geeko@buildhost) (gcc version 4.3.4 gcc-4 setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit mode. Our tape lib is TS3500, driver is 3592 E05. Our SAN switch is 2498-B24. The connection path from mainframe to tape lib is: fcp channel(A) - input port of san switch(B) - output port of san switch(C) - port of driver(D). The special thing is C point is directly connect D point. Rather than through 3953 tape lib controller. The following is my detail work of installing tape driver: (1) download tape driver from website of System Storage Interoperation Center. Before selecting correct driver, we selected following values to narrow target drivers on website search. Product Family - IBM System Storage Enterprise Tape Product Model - TS3500 (3584) with TS1120 (3592-E05) Drives (I asked this info from HW guy) Product Version - TS3500 (B150) with TS1120 (3592-E05) Drives (D3I1_EE9) (I select the last one of pull-down menu, because I thought it is the up-to-date version) Host Platform - IBM System z Operating System - Novell SUSE Linux Enterprise Server 11 SP1 Adapter Model - FC 3324 (I ask this info from HW guy) SAN or Networking Model - IBM SAN24B-4 (2498-B24) (I checked on SAN switch label) The most unsure item is Product Version. I don't know if it is correct for us. I downloaded 2 files. One is lin_tape-1.61.0-1.src.rpm, the other is lin_taped-1.61.0-sles11.s390x.rpm. (2) I'm sure that zfcp device driver is loaded into kernel, because we have scsi disk connected through zfcp device driver. (3) rpmbuild -rebuild lin_tape-1.61.0-1.src.rpm This step produced lin_tape package on /usr/src/packages/RPMS/s390x/lin_tape-1.61.0-1.s390x.rpm (4) rpm -ivh /usr/src/packages/RPMS/s390x/lin_tape-1.61.0-1.s390x.rpm This step produced below error: Preparing... ### [100%] 1:lin_tape ### [100%] Starting lin_tape: FATAL: module '/lib/modules/2.6.32.12-0.7-default/kernel/drivers/scsi/lin_tape.ko' is unsupported Use --allow-unsupported or set allow_unsupported_modules to 1 in /etc/modprobe.d/unsupported-modules lin_tape loaded I don't know why this error occured. Is it means incorrect version of tape driver I used? (5) rpm -ivh /usr/src//lin_taped-1.x.x.x..0-sles11.s390x.rpm This step install lin_taped daemon. But I got similar error as step 4: Preparing... ### [100%] 1:lin_taped ### [100%] Starting lin_tape: FATAL: module '/lib/modules/2.6.32.12-0.7-default/kernel/drivers/scsi/lin_tape.ko' is unsupported Use --allow-unsupported or set allow_unsupported_modules to 1 in /etc/modprobe.d/unsupported-modules lin_tape loaded Anybody has idea for this error? -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Install tape driver error on zlinux
On 10/18/2011 09:14 AM, Lu GL Gao wrote: Our linux is SUSE Enterprise Server 11 SP1 running on z/VM V5.4. Our tape lib is TS3500, driver is 3592 E05. (1) download tape driver from website of System Storage Interoperation Center. I downloaded 2 files. One is lin_tape-1.61.0-1.src.rpm, the other is lin_taped-1.61.0-sles11.s390x.rpm. (2) I'm sure that zfcp device driver is loaded into kernel, because we have scsi disk connected through zfcp device driver. (3) rpmbuild -rebuild lin_tape-1.61.0-1.src.rpm This step produced lin_tape package on /usr/src/packages/RPMS/s390x/lin_tape-1.61.0-1.s390x.rpm (4) rpm -ivh /usr/src/packages/RPMS/s390x/lin_tape-1.61.0-1.s390x.rpm This step produced below error: Preparing... ### [100%] 1:lin_tape ### [100%] Starting lin_tape: FATAL: module '/lib/modules/2.6.32.12-0.7-default/kernel/drivers/scsi/lin_tape.ko' is unsupported Use --allow-unsupported or set allow_unsupported_modules to 1 in /etc/modprobe.d/unsupported-modules Since you (had to) build the lin_tape device driver kernel module yourself it is formally flagged as not supported by SLES11 and therefore modprobe denies loading the module. This is indicated by above message for which you can find more details in: http://www.novell.com/support/viewContent.do?externalId=7002793sliceId=1 http://www.novell.com/linux/releasenotes/s390x/SUSE-SLES/11-SP1/#KernelModules Unfortunately, I don't know how this case is handled with SLES regarding distribution support for SCSI tape drives. Hoping for Mark Post to step in here. Steffen Linux on System z Development IBM Deutschland Research Development GmbH Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen Registergericht: Amtsgericht Stuttgart, HRB 243294 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Install tape driver error on zlinux
On Tue, 18 Oct 2011 11:41:47 +0200 Steffen Maier wrote: Since you (had to) build the lin_tape device driver kernel module yourself it is formally flagged as not supported by SLES11 and therefore modprobe denies loading the module. I wonder how this sits philosophically with users. At least they didn't mark it as crap I suppose (see https://lkml.org/lkml/2011/10/6/317) Shane ... -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Install tape driver error on zlinux
On 10/18/2011 at 05:41 AM, Steffen Maier ma...@linux.vnet.ibm.com wrote: Since you (had to) build the lin_tape device driver kernel module yourself it is formally flagged as not supported by SLES11 and therefore modprobe denies loading the module. This is indicated by above message for which you can find more details in: http://www.novell.com/support/viewContent.do?externalId=7002793sliceId=1 http://www.novell.com/linux/releasenotes/s390x/SUSE-SLES/11-SP1/#KernelModul es Unfortunately, I don't know how this case is handled with SLES regarding distribution support for SCSI tape drives. Hoping for Mark Post to step in here. We do provide native support for SCSI tapes in the distribution. I don't know what lin_tape provides over and above that. If nothing additional is needed, then just don't use it and use the native support. If the OP _has_ to use lin_tape for whatever reason, he needs to understand that running with a tainted kernel _might_ put some additional burden on him in the future. If a support request is opened, and the lin_tape kernel module is suspected of interfering with the normal operation of the system, then the problem will have to be recreated without the lin_tape module loaded. I have run into this before. In one situation a customer was using a 3rd party kernel module that resulted in it looking as though nearly all of /sys was missing. If that module wasn't loaded, everything was fine, so the customer had to go talk to that 3rd party vendor about the problem. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Cannot Ping SLES11 guests from z/VM through hypersockets
We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? SLES10 Guest HSI0 hsi0 Link encap:Ethernet HWaddr 06:00:EF:05:00:06 inet addr:161.186.86.150 Bcast:162.186.86.191 Mask:255.255.255.192 inet6 addr: fe80::600:ef9f:4005:6/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:16384 Metric:1 RX packets:207 errors:0 dropped:0 overruns:0 frame:0 TX packets:291 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:16704 (16.3 Kb) TX bytes:33137 (32.3 Kb) SLES11 Guest HSI0 hsi0 Link encap:Ethernet HWaddr 06:00:EF:05:00:1A inet addr:161.186.86.154 Bcast:161.186.86.191 Mask:255.255.255.192 inet6 addr: fe80::400:efff:fe05:1a/64 Scope:Link UP BROADCAST RUNNING NOARP MULTICAST MTU:16384 Metric:1 RX packets:98 errors:0 dropped:0 overruns:0 frame:0 TX packets:154 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8816 (8.6 Kb) TX bytes:16149 (15.7 Kb) Peter This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Cannot Ping SLES11 guests from z/VM through hypersockets
On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? Do you have the fix for z/VM APAR PK80882 installed? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Cannot Ping SLES11 guests from z/VM through hypersockets
Yes, PTF shows applied UK46027: VMFSRV1226I TCPIP (5VMTCP40%TCPIP) APAR PK80882 (PTF UK46027) status: VMFSRV1226IRECEIVED 06/17/10 07:50:18 VMFSRV1226IAPPLIED 10/06/09 20:16:49 VMFSRV1226IBUILT 06/17/10 07:51:47 VMFSRV1226IPUT2PROD 06/17/10 09:18:43 VMFSRV2760I SERVICE processing completed successfully From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/18/2011 06:53 PM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? Do you have the fix for z/VM APAR PK80882 installed? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Cannot Ping SLES11 guests from z/VM through hypersockets
Peter, Are you by any chance hitting: Applying SLES 11 SP 1 Causing Communication Issues http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexternalId=7007649sliceId=1docTypeID=DT_TID_1_1 Mike O'Reilly IBM Linux Change Team Peter E. Abresch Jr. - at Pepco peabresch@pepco. To com LINUX-390@vm.marist.edu Sent by: Linux on cc 390 Port linux-...@vm.mar Subject ist.edu Re: Cannot Ping SLES11 guests from z/VM through hypersockets 10/18/2011 04:04 PM Please respond to Linux on 390 Port linux-...@vm.mar ist.edu Yes, PTF shows applied UK46027: VMFSRV1226I TCPIP (5VMTCP40%TCPIP) APAR PK80882 (PTF UK46027) status: VMFSRV1226IRECEIVED 06/17/10 07:50:18 VMFSRV1226IAPPLIED 10/06/09 20:16:49 VMFSRV1226IBUILT 06/17/10 07:51:47 VMFSRV1226IPUT2PROD 06/17/10 09:18:43 VMFSRV2760I SERVICE processing completed successfully From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/18/2011 06:53 PM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? Do you have the fix for z/VM APAR PK80882 installed? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Cannot Ping SLES11 guests from z/VM through hypersockets
Maybe, net.ipv4.conf.all.rp_filter was set to 1. I took one of my SLES11-SP1 guest and set it to 2. It now pings from z/VM. When I set it back to 1, it still pings. When I set it to 0, it still pings. I went to a different SLES11 guest. It did not ping, but once I set net.ipv4.conf.all.rp_filter to 0, it pinged fine. I returned it to 1 and it still pings. I am confused. Why is it pinging all of a sudden or is it just the nature of the beast. Should I set it to 2 globally? Peter From: Michael O'Reilly mik...@us.ibm.com To: LINUX-390@vm.marist.edu Date: 10/18/2011 07:24 PM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu Peter, Are you by any chance hitting: Applying SLES 11 SP 1 Causing Communication Issues http://www.novell.com/support/search.do?cmd=displayKCdocType=kcexternalId=7007649sliceId=1docTypeID=DT_TID_1_1 Mike O'Reilly IBM Linux Change Team Peter E. Abresch Jr. - at Pepco peabresch@pepco. To com LINUX-390@vm.marist.edu Sent by: Linux on cc 390 Port linux-...@vm.mar Subject ist.edu Re: Cannot Ping SLES11 guests from z/VM through hypersockets 10/18/2011 04:04 PM Please respond to Linux on 390 Port linux-...@vm.mar ist.edu Yes, PTF shows applied UK46027: VMFSRV1226I TCPIP (5VMTCP40%TCPIP) APAR PK80882 (PTF UK46027) status: VMFSRV1226IRECEIVED 06/17/10 07:50:18 VMFSRV1226IAPPLIED 10/06/09 20:16:49 VMFSRV1226IBUILT 06/17/10 07:51:47 VMFSRV1226IPUT2PROD 06/17/10 09:18:43 VMFSRV2760I SERVICE processing completed successfully From: Mark Post mp...@novell.com To: LINUX-390@vm.marist.edu Date: 10/18/2011 06:53 PM Subject:Re: Cannot Ping SLES11 guests from z/VM through hypersockets Sent by:Linux on 390 Port LINUX-390@vm.marist.edu On 10/18/2011 at 06:42 PM, Peter E. Abresch Jr. - at Pepco peabre...@pepco.com wrote: We are running z/VM Version 5 Release 4.0, service level 1001 (64-bit). We can ping all of our SLES10 guests through our real hypersockets from z/VM. however we cannot ping our SLES11 guests from z/VM through our real hypersockets. All our Linux guests (SLES10 and SLES11) can ping each other fine through hypersockets. z/OS can ping SLES10 and SLES11 guests through hypersockets fine. SLES10 and SLES11 Linux guest can ping everything fine through hypersockets. The only problem is pinging SLES11 guests from z/VM. Has anyone else experienced this problem or have any suggestions? Do you have the fix for z/VM APAR PK80882 installed? Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates (PHI). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: Install tape driver error on zlinux
On Tue, 18 Oct 2011 13:51:37 -0600 Mark Post wrote: If the OP _has_ to use lin_tape for whatever reason, he needs to understand that running with a tainted kernel _might_ put some additional burden on him in the future. Is this not GPL licensed code ?. If so, just how does running it result in a tainted kernel ?. Shane ... -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Install tape driver error on zlinux
On 10/19/2011 at 12:36 AM, Shane ibm-m...@tpg.com.au wrote: Is this not GPL licensed code ?. I have no idea if it is or not. If so, just how does running it result in a tainted kernel ?. We didn't build it, so we don't support it. Tainting is not a one bit flag, it is multiple bits, having different uses. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Install tape driver error on zlinux
Let me explain the reason of installing tape driver is we are going to install Tivoli Storage Manager which will be the only tool to backup our systems. Our linux is newly installed which was provided by IBM. Nobody modified it, and even nobody begin to use it. I also downloaded tape driver from IBM storage support website. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
Re: Install tape driver error on zlinux
We ran it for a while on SLES 10. There was a tainted message there too at boot time, but no special action like SLES 11 seems to require. We needed it to drive an IBM ATL. There is no native Linux support for that. Just know that if you do have a problem and Novell is providing your support, you *may* have to pull it out and recreate the problem without it. Probably pretty unlikely, but just be aware. You also have to rebuild the thing after each kernel update. Kind of a pain. Especially if you forget and it's not functional anymore :) Marcy -Original Message- From: Linux on 390 Port [mailto:LINUX-390@vm.marist.edu] On Behalf Of Lu GL Gao Sent: Tuesday, October 18, 2011 9:52 PM To: LINUX-390@vm.marist.edu Subject: Re: [LINUX-390] Install tape driver error on zlinux Let me explain the reason of installing tape driver is we are going to install Tivoli Storage Manager which will be the only tool to backup our systems. Our linux is newly installed which was provided by IBM. Nobody modified it, and even nobody begin to use it. I also downloaded tape driver from IBM storage support website. -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For more information on Linux on System z, visit http://wiki.linuxvm.org/
