On 10/18/2011 09:51 PM, Mark Post wrote:
On 10/18/2011 at 05:41 AM, Steffen Maierma...@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
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 :)
Look into DKMS. It can be configured to rebuild kernel modules automagically
when the kernel changes. Works fine for most of the parallel filesystem stuff
You're making too much sense here, David :)
Scott Rohling
On Wed, Oct 19, 2011 at 6:40 AM, David Boyes dbo...@sinenomine.net wrote:
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 :)
Look into DKMS. It
You're making too much sense here, David :)
And that's on only one cup of coffee. After three more cups, I'll be invisible.
-- db
--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to
On 10/19/2011 at 05:15 AM, Steffen Maier ma...@linux.vnet.ibm.com wrote:
Assuming you refer to the st SCSI tape driver by native support,
then multipathing comes to mind as additional feature of lin_tape.
I was thinking more of the kernel module only, but this is good to know.
Mark Post
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
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,
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
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
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
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,
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
: 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
13 matches
Mail list logo
